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

Eliot Lear <lear@lear.ch> Wed, 05 January 2022 07:25 UTC

Return-Path: <lear@lear.ch>
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 292913A0D39 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 23:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 Pn6M8_Dx5xvm for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 23:25:09 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9703F3A0D38 for <rfced-future@iab.org>; Tue, 4 Jan 2022 23:25:09 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 2057P0bm2505218 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 5 Jan 2022 08:25:01 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1641367502; bh=i9wZbaRQ40IheubrwAhh4rwludcBf+WW7KDYZuWtzaU=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=JgiOfXtcOlOG3nY04TU/a02ZcPR7Bsg1BggzESjWkRkYj6Mmug66qt939I4k18SWo xoCCOKaWhbngAFaDpDOOR3IOnpCO65S48Dg5jD5jQ366r2PFMoL8OKBruigRTD7Xhy PZzGVTFsXX2IPv5D3G5/rCLwpqJCRNSe1beU0r2I=
Message-ID: <0ac6a85a-b15d-8efc-550d-b8e3797a10ff@lear.ch>
Date: Wed, 05 Jan 2022 08:24:58 +0100
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
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>
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> <5864d952-7e83-814e-b6dc-cf4866462c0e@nthpermutation.com> <88486756-40d0-2061-ffa8-37791fd9cdfd@lear.ch> <CABcZeBMKjzXHXKaz9ZRVTb8wyr6R_B+38_V7dNG5-RrLULPkhw@mail.gmail.com> <a30e4f00-3fcd-3b16-85c9-f44cf424b03f@stpeter.im>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <a30e4f00-3fcd-3b16-85c9-f44cf424b03f@stpeter.im>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------6FTE1BGugeBU961zvGI1SKqI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Ugp1MRKbNC4LMiNwDC5DkWpz0v4>
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: Wed, 05 Jan 2022 07:25:15 -0000

Hi Peter & EKR

On 04.01.22 22:33, Peter Saint-Andre wrote:
> On 1/4/22 2:18 PM, Eric Rescorla wrote:
>> Well, it's not an *additional* bullet but rather a replacement 
>> bullet, I think.
>
> That sounds right.

Yes, that's right.  I stand corrected.

>
>> I think this also still leaves the question of whether it's exhaustive.
Indeed.
>
> IIRC, in our original discussion this was intended to be exhaustive. 
> Personally (no editor hat on) I've only ever been ~90% comfortable 
> with that, but I can certainly live with it.
>
I don't think we intended it to be exhaustive, but I will admit that I 
didn't get a strong sense one way or another from the group.  So let's 
discuss.

Allow me to attempt to frame this a bit with two questions:

  * When can the RSAB trigger a broader community review?
  * What is the harm and redress if the RSAB triggers an "inappropriate"
    broader review?

Imagine a proposal to change the archival format (for whatever reason– 
let's assume there's some good reason to do so).  This would NOT offend 
the principles in Section 7, but might be viewed as a sufficiently large 
change that perhaps a broader review would be considered appropriate.  I 
could envision two scenarios:

 1. The RSWG *asks* the RSAB and the RSCE for help with a broader
    review.  One could envision such a situation where the RSWG
    participants believe they are either at their limits or beyond their
    expertise and really want to hear from others. This is not
    controversial, and I would imagine it would just happen without much
    if any change to the existing text.
 2. The RSAB thinks the proposal is at or beyond the limits of the RSWG
    participants or that the proposal might be harmful to the long term
    health of the series or have impact that they do not yet see (say
    with accessibility), and wants that broader review, without a
    request from the RSWG.

I think it's the 2nd scenario we need to discuss, and you might want to 
delve into it a bit.

And let's turn this around: what bad things happen if the RSAB triggers 
a broader review for something that is trivial?  Perhaps the answer is 
“not much”.  What would be the redress?  I see two answers to that:

  * Appeal on process failure.
  * Complaint to the streams and NOMCOM (probably the IAB, as a
    practical matter) of unwise/inappropriate use of authority.

I mention this because this group can afford to allow for some judgment 
on the part of the RSAB if we are comfortable with the risks of 
inappropriate use of the authority and the redress. Otherwise, we should 
be more restrictive.

Comments?

Eliot