| Internet-Draft | RFC Editor Model | January 2022 |
| Saint-Andre | Expires 17 July 2022 | [Page] |
This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposals. Second, policy implementation is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC).¶
This document obsoletes RFC 8728. This document updates RFC 7841, RFC 8729, and RFC 8730.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 17 July 2022.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Request for Comments (RFC) Series is the archival series dedicated to documenting Internet technical specifications, including general contributions from the Internet research and engineering community as well as standards documents. RFCs are available free of charge to anyone via the Internet. As described in [RFC8700], RFCs have been published continually since 1969. The overall framework for the RFC Series and the RFC Editor function is described in [RFC8729] and is updated by this document.¶
The processes and organizational models for publication of RFCs have changed significantly over the years. Most recently, in 2009 [RFC5620] defined the RFC Editor Model (Version 1) and in 2012 [RFC6635] defined the RFC Editor Model (Version 2), since modified slightly in 2020 by [RFC8728].¶
This document reflects experience gained with version 1 and version 2 of the Model, and therefore describes version 3 of the Model while remaining consistent with [RFC8729].¶
In 2020, following meetings led by the RFC Series Editor in 2019, the IAB formed an open program to conduct a community discussion and consensus process for the further evolution of the RFC Editor model. Under the auspices of this program, the community considered changes that would increase transparency and community input regarding the definition of policies for the RFC Series as a whole, while at the same time ensuring the continuity of the RFC Series, maintaining RFC quality, maintaining timely processing, ensuring document accessibility, and clarifying lines of authority and responsibility.¶
More specifically, in order to ensure sustainable maintenance and support of the RFC Series based on the principles of expert implementation, clear management and direction, and appropriate community input [RFC8729], this document divides the responsibilities for the RFC Series into two high-level tasks:¶
In this model, RFCs are produced and approved by multiple document streams. The stream approving body [RFC8729] for each stream is responsible for the content of that stream. The RFC Editor function is responsible for the packaging and distribution of all RFCs; specifically, RFCs from all of the streams are edited and published by the Production Center.¶
The four streams that now exist are described in [RFC8729]. This document adds a fifth stream, the Editorial Stream.¶
This document obsoletes [RFC8728] by defining version 3 of the RFC Editor Model. This document updates [RFC7841] by defining boilerplate text for the Editorial Stream. This document updates [RFC8729] by replacing the RFC Editor role with the RSWG, RSAB, and RSCE. This document updates [RFC8730] by removing the dependency on certain policies specified by the IAB and RSE. More detailed information about changes from version 2 of the Model can be found under under Section 8.¶
Version 2 of the RFC Editor Model [RFC8728] defined a structure consisting of the RFC Series Editor, the RFC Production Center, and the RFC Publisher, with oversight provided by the RFC Series Oversight Committee (RSOC) on behalf of the Internet Architecture Board (IAB).¶
By contrast, version 3 of the RFC Editor Model, specified here, provides a more consensus-oriented framework (similar in some respects to the structure of technical work within the IETF) that retains roles for specialized expertise in document editing and publication.¶
Policy definition happens within the RFC Series Working Group (RSWG), which produces policy proposals that are subject to approval by the RFC Series Approval Board (RSAB), after which such policies are formally established through publication in the Editorial Stream within the RFC Series. The RSWG is an open working group (as described in Section 3.1.1) that seeks input and participation through a public process from a wide range of individuals who have an interest in the RFC Series. The RSAB consists of appointed members who represent the various RFC streams [RFC8728] as well as an expert in technical publishing, the RFC Series Consulting Editor (RSCE).¶
Policy implementation is performed by the RFC Production Center (RPC), as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC).¶
In short:¶
This model is designed to ensure public processes and policy documents, clear responsibilities and mechanisms for updates and changes to policies governing the RFC Series as a whole, and effective operational implementation of the RFC Series, thus meeting the requirements specified in Section 4 of [RFC8729].¶
The remainder of this document describes the model in greater detail.¶
Policies governing the RFC Series as a whole are defined via open and public discussion through proposals that are adopted by and discussed within the RFC Series Working Group (RSWG), that pass a last call for comments in the working group and broader community, and that are then approved by the RFC Series Approval Board (RSAB).¶
Policies under the purview of the RSWG and RSAB might include, but are not limited to, document formats, processes for publication and dissemination of RFCs, and overall management of the RFC Series.¶
The RFC Series Working Group (RSWG) is the primary venue in which members of the community collaborate regarding the policies that govern the RFC Series.¶
All interested individuals are welcome to participate in the RSWG (subject to anti-harassment policies as described under Section 3.2.5). This includes participants in the IETF and IRTF, IAB and IESG members, individuals who use RFCs in procurement decisions, authors of RFCs and Internet-Drafts, developers of tools used to author RFCs, scholarly researchers, and so on. The IETF LLC Board members, staff, contractors, and the IETF Executive Director are invited to participate as community members in the RSWG to the extent permitted by any relevant IETF LLC policies. Members of the RSAB are also expected to participate actively.¶
The RSWG shall have two chairs, one appointed by the IESG and the other appointed by the IAB. When the RSWG is formed, the chair appointed by the IESG shall serve for a term of one (1) year and the chair appointed by the IAB shall serve for a term of two (2) years; thereafter, chairs shall serve for a term of two (2) years, with no term limits on renewal. The IESG and IAB shall determine their own processes for making these appointments. Community members who have concerns about the performance of an RSWG chair should direct their feedback to appointing body. The IESG and IAB shall have the power to remove their appointed chairs at their discretion at any time, and to name a replacement who shall serve the remainder of the original chair's term.¶
It is the responsibility of the chairs to encourage rough consensus within the RSWG and to follow that consensus in their decision making, for instance regarding acceptance of new proposals and advancement of proposals to the RSAB.¶
The intent is that the RSWG shall operate in a way similar to working groups in the IETF and research groups in the IRTF. Therefore, all RSWG meetings and discussion venues shall be open to all interested individuals, and all RSWG contributions shall be subject to intellectual property policies, which must be consistent with those of the IETF as specified in [BCP78] and [BCP79].¶
The RSWG shall operate by rough consensus, a mode of operation informally described in [RFC2418].¶
When the RSWG is formed, all discussions shall take place on an open email discussion list, which shall be publicly archived.¶
The RSWG is empowered to hold in-person or online-only meetings, which should be announced with sufficient notice to enable broad participation; the IESG Guidance on Face-to-Face and Virtual Interim Meetings provides a reasonable baseline. In-person meetings should include provision for effective online participation for those unable to to attend in person.¶
The RSWG may decide by rough consensus to use additional tooling (e.g., GitHub as specified in [RFC8874]), forms of communication, and working methods (e.g., design teams) as long as they are consistent with [RFC2418].¶
Absent specific guidance in this document regarding the operation of the RSWG, the general guidance provided in Section 6 of [RFC2418] should be considered appropriate.¶
The RFC Series Approval Board (RSAB) shall act as the approving body for proposals generated within the RSWG. The only policy-making role of the RSAB is to review policy proposals generated by the RSWG; it shall have no independent authority to formulate policy on its own. It is expected that the RSAB will respect the rough consensus of the RSWG wherever possible, without ceding its responsibility to provide appropriate review of RSWG proposals.¶
The RSAB consists primarily of certain voting members. As specified herein, the RSAB also includes certain non-voting members.¶
The voting members of the RSAB are as follows:¶
If and when a new stream is created, the document that creates the stream shall specify if a voting member representing that stream shall also be added to the RSAB, along with any rules and processes related to that representative (e.g., whether the representative is a member of the body responsible for the stream or an appointed delegate thereof).¶
To ensure the smooth operation of the RFC Series, the RSAB shall include the following non-voting, ex-officio members:¶
In addition to the foregoing, the RSAB may at its discretion include other non-voting members, whether ex-officio members or liaisons from groups or organizations with which the RSAB deems it necessary to formally collaborate or coordinate.¶
The appointing bodies, i.e., the stream approving bodies (IESG, IAB, IRTF chair, ISE), shall determine their own processes for appointing RSAB members (note that processes related to the RSCE are described under Section 5). Each appointing body shall have the power to remove its appointed RSAB member at its discretion at any time. Appointing bodies should ensure that voting members are seated at all times and should fill any vacancies with all due speed, if necessary on a temporary basis.¶
In the case that the IRTF chair or ISE is incapacitated or otherwise unable to appoint another person to serve as a delegate, the IAB (as the appointing body for the IRTF chair and ISE respectively) shall act as the temporary appointing body for those streams and shall appoint a temporary member of the RSAB until the IAB has appointed an IRTF chair or ISE, who can then act as an RSAB member or appoint a delegate through normal processes.¶
In the case of vacancies by voting members, the RSAB shall operate as follows:¶
The RSAB shall annually choose a chair from among its members using a method of its choosing. If the chair position is vacated during the chair's term, the RSAB chooses a new chair from among its members.¶
The RSAB is expected to operate via an email discussion list, in-person meetings, teleconferencing systems, and any additional tooling it deems necessary.¶
The RSAB shall keep a public record of its proceedings, including minutes of all meetings and a record of all decisions. The primary email discussion list used by the RSAB shall be publicly archived, although topics that require confidentiality (e.g., personnel matters) may be elided from such archives or discussed in private. Similarly, meeting minutes may exclude detailed information about topics discussed under executive session, but should note that such topics were discussed.¶
The RSAB shall announce plans and agendas for their meetings on the RFC Editor website and by email to the RSWG at least a week before such meetings. The meetings shall be open for public attendance and the RSAB may consider allowing open participation. If the RSAB needs to discuss a confidential matter in executive session, that part of the meeting shall be private to the RSAB, but must be noted on the agenda, and must be documented in the minutes with as much detail as confidentiality requirements permit.¶
The intent is to provide an open forum by which policies related to the RFC Series are defined and evolved. The general expectation is that all interested parties will participate in the RSWG, and that only under extreme circumstances should RSAB members need to hold "CONCERN" positions (as described under Section 3.2.2).¶
Because policy issues can be difficult and contentious, RSWG participants and RSAB members are strongly encouraged to work together in a spirit of good faith and mutual understanding to achieve rough consensus (see [RFC2418]). In particular, RSWG members are encouraged to take RSAB concerns seriously, and RSAB members are encouraged to clearly express their concerns early in the process and to be responsive to the community. All parties are encouraged to respect the value of each stream and the long-term health and viability of the RFC Series.¶
This process is intended to be one of continuous consultation. RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis, so that when the time comes to consider the approval of a proposal, there should be no surprises. Appointing bodies are expected to establish whatever processes they deem appropriate to facilitate this goal.¶
The following process shall be used to formulate or modify processes related to the RFC Series:¶
Within a reasonable period of time, the RSAB will then poll among its members regarding the proposal. Positions may be as follows:¶
Any RSAB member holding a "CONCERN" position must explain their concern to the community in detail. The explanation might or might not be actionable.¶
There are three reasons why an RSAB member may file a position of CONCERN:¶
Because RSAB members are expected to participate in the discussions within the RSWG and to raise any concerns and issues during those discussions, most CONCERN positions should not come as a surprise to the RSWG. Notwithstanding, late CONCERN positions are always possible if issues are identified during RSAB review or the community call for comment.¶
The RSAB is responsible for initiating and managing community calls for comment on proposals that have gained consensus within the RSWG. The RSAB should actively seek a wide range of input. The RSAB seeks such input by, at a minimum, sending a notice to the rfc-interest mailing list or to its successor or future equivalent. RSAB members should also send a notice to the communities they directly represent (e.g., the IETF and IRTF). Notices are also to be made available and archived on the RFC Editor website. In addition, other communication channels can be established for notices (e.g., via an RSS feed or by posting to social media venues).¶
In cases where a proposal has the potential to significantly modify policies of long standing or historical characteristics of the Series as described under Section 7, the RSAB should take extra care to reach out to even broader communities that make use of RFCs, such as scholarly researchers, procurement managers, and standards development organizations. The RSAB should work with the stream representatives and the IETF LLC to identify and establish contacts in such communities, assisted in particular by the RSCE.¶
The RSAB should maintain a public list of communities that are contacted during calls for comment.¶
A notice of a community call for comment contains the following:¶
A comment period will last not less than two weeks and should be longer if wide outreach is required. Comments will be publicly archived on the RFC Editor website.¶
The RSAB is responsible for considering comments received during a community call for comment. If RSAB members conclude that such comments raise important issues that need to be addressed, they should do so by discussing those issues within the RSWG or (if the issues meet the criteria specified under Step 9 of Section 3.2.2) lodging a position of "CONCERN" during RSAB balloting.¶
Appeals of RSWG chair decisions shall be made to the RSAB. Decisions of the RSWG chairs can be appealed only on grounds of failure to follow the correct process. Appeals should be made within thirty (30) days of any action, or in the case of failure to act, of notice having been given to the RSWG chairs. The RSAB will then decide if the process was followed and will direct the RSWG chairs as to what procedural actions are required.¶
Decisions of the RSAB can be appealed on grounds of failure to follow the correct process. Where the RSAB makes a decision in order to resolve a disagreement between authors and the RPC (as described under Section 4.4), appeals can be filed on the basis that the RSAB misinterpreted an approved policy. Aside from these two cases, disagreements about the conduct of the RSAB are not subject to appeal. Appeals of RSAB decisions shall be made to the IAB and should be made within thirty (30) days of public notice of the relevant RSAB decision (typically, when minutes are posted). The IAB shall decide whether a process failure occurred and what if any corrective action should take place.¶
The IETF anti-harassment policy also applies to the RSWG and RSAB, which strive to create and maintain an environment in which people of many different backgrounds are treated with dignity, decency, and respect. Participants are expected to behave according to professional standards and to demonstrate appropriate workplace behavior. For further information about these policies, see [RFC7154], [RFC7776], and [RFC8716].¶
As part of the RFC Style Guide (see [RFC7322] and [STYLEGUIDE]), new or modified RFC boilerplates (see [RFC7841]) considered under version 3 of the RFC Editor Model must be approved by the following parties, each of which has a separate area of responsibility with respect to boilerplates:¶
Publication of RFCs is handled by the RFC Production Center (RPC).¶
A few general considerations apply:¶
All matters of budget, timetable, and impact on its performance targets, are between the RPC and IETF LLC.¶
The RPC shall regularly provide reports to the IETF LLC, RSAB, RSWG, and broader community regarding its activities and any key risks or issues affecting it.¶
In the event that the RPC is required to make a decision without consultation that would normally deserve consultation, or makes a decision against the advice of the RSAB, the RPC must notify the RSAB.¶
This document does not specify the exact relationship between the IETF LLC and the RPC; for example, the work of the RPC could be performed by a separate corporate entity under contract to the IETF LLC, it could be performed by employees of the IETF LLC, or the IETF LLC could engage with independent contractors for some or all aspects of such work. The exact relationship is a matter for the IETF LLC to determine.¶
The IETF LLC is responsible for the method of and management of the engagement of the RPC. Therefore, the IETF LLC has authority over negotiating performance targets for the RPC and also has responsibility for ensuring that those targets are met. Such performance targets are set based on the RPC's publication load and additional efforts required by policies specified in the Editorial Stream, in legacy RFCs which apply to the RPC and which have not yet been superseded by Editorial Stream RFCs, and in the requisite contracts. The IETF LLC may consult with the community regarding these targets. The IETF LLC is empowered to appoint a manager or to convene a committee to complete these activities.¶
If individuals or groups within the community have concerns about the performance of the RPC, they can request that the matter be investigated by the IETF LLC board, the IETF LLC Executive Director, or a point of contact designated by the IETF LLC Board. Even if the IETF LLC opts to delegate this activity, concerns should be raised with the IETF LLC. The IETF LLC is ultimately answerable to the community via the mechanisms outlined in its charter.¶
In the absence of a high-level policy documented in an RFC, or to specify the detail of its implementation, the RPC can document working practices regarding the editorial preparation and final publication and dissemination of RFCs. Examples include:¶
The core responsibility of the RPC is the implementation of RFC Series policies through publication of RFCs (including the dimensions of document quality, timeliness of production, and accessibility of results), while taking into account issues raised by the community through the RSWG and by the stream approving bodies. More specifically, the RPC's responsibilities at the time of writing include the following:¶
Publishing RFCs, which includes:¶
During the process of editorial preparation and publication, disagreements can arise between the authors of an RFC-to-be and the RPC. Where an existing policy clearly applies, typically such disagreements are handled in a straightforward manner through direct consultation between the authors and the RPC, sometimes in collaboration with other individuals such as a document shepherd, IETF working group chair, IRTF research group chair, or IETF Area Director.¶
However, if it is unclear whether an existing policy applies, or if it is unclear how to interprete an existing policy, the parties may need to consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or stream approving bodies) to help achieve a resolution. The following points are intended to provide more specific guidance.¶
From time to time, individuals or organizations external to the IETF and the broader RFC Series community may have questions about the RFC Series. Such inquiries should be directed to the rfc-editor@rfc-editor.org email alias or to its successor or future equivalent and then handled by the appropriate bodies (e.g., RSAB, RPC) or individuals (e.g., RSWG chairs, RSCE).¶
The exact implementation of the administrative and contractual activities described here are a responsibility of the IETF LLC. This section provides general guidance regarding several aspects of such activities.¶
Vendor selection is done in cooperation with the streams and under the final authority of the IETF LLC.¶
The IETF LLC develops the work definition (the Statement of Work) for the RPC and manages the vendor selection process. The work definition is created within the IETF LLC budget and takes into account the RPC responsibilities (as described under Section 4.3), the needs of the streams, and community input.¶
The process to select and contract for an RFC Production Center and other RFC-related services is as follows:¶
Most expenses discussed in this document are not new expenses. They have been and remain part of the IETF LLC budget.¶
The RFC Series portion of the IETF LLC budget shall include funding to support the RSCE, the RFC Production Center, and the Independent Stream.¶
The IETF LLC has the responsibility to approve the total RFC Editor budget (and the authority to deny it). All relevant parties must work within the IETF LLC budgetary process.¶
The RFC Series Consulting Editor (RSCE) is a senior technical publishing professional who will apply their deep knowledge of technical publishing processes to the RFC Series.¶
The primary responsibilities of the RSCE are as follows:¶
Matters on which the RSCE might provide guidance could include the following (see also Section 4 of [RFC8729]):¶
The IETF LLC is responsible for the method of and management of the engagement of the RSCE, including selection, evaluation, and the timely filling of any vacancy. Therefore, whether the RSCE role is structured as a contractual or employee relationship is a matter for the IETF LLC to determine.¶
Responsibility for making a recommendation to the IETF LLC regarding the RSCE role will lie with a selection committee. The IETF LLC should propose an initial slate of members for this committee, making sure to include community members with diverse perspectives, and consult with the stream representatives regarding the final membership of the committee. In making its recommendation for the role of RSCE, the selection committee will take into account the definition of the role as well as any other information that the committee deems necessary or helpful in making its decision. The IETF LLC is responsible for contracting or employment of the RSCE.¶
Periodically, the IETF LLC will evaluate the performance of the RSCE, including a call for confidential input from the community. The IETF LLC will produce a draft evaluation of the RSCE's performance for review by RSAB members other than the RSCE, who will provide feedback to the IETF LLC.¶
In the case that the currently appointed RSCE is expected to be unavailable for an extended period, the IETF LLC may appoint a Temporary RSCE through whatever recruitment process it considers appropriate. A Temporary RSCE acts as the RSCE in all aspects during their term of appointment.¶
The RSCE is expected to avoid even the appearance of conflict of interest or judgment in performing their role. To ensure this, the RSCE will be subject to a conflict of interest policy established by the IETF LLC.¶
The RPC service provider may contract services from the RSCE service
provider, and vice versa, including for services provided to the IETF
LLC. All contracts between the two must be disclosed to the IETF LLC.
Where those services are related to services provided to the IETF LLC,
IETF LLC policies shall apply, including publication of relevant parts
of the contract.¶
This document creates the Editorial Stream as separate space for publication of policies, procedures, guidelines, rules, and related information regarding the RFC Series as a whole.¶
The Editorial Stream shall be used only to specify and update policies, procedures, guidelines, rules, and related information regarding the RFC Series as a whole; no other use of the Editorial Stream is authorized by this memo and no other streams are so authorized. This policy may be changed only by agreement of the IAB, IESG, and IETF LLC.¶
All documents produced by the RSWG and approved by the RSAB shall be published as RFCs in the Editorial Stream with a status of Informational. (Note that the Editorial Stream is not authorized to publish RFCs that are Standards Track or Best Current Practice, since such RFCs are reserved to the IETF Stream [RFC8729].)¶
The requirements and process for creating any additional RFC streams are outside the scope of this document.¶
The IAB requests that the IETF Trust and its Trustees assist in meeting the goals and procedures set forth in this document.¶
The Trustees are requested to publicly confirm their willingness and ability to accept responsibility for the Intellectual Property Rights for the Editorial Stream.¶
Specifically, the Trustees are asked to develop the necessary boilerplate to enable the suitable marking of documents so that the IETF Trust receives the rights as specified in [BCP78]. These procedures need to also allow authors to indicate either no rights to make derivative works, or preferentially, the right to make unlimited derivative works from the documents. It is left to the Trust to specify exactly how this shall be clearly indicated in each document.¶
As specified above, contributors of documents for the Editorial Stream are expected to use the IETF Internet-Draft process, complying therein with the rules specified in the latest version of [BCP9]. This includes the disclosure of Patent and Trademark issues that are known, or can be reasonably expected to be known, to the contributor.¶
Disclosure of license terms for patents is also requested, as
specified in the most recent version of [BCP79]. The Editorial
Stream has chosen to use the IETF's IPR disclosure mechanism,
https://www.ietf.org/ipr/, for this purpose. The IAB would prefer that
the most liberal terms possible be made available for Editorial Stream
documents. Terms that do not require fees or licensing are preferable.
Non-discriminatory terms are strongly preferred over those that
discriminate among users. However, although disclosure is required
and the RSWG and the RSAB may consider disclosures and terms in making
a decision as to whether to submit a document for publication, there
are no specific requirements on the licensing terms for intellectual
property related to Editorial Stream publication.¶
This document specifies the following text for the "Status of This Memo" section of RFCs published in the Editorial Stream. Any changes to this boilerplate must be made through the RFC Series Policy Definition process specified in this document.¶
Because all Editorial Stream RFCs have a status of Informational, the first paragraph of the "Status of This Memo" section shall be as specified in Appendix A.2.1 of [RFC7841].¶
The second paragraph of the "Status of This Memo" section shall be as follows:¶
This document is a product of the RFC Series Policy Definition process. It represents the consensus of the RFC Series Working Group approved by the RFC Series Approval Board. Such documents are not candidates for any level of Internet Standard; see Section 2 of RFC 7841.¶
The third paragraph of the "Status of This Memo" section shall be as specified in Section 3.5 of [RFC7841].¶
This section lists some of the properties that have been historically regarded as important to the RFC Series. Proposals that affect these properties are possible within the processes defined in this document. As described under Section 3.2.2 and Section 3.2.3, proposals that might have a detrimental effect on these properties should receive heightened scrutiny during RSWG discussion and RSAB review. The purpose of this scrutiny is to ensure that all changes are deliberate and that the consequences of a proposal, as far as they can be identified, have been carefully considered.¶
Documents in the RFC Series have been available for many decades, with no restrictions on access or distribution.¶
RFC Series documents have been published in a format that was intended to be as accessible as possible to those with special needs, e.g., for those with impaired sight.¶
All existing RFC Series documents have been published in English. However, since the beginning of the RFC series, documents have been published under terms that explicitly allow translation into languages other than English without asking for permission.¶
The RFC series has included many types of documents including standards for the Internet, procedural and informational documents, thought experiments, speculative ideas, research papers, histories, humor, and even eulogies.¶
Several responsibilities previously assigned to the "RFC Editor" or, more precisely, the "RFC Editor function" are now performed by the RSWG, RSAB, RPC, and IETF LLC (alone or in combination). These include various aspects of strategic leadership (Section 2.1.1 of [RFC8728]), representation of the RFC Series (Section 2.1.2 of [RFC8728]), development of RFC production and publication (Section 2.1.3 of [RFC8728]), development of the RFC Series (Section 2.1.4 of [RFC8728]), operational oversight (Section 3.3 of [RFC8729]), policy oversight (Section 3.4 of [RFC8729]), the editing, processing, and publication of documents (Section 4.2 of [RFC8729]), and development and maintenance of Series-wide guidelines and rules (Section 4.4 of [RFC8729]). Among other things this changes the dependency on the RSE included in Section 2.2 of [RFC8730] with regard to "coordinating work and conforming to general RFC Series policies as specified by the IAB and RSE." In addition, various details regarding these responsibilities have been modified to accord with the new framework defined in this document.¶
Implied by the changes outlined in the previous section, the responsibilities of the RFC Series Editor (RSE) as a person or role (contrasted with the overall "RFC Editor function") are now split or shared among the RSWG, RSAB, RPC, and IETF LLC (alone or in combination). More specifically, the responsibilities of the RFC Series Consulting Editor (RSCE) under version 3 of the RFC Editor Model differ in many ways from the responsibilities of the RFC Series Editor under version 2 of the Model. In general, references in existing documents to the RSE can be taken as referring to the "RFC Editor function" as described herein, but should not be taken as referring to the RSCE.¶
In practice the RFC Production Center (RPC) and RFC Publisher roles have been performed by the same entity and this practice is expected to continue; therefore this document dispenses with the distinction between these roles and refers only to the RPC.¶
Under earlier versions of the RFC Editor Model, the IAB was responsible for oversight of the RFC Series and acted as a body for final conflict resolution regarding the Series. The IAB's authority in these matters is described in the IAB's charter ([RFC2850] as updated by [I-D.draft-carpenter-rfced-iab-charter]). Under version 2 of the Model, the IAB delegated some of its authority to the RFC Series Oversight Committee (see Section 8.5). Under version 3 of the Model, authority for policy definition resides with the RSWG as an independent venue for work by members of the community (with approval of policy proposals as the responsibility of the RSAB, representing the streams and including the RSCE), whereas authority for policy implementation resides with the IETF LLC.¶
In practice, the relationships and lines of authority and responsibility between the IAB, RSOC, and RSE have proved unwieldy and somewhat opaque. To overcome some of these issues, this document dispenses with the RSOC. References to the RSOC in documents such as [RFC8730] are obsolete because this document disbands the RSOC.¶
Version 1 of the RFC Editor Model [RFC5620] specified the existence of the RFC Series Advisory Group (RSAG), which was no longer specified in version 2 of the Model. For the avoidance of doubt, this document affirms that the RSAG has been disbanded. (The RSAG is not to be confused with the RFC Series Approval Board (RSAB), which this document establishes.)¶
This document creates the Editorial Stream in addition to the streams already described in [RFC8729].¶
Updates, amendments, and refinements to this document can be produced using the process documented herein, but shall be operative only after (a) obtaining the agreement of the IAB and the IESG, and (b) ensuring that the IETF LLC has no objections regarding its ability to implement any proposed changes.¶
The same security considerations as those in [RFC8729] apply. The processes for the publication of documents must prevent the introduction of unapproved changes. Since the RFC Editor maintains the index of publications, sufficient security must be in place to prevent these published documents from being changed by external parties. The archive of RFC documents, any source documents needed to recreate the RFC documents, and any associated original documents (such as lists of errata, tools, and, for some early items, originals that are not machine-readable) need to be secured against data storage failure.¶
The IETF LLC should take these security considerations into account during the implementation and enforcement of any relevant contracts.¶
This document places responsibility for coordination of registry value assignments with the RPC. The IETF LLC facilitates management of the relationship between the RPC and IANA.¶
This document does not create a new registry nor does it register any values in existing registries, and no IANA action is required.¶
Portions of this document were borrowed from [RFC5620], [RFC6635], [RFC8728], [RFC8729], the Frequently Asked Questions of the IETF Trust, and earlier proposals submitted within the IAB's RFC Editor Future Development Program by Martin Thomson, Brian Carpenter, and Michael StJohns. Thanks to Eliot Lear and Brian Rosen in their role as chairs of the Program for their leadership and assistance. Thanks also for feedback and proposed text to Jari Arkko, Sarah Banks, Carsten Bormann, Scott Bradner, Nevil Brownlee, Ben Campbell, Jay Daley, Martin Duerst (note: replace "ue" with U+00FC before publication), Lars Eggert, Adrian Farrel, Stephen Farrell, Sandy Ginoza, Bron Gondwana, Joel Halpern, Wes Hardaker, Bob Hinden, Russ Housley, Christian Huitema, Ole Jacobsen, John Klensin, Mirja Kuehlewind, Ted Lemon, John Levine, Lucy Lynch, Andrew Malis, Larry Masinter, S. Moonesamy, Mark Nottingham, Tommy Pauly, Colin Perkins, Julian Reschke, Eric Rescorla, Adam Roach, Alice Russo, Doug Royer, Rich Salz, Tim Wicinski, and Nico Williams.¶