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

Peter Saint-Andre <stpeter@stpeter.im> Fri, 07 January 2022 02:24 UTC

Return-Path: <stpeter@stpeter.im>
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 F06E93A0E3A for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:24:41 -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 (2048-bit key) header.d=stpeter.im header.b=kinvD9zH; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lGbYKqu9
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 wvHsp9KIiPeh for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:24:36 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB98E3A0E2A for <rfced-future@iab.org>; Thu, 6 Jan 2022 18:24:36 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A05335C01AE; Thu, 6 Jan 2022 21:24:35 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 06 Jan 2022 21:24:35 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:from:to:cc:references :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=e YktRmI0+Vqo9lKy8fuBzJSr22QsPcq9pz9Dc0qqPeQ=; b=kinvD9zHWKO1BOMG3 9BD4GVffDpGi1/Jjb//QAItOl7yv1rGS7P8bgTtieH3Y5B2TkodjTOG27cRkBSPz UBQ2JBeiojkVxOmdb+5Bazkn++wFFWPOjgd+VSgTNh41XJjRgGd9yAo3jFBIqJlh gDeYGQueJQVUsJHtwQY8F8XXp4HhEJkPJAXuB97D011JMiZn3MmfBQK4J8v05eJH kIwJrAhTU/9oK5UKw+xa8IM3f8TeStuyc2Jo8F3X9tDT98AP8PdWniyXIyd2W9eg gB6afzYefVeZSYoSubWOT/Qp0d27YoCY/iLEnA10puvPNK0/50MbJyOIi9pQFRit myj+Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=eYktRmI0+Vqo9lKy8fuBzJSr22QsPcq9pz9Dc0qqP eQ=; b=lGbYKqu9I7ISkGuFfBMxGkhDW0RBHivMtgLAlxOrq3ntilUox/FiNBNiP Tf422Qq36zj3aRkOLtC/q8uHmGs5D/xjEoJT2sd6Ek2UIUu29tvr6OHGQsB6r2GV +4l4h6qPM+rJ210nvzwBNnGOgc7vz4cpLFVpPQBynGu54wxxpt0HJEtGi20Myn2N U4hOW8eIG8M+TF6AekvEbxiqeDzTdGep5i0J8SqeQVETggsCG38VB1iIZ3MawI3S HwOR+fxeYonP5UiqXjQ1XicCZL0ltKJMxF2mpZ2a8a2pyO6AWsP0nUGAmO/XL4sJ N2iIdb1cDqYtOrgWVoZROxKBAFVUA==
X-ME-Sender: <xms:Y6TXYbPrUM5zq9Z8PHXI6olUfYVxp7RTp23AAfftVxE29txP7Mi65g> <xme:Y6TXYV9JMVfm0iIbFziDlf-yzEQd5Ti1e0CgWXwje0JbsynTFA6lANV4rPNQJeGfX SS47GDZh8zvcv4MmQ>
X-ME-Received: <xmr:Y6TXYaTv22SrcbxzSBur6GXDKOdlSzC2pwJTnfN_6oKKJelPqzU-qRNpvB9qsyw97Of2DZU5NiILayIIkbIGuFHchIr3HgibZWumsW8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegtddggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffhvfhfjggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhephfeludeiffduffehhfeifeefhfdtvedvjeefvdejfffhteef ueeifeevgfffgeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:Y6TXYfvMBfOT8VKHDsmoRpOC4zBY6Dg6JGzfztdiJjl-CYmF8Nkxpg> <xmx:Y6TXYTeNSY2yQUG9xd4L12aT7vfhgaxx8KKWoSn_walXzf3jvnXm2A> <xmx:Y6TXYb0my562GZtcuT51QsA0xKJDZPs7XgbmnpBjX2Kl7WB5ZRW_1g> <xmx:Y6TXYf7GOIcZHbghWfQoE_Ve_-3K7oLmXkqY1_wqFnR4Q7sVqDrYNw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Jan 2022 21:24:34 -0500 (EST)
Message-ID: <8f81801e-d6f5-181e-02f8-c9eef34e6c74@stpeter.im>
Date: Thu, 06 Jan 2022 19:24:31 -0700
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
From: Peter Saint-Andre <stpeter@stpeter.im>
To: 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>
In-Reply-To: <7608db96-fd32-ed68-e828-7c0c3d1993ac@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/-3-lC4mOW6DdVuua-kj9WnrJ6mk>
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:24:42 -0000

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