RFC 5046
E922717
RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5046 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T11351403 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5046 Context triple: [iWARP, isSpecifiedIn, RFC 5046]
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
C.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 5045
RFC 5045 is an IETF standard that defines the protocol mechanisms for implementing iWARP, enabling RDMA (Remote Direct Memory Access) over TCP/IP networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5046 Target entity description: RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
C.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 5045
RFC 5045 is an IETF standard that defines the protocol mechanisms for implementing iWARP, enabling RDMA (Remote Direct Memory Access) over TCP/IP networks.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| abbreviation | MPA NERFINISHED ⓘ |
| applicationDomain |
data center networking
ⓘ
high-performance networking ⓘ storage networking ⓘ |
| area | Transport ⓘ |
| category | Standards Track ⓘ |
| defines | Marker PDU Aligned Framing NERFINISHED ⓘ |
| definesLayering | MPA over TCP ⓘ |
| definesProtocolFor | RDMA over TCP/IP ⓘ |
| definesTerm |
CRC for framed PDUs
ⓘ
FPDU (Framed Protocol Data Unit) NERFINISHED ⓘ Marker PDU NERFINISHED ⓘ |
| enables | RDMA semantics over standard TCP/IP networks ⓘ |
| format |
PDF
ⓘ
text ⓘ |
| hasURL | https://www.rfc-editor.org/rfc/rfc5046 ⓘ |
| intendedFor | lossless, low-latency data transfer over TCP/IP ⓘ |
| language | English ⓘ |
| networkProtocol | TCP NERFINISHED ⓘ |
| obsoletedBy | RFC 8937 NERFINISHED ⓘ |
| organization | Internet Engineering Task Force NERFINISHED ⓘ |
| partOf | iWARP protocol suite NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedRFC |
RFC 5040
ⓘ
RFC 5041 NERFINISHED ⓘ RFC 5042 NERFINISHED ⓘ RFC 5044 NERFINISHED ⓘ |
| relatedTo |
RDMA
ⓘ
TCP NERFINISHED ⓘ iWARP NERFINISHED ⓘ remote direct memory access ⓘ |
| RFCNumber | 5046 ⓘ |
| securityConsiderationsSection | yes ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifies | marker-based framing for TCP byte streams ⓘ |
| standardizes | framing protocol for RDMA over TCP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Infiniband Trade Association (IBTA) Marker PDU Aligned Framing (MPA) for TCP NERFINISHED ⓘ |
| transportLayer | TCP NERFINISHED ⓘ |
| updates | RFC 4297 NERFINISHED ⓘ |
| usedIn | iWARP architecture ⓘ |
| workingGroup | RDDP NERFINISHED ⓘ |
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.
Instruction
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.
Input
Subject: RFC 5046 Description of subject: RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.