RFC 4380
E123431
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4380 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077121 — 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 4380 Context triple: [Teredo, definedIn, RFC 4380]
-
A.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- 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 4380 Target entity description: RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
A.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard specification ⓘ |
| addressesProblem |
IPv6 connectivity through IPv4 Network Address Translators
ⓘ
NAT traversal for IPv6 traffic ⓘ |
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines | Teredo IPv6-over-UDP tunneling mechanism ⓘ |
| definesBehavior |
Teredo client behavior
ⓘ
Teredo relay behavior ⓘ Teredo server behavior ⓘ |
| definesComponent |
Teredo IPv6 address format
ⓘ
Teredo IPv6 service prefix ⓘ Teredo bubble packets ⓘ Teredo client ⓘ
linked to:
Teredo
Teredo maintenance mechanisms ⓘ Teredo relay ⓘ
linked to:
Teredo
Teredo server ⓘ
linked to:
Teredo
|
| definesField |
Teredo IPv6 address embedding IPv4 server address
ⓘ
Teredo IPv6 address embedding UDP port and flags ⓘ |
| documentType | Standards-track RFC ⓘ |
| enables |
IPv6 connectivity for nodes behind IPv4 NATs
ⓘ
IPv6 connectivity over IPv4 networks ⓘ |
| format | text ⓘ |
| intendedUse | transition from IPv4 to IPv6 ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 5991
ⓘ
RFC 6081 ⓘ |
| protocolType |
IPv6 transition mechanism
ⓘ
tunneling protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
IPv4
ⓘ
IPv6 ⓘ IPv6 transition technologies ⓘ NAT traversal ⓘ Network Address Translation ⓘ
linked to:
NAT64
|
| securityConsiderations | describes security issues of Teredo tunneling ⓘ |
| specifiesProtocol | Teredo ⓘ |
| standardizes | automatic tunneling of IPv6 over UDP/IPv4 ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Obsoleted ⓘ |
| title |
Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
ⓘ
linked to:
Teredo
|
| tunnels | IPv6 over IPv4 ⓘ |
| usesTransportProtocol | UDP ⓘ |
| workingGroup | NGTRANS ⓘ |
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 4380 Description of subject: RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.