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

Martin Thomson <mt@lowentropy.net> Wed, 05 January 2022 10:18 UTC

Return-Path: <mt@lowentropy.net>
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 7CDF13A0403 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 02:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=ijMf2zIW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IJzylD0v
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 5pcOwcuplfxm for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 02:18:07 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 930AE3A03FA for <rfced-future@iab.org>; Wed, 5 Jan 2022 02:18:07 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id B8ED432009DF for <rfced-future@iab.org>; Wed, 5 Jan 2022 05:18:04 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 05 Jan 2022 05:18:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=4o9ZjkCN/NV0YaW6ZGSE+XQWElHUB2T b+NnToo+ki1Q=; b=ijMf2zIWOgs00Kgrf2ChPQCSoATnsthuIjW4tvJ41sN4S80 ch/wmdyypyrIWhsRb3+M07B6ryGb5WT7cD/4PM2iOQxNDSO/3QnsB7A7DL3r7QJI JFW5oJSHD+eFMMvcdp4KLwEbgqixWNBuA0bXcHttKMt6ZvDnp/RXjmghU27sqebr 4lFoFjawsOKWaIc7EyDd4g8q1cK3X2qhHMy/TQXHSXX2PvXoWA89yTmNVCq2RM45 qemWHeNuXdX2Wpaolr81jb+yA7iUxYSDN98qsaROM9ZDJ7XYewgo1MhqjoUgxHmj SiPoXbPA1FRncWoIkbC30jR/Keqpy7w+Pi//LQw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=4o9Zjk CN/NV0YaW6ZGSE+XQWElHUB2Tb+NnToo+ki1Q=; b=IJzylD0vzGZRy93CMW9OP1 i3W8UmMJXPBdhi9GyxeZk7X7nIIH6qcmHtuu85DuKmUKhdBCxnISHwOMe6YrnH4e HxOMxI2DypuROM4qFeZe0iIeKkCdFPxvAKV/5Z/6uENP4rgC/xByoZYNHHVSQL+5 iy+0NPJQ1Qz971zVK7esZz9NUNJHqXK4IKzsdj1ASYlerqtCcEAkMY6uj4q2Xtps U8S+dEAFwR/FPYB4eNhzuOtENngisAOc4zgUeRZxOEZZ3v/vXrBNCFv6mVM33KfY LsjpPWuCaBZFjSHkkzL8GfTss7ZlsjFusbEGEXQO7309aIwUFhkbUJbUzNakaELA ==
X-ME-Sender: <xms:W3DVYUQsyZgoMVNMoVTmPN-6nj1aIqdFjf3uw1iop1SvQPOO1M4wgw> <xme:W3DVYRwNE9p79GYcE3yBw4RGr0bG9GPhqinhgmlpVdeqHzH_M0QT8FVYKsVyfeZ1S xk1m1oH1WJ8OOAiZG4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudefhedgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeekteeuieektdekleefke evhfekffevvdevgfekgfeluefgvdejjeegffeigedtjeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvg ht
X-ME-Proxy: <xmx:W3DVYR0VFE1E7KpAKCozkfTD_nQjGfPJfWuNUE-l4fu_YzkdpM9yvQ> <xmx:W3DVYYB3JL67YNbeuCYP-JkKwoHmjhakRD1ChCVM0w6inb4rE_ugaw> <xmx:W3DVYdilJx8StbdTWzQxzPWkAzPY7M6poFnvqDK06zZZInIzwtOn7w> <xmx:XHDVYYtbkdL88CSfFUmzzvaFtrrTB6NCVUGsYVw-ELjInHEsrIhVKw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E282A3C0465; Wed, 5 Jan 2022 05:18:03 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4525-g8883000b21-fm-20211221.001-g8883000b
Mime-Version: 1.0
Message-Id: <22544d5b-08d1-49eb-b82d-36acd468d9d0@beta.fastmail.com>
In-Reply-To: <0ac6a85a-b15d-8efc-550d-b8e3797a10ff@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>
Date: Wed, 05 Jan 2022 21:17:43 +1100
From: Martin Thomson <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/EF4A_p0yvpFJjITPmOFRfTLXqSs>
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 10:18:13 -0000

On Wed, Jan 5, 2022, at 18:24, Eliot Lear wrote:
> 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?

Maybe don't worry about nailing this down.

Any RSWG participant can attempt to call on others to provide input.  That's all that would need to be.

That's not a formal "community review" as defined in process, but it's perfectly fine to ask for input.  Almost by any means or at any time.

What the input is will determine its effect.  If this input arrives during RSAB review, it might cause RSAB members to notice something of CONCERN.  Otherwise, it's more input to discussions.

That is, 

> If the RSAB receives input during its evaluation that indicates a potential problem with a proposal, an RSAB member can ballot a CONCERN position. The CONCERN position can cite the input that was provided and request that the RSWG consider what, if anything, to do to handle this problem.

As far as I can see, that's not a criterion for a CONCERN, it's a path to exercising one of the existing criteria.