RFC 5308
E130003
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5308 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1081805 — 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 5308 Context triple: [IS-IS for IPv6, definedIn, RFC 5308]
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- 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 5308 Target entity description: RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
IS-IS for IPv6
ⓘ
IS‑IS ⓘ
surface form:
Intermediate System to Intermediate System
|
| area | Routing ⓘ |
| category | Standards Track ⓘ |
| defines |
IPv6 metric encoding in IS-IS
ⓘ
IPv6 prefix advertisement in IS-IS ⓘ IPv6 reachability TLVs for IS-IS ⓘ backward compatibility considerations with IPv4-only IS-IS ⓘ encoding of IPv6 prefixes in IS-IS ⓘ mechanisms for advertising IPv6 interface addresses in IS-IS ⓘ mechanisms for advertising IPv6 reachability in IS-IS ⓘ multi-topology considerations for IPv6 in IS-IS ⓘ use of TLV 236 for IPv6 reachability ⓘ use of TLV 237 for IPv6 interface addresses ⓘ |
| documentType | Standards-track RFC ⓘ |
| extends |
IS‑IS
ⓘ
surface form:
IS-IS routing protocol
|
| focusesOn | link-state routing for IPv6 using IS-IS ⓘ |
| hasNumber | 5308 ⓘ |
| intendedFor | IPv6-capable IS-IS routers ⓘ |
| intendedStatus | Standards Track ⓘ |
| language | English ⓘ |
| networkLayer | Layer 3 ⓘ |
| obsoletes | RFC 5302 ⓘ |
| partOf |
IETF Internet standards process
ⓘ
surface form:
Internet Standards process
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedOn | October 2008 ⓘ |
| relatedTo |
IPv6 unicast routing
ⓘ
intra-domain routing ⓘ link-state IGPs ⓘ |
| series | RFC series ⓘ |
| specifiesProtocolExtensionFor |
IS‑IS
ⓘ
surface form:
IS-IS
|
| standardsTrackStatus | Proposed Standard ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| supports |
IPv6 addressing
ⓘ
IPv6 routing ⓘ |
| title |
IS-IS for IPv6
ⓘ
surface form:
Routing IPv6 with IS-IS
|
| topic |
IPv6
ⓘ
IS‑IS ⓘ
surface form:
IS-IS
link-state routing ⓘ routing protocols ⓘ |
| updates | IS-IS protocol to carry IPv6 information ⓘ |
| uses | TLV-based encoding in IS-IS ⓘ |
| year | 2008 ⓘ |
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 5308 Description of subject: RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.