IETF Logo Mail Archive

[TLS] Re: Mike Bishop's Yes on draft-ietf-tls-8773bis-10: (with COMMENT)

Russ Housley <housley@vigilsec.com> Tue, 02 September 2025 19:06 UTC

Return-Path: <housley@vigilsec.com>
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 AEC205C3E8ED; Tue, 2 Sep 2025 12:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=vigilsec.com
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 UlekmsA0NR_T; Tue, 2 Sep 2025 12:06:37 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 395B45C3E8D8; Tue, 2 Sep 2025 12:06:37 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 1B6D01A0BCF; Tue, 2 Sep 2025 15:06:37 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id F41171A28E9; Tue, 2 Sep 2025 15:06:36 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <175683741490.1938744.15847517342041403830@dt-datatracker-67876766b7-bkzgr>
Date: Tue, 02 Sep 2025 15:06:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E75F643-FD38-41C3-9011-09E1070C98AF@vigilsec.com>
References: <175683741490.1938744.15847517342041403830@dt-datatracker-67876766b7-bkzgr>
To: Mike Bishop <mbishop@evequefou.be>
X-Mailer: Apple Mail (2.3826.700.81)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=jBypY7jInEUB/8lwjBEuPnP12VdXI317mzNDcC0yzpk=; b=AfOxvPK+nnC5G9/+WddrczYFcgq2RMjRp3TPXvbtlJCcr56BvxFe8zwGOxuHfW/LoQhmli9UzNpPRdvq3TOfLRRF0ick9/DyAHjI9KcAdeav2+iuIMUctZrmuG91CFRIIW4ESRU5gvMOwf5bQJ0TpG6ms81tGTD8oDthiiG5scjdymjU+K1nwez8w28YnQvhVtTUcHZWrYixcERFoR8k7QV7HMYjOs9vTNC1CNcSYw4VrRdS957KtSJguEDFUMez0ii8pm332RoHDtTcd/vXrRFR1uiKBMVUpcM/bKRuzZ8MkEIeEsCf9K84qWh2YjQktQSnExU+4KcZjKVQ8JaNXg==
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Message-ID-Hash: B2FBIUD6NJAETCAYADTUM3AJ3QPRTPIL
X-Message-ID-Hash: B2FBIUD6NJAETCAYADTUM3AJ3QPRTPIL
X-MailFrom: housley@vigilsec.com
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: IESG <iesg@ietf.org>, draft-ietf-tls-8773bis@ietf.org, tls-chairs@ietf.org, IETF TLS <tls@ietf.org>, Joe Salowey <jsalowey@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Mike Bishop's Yes on draft-ietf-tls-8773bis-10: (with COMMENT)
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/CLEIlTRnIJNJBskh3RwxjHcztng>
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>

Mike:

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 4: "MAY also find it useful" means that the client is permitted, but
> not required, to find the extension useful. Is that the intended sense? I'd
> suggest that this is a lowercase "may" or better yet "might".

Suggestion:

The client MAY also include the "supported_groups" extension.

Russ

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