RFC 8728
E184124
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8728 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631828 — 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 8728 Context triple: [RFC Editor, documentedIn, RFC 8728]
-
A.
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.
-
B.
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.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
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 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
- 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 8728 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
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 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
IETF document
ⓘ
Request for Comments ⓘ |
| addresses |
community input into RFC Series management
ⓘ
responsibilities of the RFC Series Editor ⓘ responsibilities of the RFC Series Oversight Committee ⓘ role of the RFC Editor in the publication process ⓘ |
| area | General ⓘ |
| bcpNumber | 125 ⓘ |
| category | BCP ⓘ |
| countryOfPublication |
United States of America
ⓘ
surface form:
United States
|
| defines |
RFC Series Editor role
ⓘ
RFC Series Oversight Committee ⓘ RFC Series Working Group ⓘ RSE ⓘ RSOC ⓘ community representation in the RFC Series ⓘ |
| focusesOn |
RFC Editor function
ⓘ
RFC Editor model ⓘ governance of the RFC Series ⓘ |
| format |
HTML
ⓘ
PDF ⓘ text ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc8728 ⓘ |
| language | English ⓘ |
| medium | online publication ⓘ |
| obsoletes | RFC 6635 ⓘ |
| partOf |
RFCs
ⓘ
surface form:
RFC Series
|
| publishedBy |
Internet Engineering Task Force
ⓘ
RFC Editor ⓘ |
| publisher | RFC Editor ⓘ |
| rfcNumber | 8728 ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| standardizationBody |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Internet standards process
ⓘ
RFC publication process ⓘ technical documentation governance ⓘ |
| title |
RFC Editor
ⓘ
surface form:
RFC Editor Model (Version 2) – Community Representation in the RFC Series and RFC Editor Function
|
| type | Best Current Practice document ⓘ |
| updates |
RFC 4844
ⓘ
RFC 5620 ⓘ |
| workingGroup | rfc-interest ⓘ |
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 8728 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.