IETF Logo Mail Archive

[Atp] Re: Possible changes for IETF version

"Maxine S. Fritz" <max+ietf@mfzx.net> Thu, 09 July 2026 20:39 UTC

Return-Path: <max+ietf@mfzx.net>
X-Original-To: atp@mail2.ietf.org
Delivered-To: atp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id ABD1E11438EA3 for <atp@mail2.ietf.org>; Thu, 9 Jul 2026 13:39:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783629547; bh=lZaodojDxyAtifzWGEnPCmN9/OMe+MSIO5vGXqhprv8=; h=Date:Subject:To:References:From:In-Reply-To; b=tRz7DjijfoTMx650PgV1Acl9hN/9ZtluC1RtnoB97grCcbnCesTlR+jFg+FLIwF/P wzk6HDs1eqo/Pcq4Ut67b5A7rUdYJr1v2FIEPz5v5wmBrlMH+OU2Avv+x1curW77lO /o+/NsjZMkcE7sZ2bkl3odBDI6FtjGFGWMXKIWm4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=mfzx.net header.b="Br6zDED7"; dkim=pass (2048-bit key) header.d=purelymail.com header.b="SF01OnOK"
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 jvU9oTOxCce4 for <atp@mail2.ietf.org>; Thu, 9 Jul 2026 13:39:07 -0700 (PDT)
Received: from sendmail.purelymail.com (sendmail.purelymail.com [34.202.193.197]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 47DD811438E9E for <atp@ietf.org>; Thu, 9 Jul 2026 13:39:07 -0700 (PDT)
DKIM-Signature: a=rsa-sha256; b=Br6zDED7JvvtYM8Pu2AnBXvslTrNB7OwYJWx/S3aTPgbvkQgCJu3QmnZRDcc3xGIqmvhfwXVsdkEvzK/CLwH7HW5cgScT/1sRKgSvgvnCCIBHJ8nrjjyEOAYGMqhy2qLE/H0W3IcfnT78oCxLqIKLYEQOFscTAFYc89k/22wjsEtSxucRtl7tBRGbemqdgVMEjhtQTARVT50EWSDsJqSrat0GLzEa2ixSiOuPte2bOeDDZi9dmONNtvrEw7VnrIA7QnGi2iwnjjkMAfndhnJd2tPuZvBry78i5rGEB4wyt7Jb6+Hd7cIiAAMYz5HJkBa8RX3JYYwVZaNhM5gViVLUQ==; s=purelymail1; d=mfzx.net; v=1; bh=lZaodojDxyAtifzWGEnPCmN9/OMe+MSIO5vGXqhprv8=; h=Received:Date:Subject:To:From;
DKIM-Signature: a=rsa-sha256; b=SF01OnOKhmeXVDtPtufLt9FYNnRrrEfA3lv+khJosUOTyw7WEH5jqXvR0IKvx6+lZwYXb8XNl+smxxRouaaFkJFfLqtK2pjUqsa2UbW8Joo5hRO7e90y3JSfmpPI5btsetKkkjYDAzTmTkC22UTyGPAwCWFMTaQ/TBhZSgCWNcX2Jk9d1cYzybqSMoRtWnO4ih5D/PXIJmplBNZWkvPLUhfGWamoMOYs6v9WmU0qcgfJJZ26YUutD/ywttOMrrUhqEJCVDNnNK6Ji8+cNONdcL1DDTP3aM0kly91H2dK2EF/Wjk+NY6j+r6GF5bJskdEzKhhZ+TlEAEX+2hgO73F1w==; s=purelymail1; d=purelymail.com; v=1; bh=lZaodojDxyAtifzWGEnPCmN9/OMe+MSIO5vGXqhprv8=; h=Feedback-ID:Received:Date:Subject:To:From;
Feedback-ID: 301779:25725:null:purelymail
X-Pm-Original-To: atp@ietf.org
Received: by smtp.purelymail.com (Purelymail SMTP) with ESMTPSA id -943586725 for <atp@ietf.org> (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Thu, 09 Jul 2026 20:39:05 +0000 (UTC)
Message-ID: <0acf8c37-995c-4ceb-b109-ae0ffa3fbbd5@mfzx.net>
Date: Thu, 09 Jul 2026 15:39:03 -0500
MIME-Version: 1.0
To: atp@ietf.org
References: <CAGZK71=G+QCjCtNxWH=1fE+mNpO4Lhm_X+bD4MUPc9vKmqhWkg@mail.gmail.com> <CABcZeBNN2cVvEwZ907pyyCwgOGUj8TEkyBaW-0Hu5JkV5k+-Bw@mail.gmail.com> <b3eaabc8-8712-479e-9c18-50056f18c649@mfzx.net> <CABcZeBPazLJK06Xo85HBPkyarX+cv+RuYy-2AHYrprJ6BS6c0g@mail.gmail.com> <55825515-5e61-4331-b6cb-876ea3a87e4e@mfzx.net> <CABcZeBMQAVc5Q6e66kAtL9gW03pviF9O=9uw2WJHsT1D12mpsA@mail.gmail.com> <865f7312-880b-47fe-80fa-fec524ed746b@mfzx.net> <CABFYohi+2Vr3MaWZhYhmS3+EW2r3d_4xndwRreQm-KT2+AYXBg@mail.gmail.com>
From: "Maxine S. Fritz" <max+ietf@mfzx.net>
Content-Language: en-US
In-Reply-To: <CABFYohi+2Vr3MaWZhYhmS3+EW2r3d_4xndwRreQm-KT2+AYXBg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by Purelymail
Message-ID-Hash: QMDTWODZQLBCFOECCXNQCH3QNSENPR7E
X-Message-ID-Hash: QMDTWODZQLBCFOECCXNQCH3QNSENPR7E
X-MailFrom: max+ietf@mfzx.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Atp] Re: Possible changes for IETF version
List-Id: Authenticated Transfer <atp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/atp/57i_BfKt9sPW78T9VmvwwVew7ow>
List-Archive: <https://mailarchive.ietf.org/arch/browse/atp>
List-Help: <mailto:atp-request@ietf.org?subject=help>
List-Owner: <mailto:atp-owner@ietf.org>
List-Post: <mailto:atp@ietf.org>
List-Subscribe: <mailto:atp-join@ietf.org>
List-Unsubscribe: <mailto:atp-leave@ietf.org>

Bryan Newbold <bryan@blueskyweb.xyz> wrote on 2026-07-09 14:33:23 -0500:
> As a middle path, we could make support for K-256 keys mandatory on the validation side, but
> recommend against their use for new accounts and keypairs. I think this could help with
> signaling intent and getting broader ecosystem convergence. This could be done in the current
> REPO document cryptography appendix, or in an "operational best practices" document.
I'm in favor of this transition path; Ed25519 as the recommended replacement for K-256 is great.

-- 
Maxine S. Fritz <max+ietf@mfzx.net>
Have a day :)

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