[TLS] Mike Bishop's No Objection on draft-ietf-tls-esni-24: (with COMMENT)
Mike Bishop via Datatracker <noreply@ietf.org> Wed, 07 May 2025 13:09 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: tls@ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from [10.244.8.181] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 5A03525E4419; Wed, 7 May 2025 06:09:16 -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.39.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174662335626.992684.12434538128929417422@dt-datatracker-58d4498dbd-6gzjf>
Date: Wed, 07 May 2025 06:09:16 -0700
Message-ID-Hash: J2GILSMNC3B3S2SD4B7MFDHTUUQIVNWV
X-Message-ID-Hash: J2GILSMNC3B3S2SD4B7MFDHTUUQIVNWV
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-esni@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 No Objection on draft-ietf-tls-esni-24: (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/z_9J6xGhXfXaHvtqNxCU5taW0VI>
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-esni-24: No Objection 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-esni/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I've previously reviewed this document and have very few additional comments; these comments can be incorporated or ignored at the authors' and responsible AD's discretion. 6.1.8: "has been forced to change" imputes external events that aren't relevant to the protocol. The server's configuration may have changed since the client received the retry configs; the client doesn't need to speculate on why. 10.9 notes that there's no collision between ECH acceptance (in 1.3) and downgrade protection (in <1.3) because of the version scoping. It's worth noting, however, that this forecloses using the same approach to guard against downgrades to 1.3 from future TLS versions.
- [TLS] Mike Bishop's No Objection on draft-ietf-tl… Mike Bishop via Datatracker
- [TLS] Re: Mike Bishop's No Objection on draft-iet… Eric Rescorla