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

Eric Rescorla <ekr@rtfm.com> Tue, 04 January 2022 20:36 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 D7B033A0819 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:36:44 -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 qb-J6fD_lJLg for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:36:40 -0800 (PST)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 8691A3A0812 for <rfced-future@iab.org>; Tue, 4 Jan 2022 12:36:40 -0800 (PST)
Received: by mail-il1-x131.google.com with SMTP id j6so29254221ila.4 for <rfced-future@iab.org>; Tue, 04 Jan 2022 12:36:40 -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=yiUejhkeRYExrJBWVLNovx33cSkqbv8a3zSKd4SsQlY=; b=DXnDZM4hiyupcxANrd/Xr+5QkspgysPlDNRsropJ/Ot/PG+52BW4M81gk1cot9ocL2 DGUh7wanT87XQmuL88P7YpdmNn8cUaBUJNGE0scdQzUj7EBaNQFmMoJ56w3X/a8v+v1H 2Al7i5wTv/TmmIQCl66mZF4NMNDpa9nYWz0CId8keY4reyzLdRUMBz/ljUltpJEL2q20 +gH89GNSWylLbU4Y1wD9v7OZLv+BIsNl0n8Jh0BR/tVMn2Upk68t3//qBYLXA6bOmuHu XRuczK/cm5sTP+LZzlXO3oyf4MukskP2aKBO2/gZfVv7n3epwkl4zpTWu8rcexssbP1N 14Kw==
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=yiUejhkeRYExrJBWVLNovx33cSkqbv8a3zSKd4SsQlY=; b=4tlRNLbw4aiJmiMAR4Xtw9o8Tuv4b11/CiiFwFHcvfqXEVA3okshiKpseXn9ppmQFn fVXagdAU/FHgFPkhbizY3ddMktyHnlBTx/W9Ek+z6uXuD/Pnx8zq+arRx+wFnVKvDDd4 0A9KBXt/1Czd2xmonzm32q/anj6pVRubJx4conbdc8cG1yMo94QZ+3+fNuI8qvdDPcoL hVvmrfVrniV273IQ0o+SKxtpaHNaURxl6A8v41Qos5+TFJi2HePBY6FqRHSJ/NT0Wvpg HGzeQhAG8IODQZ6PKpj8PI9t24KbXMxBiR6NcFQcyBQD2Uv95TPkCowJ8lRcEreVQEcD oq2Q==
X-Gm-Message-State: AOAM531W0+XwfMG4i5oFjE2NTllYnnLZ+gsjuSd+YkozMWroeFO7x2LO sbp2ltqVcLjTRU+ChZmuPQk4qb5XlS0pyBfO8KGYYQ==
X-Google-Smtp-Source: ABdhPJwnR636ejiRrJG44V3MkZNRj8pV88ZC+dBI4rdTZx5E2B5kb5v4lhXo4nguDeaDa73j8Q5tYO49MCkTtr/TssM=
X-Received: by 2002:a05:6e02:1747:: with SMTP id y7mr21105322ill.10.1641328599066; Tue, 04 Jan 2022 12:36:39 -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>
In-Reply-To: <145d2db5-b44a-1c2c-7bae-79b042313445@lear.ch>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 04 Jan 2022 12:36:03 -0800
Message-ID: <CABcZeBPZ_KySAT51KV-JyY3HCO=sv8MbxVy0kzTxCzZnR2xdZQ@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="0000000000001b7f4605d4c798a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/QR0czVFiTYGlquvK1r22-Pvew7g>
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 20:36:45 -0000

On Tue, Jan 4, 2022 at 11:50 AM Eliot Lear <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.

-Ekr

Eliot
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>