RFC 8200
E23862
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8200 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T187678 — 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 8200 Context triple: [Internet Protocol version 6, definedIn, RFC 8200]
-
A.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
D.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
E.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
- 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 8200 Target entity description: RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
A.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
D.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
E.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IPv6 specification
ⓘ
Internet standard ⓘ Request for Comments ⓘ |
| area |
the internet
ⓘ
surface form:
Internet Area
|
| category | Internet Standard ⓘ |
| defines |
IPv6 authentication header reference
ⓘ
IPv6 base protocol ⓘ IPv6 destination address field ⓘ IPv6 destination options header ⓘ IPv6 encapsulating security payload reference ⓘ IPv6 extension header mechanism ⓘ IPv6 extension header ordering rules ⓘ IPv6 flow label field ⓘ IPv6 fragment header ⓘ IPv6 fragmentation behavior ⓘ IPv6 header format ⓘ IPv6 hop limit field ⓘ IPv6 hop-by-hop options header ⓘ IPv6 next header field ⓘ IPv6 no-next-header value ⓘ IPv6 options processing ⓘ IPv6 packet structure ⓘ IPv6 payload length field ⓘ IPv6 routing header ⓘ IPv6 source address field ⓘ IPv6 traffic class field ⓘ |
| obsoletes | RFC 2460 ⓘ |
| partOf | IPv6 standards suite ⓘ |
| protocolNumber | 41 ⓘ |
| protocolVersion | IPv6 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| replaces | original IPv6 specification in RFC 2460 ⓘ |
| specifies |
IPv6 addressing model at the packet level
ⓘ
IPv6 extension header processing ⓘ IPv6 fragmentation rules ⓘ IPv6 minimum MTU requirements ⓘ IPv6 packet processing rules ⓘ IPv6 path MTU discovery behavior ⓘ IPv6 upper-layer checksum considerations ⓘ core IPv6 protocol architecture ⓘ |
| standardizes |
128-bit IPv6 addresses
ⓘ
IPv6 base header size of 40 bytes ⓘ |
| standardsTrackStatus | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
Internet Protocol version 6
ⓘ
surface form:
Internet Protocol, Version 6 (IPv6) Specification
|
| updates | IPv6 protocol ⓘ |
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 8200 Description of subject: RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.