RFC 8729
E250266
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8729 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T2258941 — 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 8729 Context triple: [IETF Stream, governedBy, RFC 8729]
-
A.
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.
-
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 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
-
D.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
E.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
- 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 8729 Target entity description: 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.
-
A.
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.
-
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 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
-
D.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
E.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF document
ⓘ
Request for Comments ⓘ |
| area |
Internet standards process
ⓘ
document publication process ⓘ |
| bcpNumber | 195 ⓘ |
| category | Best Current Practice ⓘ |
| defines |
principles for the RFC Series
ⓘ
procedures for the RFC Series ⓘ relationship between RFC Editor and streams ⓘ responsibilities of the IAB regarding the RFC Series ⓘ responsibilities of the RFC Production Center ⓘ responsibilities of the RFC Publisher ⓘ responsibilities of the RFC Series Advisory Group ⓘ responsibilities of the RFC Series Editor ⓘ role of the RFC Editor ⓘ |
| documentType | Best Current Practice RFC ⓘ |
| focusesOn |
IETF Stream of the RFC Series
ⓘ
linked to:
IETF Stream
|
| format |
PDF
ⓘ
text ⓘ |
| governs |
management of the RFC Series
ⓘ
publication of documents in the IETF Stream ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc8729 ⓘ |
| intendedAudience |
IETF community
ⓘ
RFC Editor function stakeholders ⓘ |
| isPartOfProcess | Internet standards publication process ⓘ |
| language | English ⓘ |
| obsoletes | RFC 4844 ⓘ |
| partOf |
RFC Series
ⓘ
linked to:
RFCs
|
| publishedBy | Internet Engineering Task Force ⓘ |
| publishedIn | February 2020 ⓘ |
| publisher | RFC Editor ⓘ |
| replacesPrinciplesFrom | RFC 4844 ⓘ |
| rfcNumber | 8729 ⓘ |
| series |
RFC
ⓘ
linked to:
RFCs
|
| specifies |
interaction between IETF Stream and RFC Editor
ⓘ
organizational structure of the RFC Editor function ⓘ principles for managing the RFC Series ⓘ procedures for publishing RFCs ⓘ |
| standardsBody |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| status | Best Current Practice ⓘ |
| stream | IETF Stream ⓘ |
| subject |
IETF document streams
ⓘ
linked to:
IETF Stream
RFC Editor function ⓘ RFC Series governance ⓘ
linked to:
RFC Series Working Group
|
| title |
The RFC Series and RFC Editor
ⓘ
linked to:
RFCs
|
| updates | RFC 6635 ⓘ |
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 8729 Description of subject: 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.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.