RFC 2460
E123424
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2460 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077022 — 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 2460 Context triple: [RFC 8200, obsoletes, RFC 2460]
-
A.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
B.
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.
-
C.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
D.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- 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 2460 Target entity description: RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
A.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
B.
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.
-
C.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
D.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
IP networks
ⓘ
Internet ⓘ
linked to:
the internet
|
| area | Internet Area ⓘ |
| category | Standards Track RFC ⓘ |
| defines |
IPv6 base header fields
ⓘ
IPv6 destination address field ⓘ IPv6 extension header mechanism ⓘ IPv6 flow label field ⓘ IPv6 fragmentation behavior ⓘ IPv6 fragmentation via Fragment header instead of in base header ⓘ IPv6 handling of options via extension headers ⓘ IPv6 header format ⓘ IPv6 header processing rules for hosts ⓘ IPv6 header processing rules for routers ⓘ IPv6 hop limit field ⓘ IPv6 jumbogram support via Hop-by-Hop Options header ⓘ IPv6 minimum MTU requirements ⓘ IPv6 next header field ⓘ IPv6 packet format ⓘ IPv6 path MTU discovery behavior ⓘ IPv6 payload length field ⓘ IPv6 source address field ⓘ IPv6 traffic class field ⓘ IPv6 unicast, anycast, and multicast packet treatment at header level ⓘ IPv6 upper-layer checksum pseudo-header ⓘ rules for header order of IPv6 extension headers ⓘ rules for processing unknown IPv6 extension headers ⓘ |
| focusesOn | network layer ⓘ |
| language | English ⓘ |
| networkProtocolFamily |
Internet Protocol Suite
ⓘ
linked to:
TCP/IP
|
| obsoletedBy | RFC 8200 ⓘ |
| protocolSpecified |
IPv6
ⓘ
linked to:
Internet Protocol version 6
|
| protocolVersion | 6 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
RFC Editor ⓘ |
| replaces | RFC 1883 ⓘ |
| standardizes |
IPv6 addressing architecture interaction at packet level
ⓘ
IPv6 datagram structure ⓘ core IPv6 protocol ⓘ |
| status | Obsoleted ⓘ |
| successor | RFC 8200 ⓘ |
| title |
Internet Protocol, Version 6 (IPv6) Specification
ⓘ
linked to:
Internet Protocol version 6
|
| updates | IPv4 concepts for IPv6 ⓘ |
| workingGroup | IPng Working Group ⓘ |
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 2460 Description of subject: RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.