[Rfced-future] CONSENSUS CHECK: Issues 134, 143, 144, 145, 146, and 147 (Re: Fwd: New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt)

[Eliot Lear <[e-mail]>]

Ok.  Thanks, Peter yet again.  That was a lot of work.  As I see it, 
this update has addressed the following issues:

  * Issue 132: What happens if a vote doesn't pass?
  * Issue 134: How do we update this document
  * Issue 143: public archive of RSAB
  * Issue 144: other modes of operation
  * Issue 145: CONCERN for unaddressed comments
  * Issue 146: RPC Core responsibilities

Issue 147 required no edits, at least at this time.

Please consider this message a consensus check on all issues above, 
except 132 for which we already had consensus on the text. Please 
comment no later than the 22nd of January.

Eliot

On 08.01.22 00:53, Peter Saint-Andre wrote:
> As promised...
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for 
> draft-iab-rfcefdp-rfced-model-08.txt
> Date: Fri, 07 Jan 2022 15:52:19 -0800
> From: [e-mail]
> To: Peter Saint-Andre <[e-mail]>
>
>
> A new version of I-D, draft-iab-rfcefdp-rfced-model-08.txt
> has been successfully submitted by Peter Saint-Andre and posted to the
> IETF repository.
>
> Name:        draft-iab-rfcefdp-rfced-model
> Revision:    08
> Title:        RFC Editor Model (Version 3)
> Document date:    2022-01-07
> Group:        iab
> Pages:        31
> URL: https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-08.txt
> Status: https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model
> Diff: https://www.ietf.org/rfcdiff?url2=draft-iab-rfcefdp-rfced-model-08
>
> 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).
>
>    This document obsoletes RFC 8728.  This document updates RFC 7841,
>    RFC 8729, and RFC 8730.
>
>
>
>
> The IETF Secretariat
>
>