[TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt

Simon Josefsson <simon@josefsson.org> Sun, 01 March 2026 14:21 UTC

Return-Path: <simon@josefsson.org>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2F33FC0FF7E3 for <tls@mail2.ietf.org>; Sun, 1 Mar 2026 06:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=josefsson.org header.b="gh71h2H1"; dkim=pass (2736-bit key) header.d=josefsson.org header.b="L18PjFzS"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yfymlLgTmRZT for <tls@mail2.ietf.org>; Sun, 1 Mar 2026 06:21:51 -0800 (PST)
Received: from uggla.sjd.se (uggla.sjd.se [IPv6:2001:9b1:8633::107]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 08B7DC0FF733 for <tls@ietf.org>; Sun, 1 Mar 2026 06:21:48 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=ed2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=GIypP+TFa9yZMloI8hYRsrTvcL74LkUo/C3ekf3tjc8=; t=1772374902; x=1773584502; b=gh71h2H1vMKKIeDY8Zo1fADkpq1ZZPU0oIZvDFoIhMtjo8IHNd5vq3FJIPJpp6TOrwWgokNAXLt SrmUNq6GkDQ==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=rsa2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=GIypP+TFa9yZMloI8hYRsrTvcL74LkUo/C3ekf3tjc8=; t=1772374902; x=1773584502; b=L18PjFzSnV29Tj7eo/jgwJoCVYemvpxfGGYOqC+GOlZtwa2l4T86pnkhVu4TFwtB0s2hFUnaosW eCxJgB22MYMN4yrjKj2DnOB3BKHmUJYBHU7rZQg2tA2vylTASFKiDc3vSzuWDalUiYlp4zUtuRX2G PkmXQlWWa6SFtCsxTLRIffZ0hdWMNx0FpqnQAjYoXS7aqrLvkb+XA2+IdATL7sCbmAgxVtPh9OUVk /D9ucetPBjwIOsh9T/PsZd8rzQLdepL/kdtieX4Kf8YAYIILaRTYeioQXl4mKQfd1hWDDvMZTgGFR 2Ry6Be6rFGkUd1AUMrnsz8ezAsFRm4fYLlhIYaStm5nVgkPimgsE6KGezK7MLLSz4PiIq7P6/yZpb A3DjqVF5TW6p6vIX/e+VH0MqYQN307DrW1JupoSC9Fy/CPNnrUsC5LFzyBO5DEnqw1i74J8aC;
Received: from h-178-174-130-130.a498.priv.bahnhof.se ([178.174.130.130]:55286 helo=frallan) by uggla.sjd.se with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <simon@josefsson.org>) id 1vwhfo-00CIIk-M0; Sun, 01 Mar 2026 14:21:32 +0000
From: Simon Josefsson <simon@josefsson.org>
To: Richard Barnes <rlb@ipv.sx>
In-Reply-To: <CAL02cgTob3hYSMmhOgiMiUZu0MfLRM-hV-4zQeAXp3Su=7ckCw@mail.gmail.com> (Richard Barnes's message of "Mon, 23 Feb 2026 14:55:41 -1000")
References: <177189438640.2182161.16660142956175423236@dt-datatracker-6ff7c68975-7k42g> <CAL02cgTob3hYSMmhOgiMiUZu0MfLRM-hV-4zQeAXp3Su=7ckCw@mail.gmail.com>
OpenPGP: id=B1D2BD1375BECB784CF4F8C4D73CF638C53C06BE; url=https://josefsson.org/key-20190320.txt
X-Hashcash: 1:23:260301:tls@ietf.org::DGxFwPlPBVrOHiyi:67rt
X-Hashcash: 1:23:260301:rlb@ipv.sx::yrOm7w3r9SIFiOrH:iioQ
Date: Sun, 01 Mar 2026 15:21:52 +0100
Message-ID: <875x7ftytb.fsf@josefsson.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Message-ID-Hash: QTSOVISDDZAFN6IQTSTXFKIRXAIBMPRW
X-Message-ID-Hash: QTSOVISDDZAFN6IQTSTXFKIRXAIBMPRW
X-MailFrom: simon@josefsson.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "<tls@ietf.org>" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/qWhUXSSI4o7IYCvS1xCjuGb65iU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

+1

I suggested to publish the non-hybrid ML-KEM document outside of the TLS
WG, and your proposal turns that into the new general rule.

In fact, I'd go further to suggest that we go back to the olden time
without the 'Recommended' column.  Anyone can register stuff at the
IANA.  Only RFCs turn registered algorithms into recommendations.
Everything else is not recommended implicitly.

I never understood/agreed with the justification for the 'Recommended'
column, and it seems to have consumed a significant amount of time in
both the TLS WG and SSHM WG.  Introducing it looks indistinguishable
from a successful attack on the use of IETF engineering time.

/Simon

Richard Barnes <rlb@ipv.sx> writes:

> Hi TLS folks,
>
> Those who have worked with me know that I hate doing unnecessary work.  It
> occurred to me that the TLS WG has been doing a lot of unnecessary work on
> drafts that just register crypto algorithms.  This draft proposes that we
> shouldn't do that.
>
> Submitted for your consideration,
> --Richard
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Mon, Feb 23, 2026 at 2:53 PM
> Subject: New Version Notification for
> draft-barnes-tls-this-could-have-been-an-email-00.txt
> To: Richard Barnes <rlb@ipv.sx>
>
>
> A new version of Internet-Draft
> draft-barnes-tls-this-could-have-been-an-email-00.txt has been successfully
> submitted by Richard Barnes and posted to the
> IETF repository.
>
> Name:     draft-barnes-tls-this-could-have-been-an-email
> Revision: 00
> Title:    Stop Doing Cryptographic Algorithm Drafts when Email to IANA is
> All You Need
> Date:     2026-02-24
> Group:    Individual Submission
> Pages:    5
> URL:
> https://www.ietf.org/archive/id/draft-barnes-tls-this-could-have-been-an-email-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-barnes-tls-this-could-have-been-an-email/
> HTML:
> https://www.ietf.org/archive/id/draft-barnes-tls-this-could-have-been-an-email-00.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-barnes-tls-this-could-have-been-an-email
>
>
> Abstract:
>
>    People keep pitching drafts to the TLS Working Group where the only
>    thing the draft does is register a code point for a cryptographic
>    algorithm.  Stop doing that.  It's unnecessary.  Write an email to
>    IANA instead.
>
>
>
> The IETF Secretariat
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>