RFC 5741
E250267
RFC 5741 is an Internet Engineering Task Force (IETF) document that defines the structure, responsibilities, and processes governing the IETF document publication streams.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5741 canonical | 1 |
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF document
ⓘ
Request for Comments ⓘ |
| area | General ⓘ |
| BCPNumber | BCP 78 ⓘ |
| category | Best Current Practice ⓘ |
| concerns |
document headers
ⓘ
document metadata ⓘ document publication procedures ⓘ |
| defines |
RFC header fields for different streams
ⓘ
boilerplate text for RFCs ⓘ common boilerplate for IAB Stream RFCs ⓘ common boilerplate for IETF Stream RFCs ⓘ common boilerplate for IRTF Stream RFCs ⓘ common boilerplate for Independent Submission Stream RFCs ⓘ processes for RFC streams ⓘ relationship between RFC Editor and streams ⓘ responsibilities of RFC streams ⓘ structure of RFC streams ⓘ |
| format | text ⓘ |
| governs |
IAB
ⓘ
surface form:
IAB Stream
IETF Stream ⓘ IETF document publication streams ⓘ IRTF ⓘ
surface form:
IRTF Stream
Independent Submission Stream ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc5741 ⓘ |
| language | English ⓘ |
| obsoletes | RFC 4844 ⓘ |
| partOfSeries |
RFCs
ⓘ
surface form:
Request for Comments series
|
| publicationMonth | December ⓘ |
| publicationYear | 2010 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| RFCNumber | 5741 ⓘ |
| specifies |
how RFC status is indicated in headers
ⓘ
how stream is indicated in RFC headers ⓘ responsibilities of stream managers ⓘ rules for stream-specific boilerplates ⓘ rules for stream-specific headers ⓘ |
| standardsBody |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | Best Current Practice ⓘ |
| stream | IETF Stream ⓘ |
| title |
IETF Stream
ⓘ
surface form:
RFC Streams, Headers, and Boilerplates
|
| topic |
IETF document streams
ⓘ
RFC publication process ⓘ |
| updates | RFC 4844 ⓘ |
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 5741 Description of subject: RFC 5741 is an Internet Engineering Task Force (IETF) document that defines the structure, responsibilities, and processes governing the IETF document publication streams.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.