Thank you for your clarification Eric. I concur with your approach.

Stewart

On 19 Mar 2025, at 21:22, Eric Rescorla <e...@rtfm.com> wrote:


Stewart,

Thanks for your review.

I have changed all but the last point, which I believe is correct as-is.

The final issue asked if we should replace the reference to RFC 5077
to RFC 8446, but this text is correct because the reference is to part
of the internal example structure in 5077 and 8446 is just agnostic on
token structure. 5077 is being used by way of analogy, not as a part
of the protocol.

-Ekr


On Tue, Mar 18, 2025 at 8:49 AM Stewart Bryant via Datatracker <nore...@ietf.org> wrote:
Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-tls-esni-23
Reviewer: Stewart Bryant
Review Date: 2025-03-18
IETF LC End Date: 2025-03-13
IESG Telechat date: Not scheduled for a telechat

Summary:A well written document with some minor nits that are easily addressed.

Major issues: None

Minor issues: None

Nits/editorial comments:

   fields, such as the ALPN list [RFC7301].  Co-located servers with
SB> ALPN needs expanding on first use.
========

   or they send a GREASE ECH
SB> I believe that GREASE is an acronym and should be expanded.
========

(see Section 2 of
   [DNS-TERMS]). 
SB> ID-NITS identifies the following concern:
  -- Obsolete informational reference (is this intentional?): RFC 8499 (ref.
     'DNS-TERMS') (Obsoleted by RFC 9499)
Should the reference be changed?
=========

   Note that, if the cookie includes a key name, analogous to Section 4
   of [RFC5077], this may leak information if different backend servers
   issue cookies with different key names at the time of the connection.

SB> From ID-NITS
  -- Obsolete informational reference (is this intentional?): RFC 5077
     (Obsoleted by RFC 8446)

Should the reference be changed?



_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org

Reply via email to