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

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 04 January 2022 20:29 UTC

Return-Path: <jmh@joelhalpern.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 21F9D3A085A for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.814
X-Spam-Level:
X-Spam-Status: No, score=-2.814 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, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 nJZGrxlA6X3U for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:29:00 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 1360F3A0831 for <rfced-future@iab.org>; Tue, 4 Jan 2022 12:29:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4JT42g3Pnhz6Gb4F; Tue, 4 Jan 2022 12:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1641328139; bh=b4mvo21g08sSppKplLF8dcN/GoQz8dzsqqNlGNu9R88=; h=Date:Subject:To:References:From:In-Reply-To:From; b=i7WPLxjQCJ1uizbP1Uo2D0byk5zBkZD8Cle/3sDoTr61zv3DJiMEIqDSvDr1PuGrU mMs8MapDPmiLdivM+qYTHykW5XtBB5gQPcZs/uvU0AwB9HMQuDvUTEyWL4h3smua4/ dszodEsNc9rG2ALLd/dgav9ugyIsdEFRbg0FhX3w=
X-Quarantine-ID: <SY4ZyFRVpS59>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4JT42f6HTwz6Gb45; Tue, 4 Jan 2022 12:28:58 -0800 (PST)
Message-ID: <aa0c12f2-d5ba-f8e4-aa81-cfb911081f3c@joelhalpern.com>
Date: Tue, 04 Jan 2022 15:28:57 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org
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> <03f489e1-1070-bbeb-c6fa-1b1dd1bb60b9@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <03f489e1-1070-bbeb-c6fa-1b1dd1bb60b9@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/kiEXsikOd0EOHhkh6Dkg7IxD9Co>
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:29:10 -0000

Huh?  The community as a whole clearly has the right to review the work. 
  Choosing not to participate in a working group does not give up ones 
right to object during last call or the equivalent.

And when we are talking about procedural activities, the range of 
grounds for participants to object seems much larger.

If the larger community is actually engaged enough to raise a clear 
objection during last call of an RFC Strategic document, then it seems 
that the RSAB needs to be able to pay attention to that.  And the RSWG 
needs to pay attention.

And if that causes a stall in changing a policy, so be it.

Yours,
Joel

On 1/4/2022 2:30 PM, Brian E Carpenter wrote:
> On 05-Jan-22 07:52, Michael StJohns wrote:
> ...
>> 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? 
> 
> I'm confused. The RSWG is open to participation by anybody. How is the 
> RSAB going to conclude that the rough consensus of the community as a 
> whole is different from the rough consensus of a WG open to the 
> community as a whole?
> 
> I see an infinite regression here. It's communities all the way down.
> 
>     Brian
>