Re: [Lake] Standards Action with Expert Review (Re: Lars Eggert's Discuss on draft-ietf-lake-edhoc-20: (with DISCUSS and COMMENT))

Carsten Bormann <cabo@tzi.org> Tue, 22 August 2023 09:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: lake@ietfa.amsl.com
Delivered-To: lake@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7647CC151065; Tue, 22 Aug 2023 02:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4CcbVUI6hx31; Tue, 22 Aug 2023 02:00:43 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AEFCC14F736; Tue, 22 Aug 2023 02:00:42 -0700 (PDT)
Received: from smtpclient.apple (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RVNbp1BzTzDCfm; Tue, 22 Aug 2023 11:00:38 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ACF4B182-7B66-45ED-AAB1-04C3D4513F29@eggert.org>
Date: Tue, 22 Aug 2023 11:00:27 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-lake-edhoc@ietf.org, lake-chairs@ietf.org, lake@ietf.org, malisa.vucinic@inria.fr
Content-Transfer-Encoding: quoted-printable
Message-Id: <2321B262-9400-4326-8C6E-860681E4EC64@tzi.org>
References: <169269257169.1146.6134251465161445844@ietfa.amsl.com> <70BC5E9D-2FDD-4CA1-866D-385FF8D403D7@tzi.org> <ACF4B182-7B66-45ED-AAB1-04C3D4513F29@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/C6uONgcmrs1bfo6cb2TZEW4UDKI>
Subject: Re: [Lake] Standards Action with Expert Review (Re: Lars Eggert's Discuss on draft-ietf-lake-edhoc-20: (with DISCUSS and COMMENT))
X-BeenThere: lake@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Lightweight Authenticated Key Exchange <lake.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lake>, <mailto:lake-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lake/>
List-Post: <mailto:lake@ietf.org>
List-Help: <mailto:lake-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lake>, <mailto:lake-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Aug 2023 09:00:46 -0000

On 22. Aug 2023, at 10:49, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> On Aug 22, 2023, at 11:42, Carsten Bormann <cabo@tzi.org> wrote:
>> I seem to remember that we had IANA registrations made by Standards Action where none of the authors, IESG members, or other reviewers were aware of a specific detail in the registration requirements.
> 
> do you have details?

That was a while ago, so I remember that it happened, but no longer the details.
(And I don’t think there is a convenient search term.)

> Given that it was a Standards Action, I'm surprised if authors and the IESG were not ware of something, given that they author and review the I-D (in addition to a Last Call).

Some registrations are to “foreign” registries that are not that much related to the technology under standardization.
The expert may be aware of some details that really are not common knowledge in the realm of the technology under standardization, and the mere fact that the foreign technology is coming up in a registration may not sufficiently alert the ADs for that technology to possibly get a specific review.

>> Do we now have processes in place that would automatically involve a registry expert in a Standards Action?
> 
> No. The theory was/is that IETF Last Call and IESG Review provide more review than Expert Review does, so it seems redundant. If nat belief is no longer held, we should update the relevant process.

More review, certainly.  But the designated experts probably are uniquely positioned here so this is not just a quantitive issue.

I believe an update would be beneficial.
Until then, "Standards Action with Expert Review” works for me as a workaround.

Grüße, Carsten