RFC 5906
E815701
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5906 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T9690818 — 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 5906 Context triple: [RFC 5905, relatedTo, RFC 5906]
-
A.
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.
-
B.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
C.
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.
-
D.
RFC 6409
RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- 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 5906 Target entity description: RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
A.
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.
-
B.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
C.
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.
-
D.
RFC 6409
RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| abbreviation | NTPv4 Autokey Specification NERFINISHED ⓘ |
| addresses |
man-in-the-middle attacks on NTP
ⓘ
replay attacks on NTP ⓘ spoofing attacks on NTP ⓘ |
| appliesTo |
broadcast NTP associations
ⓘ
multicast NTP associations ⓘ unicast NTP associations ⓘ |
| area | Internet NERFINISHED ⓘ |
| authenticationMechanism | Autokey NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
Autokey key management procedures
ⓘ
Autokey protocol for NTP ⓘ Autokey security model ⓘ NTP Autokey message formats ⓘ NTP Autokey state machine ⓘ certificate-based identity schemes for NTP ⓘ cookie-based replay protection for NTP ⓘ group keying for NTP associations ⓘ public-key based NTP association authentication ⓘ |
| definesProtocolMechanismFor | Network Time Protocol NERFINISHED ⓘ |
| focusesOn | NTP authentication ⓘ |
| format | text ⓘ |
| identifier | RFC 5906 ⓘ |
| intendedFor | secure time synchronization over IP networks ⓘ |
| language | English ⓘ |
| obsoletedBy | later NTP security mechanisms such as NTS (Network Time Security) ⓘ |
| protocolFamily | Internet Protocol Suite NERFINISHED ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
key management
ⓘ
security ⓘ time synchronization ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifiesVersionOf | NTP version 4 ⓘ |
| standardsBody | IETF NTP Working Group NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Network Time Protocol Version 4: Autokey Specification NERFINISHED ⓘ |
| topic |
network security
ⓘ
public key infrastructure ⓘ time protocols ⓘ |
| updates | NTP authentication mechanisms ⓘ |
| uses |
X.509-like certificate structures
ⓘ
digital signatures ⓘ hash functions ⓘ |
| usesCryptographyType | public key cryptography ⓘ |
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 5906 Description of subject: RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.