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

Eric Rescorla <ekr@rtfm.com> Tue, 04 January 2022 21:18 UTC

Return-Path: <ekr@rtfm.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 F388D3A0AB5 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 13:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=rtfm-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 fME_Fat2mcco for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 13:18:37 -0800 (PST)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 A82E13A0ABB for <rfced-future@iab.org>; Tue, 4 Jan 2022 13:18:37 -0800 (PST)
Received: by mail-il1-x12e.google.com with SMTP id q6so29297117ilt.6 for <rfced-future@iab.org>; Tue, 04 Jan 2022 13:18:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hdZTYto1Vnu2saqi/3U/t7RvAzRb7l5dbNQvFsdga/A=; b=xie8FVTaIq4IA3+8Z6S4AVvUhtbakYfajZIOPJ+1oRs0JUv+J1545WmaDvQOkOKen1 e2gdQj4SfH02Ace2Lot0U+sXPOnJ3g40qv4ImwczSP+fe6u6oTPgAcKo+NNLWy5H8bAK LKifP6nAf9uVh0ZAJofu1wMOgwKVTpY0Wqn8xLVcpXTiv1GTvRTr8OjDHtjw+8r+/qGQ h6PmWAVQVTqKlLjCZuNjtrFpbepY1t/6h3OPRt2pf3zS9AgZnKm9C+tDXUdB1ERMi8co s8nt2pHqjwqpWU08QrFwqwnSNNVJxaeX/0U9lZSvnmUKHWRf6uRHlgST7YSaRplWxww+ UkxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hdZTYto1Vnu2saqi/3U/t7RvAzRb7l5dbNQvFsdga/A=; b=s/NHsePenZ1tt42/jZcKTX3rUClvuQY/C8O/ueW/Frvou6U0tdSaoJr8O9hUv49dR1 gJlTQTmBF8dyzuXo59c+Wd+DjiFvG05gGHwp/c5ezDfJR/P1u/5NGl81o8Pb120OGt9E C5JyNhWMXn7s8dGLEn2ALt4ctLYi1+JTd9SyA+g9ETHomX59BaIe+Fk5RdpI1+GJ3bwj f2Lbhkdrk0upVu4XVgjNkyTujxOcLZcPLcrkeer74p3tmxAVAOd6M/JC2ylSE/GJAyib tlDMxrrriDtM+VWiLu/sYmf2CmFGp0HR3U27+NoLXZ8BL//s1gUbPHx5YTVX/lmu86c6 FQKg==
X-Gm-Message-State: AOAM530qwcXJmrsl67S27gbjdQk0lHdvhcEsnyhyYR6eJ9ZXK8/BgZ9n wkHFDfRBzeRNL8uqDyIDnpPv3/e6rhf8rDhhdcX+AA==
X-Google-Smtp-Source: ABdhPJztq5qmIMgKjb6TGzwDL0BLs256w5mBA8Vm9/EPSNzOWcW1oV86btenXoeARjiYTXA3N+7hHXRI/0J/Si4CpFs=
X-Received: by 2002:a92:c210:: with SMTP id j16mr25490664ilo.219.1641331116063; Tue, 04 Jan 2022 13:18:36 -0800 (PST)
MIME-Version: 1.0
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> <5864d952-7e83-814e-b6dc-cf4866462c0e@nthpermutation.com> <88486756-40d0-2061-ffa8-37791fd9cdfd@lear.ch>
In-Reply-To: <88486756-40d0-2061-ffa8-37791fd9cdfd@lear.ch>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 04 Jan 2022 13:18:00 -0800
Message-ID: <CABcZeBMKjzXHXKaz9ZRVTb8wyr6R_B+38_V7dNG5-RrLULPkhw@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="00000000000021d6ca05d4c82e6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/j_FWPPLNrXZNNg3SQ9r_fRNdLn0>
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: Tue, 04 Jan 2022 21:18:42 -0000

Well, it's not an *additional* bullet but rather a replacement bullet, I
think.

I think this also still leaves the question of whether it's exhaustive.

-Ekr


On Tue, Jan 4, 2022 at 12:45 PM Eliot Lear <lear@lear.ch> wrote:

> Ok, if I understand correctly, you and EKR are aligned with an additional
> bullet about lacking community consensus.  Unless people object, why don't
> we run with that?
>
> Eliot
> On 04.01.22 21:09, Michael StJohns wrote:
>
> On 1/4/2022 2:50 PM, Eliot Lear 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.
>
> Eliot
>
> Hi Eliot -
>
> My first thought was this was spot on.  More thought suggested otherwise.
> The problem is that language suggests the RSWG chairs would be evaluating
> community consensus rather than just WG consensus and that's probably not a
> useful model.  Maybe instead:
>
> Leave 8 as it is.  Add "LACKS CONSENSUS" to the vote possibilities in 9.
> It's a more specific subset of CONCERN that generally suggests that the
> voter believes that community comment indicates fundamental flaws in the
> proposal.  I.e., this is not "the document reads poorly or has fixable
> bugs", but "the community thinks the overall idea lacks merit and changes
> to the document are unlikely to change that".  The document is still
> returned to the RSWG.
>
> And that's conditional on any changes EKR proposes to the other text.
>
> Mike
>
>
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>