RFC 4330
E815699
RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4330 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9690786 — 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 4330 Context triple: [RFC 5905, obsoletes, RFC 4330]
-
A.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
B.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
C.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
D.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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 4330 Target entity description: RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
-
A.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
B.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
C.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
D.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ OSI NERFINISHED ⓘ |
| area | Internet NERFINISHED ⓘ |
| author | David L. Mills NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
SNTP client behavior
ⓘ
SNTP error checking requirements ⓘ SNTP multicast and broadcast modes ⓘ SNTP packet formats ⓘ SNTP protocol operations ⓘ SNTP security considerations ⓘ SNTP server behavior ⓘ SNTP timestamp formats ⓘ SNTP unicast mode ⓘ Simple Network Time Protocol NERFINISHED ⓘ |
| definesAbbreviation | SNTP NERFINISHED ⓘ |
| definesProtocolType | time synchronization protocol ⓘ |
| definesPurpose | synchronizing computer clocks over IP networks ⓘ |
| definesScope | SNTP Version 4 for IPv4, IPv6 and OSI NERFINISHED ⓘ |
| documentType | Internet Standard Track RFC ⓘ |
| focus | simple subset of NTP ⓘ |
| identifier | RFC 4330 NERFINISHED ⓘ |
| intendedUse |
clients with less stringent accuracy requirements
ⓘ
simple network devices ⓘ |
| isPartOf | Network Time Protocol document family NERFINISHED ⓘ |
| language | English ⓘ |
| networkLayer | IP NERFINISHED ⓘ |
| obsoletes | RFC 2030 NERFINISHED ⓘ |
| protocolVersion | Version 4 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo | Network Time Protocol NERFINISHED ⓘ |
| relatedToAbbreviation | NTP NERFINISHED ⓘ |
| standardizes | on-the-wire behavior of SNTP clients and servers ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI NERFINISHED ⓘ |
| topic |
Internet protocols
ⓘ
network time synchronization ⓘ |
| updatesFrom | NTP Version 4 specification concepts ⓘ |
| useCase |
synchronizing system clocks
ⓘ
timekeeping in distributed systems ⓘ |
| workingGroup | Network Time Protocol Working Group NERFINISHED ⓘ |
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 4330 Description of subject: RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.