With the RFC Series mission outlined above, this document describes a framework for supporting
the operational implementation of the RFC Series,
public process and definition documents,
for which there are
clear responsibilities and mechanisms for update and change.
Generally speaking, the RFC Editor is responsible for the operational implementation of the RFC Series. As outlined in Section 3.3
, the IETF Executive Director provides the oversight of this operational role.
The process and definition documents are detailed below, including responsibility for the individual process documents (maintenance and update). The RFC Editor works with the appropriate community to ensure that the process documents reflect current requirements. The IAB is charged with the role of verifying that appropriate community input has been sought and that any changes appropriately account for community requirements.
There are three categories of activity, and a fourth category of series-wide rules and guidelines, described for implementing the RFC Series to support its mission:
Approval of documents.
Editing, processing, and publication of documents.
Archiving and indexing the documents and making them accessible.
Series rules and guidelines.
The RFC Series mission implicitly requires that documents be reviewed and approved for acceptance into the series.
describes the different streams of documents that are put to the RFC Editor for publication as RFCs today. While there may be general policies for approval of documents as RFCs (to ensure the coherence of the RFC Series), there are also policies defined for the approval of documents in each stream. Generally speaking, there is a different approving body for each stream. The current definitions are catalogued in Section 5.1
Each stream has its own documented approval process. The RFC Editor is responsible for the approval of documents in one of the streams (Independent Submission stream, see Section 5.1.4
) and works with the other approving bodies to ensure smooth passage of approved documents into the next phases, ultimately to publication and archiving as an RFC.
From time to time, it may be necessary to change the approval processes for any given stream, or even add or remove streams. This may occur when the RFC Editor, the IAB, the body responsible for a given stream of documents, or the community determines that there are issues to be resolved in general for RFC approval or for per-stream approval processes.
In this framework, the general approach is that the IAB will work with the RFC Editor and other parties to get community input, and it will verify that any changes appropriately account for community requirements.
The existing documents describing the approval processes for each stream are detailed in Section 5.1
Producing and maintaining a coherent, well-edited document series requires specialized skills and subject matter expertise. This is the domain of the RFC Editor. Nevertheless, the community served by the RFC Series and the communities served by the individual streams of RFCs have requirements that help define the nature of the series.
General and stream-specific requirements for the RFC Series are documented in community-approved documents (catalogued in Section 5.2
Any specific interfaces, numbers, or concrete values required to make the requirements operational are the subject of agreements between the IASA and the RFC Editor (e.g., contracts, statements of work, service level agreements, etc).
The RFC Editor is responsible for ensuring that editing, processing, and publication of RFCs are carried out in a way that is consistent with the requirements laid out in the appropriate documents. The RFC Editor works with the IASA to provide regular reporting and feedback on these operations.
From time to time, it may be necessary to change the requirements for any given stream, or the RFC Series in general. This may occur when the RFC Editor, the IAB, the approval body for a given stream of documents, or the community determines that there are issues to be resolved in general for RFCs or for per-stream requirements.
In this model, the general approach is that the IAB will work with the RFC Editor to get community input, and it will approve changes by validating appropriate consideration of community requirements.
Documents describing existing requirements for the streams are detailed in Section 5.2
The activities of archiving, indexing, and making accessible the RFC Series can be informed by specific subject matter expertise in general document series editing. It is also important that they are informed by requirements from the whole community. As long as the RFC Series is to remain coherent, there should be uniform archiving and indexing of RFCs across all streams and a common method of accessing the resulting documents.
In principle, there should be a community consensus document describing the archiving, indexing, and accessibility requirements for the RFC Series. In practice, we continue with the archive as built by the capable RFC Editors since the series' inception.
Any specific concrete requirements for the archive, index, and accessibility operations are the subject of agreements between the IASA and the RFC Editor (e.g., contracts, statements of work, service level agreements, etc).
The RFC Editor is responsible for ensuring that the RFC archive and index are maintained appropriately and that the resulting documents are made available to anybody wishing to access them via the Internet. The RFC Editor works with the IASA for regular reporting and feedback.
Should there be a community move to propose changes to the requirements for the RFC archive and index or accessibility, the IAB will work with the RFC Editor to get community input, and it will approve changes by validating appropriate consideration of community requirements.
There are no applicable process documents.
The RFC Series style and content can be shaped by subject matter expertise in document series editing. They are also informed by requirements by the using community. As long as the RFC Series is to remain coherent, there should be uniform style and content for RFCs across all streams. This includes, but is not limited to, acceptable language, use of references, and copyright rules.
In principle, there should be a community consensus document (or set of documents) describing the content requirements for the RFC Series. In practice, some do exist, though some need reviewing and more may be needed over time.
The RFC Editor is responsible for ensuring that the RFC Series guidelines are upheld within the RFC Series.
When additions or changes are needed to series-wide definitions, the IAB will work with the RFC Editor and stream stakeholders to get community input and review. The IAB will approve changes by validating appropriate consideration of community requirements.
Existing series-wide rules and guidelines documents include: