Skip to main content

Last Call Review of draft-ietf-tls-esni-23
review-ietf-tls-esni-23-tsvart-lc-pauly-2025-03-05-00

Request Review of draft-ietf-tls-esni
Requested revision No specific revision (document currently at 25)
Type IETF Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2025-03-13
Requested 2025-02-20
Authors Eric Rescorla , Kazuho Oku , Nick Sullivan , Christopher A. Wood
I-D last updated 2025-11-14 (Latest revision 2025-06-14)
Completed reviews Dnsdir IETF Last Call review of -23 by R. (Miek) Gieben (diff)
Artart IETF Last Call review of -23 by Carsten Bormann (diff)
Secdir IETF Last Call review of -23 by Adam W. Montville (diff)
Tsvart IETF Last Call review of -23 by Tommy Pauly (diff)
Genart IETF Last Call review of -23 by Stewart Bryant (diff)
Opsdir IETF Last Call review of -24 by Giuseppe Fioccola (diff)
Dnsdir Telechat review of -24 by R. (Miek) Gieben (diff)
Intdir Telechat review of -24 by Tommy Pauly (diff)
Assignment Reviewer Tommy Pauly
State Completed
Request IETF Last Call review on draft-ietf-tls-esni by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/CEn1FLHFBg4oMgDMu7CX5wLRriA
Reviewed revision 23 (document currently at 25)
Result Ready
Completed 2025-03-05
review-ietf-tls-esni-23-tsvart-lc-pauly-2025-03-05-00
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.