RFC 6864
E712095
RFC 6864 is an Internet Engineering Task Force (IETF) standards-track document that revises and clarifies the semantics and usage of the IPv4 Identification field in IP packet headers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6864 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928676 — 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 6864 Context triple: [RFC 8999, updates, RFC 6864]
-
A.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
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.
-
D.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
E.
RFC 6409
RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
- 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 6864 Target entity description: RFC 6864 is an Internet Engineering Task Force (IETF) standards-track document that revises and clarifies the semantics and usage of the IPv4 Identification field in IP packet headers.
-
A.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
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.
-
D.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
E.
RFC 6409
RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standards-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | IPv4 ID Update NERFINISHED ⓘ |
| addresses |
fragmentation behavior in IPv4
ⓘ
interaction of IPv4 Identification field with middleboxes ⓘ non-fragmented IPv4 packets and the Identification field ⓘ security considerations of the IPv4 Identification field ⓘ |
| aimsTo |
enable efficient implementation of IPv4 Identification handling
ⓘ
improve interoperability of IPv4 implementations ⓘ reduce ambiguity in IPv4 Identification field usage ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| clarifies |
requirements for setting the IPv4 Identification field
ⓘ
requirements for uniqueness of the IPv4 Identification field ⓘ usage of the IPv4 Identification field ⓘ |
| concernsLayer | Internet layer NERFINISHED ⓘ |
| defines | updated semantics for the IPv4 Identification field ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOnProtocol | IPv4 NERFINISHED ⓘ |
| intendedFor |
implementers of IPv4 stacks
ⓘ
network protocol designers ⓘ operators of IP networks ⓘ |
| language | English ⓘ |
| obsoletes | use of IPv4 Identification field for purposes other than fragmentation ⓘ |
| partOf | Internet Standards process NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| recommends |
constraints on reuse of IPv4 Identification values for fragmentable packets
ⓘ
that IPv4 Identification field uniqueness is required only for packets that may be fragmented ⓘ that non-fragmentable IPv4 packets may use arbitrary Identification values ⓘ |
| relatedTo |
IP fragmentation
ⓘ
IPv4 header format ⓘ network performance ⓘ network security ⓘ packet reassembly ⓘ |
| revises |
requirements from earlier IPv4 specifications regarding the Identification field
ⓘ
semantics of the IPv4 Identification field ⓘ |
| standardizes | IPv4 Identification field semantics ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Updated Specification of the IPv4 ID Field NERFINISHED ⓘ |
| updatesSpecificationOf | IPv4 header Identification field ⓘ |
| workingGroup | Internet Area Working Group 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 6864 Description of subject: RFC 6864 is an Internet Engineering Task Force (IETF) standards-track document that revises and clarifies the semantics and usage of the IPv4 Identification field in IP packet headers.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.