[TLS] Tsvart last call review of draft-ietf-tls-esni-23

Tommy Pauly via Datatracker <noreply@ietf.org> Wed, 05 March 2025 17:56 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tommy Pauly via Datatracker <noreply@ietf.org>
To: tsv-art@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174119740746.828825.15924277362435972131@dt-datatracker-5dd67b77bb-4k4zh>
Date: Wed, 05 Mar 2025 09:56:47 -0800
Message-ID-Hash: DKMG2NXTJ5JLYLGUMHVASVQGNAYYIJYH
CC: draft-ietf-tls-esni.all@ietf.org, last-call@ietf.org, tls@ietf.org
Reply-To: Tommy Pauly <tpauly@apple.com>
Subject: [TLS] Tsvart last call review of draft-ietf-tls-esni-23
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/uYdfLslEWSFgaIvvceAkbppQ4Do>

Reviewer: Tommy Pauly
Review result: Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Thanks to the authors for producing a clear and well-written document.
In reviewing it, I did not find any issues from a transport perspective
that raise concern. This protocol extension is defined to work with various
transport cases (TLS over TCP, DTLS over UDP, QUIC, etc), and otherwise
does not fundamentally change their properties.

>From a privacy and security perspective, it is good to see this work
progressing.

[TLS] Tsvart last call review of draft-ietf-tls-e… Tommy Pauly via Datatracker