RFC 5996
E522218
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5996 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479159 — 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 5996 Context triple: [IKEv2, updatedBy, RFC 5996]
-
A.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
B.
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.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
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 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 5996 Target entity description: 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.
-
A.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
B.
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.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
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 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 (44)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Internet Standard ⓘ Request for Comments ⓘ |
| abbreviation |
IKEv2
ⓘ
linked to:
Internet Key Exchange Protocol Version 2
|
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
CHILD_SA (Child Security Association)
ⓘ
IKE_SA (IKE Security Association) ⓘ
linked to:
IKEv2
|
| definesProtocol |
IKEv2
ⓘ
linked to:
Internet Key Exchange Protocol Version 2
Internet Key Exchange Protocol Version 2 ⓘ |
| documentType | technical specification ⓘ |
| intendedUse | Internet-wide key management for IPsec ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 7296 ⓘ |
| obsoletedStandard | Internet Key Exchange Protocol Version 2 (IKEv2) specification later updated in RFC 7296 ⓘ |
| obsoletes | RFC 4306 ⓘ |
| protocolFamily | IKE ⓘ |
| protocolLayer | Key management ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedRFC |
RFC 4306
ⓘ
RFC 7296 ⓘ |
| relatedToProtocol | IPsec ⓘ |
| replacesProtocolVersion | IKEv1 ⓘ |
| scope | Internet-wide ⓘ |
| securityProperty |
mutual authentication
ⓘ
perfect forward secrecy (when configured) ⓘ protection against replay attacks ⓘ |
| specifies |
IKEv2 NAT traversal behavior
ⓘ
IKEv2 authentication mechanisms ⓘ IKEv2 error handling ⓘ IKEv2 message formats ⓘ IKEv2 mobility and multihoming support ⓘ IKEv2 negotiation of cryptographic algorithms ⓘ IKEv2 payload types ⓘ IKEv2 rekeying procedures ⓘ IKEv2 state machine ⓘ |
| standardsBody | IETF IPsec Working Group ⓘ |
| status | Obsoleted ⓘ |
| title |
Internet Key Exchange Protocol Version 2 (IKEv2)
ⓘ
linked to:
IKEv2
|
| updatesSpecificationOf |
Internet Key Exchange
ⓘ
linked to:
IKEv1
|
| useCase |
VPNs
ⓘ
establishing IPsec security associations ⓘ secure tunneling ⓘ |
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 5996 Description of subject: 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.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.