RFC 4833
E167595
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4833 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1459804 — 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 4833 Context triple: [RFC 6557, obsoletes, RFC 4833]
-
A.
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).
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
E.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
- 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 4833 Target entity description: 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.
-
A.
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).
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
E.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
IPv4 networks
ⓘ
IPv6 networks (via DHCPv6 options) ⓘ |
| area | Internet Area ⓘ |
| author |
Bernie Volz
ⓘ
N. Brunner ⓘ Ted Lemon ⓘ |
| category | Standards Track ⓘ |
| datePublished | April 2007 ⓘ |
| defines |
DHCP option for POSIX timezone string
ⓘ
DHCP option for daylight saving time (DST) rules ⓘ DHCP option for time zone information ⓘ |
| definesField |
DHCPv4 Timezone Database (TZDB) name option
ⓘ
DHCPv4 Timezone POSIX String option ⓘ |
| definesProtocolExtensionFor |
DHCP
ⓘ
DHCP ⓘ
surface form:
Dynamic Host Configuration Protocol
|
| fullTitle | RFC 4833: A Timestamp Option for the Dynamic Host Configuration Protocol (DHCP) ⓘ |
| hasDOI | 10.17487/RFC4833 ⓘ |
| hasRFCNumber | 4833 ⓘ |
| intendedAudience |
network administrators
ⓘ
protocol implementers ⓘ |
| isPartOfSeries |
RFCs
ⓘ
surface form:
Request for Comments (RFC)
|
| language | English ⓘ |
| obsoletedBy | RFC 8536 ⓘ |
| obsoletes |
RFC 2132
ⓘ
surface form:
RFC 2132 (in part, for time offset options)
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatesTo |
daylight saving time configuration
ⓘ
time configuration in IP networks ⓘ time zone configuration ⓘ |
| relation | is related to timekeeping and timezone configuration in IP networks ⓘ |
| status | Proposed Standard ⓘ |
| stdStatus | Standards Track ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | RFC 4833 self-link ⓘ |
| topic |
network time distribution
ⓘ
time configuration via DHCP ⓘ |
| updates |
RFC 2131
ⓘ
RFC 2132 ⓘ |
| workingGroup |
DHCP
ⓘ
surface form:
Dynamic Host Configuration (dhc)
|
| yearPublished | 2007 ⓘ |
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 4833 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.