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

Eric Rescorla <ekr@rtfm.com> Fri, 07 January 2022 04:04 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 8AAAB3A1277 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 20:04: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 fkAo3pQ77KwM for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 20:04:36 -0800 (PST)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 CF0423A1275 for <rfced-future@iab.org>; Thu, 6 Jan 2022 20:04:36 -0800 (PST)
Received: by mail-io1-xd29.google.com with SMTP id y11so5637082iod.6 for <rfced-future@iab.org>; Thu, 06 Jan 2022 20:04:36 -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=T11YoIpl1AmbEISg8FFxSpu9FLz3JqMB9FyjFuwWBYs=; b=qRGbck+Tbx77E7fSWN66A9/uK1QBFAGlTc62kn7Xprq99Fv684VprHMSIfSZR+N+XV fcG2Ar3q2c33leA6gxHNJusmtVO/YbO12BSUMCROKNzQXio6oxHRL5bqYJnW8I9u7uZ2 8USWXP3RpLsLu7qe9+n7LPucK9saYRgsJKuzJd5//gB/XXoV0JomT7+eXVAUVdEJWXGZ vDizWwdquOZ69XIjIdysaT6QaqNjulG1HzvihXF/FJGXaaaqezPqEaPJUP0f/kK9goQV JBm6i3zAJ0AXLpZFEa9Sg7s0O+QQH/a3VjNMXYpj2Ta8OGlbDutdl+Z5GHMlnYzSjmY4 xKdg==
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=T11YoIpl1AmbEISg8FFxSpu9FLz3JqMB9FyjFuwWBYs=; b=ytDhalGJst2+VHCtZvHmHBhqQc9FD5OyW78fpNuIYlJn4w+xiIuKd2o//zoZgbAAT6 8qRjGyJ1rbY+E3Asv9uDDoIEZWsrP65SQ+W0cSCgI8PbkkwYdElWcSpw1PDeULkJ/zUC dYJD/n9WLZdNA+1qczHfKcm4TISYlOuYeD7T8yFtRF11U8nxEm6T82BcGaHcvPSXXAKI dzJQi6M2eCF9JnHz9a1HZMJN4UUMqkGTeB2DuKlc7neYs6W0fwJG42rb84dMW+UqNjbm CB2XgIqGnaguzmUlDHTq1CX9aAiOrYXd2MuEs6mnlnwyYNOmJiK6M2NtJSYbw0OaY0d0 C/Qg==
X-Gm-Message-State: AOAM532LOR6U8QElGHoP5V2pCACAHM9q8OKQrzrp3rOIbPIReoAFMIE+ VCBM6ch3XFaYYhHSI40Zxf2bW8yjVE39t9W4W19jRXaq5fA=
X-Google-Smtp-Source: ABdhPJxxfe/kkS4J1ouPXas5kFvwdqDnrZl3YRbhJGZFDDhUrylL/g55hfMpXa3WnN29oHCqduVHkSIAPpxjPc0iHCM=
X-Received: by 2002:a05:6602:3404:: with SMTP id n4mr3104322ioz.148.1641528275306; Thu, 06 Jan 2022 20:04:35 -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> <CABcZeBPZ_KySAT51KV-JyY3HCO=sv8MbxVy0kzTxCzZnR2xdZQ@mail.gmail.com> <7608db96-fd32-ed68-e828-7c0c3d1993ac@stpeter.im> <8f81801e-d6f5-181e-02f8-c9eef34e6c74@stpeter.im> <3ffb9dbe-2a2a-2ae7-047b-7bae527a50f0@nthpermutation.com>
In-Reply-To: <3ffb9dbe-2a2a-2ae7-047b-7bae527a50f0@nthpermutation.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 06 Jan 2022 20:03:59 -0800
Message-ID: <CABcZeBPUL1LLfXrwav2yr+_U_-5M8gdGo-h5mu1aZCe_SVBibA@mail.gmail.com>
To: Michael StJohns <msj@nthpermutation.com>
Cc: Peter Saint-Andre <stpeter@stpeter.im>, Eliot Lear <lear@lear.ch>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="000000000000bd27fe05d4f61561"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HLjVX7xx_uUI0wa2OSW8ZdwJrDc>
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 04:04:42 -0000

On Thu, Jan 6, 2022 at 7:05 PM Michael StJohns <msj@nthpermutation.com>
wrote:

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

I am not in favor of this. It brings in precisely the concern I had on
reading this
text of the RSWG laundering otherwise inadmissable objections that happen
to be raised by a community member.

-Ekr


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