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

Colin Perkins <csp@csperkins.org> Wed, 05 January 2022 12:27 UTC

Return-Path: <csp@csperkins.org>
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 226893A0CCA for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 04:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_PASS=-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=csperkins.org
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 I8BdRqTFEFsp for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 04:27:20 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 B0DE03A0CC6 for <rfced-future@iab.org>; Wed, 5 Jan 2022 04:27:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=MG9qlVq5iPZHksxaGedtDlJH+YsyO41oSheCtHE0xMg=; b=NrTIzpb2+dD+f/uPq3WYj7AcqV JjGSpkpIZlmL7p8SQAGHc/IseSyqhD1pGMkxHuoWzf4kNtrRMBwopMOGbQxKyVuoVazBXFwGGwZ1V 5vNPnPuZt2EBE5nwhPR/P8lHoii0O4/PYOy3axx9x+DQTubVr6hM6Hxk8yUyMiQ/+nVpau3ufIApb 8iuRdRhJLNxBCCQ0nBZKs+vwbjXCCAYmofqT14aSUB4AVCUtm0SZSt+MXsjpDUcYNBAhk7ccAkYK+ eVyDhBPKnLwEuK1os/8zjoMDOquMFH+jbvgNceUnW704Vhk8oL/x0NSljmbnm9AikQrEFeswH3SdH Ru0g/xBw==;
Received: from [81.187.2.149] (port=45055 helo=[192.168.0.67]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1n55Nn-0007lV-9E; Wed, 05 Jan 2022 12:27:15 +0000
From: Colin Perkins <csp@csperkins.org>
Message-Id: <0B425B35-0969-4031-B93E-CF6FE5D58EF2@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_58A94894-AF45-4573-BA0B-3990DBF0D584"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 05 Jan 2022 12:27:04 +0000
In-Reply-To: <0ac6a85a-b15d-8efc-550d-b8e3797a10ff@lear.ch>
Cc: Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org
To: Eliot Lear <lear@lear.ch>
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> <0ac6a85a-b15d-8efc-550d-b8e3797a10ff@lear.ch>
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/-CHoD9LBb-rYEADOem1D_Sy8jL0>
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 12:27:25 -0000

Hi,

I’m perhaps confused, but doesn’t the current draft require the RSAB to "actively seek a wide range of input” from the community as part of the community call for comment? 

If we require the RSAB to seek such review, and I think we must, then there has to be a way for the RSAB to send a draft back to the RSWG for further review to think about those comments. I don’t believe we can remove the bullet point ("Comments received during a community call for comment need to be addressed, as described under Section 3.2.3.”) that permits that. 

(At this stage, it’s very hard to follow what specific text changes are being proposed – can the chairs summarise?)

Colin



> On 5 Jan 2022, at 07:24, Eliot Lear <lear@lear.ch> wrote:
> 
> 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:
> 
> 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.
> 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
> 
> <OpenPGP_0x87B66B46D9D27A33.asc>-- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future



-- 
Colin Perkins
https://csperkins.org/