RFC 5047
E920321
RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5047 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T11351404 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: RFC 5047 Context triple: [iWARP, isSpecifiedIn, RFC 5047]
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4347
RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
-
C.
RFC 6147
RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 5047 Target entity description: RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4347
RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
-
C.
RFC 6147
RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track RFC ⓘ |
| appliesTo |
RDMA-capable network adapters
ⓘ
iWARP implementations ⓘ |
| area | Transport Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
DDP
NERFINISHED
ⓘ
DDP over reliable transports ⓘ Direct Data Placement ⓘ RDMA over TCP/IP NERFINISHED ⓘ RDMA over reliable transports NERFINISHED ⓘ Remote Direct Memory Access Protocol over TCP/IP NERFINISHED ⓘ |
| definesConcept |
direct data placement into application buffers
ⓘ
message boundaries over byte-stream transports ⓘ protection domains for RDMA and DDP ⓘ stream-based transport mapping for DDP ⓘ tagged and untagged DDP operations ⓘ zero-copy data transfer semantics over TCP ⓘ |
| format | text ⓘ |
| intendedFor |
RDMA implementers
ⓘ
iWARP device vendors ⓘ network protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 5040
NERFINISHED
ⓘ
RFC 5041 NERFINISHED ⓘ RFC 5042 NERFINISHED ⓘ iWARP architecture ⓘ |
| RFCNumber | 5047 ⓘ |
| specifies |
error handling for DDP and RDMA over TCP
ⓘ
framing requirements for DDP segments ⓘ framing requirements for RDMA messages ⓘ ordering rules for DDP and RDMA traffic ⓘ protocol requirements for DDP over TCP ⓘ protocol requirements for RDMA over TCP ⓘ security considerations for DDP and RDMA over TCP ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| title | Direct Data Placement over Reliable Transports NERFINISHED ⓘ |
| updates |
DDP architecture specifications
ⓘ
RDMA protocol architecture specifications ⓘ |
| usesTransport |
TCP
NERFINISHED
ⓘ
reliable transports ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: RFC 5047 Description of subject: RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.