RFC 1305
E234529
RFC 1305 is an Internet standards document that specifies version 3 of the Network Time Protocol (NTP) for synchronizing computer clocks over packet-switched, variable-latency data networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1305 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T2108329 — 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 1305 Context triple: [Network Time Protocol, previouslyDefinedIn, RFC 1305]
-
A.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
B.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
C.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
D.
RFC 1905
RFC 1905 is an Internet standards document that specifies the protocol operations for the Simple Network Management Protocol version 2 (SNMPv2).
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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 1305 Target entity description: RFC 1305 is an Internet standards document that specifies version 3 of the Network Time Protocol (NTP) for synchronizing computer clocks over packet-switched, variable-latency data networks.
-
A.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
B.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
C.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
D.
RFC 1905
RFC 1905 is an Internet standards document that specifies the protocol operations for the Simple Network Management Protocol version 2 (SNMPv2).
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 1305 ⓘ |
| appliesTo |
packet-switched data networks
ⓘ
variable-latency networks ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
|
| author | David L. Mills ⓘ |
| category | Internet Standard ⓘ |
| defines |
NTP association modes (client, server, symmetric, broadcast)
ⓘ
NTP error analysis model ⓘ NTP operating modes ⓘ NTP packet format for version 3 ⓘ NTP reference clock concept ⓘ NTP state variables ⓘ NTP strata hierarchy ⓘ NTP stratum levels from 1 to 15 ⓘ NTP synchronization distance and dispersion ⓘ NTP timestamp format ⓘ algorithms for synchronizing computer clocks over packet-switched, variable-latency data networks ⓘ clock discipline algorithms ⓘ clock filtering algorithms ⓘ clock selection algorithms ⓘ leap indicator field in NTP header ⓘ poll interval and precision fields in NTP header ⓘ |
| definesLayer | application layer protocol ⓘ |
| editor | David L. Mills ⓘ |
| intendedUse | synchronizing computer clocks over IP networks ⓘ |
| language | English ⓘ |
| number | 1305 ⓘ |
| obsoletedBy |
Network Time Protocol Version 4: Protocol and Algorithms Specification
ⓘ
linked to:
Network Time Protocol
RFC 5905 ⓘ |
| obsoletes |
RFC 1119
ⓘ
earlier NTP specifications for versions prior to 3 ⓘ |
| portNumber |
123/TCP
ⓘ
123/UDP ⓘ |
| protocolFamily | Network Time Protocol ⓘ |
| publisher |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| series |
RFC
ⓘ
linked to:
RFCs
|
| specifiesProtocol |
NTPv3
ⓘ
linked to:
Network Time Protocol
Network Time Protocol version 3 ⓘ
linked to:
Network Time Protocol
|
| standardsTrack | yes ⓘ |
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| subject |
clock synchronization over packet-switched networks
ⓘ
network protocols ⓘ time synchronization ⓘ |
| title |
Network Time Protocol (Version 3) Specification, Implementation and Analysis
ⓘ
linked to:
Network Time Protocol
|
| usesTransportProtocols |
TCP (less common)
ⓘ
UDP ⓘ |
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 1305 Description of subject: RFC 1305 is an Internet standards document that specifies version 3 of the Network Time Protocol (NTP) for synchronizing computer clocks over packet-switched, variable-latency data networks.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.