IETF RFC 4392
E1429941
UNEXPLORED
IETF RFC 4392 is a standards-track document from the Internet Engineering Task Force that specifies how to encapsulate and transport IP traffic over InfiniBand networks.
All labels observed (4)
| Label | Occurrences |
|---|---|
| IETF RFC 4390 | 1 |
| IETF RFC 4392 canonical | 1 |
| IETF RFC 4393 | 1 |
| IETF RFC 4394 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T20399919 — 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: IETF RFC 4392 Context triple: [IP over InfiniBand, definedIn, IETF RFC 4392]
-
A.
IETF RFC 4391
IETF RFC 4391 is a standards-track document from the Internet Engineering Task Force that specifies how the Internet Protocol (IP) operates over InfiniBand networks.
-
B.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
C.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
-
D.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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: IETF RFC 4392 Target entity description: IETF RFC 4392 is a standards-track document from the Internet Engineering Task Force that specifies how to encapsulate and transport IP traffic over InfiniBand networks.
-
A.
IETF RFC 4391
IETF RFC 4391 is a standards-track document from the Internet Engineering Task Force that specifies how the Internet Protocol (IP) operates over InfiniBand networks.
-
B.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
C.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
-
D.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: IETF RFC 4392
linked to: IETF RFC 4392
linked to: IETF RFC 4392