Hi - - Just getting this in under the wire.
Section 3.1.1.3 - Reads poorly. Instead "The RSWG has two chairs, one
appointed by the IAB and one by the IESG. Both chairs serve staggered
2-year terms, with the IAB-appointed chair's term beginning (and ending)
at the end of the First IETF meeting in [even|odd] years, and the
IESG-appointed chair similarly in [even|odd] years. Chairs may be
reappointed to additional terms at the discretion of the appointing body."
s/determined/determine/ - they can change at any time rather than
implying the choice is fixed.
In the line about directing comments - why not actually state the
current mechanism(s) now that we know it? E.g. send it to which email
list or drop box or comment page?
s/have the power to remove/may remove/
Section 3.1.1.4 - 2nd to last para "The IETF LLC, through agreement,
provides....". Delete the last paragraph.
Section 3.1.2.6 Ditto for the RSAB operation.
Section 5.2 - this didn't change, but I think it needs to. This has the
tail wagging the dog. The RCSE works (is employeed by or contracted)
for the LLC who has hire/fire authority. The LLC needs input FROM the
RSAB (or its members individually) and it's unclear that providing an
internal LLC evaluation to the RSAB is a legitimate approach. That
said, the LLC can involve the IAB and IESG chairs as an LLC discussion
if they think it necessary. I don't expect this to fly given that the
RSAB is writing the document, but it's worth a try.
Later, Mike
On 6/3/2025 4:07 PM, 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 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]
_______________________________________________
rfc-interest mailing list -- [email protected]
To unsubscribe send an email to [email protected]
