RFC 6860
E554473
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6860 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5770880 — 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 6860 Context triple: [RFC 5340, obsoletedBy, RFC 6860]
-
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 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
C.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
D.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
E.
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.
- 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 6860 Target entity description: 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.
-
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 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
C.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
D.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
E.
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.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
IETF RFC
ⓘ
standards-track document ⓘ |
| addresses | security mechanisms for OSPFv3 ⓘ |
| aimsTo |
improve security of OSPFv3 routing exchanges
ⓘ
replace earlier, weaker authentication methods for OSPFv3 ⓘ |
| area |
link-state routing protocols
ⓘ
routing security ⓘ |
| category | Standards Track ⓘ |
| clarifies |
backward compatibility with earlier OSPFv3 authentication mechanisms
ⓘ
interaction of OSPFv3 authentication with IPsec ⓘ use of AH and ESP with OSPFv3 ⓘ use of cryptographic authentication for OSPFv3 ⓘ |
| defines |
HMAC-SHA-based authentication for OSPFv3
ⓘ
authentication key ID handling for OSPFv3 ⓘ error handling for authentication failures in OSPFv3 ⓘ procedures for key rollover in OSPFv3 ⓘ |
| focusesOn |
HMAC-SHA algorithms
ⓘ
OSPFv3 packet authentication ⓘ cryptographic authentication ⓘ |
| intendedFor |
network operators
ⓘ
router implementers ⓘ security engineers ⓘ |
| language | English ⓘ |
| obsoletes | none ⓘ |
| partOf |
OSPFv3 security specifications
ⓘ
linked to:
OSPFv3
|
| protocolFamily | OSPF ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2328
ⓘ
RFC 4552 ⓘ RFC 5340 ⓘ |
| specifies |
authentication trailer for OSPFv3
ⓘ
key management considerations for OSPFv3 authentication ⓘ processing rules for authenticated OSPFv3 packets ⓘ requirements for cryptographic key strength in OSPFv3 ⓘ use of HMAC-SHA-256 for OSPFv3 ⓘ use of HMAC-SHA-384 for OSPFv3 ⓘ use of HMAC-SHA-512 for OSPFv3 ⓘ |
| standardizes | cryptographic authentication for OSPFv3 ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | HMAC-SHA Cryptographic Authentication for OSPFv3 ⓘ |
| updates | RFC 4552 ⓘ |
| updatesProtocol | OSPFv3 ⓘ |
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 6860 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.