Re: [Rfced-future] WGLC Review of the draft

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 07 January 2022 02:54 UTC

Return-Path: <jmh@joelhalpern.com>
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 DAF753A10EB for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:54:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 A-ah_jgq_omY for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:54:36 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 4F0BF3A10E9 for <rfced-future@iab.org>; Thu, 6 Jan 2022 18:54:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4JVSVg66DSz1pLsJ; Thu, 6 Jan 2022 18:54:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1641524075; bh=UsEaZMXW1NTZEE08OhMQ508e/820WieddcwZGLyakGo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=JSiKqgS8vkHL77GjWzJ1rKmfTOoMTjFWsOXg822jmW8zPu4J7M6uPpybvQ6Id8Axh y/RkwkRXRhidnnPIH2qtu9p2nWYC/PvBqeUFTgz1dSM74rJcThUBnO5Gg+3afKfZyW QlRa4R3u/w0G8oC8Zocpy75pqyfQ15pCCBya5akk=
X-Quarantine-ID: <J6_skkU3wwsD>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4JVSVd64XMz1ntTm; Thu, 6 Jan 2022 18:54:33 -0800 (PST)
Message-ID: <38487567-e6a7-8649-08a0-5174f53b7a9c@joelhalpern.com>
Date: Thu, 06 Jan 2022 21:54:31 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>, Eliot Lear <lear@lear.ch>
Cc: rfced-future@iab.org, Michael StJohns <msj@nthpermutation.com>
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <CABcZeBMtZUa9cdr6a7znjdMY3UwNPpg2d0d4KwosfmzE1KqmxQ@mail.gmail.com> <87ea0c57-3269-d8ea-90ec-0f91096f1d28@nthpermutation.com> <145d2db5-b44a-1c2c-7bae-79b042313445@lear.ch> <CABcZeBPZ_KySAT51KV-JyY3HCO=sv8MbxVy0kzTxCzZnR2xdZQ@mail.gmail.com> <7608db96-fd32-ed68-e828-7c0c3d1993ac@stpeter.im> <8f81801e-d6f5-181e-02f8-c9eef34e6c74@stpeter.im>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <8f81801e-d6f5-181e-02f8-c9eef34e6c74@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/A31tTCyA6Dqw1jxh_VsEpMvSQwA>
Subject: Re: [Rfced-future] WGLC Review of the draft
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: Fri, 07 Jan 2022 02:54:41 -0000

Thank you Peter.  This looks to me like good text and a useful improvement.

Yours,
Joel

On 1/6/2022 9:24 PM, Peter Saint-Andre wrote:
> On 1/6/22 7:15 PM, Peter Saint-Andre wrote:
>> On 1/4/22 1:36 PM, Eric Rescorla wrote:
>>>
>>>
>>> On Tue, Jan 4, 2022 at 11:50 AM Eliot Lear <lear@lear.ch 
>>> <mailto:lear@lear.ch>> wrote:
>>>
>>>     Hi Mike,
>>>
>>>     Just to preface, I'm offering some text below just to clarify a
>>>     point on which I suspect the group agrees.
>>>
>>>     On 04.01.22 19:52, Michael StJohns wrote:
>>>>
>>>>     It wouldn't work for me.
>>>>
>>>>     What I think EKR is saying - and let me use a concrete example -
>>>>     is that if 5 people that think changing the numbering system of
>>>>     the RFC series proposes that in the RSWG, gets RSWG consensus, but
>>>>     then the community overwhelmingly thinks that's a bad idea - well
>>>>     so what?   The RSAB still has to approve the document?
>>>>
>>>>     I would hope not.
>>>>
>>>     Perhaps a tweak to Step 8 might help?
>>>
>>>     OLD:
>>>
>>>>         8.  Once the RSWG chairs confirm that concerns received 
>>>> during the
>>>>             community call(s) for comment have been addressed, ...
>>>
>>>     NEW:
>>>
>>>>         8. Once the RSWG chairs confirm that concerns received 
>>>> during the
>>>>            community call(s) for comment have been addressed*and 
>>>> that ****there is rough consensus of the community for the result*,...
>>>
>>>     Or some such?  And the RSAB could send out further calls for comment
>>>     based on revisions, just to be certain.
>>>
>>> Or some such. I also would not object to adding there not being 
>>> consensus of the community to the RSAB CONCERN
>>> reasons.
>>
>> IMHO that's a reasonable path forward.
> 
> Here is proposed text:
> 
> ###
> 
> There are three reasons why an RSAB member may file a position of CONCERN:
> 
>     * The RSAB member believes that the proposal represents a serious
>       problem for one or more of the individual streams.
>     * The RSAB member believes that the proposal would cause serious harm
>       to the overall Series, including harm to the long-term health and
>       viability of the Series.
>     * The RSAB member believes, based on the results of the community
>       call(s) for comment {{cfc}}, that there is no consensus to advance
>       the proposal.
> 
> ###
> 
> Then I suggest we clean up my proposed text in the CFC section, too:
> 
> ###
> 
> The RSAB is responsible for considering comments received during
> a community call for comment. If RSAB members conclude that such
> comments raise important issues that need to be addressed, they
> should do so by discussing those issues within the RSWG or (if
> the issues meet the criteria specified under Step 9 of {{workflow}})
> lodging a position of "CONCERN" during RSAB balloting.
> 
> ###
> 
> Peter
>