Updates to RFC Editor Model (Version 3)

Status of This Memo

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 20 July 2025.¶

Copyright Notice

Copyright (c) 2025 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.¶

Table of Contents

1. Introduction

[RFC9280] 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 [RFC9280] based on these findings.¶

2. Updates from "RFC Formats and Versions"

[I-D.draft-rswg-rfc7990-updates], "RFC Formats and Versions", updated RFC 9280.¶

3. Purview of the RSWG and RSAB

Section 3 of [RFC9280] 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 [RFC9280], with community consultation as for other tools and services supported by IETF LLC [RFC8711]."¶

4. 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 %%¶

5. 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) %%¶

6. Security Considerations

There are no security considerations for the changes listed in this document.¶

7. IANA Considerations

This document contains no actions for IANA.¶

8. Normative References

[I-D.draft-rswg-rfc7990-updates]

Hoffman, P. E. and H. Flanagan, "RFC Formats and Versions", Work in Progress, Internet-Draft, draft-rswg-rfc7990-updates-12, 6 August 2024, <https://datatracker.ietf.org/doc/html/draft-rswg-rfc7990-updates-12>.

[RFC8711]

Haberman, B., Hall, J., and J. Livingood, "Structure of the IETF Administrative Support Activity, Version 2.0", BCP 101, RFC 8711, DOI 10.17487/RFC8711, February 2020, <https://www.rfc-editor.org/rfc/rfc8711>.

[RFC9280]

Saint-Andre, P., Ed., "RFC Editor Model (Version 3)", RFC 9280, DOI 10.17487/RFC9280, June 2022, <https://www.rfc-editor.org/rfc/rfc9280>.

Author's Address