Re: [Rfced-future] [rfc-i] RSWG & AUTH48 (was Re: [admin-discuss] Public archival of AUTH48 communications)

Eliot Lear <lear@lear.ch> Wed, 02 March 2022 16:09 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 C40863A0BE6 for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 08:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 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.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 4qZxgxrfKMFM for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 08:09:46 -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 C693B3A0BB3 for <rfced-future@iab.org>; Wed, 2 Mar 2022 08:09:44 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::6] ([IPv6:2001:420:c0c0:1011:0:0:0:6]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 222G9Xow010416 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 2 Mar 2022 17:09:34 +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=1646237375; bh=obOIUoIiJub3hXkpj+brHnh+NXjiMhsaObpNs29JtKQ=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=foTlMIbNpzTMkzdV/FGW0Y0xm+NtqMiBYCcShTurS68QD0L9dM6CTwcFSRvXJc3qx qDq2gigiFkA0zCcmbUoBafNRk2eNexoqatu/k4TVWxtnj405/iYtrXyTaEzmSX3lQg az2/lGtbpd56waSl/VWmrYNbLygXS9DW08BS96xw=
Message-ID: <639057f9-e5f4-e3e1-d74e-538615fa7330@lear.ch>
Date: Wed, 02 Mar 2022 17:09:32 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Lars Eggert <lars@eggert.org>, John C Klensin <john-ietf@jck.com>
Cc: rfced-future@iab.org, "HANSEN, TONY L" <tony@att.com>, RFC Interest <rfc-interest@rfc-editor.org>
References: <164574145917.13799.12710132950530774405@ietfa.amsl.com> <CA+9kkMC+vkyMPbt755Bu0cZHfmY-Pz6CdU1-J+8sBa8cPkA0dg@mail.gmail.c om> <CABcZeBMeRFOU+az=b8QJmD+-4GHivwZenMHEXsrbnamuoEmwEA@mail.gmail.com> <CA+9kkMAg_xbTODu=UE288uxTVhL=+r18p5ywC6ZGaUvpyXO8bA@mail.gmail.c om> <7C442BD6-F634-4129-9764-1BE29382D629@att.com> <8129A65C40CD88E0B5C94AA8@PSB> <7BC3F808-434B-48CF-B96B-0CF7D8B9F3A7@tzi.org> <EEF0F457622EDF74E090BC66@PSB> <BEB26FE0-CC24-4EC2-B7E5-6556A2425A24@eggert.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <BEB26FE0-CC24-4EC2-B7E5-6556A2425A24@eggert.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------5H03tMk8cuFUzBofE5k2IJ0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/zZDvmxFclF6oWNlGwIxMR5Xjsf0>
Subject: Re: [Rfced-future] [rfc-i] RSWG & AUTH48 (was Re: [admin-discuss] Public archival of AUTH48 communications)
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, 02 Mar 2022 16:09:51 -0000

Hi Lars,

On 02.03.22 16:41, Lars Eggert wrote:
> Hi,
>
> (changing the subject and adjusting the CC a bit.)
>
> On 2022-2-26, at 18:50, John C Klensin <john-ietf@jck.com> wrote:
>> Or maybe we postpone spending energy on new lists and tooling --
>> both of which tend to create inertia for keeping "experiments"
>> -- until the RSAB/RSWG are in place and, since AUTH48 is really
>> part of the RFC Production process, allow them to define and
>> oversee the experiment along with the IESG.
> I thought about this a bit, and it's not immediately obvious to me that procedures for AUTH48 handling are under the purview of the RSWG. I could see an argument being made that they are under the purview of the individual streams. There are already minor differences between the streams, for example, the IRSG is in the loop for AUTH48 exchanges or the IRTF stream, but the IESG is not for the IETF stream.
>
> It's true that so far, all streams have used - more or less, see above - the same process for handling AUTH48 processing. If that is intended to be one of the invariants of the RFC series, I agree that any changes would be under the purview of the RSWG, and any changes would then also apply to all streams.
>
> But I could also see a future where one stream would want to revise how AUTH48 should be handled for their documents. If this is something we would like to allow - and personally (with no hats) I think that could be attractive - then I don't see how this could be under the purview of the RSWG, given that they are setting policies for the series (but not the individual streams).

I think the first question you have to ask is whether you have the 
appropriate decision points and processes defined with the RPC.  If you 
do, then this is not a matter for the RPC, since you are not asking for 
them to change anything.  At the point that you are asking them to 
change their processes, that is where the RSWG should come in, barring 
minor stuff.

Eliot