[TLS] Re: draft-connolly-tls-mlkem-key-agreement

Jay Daley <jay@staff.ietf.org> Thu, 12 December 2024 20:43 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B99C18DB99 for <tls@ietfa.amsl.com>; Thu, 12 Dec 2024 12:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
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 6uJZM-m4nPYS for <tls@ietfa.amsl.com>; Thu, 12 Dec 2024 12:43:55 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 A2FDDC14F6BC for <tls@ietf.org>; Thu, 12 Dec 2024 12:43:55 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-2166360285dso10328865ad.1 for <tls@ietf.org>; Thu, 12 Dec 2024 12:43:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1734036235; x=1734641035; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=OuUIiUD10xlGkha9ef6J448lj8LH7hdwgdNFATieCr8=; b=fIZZ17O4bhDQ9Y8j2Et5M1awRbM/bh+rxH7ZzATHSAFR/8wJia6IhazUnboj4TUe1t qwsPbWaxeF2vSIEe8gfKb38v3C3VsIydGJfdyFX4IWIJBCy2glJD3EmvJXG+g6SXM4Qy hgylkULZb1NkOXsTbYaP4nqE1a6luyJO2HMM/0ZE2Jqug56aO0Ft6bU7DB/UAtBtggAA PXbthw6E6bahSOBdmTNsPMHYx4hRCcTjXC2ivY9WM3tvdr37wy+gyvItLb6zTHuMGqmK GQFOzHcEYNNsncRKWfqZhongrHmWuymVEZcmAdOnuFHIAxO8+rMKziIA0Qk5smCw4f8l IKag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734036235; x=1734641035; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=OuUIiUD10xlGkha9ef6J448lj8LH7hdwgdNFATieCr8=; b=S2hv1cZ8XlYQSFscEM2Fy6sjnz3CZ99bZzSz9paiD4q1iB2+szU8dQlTKs1u/i9vlJ grGMttZd8e6IzlkEF8mfcUE0dtfReQXYRIhD9+mCwCCAat10fOVTF8E8ybCHJqzzTPS0 aq7l1RbAMaHijcnpwtFXD110Bib2mSUjOt1NfnatYWfT1f7pLI5vvW+5SadVc3n+nf5v eqYSSL0X3PtxrBPXP1AYo1TXQNDDrY0wIpwa7Tcr8wob8MAQaKft6GbHQQFo02GvEJDs tR+KCeuykl97Ve/4d29z0S1MR9Gou+GYYOKZy9ujM4dWtsdzm6w3p3cgCllR89uMU2iK Ta9w==
X-Gm-Message-State: AOJu0YykRGON56xfXrzqvxK6hyovA9OPIhM8tXre5CZfdaHmthZH9Uef o69t/nd1ZcI+8sgCrWMhJw+kSqU1hV+OM/u6aR9lJrgX0j28g89+EXUbrm31BrZcxSA5EFbr9GY lGdA=
X-Gm-Gg: ASbGncum+g6KQcXb/u4qss+j0/fZLy3FiuLLSnMZsMB/GJFAHy5VFIo2jM1xWUU9z5D DXknFyUEsZqQkTx3MBARvb++0HoHSstBhjNSaU1N6fYap5+S3uUbrEDuI+irv00hn5QAJ8gEDBw T9EKsZWeZcHk34slntFtRZdBdElPKUO1w23qzu2a/YAUsAJuN2quNhCdnGUFx3qyEAwUX0sBhRe eAPW4i7vJ1xKitN4lZU8Q5n0D9UNC/P4MWNoUzpi8TSZZ2KXbuUCp2xZEbSP5+ATtjS4hjvhetY SBFna79QXe2IYxycRD3TT7Ev+bsshhomZWynV3jjwc7O5Kwa
X-Google-Smtp-Source: AGHT+IGZd/RH1SyKMDZxKamQ2+9KcOp7toG85bqddzjfbiqSHYwxq9HT20th4ImoicbjoS2ql15yNQ==
X-Received: by 2002:a17:902:d342:b0:215:9379:4650 with SMTP id d9443c01a7336-21892a5476bmr1398775ad.42.1734036234681; Thu, 12 Dec 2024 12:43:54 -0800 (PST)
Received: from smtpclient.apple (203-96-136-224.dsl-dynamic.connections.net.nz. [203.96.136.224]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-21654150cc2sm70494185ad.68.2024.12.12.12.43.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Dec 2024 12:43:53 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
From: Jay Daley <jay@staff.ietf.org>
In-Reply-To: <20241212172840.553101.qmail@cr.yp.to>
Date: Fri, 13 Dec 2024 09:43:39 +1300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FE3BD8B-8260-4B0F-B48A-5EC61CEF3494@staff.ietf.org>
References: <20241212172840.553101.qmail@cr.yp.to>
To: "D. J. Bernstein" <djb@cr.yp.to>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
Message-ID-Hash: 5OC7YSSQ26AQ42T72Q3OKDPYDKZEGWFT
X-Message-ID-Hash: 5OC7YSSQ26AQ42T72Q3OKDPYDKZEGWFT
X-MailFrom: jay@staff.ietf.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, legal@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: draft-connolly-tls-mlkem-key-agreement
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/RFEgRAMG0FtMBkrpbDKSecqfqZQ>
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>

Hi Daniel

> On 13 Dec 2024, at 06:28, D. J. Bernstein <djb@cr.yp.to> wrote:
> 
> RFC 9680 coauthor writes:
>> If, on the other hand, your concern is that there has been a failure
>> of IETF processes that has created an antitrust risk, then the
>> appropriate course of action is to follow the appropriate IETF process
>> for addressing that.
> 
> RFC 9680 says that it's "generally inappropriate" to discuss "market
> opportunities for specific companies". What's the IETF process for
> addressing violations of RFC 9680?

RFC 9680 is not a policy but an informational document, including information on an escalation path for antitrust concerns, and so there is no concept of “violations of RFC 9680”.  RFC 9680 carefully says “generally inappropriate” for the topics to avoid because there is a vast grey area here.  The decision on whether or not any specific action is inappropriate rests with the IETF community through its structure and processes.  

The role of IETF Counsel is to provide advice to IETF leadership to support their formal decision making role as set out in these processes, but neither they nor I have any powers beyond that.  I took your note to me as invoking the escalation path that RFC 9680 provides information on and consulted with counsel and the response is, as previously conveyed, that your concern should be addressed through the standards process.

I believe you will be getting an email in due course from the WG chairs that explains that further and addresses the rest of your points.

Jay

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org