The RSAB has received a request from the RFC Series WG (RSWG) to approve the 
following document as an Informational RFC on the editorial stream:

   <draft-editorial-rswg-rfc9280-updates> (RFC Editor Model (Version 3)

The RSAB solicits final comments from a wide range of communities. Please send 
substantive comments to the [email protected] mailing list by 2025-06-17. 
Please retain the beginning of the Subject line to allow automated sorting.

Abstract:

   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.

   Since the publication of RFC 9280, lessons have been learned about
   implementing this model.  This document lists some of those lessons
   learned and updates RFC 9280 based on that experience.  This document
   obsoletes RFC 9280.

A URL of this Internet-Draft is:

    https://datatracker.ietf.org/doc/draft-editorial-rswg-rfc9280-updates/

A process note: In accordance with RFC 9280, because this draft obsoletes RFC 
9280, if it is approved by the RSAB, it must be approved thereafter by the IESG 
and IAB, and reviewed by the LLC Board prior to publication.

_______________________________________________
rfc-interest mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to