RFC 5838
E549517
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5838 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5770879 — 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 5838 Context triple: [RFC 5340, obsoletedBy, RFC 5838]
-
A.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
B.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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 5838 Target entity description: RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
A.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
B.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
networking standard ⓘ |
| appliesTo |
IPv4 unicast routing over OSPFv3
ⓘ
IPv6 unicast routing ⓘ |
| area |
OSPF
ⓘ
routing ⓘ |
| category | Standards Track ⓘ |
| concernsLayer | network layer ⓘ |
| defines |
AF-specific LSAs in OSPFv3
ⓘ
AF-specific routing information in OSPFv3 ⓘ backward compatibility mechanisms with legacy OSPFv3 routers ⓘ capability negotiation for address families in OSPFv3 ⓘ new OSPFv3 LSA types for address families ⓘ new OSPFv3 options for address family support ⓘ procedures for AF-specific NSSA and stub areas ⓘ procedures for AF-specific SPF calculation ⓘ procedures for AF-specific forwarding address handling ⓘ procedures for AF-specific virtual links ⓘ procedures for advertising AF-specific routes ⓘ support of multiple address families in OSPFv3 ⓘ |
| documentType | Standards Track RFC ⓘ |
| enables | multiple address families within a single OSPFv3 protocol instance ⓘ |
| extendsProtocol | OSPFv3 ⓘ |
| goal |
allow OSPFv3 to carry IPv4 and IPv6 routes in a single instance
ⓘ
reduce the need for separate OSPF instances per address family ⓘ |
| language | English ⓘ |
| organization |
IETF OSPF Working Group
ⓘ
linked to:
OSPF
|
| protocolType | link-state routing protocol extension ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
OSPFv2
ⓘ
linked to:
RFC 2328
OSPFv3 ⓘ |
| standardizes |
extensions to OSPFv3 LSAs for address family support
ⓘ
extensions to OSPFv3 packet formats for address family support ⓘ mechanisms to carry multiple address families in OSPFv3 LSAs ⓘ mechanisms to negotiate address family support between OSPFv3 neighbors ⓘ |
| status | Proposed Standard ⓘ |
| supportsAddressFamily |
IPv4
ⓘ
IPv6 ⓘ |
| title | Support of Address Families in OSPFv3 ⓘ |
| updatesProtocol | OSPFv3 ⓘ |
| useCase |
dual-stack IPv4/IPv6 deployments using OSPFv3
ⓘ
migration from OSPFv2 to OSPFv3 with IPv4 support ⓘ |
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 5838 Description of subject: RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.