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

Christian Huitema <huitema@huitema.net> Fri, 04 March 2022 20:03 UTC

Return-Path: <huitema@huitema.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 6EEA33A109E for <rfced-future@ietfa.amsl.com>; Fri, 4 Mar 2022 12:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 vWVaBgkbJ5mn for <rfced-future@ietfa.amsl.com>; Fri, 4 Mar 2022 12:03:05 -0800 (PST)
Received: from mx36-out20.antispamcloud.com (mx36-out20.antispamcloud.com [209.126.121.68]) (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 C62F73A133E for <rfced-future@iab.org>; Fri, 4 Mar 2022 12:02:31 -0800 (PST)
Received: from xse206.mail2web.com ([66.113.196.206] helo=xse.mail2web.com) by mx257.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nQE8B-0001wC-J2 for rfced-future@iab.org; Fri, 04 Mar 2022 21:02:29 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4K9Jfn0CKtzBxb for <rfced-future@iab.org>; Fri, 4 Mar 2022 12:02:25 -0800 (PST)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nQE88-0004gL-TD for rfced-future@iab.org; Fri, 04 Mar 2022 12:02:24 -0800
Received: (qmail 21285 invoked from network); 4 Mar 2022 20:02:24 -0000
Received: from unknown (HELO [10.32.61.201]) (Authenticated-user:_huitema@huitema.net@[192.0.32.236]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <john-ietf@jck.com>; 4 Mar 2022 20:02:24 -0000
Content-Type: multipart/alternative; boundary="------------qik71p1fmrsJRWmepsK0UE0n"
Message-ID: <5b2322fd-b4b9-dd88-b82f-72f486714009@huitema.net>
Date: Fri, 04 Mar 2022 12:02:22 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: John C Klensin <john-ietf@jck.com>, Lars Eggert <lars@eggert.org>
Cc: rfced-future@iab.org, Michael Richardson <mcr+ietf@sandelman.ca>, Carsten Bormann <cabo@tzi.org>, Toerless Eckert <tte@cs.fau.de>, RFC Interest <rfc-interest@rfc-editor.org>
References: <CA+9kkMAg_xbTODu=UE288uxTVhL=+r18p5ywC6ZGaUvpyXO8bA@mail.gmail.com> <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> <11721.1646248947@localhost> <af3a9d13-7ec2-4e48-355a-a3870af06361@joelhalpern.com> <a52626d5-13aa-ab1a-cb13-282bd9bcf812@gmail.com> <269b5f09-4840-b038-085c-839e0a1c3c6b@huitema.net> <YiBc6Mjj2++jxE0h@faui48e.informatik.uni-erlangen.de> <D5AC5684-506B-4214-9678-75B5C1FCBED2@tzi.org> <30761.1646334921@localhost> <D1908D64BC74C4F3C9444271@PSB> <F7300C99-E183-4CB3-AECC-EDCC8028EC03@eggert.org> <D4925436BB27594C0DB4B09D@PSB>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <D4925436BB27594C0DB4B09D@PSB>
X-Originating-IP: 66.113.196.206
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.14)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+BNOkGOr1TeS9PWtp8DlmhPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5yXEnUqtuiszqcStXlDoE9S53HEEk0VSrq03gtFxbC/KmYM KJORD5FW9cMJtHf5fuvKLMyCg2dNZJAK3gbNiIydSxIRXVMlFuiz/acFNeeXtxN2fFxZWB9eYgpR BRu3UlDHMLIJYRi1cXH9Dbm+IxLV6nEMLpv52qIFdDFnq6/4WZotTbzF8bFslzcWfB/84WWaVarp Z0LfU2AP/MzLXlymkVWClPVvbW5lVyQanRxw5hTHswbbB/ha+ZWrSAi8SkwqWAikMcSxTAWn8RCv ieGEqjG/gXZAaRh1X6LVetRf2ZYIiHqfCgG4wrA3w4/kQTYKxDHA9JN9J4k4XZq11JQkMemT4rxn nByU11Ftkqf3f/PF3GUV+KdBBqrnCX8j0Gi8Ksk+aedMfNWSnJswrtlNtZo3HPHi5Q+jjsF5dcBx ehWYzrkgsp4/Fysgb2cPV4IH0+lPwKr4i5mAANUcVraZYOaeuiH/yEdZH8S1+TgcJBOjh0vPxcQO jKKOrYIQYpwamUdylUIKhf3z2GAHxH7IBAaAB9SiL80iwHtGBZiikgJ7Yk+SWN8eNDNBlkTeVa30 MNwaAJ7/nKBmfVqlmSChKK8qgoX3qtqBY7olcAAV8pXloqisSitb6n6JVjosdW/TulJRptMnEIdG JW7dfhGq92PNDpgLsd6Ddd/s7VM53iCaPgdMN395ejRWAn+TrFYOtp+q3yU+z72+fnpodgpDqAzV S5LId3k4fKMW2gs3k8cbgghBQczIF2MfQP440lBmMRr+w2X69ygMahiTQMBd7klAcqtAG18BozZn +czSbPoPFZIShBSdpVJW5HbjQTCUIzbw71BPKv8cPtVshTSLr6YHJu91A3avrF49rf9JcoEpejCA XczArXyV+OFXiMtbLPp9n350Mbemie5JWWm/MpxAyl4q1x5O0+PBD/gPmWjXVA9S7TnWXDlmMpVd cwCFwrnT0GQK/7labXRdXAB+MS+4ayUpOtEhdxekWDmK9g==
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Vz4qNWmtFXtQfK6LTyeRSsfc6Aw>
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: Fri, 04 Mar 2022 20:03:15 -0000

On 3/4/2022 10:46 AM, John C Klensin wrote:

>> This is not a concern for the IESG. We have seen no evidence
>> that the AUTH48 step is somehow systemically broken. (It does
>> often take longer than 48 hours - but that has been the case
>> for decades.)
> I did not say "systematically broken" or anything like it.  Over
> the years, I've seen several cases in which questions about
> clarity or ambiguity have come up during AUTH48 where the
> possible solutions could have substantive technical
> implications.  The decisions that have been made at that stage
> have almost always been made based on beliefs about what the WG
> intended or what the WG would say if asked.  AFAICT, those
> decisions have almost always been made correctly made -- I don't
> believe that I have ever (at least in the last couple of
> decades) heard of participants in a WG complaining that a
> document, as published, was not what they intended. However, I
> still think it is reasonable to be anxious about that way of
> making such decisions (although, frankly, not very anxious).

The process would be most transparent if the published version was 
exactly the version approved by the IESG. Or "almost exactly", if the 
changes were entirely predictable, such as removing text marked as 
"please remove before publication". But in my mind, rewriting paragraphs 
does not belong there.

-- Christian Huitema