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

Bob Hinden <bob.hinden@gmail.com> Tue, 04 January 2022 20:21 UTC

Return-Path: <bob.hinden@gmail.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 822A93A1F92 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:21:00 -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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 a0HWm8QNVbu9 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 12:20:58 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 C85513A1F91 for <rfced-future@iab.org>; Tue, 4 Jan 2022 12:20:57 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id r17so78441896wrc.3 for <rfced-future@iab.org>; Tue, 04 Jan 2022 12:20:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ksEXMGAqkVC7vwttawD6UYKglAGTIh9BdmrBsWp9gJ8=; b=lMThJyHzMT+PrnVCFOhYhzC+pduMWSo1sX08nRJ/dW742JWD3jaPa7fe2g6BTqjbW+ NEN8Vft/9R/68Pz81TO0G9ze4QuzADVEJr10iBuYIbuvd8i/b7dj3YrniIMlJWsmn4oO 2WowoOwgUHZlXnlNDzA0ac23nEIV0Qmm4YOVIQFrQb/aC2DVajKH0VvhF6Pnb8hCTFmI oXrjaDjFotFHwZ+/bNByfzCMkMrzXy8LF+EhOXRp0RwIxuY5QKdI4AeAfqSlD+t+gnL7 lyZOd3AcHbP8SKqKmvDXbYkViqw/sLDSSBtOa9KtCwoFeCs8+kRHeTTpSNubdLbxjL6Q Hp8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ksEXMGAqkVC7vwttawD6UYKglAGTIh9BdmrBsWp9gJ8=; b=vUXkbNUKqKxGE1LT5LXtLdHSg0wXfCiPauDHqfYS6QDTkn+Zm+bpfbqAc0Kv8yPK0v vRQ3iG89wBP9vdqpJmcW5iGimdwgh1YnSiDc2mjyGPe2NUwvDFNcckQDPF+4LeQU//ke T8JspW8Sy5z+8Ypj+tkrJ1XbGADKo2CbDLzjDucT6xur0Hq/IwzBNzQMlDfKW5+ZdNBd dgvOYK55EKJ3D0qqIf2B9uYIsJHPo+PHkMOmMZDPGTz2wZ64vTiDQZwvxkwHILdkq41W O3GTep705coNjpXpmDAYYAg4yJkZmlAtgLEI8ecrWmhz75npU6eGSv6dgXFWjNTReme6 091w==
X-Gm-Message-State: AOAM533HKoHra9AD9EiTA+egvUky1/Db/h+hDKKroUL9wNxjepbB1xUH gjfLGhAIkcpGRD6pfASwUUs=
X-Google-Smtp-Source: ABdhPJx0zWwUd+GLAq1RZFnUSEIiSOQyFejQ2lMZndHg7/9BLngQ5lK4ao7ntZlsu5Th1QshHuEncA==
X-Received: by 2002:a05:6000:1188:: with SMTP id g8mr35569916wrx.134.1641327654339; Tue, 04 Jan 2022 12:20:54 -0800 (PST)
Received: from [10.0.0.199] (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id c2sm43430414wri.50.2022.01.04.12.20.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jan 2022 12:20:53 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <31F77D23-E927-4401-B8FE-558AD4602575@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D786BAE2-2666-41D0-80DC-AA6F36FB54A3"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Tue, 04 Jan 2022 12:20:50 -0800
In-Reply-To: <03f489e1-1070-bbeb-c6fa-1b1dd1bb60b9@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, rfced-future@iab.org
To: Brian Carpenter <brian.e.carpenter@gmail.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> <03f489e1-1070-bbeb-c6fa-1b1dd1bb60b9@gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/xbymwL5OO_we0I3NNYpImSvl9pg>
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:21:01 -0000

Brian,

> On Jan 4, 2022, at 11:30 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> 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.

Isn’t it for the same reason the IETF does an IETF Last Call after the a working group last call?

Bob