Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt

Hi Mark,

It seems that I missed this feedback when publishing the new version 
today. My apologies for that. I can submit -10 to fix these issues, or 
wait until after this next review period.

Peter

On 1/9/22 1:23 AM, Mark Nottingham wrote:
> Hi Peter,
> 
> Thanks. Looking through the diffs, I noticed a few things:
> 
> * "The RSWG is empowered to hold in-person or online-only meetings" -- this wording could be interpreted to prevent hybrid meetings, or online participation in in-person meetings.
> 
> * "The RSAB consists primarily of certain voting members.  As specified herein, the RSAB also includes certain non-voting members." -- this is quite wordy...
> 
> * "The RFC Series Consulting Editor, in effect representing the Editorial Stream" -- my understanding was that the RSCE's inclusion on the RSAB was not only for this purpose, so this could mislead. Also, it makes this text somewhat contradictory: "Note: this method of handling vacancies does not apply to a vacancy of the RSCE role, To ensure the smooth operation of the RFC Series, the RSAB shall only of the stream representatives enumerated above."
> 
> * "Email messages sent to the RSAB email discussion list or exchanged among all members of the RSAB shall be publicly archived..." -- I think the "or exchanged among all members of the RSAB" clause is impractical and ineffective, and it should be removed. I don't feel strongly about it to formally object, though.
> 
> Cheers,
> 
> 
> 
>> On 8 Jan 2022, at 10:53 am, Peter Saint-Andre <stpeter@stpeter.im> 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: internet-drafts@ietf.org
>> To: Peter Saint-Andre <stpeter@stpeter.im>
>>
>>
>> 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
>>
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 