RFC 2401
E325865
RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2401 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081783 — 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 2401 Context triple: [RFC 3168, updates, RFC 2401]
-
A.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
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 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
- 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 2401 Target entity description: RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
-
A.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
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 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
IPsec specification ⓘ Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
Security Association Database
ⓘ
surface form:
IPsec Security Association model
IPsec processing model ⓘ IPsec security architecture ⓘ IPsec security policy model ⓘ Security Architecture for the Internet Protocol ⓘ
surface form:
Internet Protocol Security architecture
security services for IP ⓘ |
| definesConcept |
SAD
ⓘ
SPD ⓘ Security Association ⓘ Security Association Database ⓘ Security Policy Database ⓘ bypass traffic ⓘ discard traffic ⓘ protected traffic ⓘ transport mode ⓘ tunnel mode ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4301 ⓘ |
| partOf | IPsec ⓘ |
| protocolFamily | Internet Protocol ⓘ |
| protocolLayer | Network layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
Authentication Header
ⓘ
Encapsulating Security Payload ⓘ IKEv1 ⓘ
surface form:
Internet Key Exchange
RFC 2402 ⓘ RFC 2406 ⓘ RFC 2409 ⓘ |
| RFCNumber | 2401 ⓘ |
| specifies |
use of AH in IPsec architecture
ⓘ
use of ESP in IPsec architecture ⓘ use of IKE for key management in IPsec ⓘ |
| standardizes |
end-to-end security for IP
ⓘ
security services at IP layer ⓘ transport-mode IPsec ⓘ tunnel-mode IPsec ⓘ |
| status | Obsoleted ⓘ |
| title | Security Architecture for the Internet Protocol ⓘ |
| useContext |
Virtual Private Networks
ⓘ
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 2401 Description of subject: RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.