RFC 2030
E815698
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2030 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9690785 — 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 2030 Context triple: [RFC 5905, obsoletes, RFC 2030]
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
C.
RFC 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- 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 2030 Target entity description: RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
C.
RFC 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ OSI NERFINISHED ⓘ |
| area | Internet NERFINISHED ⓘ |
| author | David L. Mills NERFINISHED ⓘ |
| basedOn | Network Time Protocol Version 3 NERFINISHED ⓘ |
| category | Informational ⓘ |
| datePublished | October 1996 ⓘ |
| defines |
SNTP client behavior
ⓘ
SNTP packet format ⓘ SNTP server behavior ⓘ timestamp formats for SNTP ⓘ |
| definesAbbreviation | SNTP NERFINISHED ⓘ |
| definesProtocol | Simple Network Time Protocol NERFINISHED ⓘ |
| documentSeries | RFC NERFINISHED ⓘ |
| focusesOn |
clock synchronization over IP networks
ⓘ
simplified subset of NTP ⓘ |
| hasRFCNumber | 2030 ⓘ |
| intendedUse | clients with less stringent accuracy requirements ⓘ |
| isAccessibleFrom | https://www.rfc-editor.org/rfc/rfc2030 ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 4330
NERFINISHED
ⓘ
RFC 4330 (direct successor for SNTP) ⓘ RFC 5901 NERFINISHED ⓘ RFC 5905 NERFINISHED ⓘ RFC 5906 NERFINISHED ⓘ RFC 5907 NERFINISHED ⓘ RFC 5908 NERFINISHED ⓘ RFC 5909 NERFINISHED ⓘ RFC 5910 NERFINISHED ⓘ |
| portNumber | 123 ⓘ |
| protocolType | time synchronization protocol ⓘ |
| protocolVersion | Version 4 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatedTo |
Network Time Protocol (NTP)
NERFINISHED
ⓘ
RFC 1305 NERFINISHED ⓘ |
| standardizes | interoperable SNTP implementations ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Internet protocols
ⓘ
time synchronization ⓘ |
| title | Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI NERFINISHED ⓘ |
| updatesProtocol | Network Time Protocol NERFINISHED ⓘ |
| usesTransport | UDP NERFINISHED ⓘ |
| workingGroup | Network Time Protocol Working Group NERFINISHED ⓘ |
| yearPublished | 1996 ⓘ |
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 2030 Description of subject: RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.