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

Michael StJohns <msj@nthpermutation.com> Fri, 07 January 2022 03:05 UTC

Return-Path: <msj@nthpermutation.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 D9FF03A112A for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 19:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_NONE=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=nthpermutation-com.20210112.gappssmtp.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 zslR88UTi8bM for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 19:05:14 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59B343A1124 for <rfced-future@iab.org>; Thu, 6 Jan 2022 19:05:14 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id t66so4695752qkb.4 for <rfced-future@iab.org>; Thu, 06 Jan 2022 19:05:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=TZ1XPZTWa5AkhOBy8QCtENMxQcyz534/JFtfU99eMMI=; b=Ip03GBPp/BWCQ0a6j6P/qf2IkH+UQtcgML7G/HE7n6C16o/yPhko8RjVdd6Jv17SaX Yc/Z04/lQwjaqWXZJyCrPC8A0jsC1l/Un6bqUuXetiZ0uqJPbNVa//TIv/WBz34q9jIT cJOs9lYwdFmDVfFQfzA/Qws+Lmdnibx4sE6lAj+FMTx8+V6DLlrMNznryNhL6/PmDP+k VGDRfesrcofP2OQP/3cL7JbPIt47FIYltxe6qrsWzItt9AYy8+wyHSlNmbosKMWOwFNV fUOQ5MLjZpjM9wdYE58rcY+WmAtj5JZpq+9DAqNXAzR4nzAmdvB5SanD6T9JQKhrFux+ uWAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=TZ1XPZTWa5AkhOBy8QCtENMxQcyz534/JFtfU99eMMI=; b=qrwqzS5LhQ2s6OH0cfLOjlCw0YAWsHDs8ZPeGGUv/JekYr8HidK24bHJd/ShMkRsKw Bcs5XWhcpD7Lf8f1zK8Ylms0uFp6yFp9h+qEbmKi4PlNGqKJRythjEtA9D5fhW0/Xuch BkxuvMXQGYKuUbEAEPUv+iNGpBZsN2trVlt4Y+mDoqpvT++NIxUSysBKm0Oal9miHPVI o7PIlkYrw/qA3MyXH3ZzvwzegKT84BTkIK8sO/D4p7aBeSB5NhGhCMfy7La0tICQ++l2 llKIqog4PWZtCejEXt/WGKcPzV2casbVG8ubNdY7g0rU2bgOC8KOlrnoAGXpvnVWtvUS l0Mg==
X-Gm-Message-State: AOAM531r5bXjIQ2kzIGMXIddNSq2kgS/I7QbfJb33IZ1XgXNsJzjp7N9 1qDwu+3SLIWxhRAE9WJbaxbjW2CrNTLyitZskuc=
X-Google-Smtp-Source: ABdhPJw97hjXtNB6/rssX7FGIcL/CUMu8xgudoE9Sb7Ho2vW3DuxTLsB49Lji1N7drlCkf4IMmC4TA==
X-Received: by 2002:a05:620a:1a01:: with SMTP id bk1mr43265730qkb.539.1641524712088; Thu, 06 Jan 2022 19:05:12 -0800 (PST)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id q12sm2861579qtx.16.2022.01.06.19.05.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Jan 2022 19:05:11 -0800 (PST)
Message-ID: <3ffb9dbe-2a2a-2ae7-047b-7bae527a50f0@nthpermutation.com>
Date: Thu, 06 Jan 2022 22:05:10 -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
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: Michael StJohns <msj@nthpermutation.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/7kClLNU1E1_ldPa4rVvoDG_hwY4>
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 03:05:19 -0000

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.
>
Delete "serious" in both of the first two bullets.   Serious is way too 
subjective, and pretty meaningless here as the voter gets to decide 
whether or not the problem creates an actionable concern.  If you think 
this demands an adjective then "unmitigable" is probably the right one 
in both locations as it would prompt a discussion of how to make things 
work.

Add a 4th:

* The RSAB member believes that based on the results of the community 
call(s) for comment {{cfc}} there are previously valid unraised issues 
that need to be addressed by the RSWG prior to publication.

I.e., a CONCERN based on community call may be issued to due to either a 
perception of  a lack of community consensus, but an raised and valid 
issue that  wasn't apparent to the RSWG for some reason

> ###
>
> 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.

Delete "important" for the same reason.   Also, there's some 
plural/single issues here with respect to who "concludes" and an and/or 
issue so:

The RSAB is responsible for considering comments received during a 
community call for comment.  If [one or more | an ] RSAB member(s) 
conclude that such comments raise issues that need to be addressed, they 
should do so by discussing those issues with* the RSWG.  If they believe 
an issue meets the criteria specified under step 9 of {{workflow}}, they 
should also lodge a position of "CONCERN" during RSAB balloting.

*I believe "with" is more correct than "within" as this is RSAB to RSWG 
rather than the RSAB member as a participant in the RSWG. The former is 
an individual opinion, the latter is a positional opinion based on RSAB 
membership.  Yeah, it's a nit.

Mike


>
> ###
>
> Peter