Skip to main content

Telechat Review of draft-ietf-dnsop-svcb-https-08

Request Review of draft-ietf-dnsop-svcb-https
Requested revision No specific revision (document currently at 12)
Type Telechat Review
Team Internet Area Directorate (intdir)
Deadline 2022-02-27
Requested 2022-01-31
Requested by Éric Vyncke
Authors Benjamin M. Schwartz , Mike Bishop , Erik Nygren
I-D last updated 2022-04-19
Completed reviews Genart Last Call review of -07 by Dale R. Worley (diff)
Artart Last Call review of -07 by Cullen Fluffy Jennings (diff)
Opsdir Last Call review of -07 by Joe Clarke (diff)
Tsvart Last Call review of -07 by Kyle Rose (diff)
Intdir Telechat review of -08 by Carlos Pignataro (diff)
Dnsdir Last Call review of -12 by Matt Brown
This I-D is important for the DNS community as it will have an impact also on ADD WG. A fresh view from outside the DNS community would be a plus probably. Thanks.
Assignment Reviewer Carlos Pignataro
State Completed
Request Telechat review on draft-ietf-dnsop-svcb-https by Internet Area Directorate Assigned
Posted at
Reviewed revision 08 (document currently at 12)
Result Ready w/nits
Completed 2022-04-19
I am an assigned INT directorate reviewer for draft-ietf-dnsop-svcb-https.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see

This document specifies the "SVCB" and "HTTPS" DNS resource record (RR) types
to facilitate the lookup of information needed to make connections to network
services, such as for HTTP origins.

This document is clear and comprehensive. Specifically, rev -08 improved
structure, terminology, and readability. It seems ready modulo some nits.

Editorial suggestions:
* s/followup/follow-up/g
* "   *  Fallback to the the client's non-Alt-Svc connection behavior" -->
duplicate "the" * "IANA from the "Resource Record (RR) TYPEs" subregistry" -->
looks like that's a registry, not sub-registry (same with other parts of the
IANA sections) * s/e.g./e.g.,/g * "2 octet field" -> "2-octet field"

Editorially, I find this construct a bit interesting -- indirections, and
wonder if a bit more context can be added to S7.5. 7.5.  "mandatory"
   See Section 8.
8.  ServiceMode RR compatibility and mandatory keys

Thank you for your consideration,