RFC 1883
E522208
RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1883 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5478989 — 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.
Target entity: RFC 1883 Context triple: [RFC 2460, replaces, RFC 1883]
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
E.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 1883 Target entity description: RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
E.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
IPv6
NERFINISHED
ⓘ
IPv6 core mechanisms ⓘ IPv6 header format ⓘ |
| definesConcept |
IPv6 address types
ⓘ
IPv6 anycast addressing ⓘ IPv6 destination options header ⓘ IPv6 extension headers NERFINISHED ⓘ IPv6 flow label ⓘ IPv6 fragmentation mechanism ⓘ IPv6 header processing rules ⓘ IPv6 hop-by-hop options header ⓘ IPv6 multicast addressing ⓘ IPv6 packet format ⓘ IPv6 routing header ⓘ IPv6 unicast addressing ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 2460 NERFINISHED ⓘ |
| obsoletes | IPv4 header format for IPv6 traffic NERFINISHED ⓘ |
| protocolVersion | IPv6 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
IPv4
ⓘ
RFC 2460 NERFINISHED ⓘ |
| series | RFC series NERFINISHED ⓘ |
| specifiesField |
IPv6 Destination Address field
ⓘ
IPv6 Flow Label field ⓘ IPv6 Hop Limit field ⓘ IPv6 Next Header field ⓘ IPv6 Payload Length field ⓘ IPv6 Source Address field ⓘ IPv6 Traffic Class field ⓘ IPv6 Version field ⓘ |
| standardizes |
IPv6 basic header
ⓘ
IPv6 minimum MTU requirements ⓘ IPv6 packet handling by hosts ⓘ IPv6 packet handling by routers ⓘ |
| status | Obsoleted ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| title | Internet Protocol, Version 6 (IPv6) Specification NERFINISHED ⓘ |
| topic |
IP networking
ⓘ
Internet Protocol NERFINISHED ⓘ Internet layer ⓘ |
| updatesProtocol | Internet Protocol 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.
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.
Subject: RFC 1883 Description of subject: RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.