<NO HATS> The document seems to me to be in very good form. Thanks Paul and Alexis.
There are a few (hopefully editorial) issues I would like to see addressed prior to publication.
The abstract buries the fact that this is an update to the RFC Editor Model (Version 3). To address this, the authors could do a number of things:
* Call this version 3.1, a minor revision to the existing model (IMHO it is); or * Replace the first sentence to say, this document specifies an *updated* version 3 of the RFC Editor model; or * Some other way I haven't thought of, but more clearly indicates the change. Section 6.1:To be absolutely clear, the Trust retains rights to manage IPR, so I suggest the following changes:
OLD: It*was* left to the Trust to specify exactly how this shall be clearly indicated in each document. NEW: It*is* left to the Trust to specify exactly how this shall be clearly indicated in each document.The Chapeau in Section 7 now looks a little funny, and historically wrong, given that we appear to be changing history. To this end, I suggest the following changes:
OLD: 7. Historical Properties of the RFC Series NEW: 7. Properties of the RFC Series OLD: This section lists some of the properties that*have been historically* regarded as important to the RFC Series. NEW: This section lists some of the properties that*are* regarded as important to the RFC Series. One last nit: Section 9.5: OLD: To overcome some of these issues, [RFC9280] *dispenses* with the RSOC. NEW: To overcome some of these issues, [RFC9280] *dispensed* with the RSOC. Regards, Eliot On 03.06.2025 22:07, RFC Series Editor via Datatracker wrote:
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 ther...@rfc-editor.org 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.
_______________________________________________
IETF-Announce mailing list --ietf-annou...@ietf.org
To unsubscribe send an email toietf-announce-le...@ietf.org
OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- rswg mailing list -- rswg@rfc-editor.org To unsubscribe send an email to rswg-le...@rfc-editor.org
