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

Eliot Lear <lear@lear.ch> Wed, 05 January 2022 06:55 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 184BA3A0C70 for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 22:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level:
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 cAOEEJrs3VBD for <rfced-future@ietfa.amsl.com>; Tue, 4 Jan 2022 22:55:36 -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 BFD7D3A0C8A for <rfced-future@iab.org>; Tue, 4 Jan 2022 22:55:34 -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 2056tSKM2504917 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 5 Jan 2022 07:55:29 +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=1641365730; bh=5VRmEgBoLORCYRlgj1cMjXTQeyq34z/HROFGQvYchRs=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=jKq63TD8omdPTJdZapJ3fMl5Th6tu/x2boabtNZah+TwRtzsvjy1lKsAC+QA3WrmK 6gO53m0vaTQHindWmM7eq/60dUPvZTiSID/lVC+pWc0ChHmfCesKAEprEEInp+EMOZ xg/6DIogrIgFxL+RLsznu+C2B/PLOmx+6Ipscukg=
Message-ID: <48430d65-3f1f-7b58-dd49-7fdca48dec0b@lear.ch>
Date: Wed, 05 Jan 2022 07:55:27 +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: Carsten Bormann <cabo@tzi.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 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> <2C8A6AC2-2CB4-45CE-B796-6D95810F5E61@tzi.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <2C8A6AC2-2CB4-45CE-B796-6D95810F5E61@tzi.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------tcT5jstYk8yuCecQI1QlndgU"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/6693rhlxDJi6D660adQlOw4EIcI>
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 06:55:41 -0000

Good morning, Carsten,

The way the RSAB still has some pretty strong checks in the two bullets 
that were established: anything that might harm a stream and anything 
that might cause harm to the overall series.  We have also added the 
RSAB's ability to trigger a broader review to further involve the 
broader community.  And now we will have a third RSAB check which would 
be failure of consensus of the broader community.

You get to decide: is that enough?

Eliot

On 04.01.22 22:58, Carsten Bormann wrote:
> The current discussion gets the power relationships wrong.
>
> The underlying fiction is that there will be no late process surprises because the RSAB can participate in the RSWG.
>
> If we bind the RSAB’s hands so it no longer can provide actual supervision later, why would the RSAB members' considerations be listened to in the WG process?
>
> Later in the process, the RSAB needs to shut up as long as the new document is not entirely killing the stream/RFC series.
>
> So, essentially, the RSWG chairs call the shots; the RSAB members are essentially powerless.  (Add a boiling frog to the picture if that doesn’t concern you.)
>
> No, we do need working checks and balances.
>
> Grüße, Carsten
>