RFC 6890
E658168
RFC 6890 is an Internet Engineering Task Force (IETF) document that defines and updates the special-purpose IPv4 and IPv6 address registries used for various non-routable and reserved networking functions.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6890 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7366488 — 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 6890 Context triple: [RFC 5338, obsoletedBy, RFC 6890]
-
A.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
B.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
-
E.
RFC 6096
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- 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 6890 Target entity description: RFC 6890 is an Internet Engineering Task Force (IETF) document that defines and updates the special-purpose IPv4 and IPv6 address registries used for various non-routable and reserved networking functions.
-
A.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
B.
RFC 6860
RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
-
E.
RFC 6096
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard document
ⓘ
Request for Comments ⓘ |
| area | Internet NERFINISHED ⓘ |
| author |
Brian Haberman
NERFINISHED
ⓘ
David Meyer NERFINISHED ⓘ Leo Vegoda NERFINISHED ⓘ Michelle Cotton NERFINISHED ⓘ Wesley George NERFINISHED ⓘ |
| BCPNumber | BCP 153 NERFINISHED ⓘ |
| category | Best Current Practice ⓘ |
| concernsProtocol |
IPv4
NERFINISHED
ⓘ
IPv6 NERFINISHED ⓘ |
| defines |
IANA IPv4 Special-Purpose Address Registry
NERFINISHED
ⓘ
IANA IPv6 Special-Purpose Address Registry NERFINISHED ⓘ IANA registry fields for special-purpose IP addresses ⓘ common registry structure for IPv4 and IPv6 special-purpose addresses ⓘ criteria for inclusion of address blocks in special-purpose registries ⓘ documentation of routing and forwarding behavior for special-purpose addresses ⓘ special-purpose IPv4 address registry ⓘ special-purpose IPv6 address registry ⓘ |
| definesProperty |
forwardable property for special-purpose IP addresses
ⓘ
global routing scope for special-purpose IP addresses ⓘ global uniqueness for special-purpose IP addresses ⓘ reserved-by-protocol status for special-purpose IP addresses ⓘ termination date for special-purpose IP address allocations ⓘ |
| documentType | Standards-track related BCP ⓘ |
| hasNumber | 6890 ⓘ |
| intendedStatus | Best Current Practice ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 5156
NERFINISHED
ⓘ
RFC 5735 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedDate | 2013-04 ⓘ |
| registryMaintainer |
IANA
NERFINISHED
ⓘ
Internet Assigned Numbers Authority NERFINISHED ⓘ |
| series | RFC series ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
IP addressing
ⓘ
non-routable IP address space ⓘ reserved IP address space ⓘ special-purpose IP address blocks ⓘ |
| title | Special-Purpose IP Address Registries NERFINISHED ⓘ |
| updates |
IANA Special-Purpose Address Registries
NERFINISHED
ⓘ
procedures for managing special-purpose IP address blocks ⓘ |
| workingGroup | Internet Area Working Group NERFINISHED ⓘ |
| year | 2013 ⓘ |
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 6890 Description of subject: RFC 6890 is an Internet Engineering Task Force (IETF) document that defines and updates the special-purpose IPv4 and IPv6 address registries used for various non-routable and reserved networking functions.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.