RFC 4301
E522219
RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4301 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479165 — 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 4301 Context triple: [Security Policy Database, specifiedIn, RFC 4301]
-
A.
RFC 2401
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.
-
B.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
C.
RFC 2104
RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
-
D.
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.
-
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 4301 Target entity description: RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
-
A.
RFC 2401
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.
-
B.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
C.
RFC 2104
RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
-
D.
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.
-
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 (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
IPsec specification ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
IPsec architecture
ⓘ
IPsec processing model ⓘ IPsec security services ⓘ IPsec security services: confidentiality, integrity, authentication, anti-replay ⓘ IPsec selectors ⓘ IPsec transport mode ⓘ IPsec tunnel mode ⓘ SAD ⓘ SPD NERFINISHED ⓘ Security Architecture for IP NERFINISHED ⓘ Security Association Database NERFINISHED ⓘ Security Policy Database NERFINISHED ⓘ |
| focusesOn |
end-to-end security policies
ⓘ
network-layer security ⓘ virtual private networks ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2401 NERFINISHED ⓘ |
| protocolFamily | Internet Protocol NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| relatedTo |
IPsec key management protocols
ⓘ
RFC 4302 NERFINISHED ⓘ RFC 4303 NERFINISHED ⓘ |
| rfcNumber | 4301 ⓘ |
| specifies |
audit and management requirements for IPsec
ⓘ
bypass and discard traffic processing ⓘ interaction of IPsec with IPv4 ⓘ interaction of IPsec with IPv6 ⓘ packet handling for IPsec ⓘ processing of inbound IPsec traffic ⓘ processing of outbound IPsec traffic ⓘ use of Security Associations ⓘ |
| standardsBody | IETF IPsec Working Group NERFINISHED ⓘ |
| status | Internet Standard ⓘ |
| title | Security Architecture for the Internet Protocol NERFINISHED ⓘ |
| uses |
Authentication Header
NERFINISHED
ⓘ
Encapsulating Security Payload NERFINISHED ⓘ |
| usesAbbreviation | IPsec 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 4301 Description of subject: RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.