RFC 5338
E169882
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5338 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1459805 — 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 5338 Context triple: [RFC 6557, obsoletes, RFC 5338]
-
A.
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.
-
B.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
-
C.
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.
-
D.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
E.
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.
- 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 5338 Target entity description: 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.
-
A.
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.
-
B.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
-
C.
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.
-
D.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
E.
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.
- F. None of above. chosen
Statements (26)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standards-track document
ⓘ
Request for Comments ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
|
| category | Internet Standard ⓘ |
| defines | earlier approach to managing the IANA IPv6 Special-Purpose Address Registry ⓘ |
| documentType | Standards-track RFC ⓘ |
| governs | allocation of IPv6 special-purpose address blocks ⓘ |
| hasAbbreviation | RFC 5338 ⓘ |
| intendedAudience |
IANA administrators
ⓘ
linked to:
IANA
network operators ⓘ protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 6890 ⓘ |
| protocolFamily |
IPv6
ⓘ
linked to:
Internet Protocol version 6
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| registryManaged | IANA IPv6 Special-Purpose Address Registry ⓘ |
| relatesTo |
IANA IPv6 Special-Purpose Address Registry
ⓘ
IPv6 ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | obsoleted ⓘ |
| topic |
IP addressing
ⓘ
Internet number resource management ⓘ
linked to:
Number Resource Organization
special-purpose IP addresses ⓘ |
| updates | IANA IPv6 Special-Purpose Address Registry management procedures ⓘ |
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 5338 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.