IETF Logo Mail Archive

[saag] Re: New Version Notification for draft-rsalz-crypto-registries-00.txt

Damien Miller <djm@mindrot.org> Thu, 28 November 2024 17:14 UTC

Return-Path: <djm@mindrot.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17D22C169432; Thu, 28 Nov 2024 09:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_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=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 jvUisUP0eMpE; Thu, 28 Nov 2024 09:14:29 -0800 (PST)
Received: from bus.compute.dc.uq.edu.au (bus.compute.dc.uq.edu.au [130.102.188.58]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1CDBC1654FE; Thu, 28 Nov 2024 09:14:26 -0800 (PST)
Received: from smtp2.compute.dc.uq.edu.au (smtp2.compute.dc.uq.edu.au [10.208.138.89]) by bus.compute.dc.uq.edu.au (8.14.5/8.14.5) with ESMTP id 4ASHEBvc118885; Fri, 29 Nov 2024 03:14:11 +1000
Received: from mailhub.eait.uq.edu.au (hazel.eait.uq.edu.au [130.102.60.17]) by smtp2.compute.dc.uq.edu.au (8.14.5/8.14.5) with ESMTP id 4ASHEBd4037902 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Nov 2024 03:14:11 +1000
Received: from haru.mindrot.org (haru.mindrot.org [130.102.96.5]) by mailhub.eait.uq.edu.au (8.15.1/8.15.1) with ESMTPS id 4ASHEARQ025415 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Nov 2024 03:14:10 +1000 (AEST)
Received: from localhost (localhost [127.0.0.1]) by haru.mindrot.org (OpenSMTPD) with ESMTP id 02a559b5; Fri, 29 Nov 2024 04:14:10 +1100 (AEDT)
Date: Fri, 29 Nov 2024 04:14:10 +1100
From: Damien Miller <djm@mindrot.org>
To: Paul Wouters <paul.wouters@aiven.io>
In-Reply-To: <2A5A96D6-7F86-4B55-99D4-39A42B1CA869@aiven.io>
Message-ID: <a9585852-acb5-b7f3-2f62-0e53755b4324@mindrot.org>
References: <SY8P300MB0711C796AB6095C788556516EE292@SY8P300MB0711.AUSP300.PROD.OUTLOOK.COM> <2A5A96D6-7F86-4B55-99D4-39A42B1CA869@aiven.io>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.75 on 130.102.60.17
Message-ID-Hash: L5RB4R475Y7JYKEPNXE66W45M7AAYCPQ
X-Message-ID-Hash: L5RB4R475Y7JYKEPNXE66W45M7AAYCPQ
X-MailFrom: djm@mindrot.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-saag.ietf.org-0; header-match-saag.ietf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Tero Kivinen <kivinen@iki.fi>, Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, saag@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [saag] Re: New Version Notification for draft-rsalz-crypto-registries-00.txt
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/JuLbYJvSgWqTHiWneQdPjIMo4QQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

On Thu, 28 Nov 2024, Paul Wouters wrote:

> Sure, but the damage by leopards in this case isn't pushed to the IETF
> by rubber stamping it with an RFC.
>
> An Internet-Dreft is as stable and findable as an RFC, and does not
> come with the implied endorsement of the IETF.

Publishing an RFC alone isn't really an endorsement though in my
opinion, just an indication that there was enough community desire to
write down a standard.

Actual endorsement (again IMO) by the IETF comes in the form of
Standards Track RFCs, BCPs, making RFCs mandatory-to-implement, etc.

-d

v2.29.0 | Report a Bug | By Email | System Status