RFC 8789
E877063
RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8789 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10623789 — 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 8789 Context triple: [RFC 2026, obsoletedBy, RFC 8789]
-
A.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
B.
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.
-
C.
RFC 8179
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
-
D.
RFC 9589
RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
-
E.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
- 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 8789 Target entity description: RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
-
A.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
B.
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.
-
C.
RFC 8179
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
-
D.
RFC 9589
RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
-
E.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
- F. None of above. chosen
Statements (28)
| Predicate | Object |
|---|---|
| instanceOf |
Best Current Practice
ⓘ
IETF standards-track document ⓘ |
| category | Best Current Practice ⓘ |
| defines | refinements to Internet Standards Process ⓘ |
| focusesOn | IETF standards process evolution ⓘ |
| format |
PDF
NERFINISHED
ⓘ
text ⓘ |
| governs | process for Internet Standards ⓘ |
| governsBody |
IETF Internet Engineering Steering Group
NERFINISHED
ⓘ
IETF working groups NERFINISHED ⓘ |
| hasNumber | 8789 ⓘ |
| intendedAudience |
IETF participants
ⓘ
Internet standards developers ⓘ |
| language | English ⓘ |
| partOfSeries | Request for Comments NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
RFC Editor NERFINISHED ⓘ |
| publisherOrganization | IETF NERFINISHED ⓘ |
| refines | procedures in RFC 2026 ⓘ |
| relatesToProcess | Internet Standards Process GENERATED ⓘ |
| series | RFC NERFINISHED ⓘ |
| standardsTrackStatus | Standards Track ⓘ |
| status | Internet Standard Process document ⓘ |
| subject |
IETF procedures
ⓘ
Internet standards development ⓘ standardization process ⓘ |
| type | technical specification for process ⓘ |
| updatesDocument | RFC 2026 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 8789 Description of subject: RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.