RFC 8536
E647025
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8536 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7186946 — 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 8536 Context triple: [RFC 4833, obsoletedBy, RFC 8536]
-
A.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
B.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
E.
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.
- 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 8536 Target entity description: RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
A.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
B.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
E.
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.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| abbreviation | TZif ⓘ |
| addresses |
backward compatibility with earlier TZif versions
ⓘ
robustness of time zone data parsing ⓘ security considerations for time zone data ⓘ |
| appliesTo |
Internet ecosystem
ⓘ
time zone conversion software ⓘ time zone databases ⓘ |
| category | Standards Track ⓘ |
| defines |
Time Zone Information Format
ⓘ
semantics of UTC offsets in TZif ⓘ semantics of daylight saving time flags in TZif ⓘ semantics of leap second corrections in TZif ⓘ semantics of transition times in TZif ⓘ |
| focusesOn |
time zone data format
ⓘ
time zone data handling ⓘ |
| goal |
to ensure consistent interpretation of time zone data across systems
ⓘ
to modernize the time zone information format ⓘ |
| intendedFor |
application developers using time zone data
ⓘ
implementers of time zone libraries ⓘ operating system vendors ⓘ |
| language | English ⓘ |
| obsoletes | RFC 8536 (Internet-Draft predecessors of TZif format) ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
IANA Time Zone Database
ⓘ
linked to:
IANA time zone database
POSIX time zone rules ⓘ |
| specifies |
TZif versioning scheme
ⓘ
file header structure for TZif ⓘ interoperability requirements for TZif readers ⓘ interoperability requirements for TZif writers ⓘ leap second records ⓘ local time type records ⓘ rules for future extensions of TZif ⓘ time transition data encoding ⓘ |
| standardizes | binary file format for time zone information ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
The Time Zone Information Format (TZif)
ⓘ
linked to:
IANA time zone database
|
| updates | time zone information format specification ⓘ |
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 8536 Description of subject: RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.