Original text:
4.1. <del> These keys indicate the set of supported protocols (SVCB Section 6.1).  The default protocol is "dot", indicating support for DNS over TLS DOT. </del>  If the protocol set contains any HTTP versions (e.g. "h2", "h3"), then the record indicates support for DNS over HTTPS DOH, and the on their default ports.  Note that in this configuration, ALPN negotiation does not defend against cross-protocol downgrade attacks. <del> These keys are automatically mandatory if present.  (See Section 7 of SVCB for the definition of "automatically mandatory".) </del> 4.2. This key is used to indicate the target port for connection ((SVCB Section 6.2)).  If omitted, the client SHALL use the default port for <del> each transport protocol (853 for DNS over TLS, 443 for DNS over </del>  HTTPS). <del> This key is automatically mandatory if present. </del>  4.3. 8. A resolver at "simple.example" that supports DNS over TLS on port <del> 853 (implicitly, as this is the default protocol and its default port): </del>  A resolver at "doh.example" that supports only DNS over HTTPS (DNS over TLS is disabled): _dns.doh.example. 7200 IN SVCB 1 <del> doh.example. ( no-default-alpn alpn=h2 dohpath=/dns-query{?dns} ) </del>  A resolver at "resolver.example" that supports

Reviewer comments:
This change removes the default protocol, which is currently DNS over TLS ("dot"). Several readers have expressed concern that this default is confusing.
Blocked by URL
Section 5.1 says this: The examples are all like this: RFC 6570 says this: I assume that we don't want passed in the SVCB record. Should we clarify that MUST be in relative form, i.e., just the path portion of the URI?
As a normative matter, I think this is already settled in the text, but I'm happy to improve clarity of the description.
Yeah, I think this technically covers it (), but it would be nice to say something at the start of the paragraph to specify that this is just a path segment of the URL.
approved with 1 question

Revised text:
4.1.  <ins> This key indicates the set of supported protocols (SVCB Section 6.1). There is no default protocol, so the "no-default-alpn" key does not apply, and the "alpn" key MUST be present. </ins> If the protocol set contains any HTTP versions (e.g. "h2", "h3"), then the record indicates support for DNS over HTTPS DOH, and the on their default ports.  Note that in this configuration, ALPN negotiation does not defend against cross-protocol downgrade attacks.  4.2. This key is used to indicate the target port for connection ((SVCB Section 6.2)).  If omitted, the client SHALL use the default port for  <ins> each transport protocol (853 for DNS over TLS DOT, 443 for DNS over </ins> HTTPS).  <ins> This key is automatically mandatory if present.  (See Section 7 of SVCB for the definition of "automatically mandatory".) </ins> 4.3. 8. A resolver at "simple.example" that supports DNS over TLS on port  <ins> 853 (implicitly, as this is its default port): </ins> A resolver at "doh.example" that supports only DNS over HTTPS (DNS over TLS is disabled): _dns.doh.example. 7200 IN SVCB 1  <ins> doh.example. ( alpn=h2 dohpath=/dns-query{?dns} ) </ins> A resolver at "resolver.example" that supports