RFC 4303
E522211
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4303 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479091 — 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 4303 Context triple: [Encapsulating Security Payload, specifiedIn, RFC 4303]
-
A.
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.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
D.
RFC 4034
RFC 4034 is an Internet standards document that specifies the DNS Security Extensions (DNSSEC) resource records and their formats used to provide authentication and integrity for DNS data.
-
E.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
- 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 4303 Target entity description: RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
-
A.
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.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
D.
RFC 4034
RFC 4034 is an Internet standards document that specifies the DNS Security Extensions (DNSSEC) resource records and their formats used to provide authentication and integrity for DNS data.
-
E.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf | IETF Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
IPsec Encapsulating Security Payload header format
NERFINISHED
ⓘ
IPsec Encapsulating Security Payload trailer format NERFINISHED ⓘ processing rules for ESP ⓘ security services provided by ESP ⓘ |
| definesAbbreviation | ESP NERFINISHED ⓘ |
| definesField |
Next Header
ⓘ
Pad Length ⓘ Padding ⓘ Payload Data ⓘ Security Parameters Index NERFINISHED ⓘ Sequence Number ⓘ |
| definesProtocol | Encapsulating Security Payload NERFINISHED ⓘ |
| focusesOnLayer | network layer ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2406 NERFINISHED ⓘ |
| partOfSeries | Request for Comments NERFINISHED ⓘ |
| protocolFamily | IPsec NERFINISHED ⓘ |
| providesService |
anti-replay protection
ⓘ
confidentiality ⓘ connectionless integrity ⓘ data origin authentication ⓘ limited traffic flow confidentiality ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 4301
NERFINISHED
ⓘ
RFC 4302 NERFINISHED ⓘ |
| specifies |
handling of replay windows
ⓘ
processing of inbound ESP packets ⓘ processing of outbound ESP packets ⓘ requirements for cryptographic algorithms used with ESP ⓘ transport mode for ESP ⓘ tunnel mode for ESP ⓘ use of ESP with security associations ⓘ |
| status | Proposed Standard ⓘ |
| title | IP Encapsulating Security Payload (ESP) NERFINISHED ⓘ |
| updatesSpecificationOf | Encapsulating Security Payload NERFINISHED ⓘ |
| useContext |
Virtual Private Networks
ⓘ
remote access IPsec ⓘ site-to-site IPsec ⓘ |
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 4303 Description of subject: RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.