]> Updates to RFC Editor Model (Version 3) ICANN
paul.hoffman@icann.org
Internet-Draft RFC 9280 specifies version 3 of the RFC Editor Model. Since its publication, lessons have been learned about implementing this model. This document lists some of those lessons learned and updates RFC 9280 based on that experience. There is a repository for this draft at https://github.com/paulehoffman/9280-updates.
Introduction contained significant changes to the publication model for RFCs. Those changes created new structures and new processes for the publication of RFCs. As these structures and processes have been exercised, the community has found places where they might be improved. In addition, gaps in some of the processes have been found. This document updates based on these findings.
Updates from "RFC Formats and Versions" , "RFC Formats and Versions", updated RFC 9280.
RFCs May Be Reissued Section 7.6 of currently says:
  • Once published, RFC Series documents are not changed.
That sentence was replaced with:
  • Once published, RFCs may be reissued, but the semantic content of publication versions shall be preserved to the greatest extent possible.
Consistency Policy A new policy that would exist in Section 7 of was added:
  • 7.8. Consistency RFCs are copyedited, formatted, and then published. They may be reissued to maintain a consistent presentation.
Purview of the RSWG and RSAB Section 3 of currently says:
  • 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 following is added immediately following that seentence:
  • Such policies will not include detailed technical specifications, for example specific details of text or graphical formats or XML grammar. Such matters will be decided and documented by the RPC along with its other working practices, as discussed in section 4.2 of , with community consultation as for other tools and services supported by IETF LLC ."
Processing Drafts from the RSWG %% RSAB role in running the full-community last call, specifically deciding when it is finished and what the RSWG Chairs should do after that %%
Processes that Affect Internet Draft Processing before RFC Submission %% Where 7991 vocabulary that is draft-specific is defined %% %% What rules there are for draft format going into the RPC, if any %% %% Probably not for this document: Who specifies what the rules for draft submission are (currently the IESG) %%
Security Considerations There are no security considerations for the changes listed in this document.
IANA Considerations This document contains no actions for IANA.
Structure of the IETF Administrative Support Activity, Version 2.0 The IETF Administrative Support Activity (IASA) was originally established in 2005. In the years since then, the needs of the IETF evolved in ways that required changes to its administrative structure. The purpose of this RFC is to document and describe the IETF Administrative Support Activity, version 2.0 (IASA 2.0). It defines the roles and responsibilities of the IETF Administration LLC Board (IETF LLC Board), the IETF Executive Director, and the Internet Society in the fiscal and administrative support of the IETF standards process. It also defines the membership and selection rules for the IETF LLC Board. This document obsoletes RFC 4071, RFC 4333, and RFC 7691. RFC Editor Model (Version 3) 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). In addition, various responsibilities of the RFC Editor function are now performed alone or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor (RSCE), and IETF LLC. Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein. This document obsoletes RFC 8728. This document updates RFCs 7841, 8729, and 8730. RFC Formats and Versions ICANN Spherical Cow Consulting In order to improve the readability of RFCs while supporting their archivability, the definitive version of the RFC Series transitioned from plain-text ASCII to XML using the RFCXML vocabulary; different publication versions are rendered from that base document. This document describes how RFCs are published. This document obsoletes RFC 7990. This document also updates the stability policy in RFC 9280.