RFC 2406
E522212
RFC 2406 is an Internet standards document that originally specified the Encapsulating Security Payload (ESP) protocol for providing confidentiality, authentication, and integrity in IPsec.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2406 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479092 — 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 2406 Context triple: [Encapsulating Security Payload, obsoletes, RFC 2406]
-
A.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
E.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
- 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 2406 Target entity description: RFC 2406 is an Internet standards document that originally specified the Encapsulating Security Payload (ESP) protocol for providing confidentiality, authentication, and integrity in IPsec.
-
A.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
E.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 NERFINISHED ⓘ |
| area | Security Area ⓘ |
| category | Security ⓘ |
| context | IP Security Architecture NERFINISHED ⓘ |
| defines |
ESP authentication services
ⓘ
ESP confidentiality services ⓘ ESP header format ⓘ ESP integrity services ⓘ ESP padding requirements ⓘ ESP processing rules ⓘ ESP replay protection mechanisms ⓘ ESP security association usage ⓘ ESP sequence number handling ⓘ ESP trailer format ⓘ processing of ESP for inbound traffic ⓘ processing of ESP for outbound traffic ⓘ transport mode ESP ⓘ tunnel mode ESP ⓘ |
| hasAbbreviation | ESP NERFINISHED ⓘ |
| intendedUse | protection of IP packets ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4303 NERFINISHED ⓘ |
| partOf | IP Security Protocol (IPsec) NERFINISHED ⓘ |
| protocolLayer | Network layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
IP Authentication Header
NERFINISHED
ⓘ
RFC 2401 NERFINISHED ⓘ RFC 2402 ⓘ |
| securityDomain |
Internet security
ⓘ
network security ⓘ |
| series | STD series candidate ⓘ |
| specifies |
ESP
NERFINISHED
ⓘ
Encapsulating Security Payload NERFINISHED ⓘ |
| specifiesProtocolFor |
authentication in IPsec
ⓘ
confidentiality in IPsec ⓘ integrity in IPsec ⓘ |
| standardizes | use of cryptographic algorithms in ESP ⓘ |
| standardType | Proposed Standard ⓘ |
| status | Obsoleted ⓘ |
| title | IP Encapsulating Security Payload (ESP) ⓘ |
| updatesSpecificationOf | IPsec ESP NERFINISHED ⓘ |
| usedIn |
Virtual Private Networks
NERFINISHED
ⓘ
remote access VPNs ⓘ site-to-site VPNs ⓘ |
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 2406 Description of subject: RFC 2406 is an Internet standards document that originally specified the Encapsulating Security Payload (ESP) protocol for providing confidentiality, authentication, and integrity in IPsec.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.