Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards]

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 09 December 2024 20:22 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F7DC1519BA for <ietf@ietfa.amsl.com>; Mon, 9 Dec 2024 12:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.654
X-Spam-Level:
X-Spam-Status: No, score=-1.654 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 VCMEvqPYCUuL for <ietf@ietfa.amsl.com>; Mon, 9 Dec 2024 12:22:45 -0800 (PST)
Received: from mail-qv1-f49.google.com (mail-qv1-f49.google.com [209.85.219.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF0FC180B5D for <ietf@ietf.org>; Mon, 9 Dec 2024 12:22:45 -0800 (PST)
Received: by mail-qv1-f49.google.com with SMTP id 6a1803df08f44-6d8a2d0588bso41870166d6.2 for <ietf@ietf.org>; Mon, 09 Dec 2024 12:22:45 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733775764; x=1734380564; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8jUCMPP6alS04FX3wLj7ZRkibgPJvp23BzJrKChb9fM=; b=o6xANtyqlz08bO0mMB3OanNkCrdnzTmBE7NfRWUGhPiRO7MlJk5iK61/yHY1lhtNb+ XlNu4M8e88Tmnz4fLgTHDpeS4bYYx6haMw/kiQXNuECJ/ZMsETRT1a3yMcBBFBOBgurW G/YdhjV+gDhR/qBD/HlcCay33WZPMx/FrYiWqHY5JiEBqG90Lq7kRCK/6J4/r0yGXkH0 86ElQgA8OF4OnN/d1i9DlDI9YkvdxKxagRXYEQjqJHnj/K5bVSEIU6v/ATFGuSJhEZGt 7T3ePbcpTlzdmE8r+SLo/4dWdk/UJJm9NnDooHXzu7u4ROQ6ica9OznuDwrolLAlNvU8 Y5CA==
X-Forwarded-Encrypted: i=1; AJvYcCWb+SmZdLJJPJFChaB2NLnlViG/FIxDh9webxIeWIvv9PpffuZNLEkFDluy4uNaQOLrFA3E@ietf.org
X-Gm-Message-State: AOJu0YxlG+jFuqCcYyS4b+qMN+lTSGn4c2cxguyBDROrzX5Sv3H6nqB9 jc0eFQ9B/jJ8rFnXJrhGJDJqM1fDOh7gvU4k6zRmPpDPIO+PJm2J5fMBwAGDO9USEL5fE/jCgsd 1qeHHoZI057iV7rGTKTfFo96xLGc=
X-Gm-Gg: ASbGnctOJMQQeCmkgpUjhtuEwwc4C+i9/MeUkgL16HcmxfWpQcpLq55gaCXIa1xGvQm 2XgAU9IqU1CmCkvFqRu3PPIHk/zP5ClqFyZVKFNgwY+iml9kpenCEAVfWhOaNrqT/FkmE
X-Google-Smtp-Source: AGHT+IGZ+NH2RyKN8jdm7TATC3yypB2EJ8+oWK7BjLzcBLjpYg7c5cFqLgAIbR3pC0OgLkedpfMf9ssotRuRzdIjgvE=
X-Received: by 2002:a05:6214:ac1:b0:6d8:7a1d:4e95 with SMTP id 6a1803df08f44-6d91e3a4ee9mr34386016d6.29.1733775764559; Mon, 09 Dec 2024 12:22:44 -0800 (PST)
MIME-Version: 1.0
References: <BE95E617-C929-43BA-BB40-41E189A8158B@akamai.com> <10065.1732826193@obiwan.sandelman.ca> <CACsn0cmWVeFdJ3dzMj5SV4XpJF4rssULtfQ1moeefoq-Evhk=g@mail.gmail.com> <CAGL5yWb=tLvMOYFKT3ffVbcy7BAD=i4B0VHEUdkvwRvZ3X3Bsw@mail.gmail.com> <m2mshh4v8l.wl-randy@psg.com> <CABcZeBMjxNbBMYU2p3_a8-5VCExgmY-7XLof7die05YOEX-38A@mail.gmail.com> <70419651-6443-4393-9ca1-8a1c98a68db0@cs.tcd.ie> <CABcZeBNtBRxi5zSf9OvUip2AtyVD6Wt9+kQESuUzo-=Kur9+ZQ@mail.gmail.com> <fac981d9-2fe9-4a84-8af1-845acd72af58@cs.tcd.ie> <14124.1733073164@obiwan.sandelman.ca> <d52ee080-814b-46fd-9e0f-41349941eeac@cs.tcd.ie> <1384.1733077486@obiwan.sandelman.ca> <m2frn53g8h.wl-randy@psg.com> <a8290be2-9713-4fd3-914c-1d8090d27d38@huitema.net> <d37dd3c7-ebc3-485f-997c-e6301782a8c4@gmail.com> <bf896cdd-7f49-420b-b499-f1597eaf9bcd@lear.ch> <7A3A7128-FEB3-4208-A5CF-A10BE651CE89@strayalpha.com> <4e639df1-d236-4b8a-bde7-d091ce0654b4@lear.ch> <aeea2e00-7793-4317-9704-30ca90b3f290@gmail.com> <49167428-a8ba-454d-8b17-708fa9c63987@lear.ch>
In-Reply-To: <49167428-a8ba-454d-8b17-708fa9c63987@lear.ch>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 09 Dec 2024 15:22:33 -0500
Message-ID: <CAMm+LwjN+WNWsZ1zit1P_0PTXi9NunZ4znuNE8ALDQT0iH7utA@mail.gmail.com>
Subject: Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards]
To: Eliot Lear <lear@lear.ch>
Content-Type: multipart/alternative; boundary="0000000000009120090628dc2064"
Message-ID-Hash: 4IPWGI3YMST5Q2BSBVWPQT6QLNYLVRHY
X-Message-ID-Hash: 4IPWGI3YMST5Q2BSBVWPQT6QLNYLVRHY
X-MailFrom: hallam@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Christian Huitema <huitema@huitema.net>, Randy Bush <randy@psg.com>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YU1Q5FmMpL7JO65sfJA1fn_f1EE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

On Mon, Dec 9, 2024 at 2:57 PM Eliot Lear <lear@lear.ch> wrote:

> Yes. and now we are repeating the SAAG discussion in its entirety.
>

Like we don't repeat it there every 6 months.

I haven't waded in this time round. But as I always say, the solution to
these issues is to design the protocol so you can use an OID as an
algorithm identifier.

The big advantage of OIDs for algorithms is that anyone can define them
without IETF involvement and thus the issue of endorsement simply doesn't
come up.

XML Signature uses URIs and there is an OID URI.

For other protocols which use labels, I would construct a single registry
for all algorithms with the JOSE and COSE tags and tell all apps going that
route to use them. And I would make that specification required, again to
avoid endorsement.