Last Call Review of draft-ietf-tls-svcb-ech-06
review-ietf-tls-svcb-ech-06-artart-lc-leiba-2024-10-23-00
Request | Review of | draft-ietf-tls-svcb-ech |
---|---|---|
Requested revision | No specific revision (document currently at 06) | |
Type | Last Call Review | |
Team | ART Area Review Team (artart) | |
Deadline | 2024-11-15 | |
Requested | 2024-10-22 | |
Authors | Benjamin M. Schwartz , Mike Bishop , Erik Nygren | |
I-D last updated | 2024-10-23 | |
Completed reviews |
Dnsdir Early review of -01
by Ted Lemon
(diff)
Artart Last Call review of -06 by Barry Leiba Genart Last Call review of -06 by Lucas Pardue Dnsdir Last Call review of -06 by James Gannon |
|
Assignment | Reviewer | Barry Leiba |
State | Completed | |
Request | Last Call review on draft-ietf-tls-svcb-ech by ART Area Review Team Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/art/wKlndkfM7QGQ-RM2b3APgjOzOa0 | |
Reviewed revision | 06 | |
Result | Ready w/nits | |
Completed | 2024-10-23 |
review-ietf-tls-svcb-ech-06-artart-lc-leiba-2024-10-23-00
Just two small comments on this straightforward document: — Section 3 — Figure 1: ECH SvcParam with a public_name of "ech-sites.example.com" The example actually encodes example.net, not example.com [This was a test to see if we check these things, right? :-) ] — Section 4 — These servers SHOULD support a protocol version that is compatible with ECH. Why is this not a MUST? What might be a reason to publish an ECH record for a server that doesn’t support ECH?