RFC 5991
E524097
RFC 5991 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve its security and operational behavior.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5991 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479327 — 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 5991 Context triple: [RFC 4380, obsoletedBy, RFC 5991]
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
C.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
D.
RFC 4791
RFC 4791 is the Internet standards document that specifies the CalDAV protocol for remote access and management of calendar data over WebDAV.
-
E.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
- 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 5991 Target entity description: RFC 5991 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve its security and operational behavior.
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
C.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
D.
RFC 4791
RFC 4791 is the Internet standards document that specifies the CalDAV protocol for remote access and management of calendar data over WebDAV.
-
E.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track document ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines | security updates for Teredo IPv6 transition mechanism ⓘ |
| documentType | Internet Standard specification (proposed) ⓘ |
| focusesOn |
mitigation of Teredo-based attacks
ⓘ
operational guidance for Teredo deployment ⓘ security considerations for Teredo ⓘ |
| format |
PDF
ⓘ
text ⓘ |
| hasNumber | 5991 ⓘ |
| improves |
operational behavior of Teredo
ⓘ
security of Teredo ⓘ |
| intendedAudience |
network operators
ⓘ
protocol designers ⓘ security practitioners ⓘ |
| language | English ⓘ |
| obsoletes | RFC 4380 NERFINISHED ⓘ |
| partOf | IETF Teredo specifications NERFINISHED ⓘ |
| protocolFamily |
IPv4
ⓘ
IPv6 ⓘ |
| publicationMonth | September ⓘ |
| publicationYear | 2010 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
IPv6 transition
ⓘ
tunneling IPv6 over UDP/IPv4 ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| standardizes |
changes to Teredo client behavior
ⓘ
changes to Teredo packet processing ⓘ changes to Teredo relay behavior ⓘ changes to Teredo server behavior ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
IPv6 transition mechanisms
ⓘ
NAT traversal ⓘ Teredo NERFINISHED ⓘ network security ⓘ |
| title | Teredo Security Updates NERFINISHED ⓘ |
| updates | RFC 4380 NERFINISHED ⓘ |
| workingGroup | Behavior Engineering for Hindrance Avoidance (behave) 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 5991 Description of subject: RFC 5991 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve its security and operational behavior.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.