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

Mike Bishop via Datatracker <noreply@ietf.org> Tue, 02 September 2025 18:23 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: tls@ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from [10.244.8.117] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id ECF585C39633; Tue, 2 Sep 2025 11:23:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mike Bishop via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.47.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175683741490.1938744.15847517342041403830@dt-datatracker-67876766b7-bkzgr>
Date: Tue, 02 Sep 2025 11:23:34 -0700
Message-ID-Hash: BSRM7Q5V64KQRGMQS267QL44CGH3ZNFO
X-Message-ID-Hash: BSRM7Q5V64KQRGMQS267QL44CGH3ZNFO
X-MailFrom: noreply@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: draft-ietf-tls-8773bis@ietf.org, tls-chairs@ietf.org, tls@ietf.org, jsalowey@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Mike Bishop <mbishop@evequefou.be>
Subject: [TLS] 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/XrTciRxhIaW3aKzLNXGfnRRSkXo>
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 Bishop has entered the following ballot position for
draft-ietf-tls-8773bis-10: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tls-8773bis/



----------------------------------------------------------------------
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".