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
> On Mar 1, 2025, at 12:57 PM, Muhammad Usama Sardar
> wrote:
>
> On 01.03.25 06:27, Sean Turner wrote:
>
>> • Discussion of subjects unrelated to IETF policy, meetings, activities, or
>> technical concerns (from RFC 3683)
>
> Could the chairs please clarify about the announcement of side m
Reviewer: Adam Montville
Review result: Ready
Based on my review of this draft I would classify it as "ready" for
publication, with some minor caveats that don’t fundamentally undermine its
readiness.The draft defines a clear, well-specified mechanism for encrypting
the ClientHello. It leverages e
Hi Nick,
I'd go for option 1. The server is opting into this mechanism, so it seems
reasonable to force it to ignore the outer SNI if ECH accepts. I agree with
Stephen that we shouldn't hold up publication for this change (Option 2),
however I think the extension mechanism of ECH is appropriate fo
