IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 05 March 2022 20:17 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0071D3A0B6C for <rfced-future@ietfa.amsl.com>; Sat, 5 Mar 2022 12:17:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 EVEXhNZ7yKYn for <rfced-future@ietfa.amsl.com>; Sat, 5 Mar 2022 12:17:54 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FBFF3A0B02 for <rfced-future@iab.org>; Sat, 5 Mar 2022 12:17:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3C6BC38CD1; Sat, 5 Mar 2022 15:27:03 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LRl3g7D7ba0G; Sat, 5 Mar 2022 15:27:01 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0EA7038B20; Sat, 5 Mar 2022 15:27:01 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1646512021; bh=+J0FM3MLHdDWjAIb2lbZo74eYeOxgxGiMNcdSahNeNA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=ivxAiBm00cpmvMdO4S0UxeOWxdekgtm7H8GOSNLGkxuviqJmJ71EQJeKdCdgwtw22 e0i3mSEtuH07u0gq7OAmh+HGYexi4iJqQY+3CXbe5wl7wh2Q+QsFUaDJQwcOwrForl I+EJMeON1TRF/wxwVE0ot9EOC60dmaxgDg7xfrl58iUt3yKseU0wrhDFQ8A7mMkc2/ +DFsTMmjcdZxXI3AbwgCuMHyDIxRN1MhyIAN9PxOXn3P+33/l8w3jDrUK8lMmgphhv sZMPY1Ibnahe+AABl69J+lmc6SWKYOa9E/lHFrxOJq+trXhnRnF7uOCVfEl8S3k8X6 RDZy47TCZXmTA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 952867CD; Sat, 5 Mar 2022 15:17:48 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Lars Eggert <lars@eggert.org>, rfced-future@iab.org, RFC Interest <rfc-interest@rfc-editor.org>
In-Reply-To: <F7300C99-E183-4CB3-AECC-EDCC8028EC03@eggert.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>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 05 Mar 2022 15:17:48 -0500
Message-ID: <17103.1646511468@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/W7TYocrXfWu11dkJ1u8PBK-N8-k>
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: Sat, 05 Mar 2022 20:18:02 -0000

Lars Eggert <lars@eggert.org> wrote:
    > On 2022-3-4, at 5:07, John C Klensin <john-ietf@jck.com> wrote:
    >> Concern 1: There is a suspicion that something nefarious is
    >> going on.

    > The IESG doesn't have this suspicion, and I'd be surprised to learn
    > that a significant part of the community has this suspicion, given that
    > is extremely rare for any individual AUTH48 to result in any
    > significant discussion.

Of course not.
The IESG knows what goes on during AUTH48.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email