Re: [Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)

[Adrian Farrel <[e-mail]>]

Yeah, well, I think the hardest work was done by you and Brian.

So, thanks for the leadership and herding of cats.

Adrian

 

From: Rfced-future <[e-mail]> On Behalf Of Eliot Lear
Sent: 30 June 2022 20:35
To: [e-mail]
Subject: [Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)

 

Colleagues,

I'd like to congratulate you on your hard work.  This wasn't easy- there was a lot of give and take by everyone.  Now the fun begins.  I hope to see you all in the RSWG!

Eliot



-------- Forwarded Message -------- 


Subject: 

RFC 9280 on RFC Editor Model (Version 3)


Date: 

Thu, 30 Jun 2022 11:52:04 -0700 (PDT)


From: 

[e-mail] <mailto:[e-mail]> 


To: 

[e-mail] <mailto:[e-mail]> , [e-mail] <mailto:[e-mail]> 


CC: 

[e-mail] <mailto:[e-mail]> , [e-mail]



A new Request for Comments is now available in online RFC libraries.

RFC 9280

Title: RFC Editor Model (Version 3) Author: P. Saint-Andre, Ed.
Status: Informational
Stream: IAB
Date: June 2022
Mailbox: [e-mail] <mailto:[e-mail]> 
Pages: 27
Obsoletes: RFC 8728
Updates: RFC 7841, RFC 8729, RFC 8730

I-D Tag: draft-iab-rfcefdp-rfced-model-13.txt

URL: https://www.rfc-editor.org/info/rfc9280

DOI: 10.17487/RFC9280

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.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail] <mailto:[e-mail]> . Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list
[e-mail] <mailto:[e-mail]> 
https://www.ietf.org/mailman/listinfo/ietf-announce