Re: [kitten] Murray Kucherawy's No Objection on draft-ietf-kitten-krb-spake-preauth-11: (with COMMENT)

Russ Allbery <eagle@eyrie.org> Sat, 20 January 2024 18:19 UTC

Return-Path: <eagle@eyrie.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F12C3C14F5F8; Sat, 20 Jan 2024 10:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 rszapVphvpUo; Sat, 20 Jan 2024 10:19:23 -0800 (PST)
Received: from haven.eyrie.org (haven.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3539]) (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 60B04C14F5E0; Sat, 20 Jan 2024 10:19:21 -0800 (PST)
Received: from wanderer.eyrie.org (unknown [69.4.128.97]) (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 haven.eyrie.org (Postfix) with ESMTPS id 4ABDD118002; Sat, 20 Jan 2024 10:19:19 -0800 (PST)
Received: by wanderer.eyrie.org (Postfix, from userid 1000) id 7F5CE2ED5297; Sat, 20 Jan 2024 10:19:17 -0800 (PST)
From: Russ Allbery <eagle@eyrie.org>
To: Nico Williams <nico@cryptonector.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, kitten@ietf.org, kitten-chairs@ietf.org, draft-ietf-kitten-krb-spake-preauth@ietf.org, The IESG <iesg@ietf.org>
In-Reply-To: <Zav47pSFM0Y/r+wJ@ubby> (Nico Williams's message of "Sat, 20 Jan 2024 10:46:38 -0600")
Organization: The Eyrie
References: <170559100930.21281.8142882686300667918@ietfa.amsl.com> <d5d9e798-c6c1-4f15-a1f2-4e08580a70c4@mit.edu> <CAL0qLwZUOepsqoGY+kb5tB8CBc=EOYAtoSXk35XAMD4LF5Hw8w@mail.gmail.com> <ZaoDKjMhV3g1w4pp@ubby> <CAL0qLwbueeYOCQSgapa6yx1DzbXLYXuNUMzUvH3m1X-LzaNNxA@mail.gmail.com> <Zav47pSFM0Y/r+wJ@ubby>
User-Agent: Gnus/5.13 (Gnus v5.13)
Date: Sat, 20 Jan 2024 10:19:17 -0800
Message-ID: <87v87nuau2.fsf@hope.eyrie.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/aEmZmkQkrSsoMGSXYxqoaCDgckA>
Subject: Re: [kitten] Murray Kucherawy's No Objection on draft-ietf-kitten-krb-spake-preauth-11: (with COMMENT)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jan 2024 18:19:27 -0000

Nico Williams <nico@cryptonector.com> writes:
> On Fri, Jan 19, 2024 at 10:39:32PM -0800, Murray S. Kucherawy wrote:

>> If I'm an implementer following a link from an IANA registration to an
>> I-D, but then there's a big colorful warning that the I-D is expired,
>> wouldn't it be reasonable for me to believe that the registration, the
>> document, or both are no longer valid?  This seems really strange to
>> me.  I would expect to find a link to something current.

[...]

> But this registry is Expert Review, which means NOT EVEN any
> specification is needed, not even an expired I-D.

I think this is the key point.  The requirement is for Expert Review.  An
I-D is a mechanism for getting expert review and documents precisely what
the expert is reviewing.  In that sense it's a lot better than some expert
reviews, where a specification may not be easy to find after the fact.

The fact that the I-D has then expired matters for stronger requirements,
like having a published standard, but it seems fairly irrelevant for
expert review.  That the I-D subsequently expired doesn't change the fact
that it received expert review, and the expired I-D is documentation of
what was reviewed at the time (and hence is still useful).

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>