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

Eliot Lear <lear@lear.ch> Thu, 13 January 2022 22:14 UTC

Return-Path: <lear@lear.ch>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07EB13A1632 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 14:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.804
X-Spam-Level:
X-Spam-Status: No, score=-2.804 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVDKf0Y-tod8 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 14:14:13 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB69C3A1630 for <rfced-future@iab.org>; Thu, 13 Jan 2022 14:14:11 -0800 (PST)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 20DME9VS014009 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 13 Jan 2022 23:14:09 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1642112049; bh=3FyS/FvbmOX/q3OrAOeX7gw31snpqXefyGhd+MiaizM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=wBUtFrbDRHaviJwm7XhLCSPY0eWJ6LqVXgPh7DFfD4MwhqiLSgjHIXelpF/rt8p+8 Mc3mgZF6elgxI8rEZ37kbjuB1nxLdwxv9W9Gheeb4wglEpMtPUN5zyYuYIXvf34doJ mp7SrMsx7CtQDF19nMTkELIPTVKjEgb7bDVX9qho=
Message-ID: <e9a8e7ae-c11c-4ab3-d6f5-5ab2b2bcde09@lear.ch>
Date: Thu, 13 Jan 2022 23:14:08 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Peter Saint-Andre <stpeter@stpeter.im>, Mark Nottingham <mnot@mnot.net>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
References: <164159953944.5205.10517887235280838552@ietfa.amsl.com> <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im> <116833C8-6D7C-43B3-A91A-E63FCCE7C448@mnot.net> <14bde881-ae07-a3a6-b458-39ed69c05c36@stpeter.im>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <14bde881-ae07-a3a6-b458-39ed69c05c36@stpeter.im>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------OqtUtTzHnXuvwaDbNMH0FMfy"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KHTzPlfkLDYOIhpUJLTazvIVgGE>
Subject: Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2022 22:14:16 -0000

If it's not too much trouble, let's tackle Mark's feedback so we can get 
as clean a version for LC as possible.  Please see below.

On 13.01.22 23:04, Peter Saint-Andre wrote:
> 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...

This is editorial.

>>
>> * "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."
This needs to be addressed.
>>
>> * "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.

This is addressed, I think.

Eliot