[DNSOP] Comments on draft-ietf-dnsop-svcb-httpssvc-02

[Dragana Damjanovic <[e-mail]>]

I have some minor comments and clarification questions.

1) in "Example: Protocol enhancements":

> and the key=value pairs indicate that it supports QUIC in addition to
> HTTPS over TLS
>

Should  "HTTPS over TLS" be "HTTPS over TCP"? HTTP3 is also HTTPS over TLS


2) Clarification question: Can  SvcDomainName point to another AliasForm
record? As I understand it, it cannot. It can point to a CNAME that points
to an AliasForm record.
The descriptions of the server and client behavior sections do not mention
this. Should they mention this again?
I am just wondering if the description in "Client behavior" and "DNS Server
Behavior" should be more precise and mention this constraint and also the
limit for a chains of CNAME and SVCB of 8?


3) Proxies should not use SVCB/HTTPSSVC. section "Clients using a Proxy"
should say that explicitly. (To make useful for a proxy to use
SVCB/HTTPSSVC records, there should be a way to communicate back to the
client about that SVCB/HTTPSSVC parameters. This does not exist at the
moment and will add a delay in some cases, etc.)

4) If no-default-alpn is present the alpn parameter must be present as
well, otherwise the "ALPN set" is empty?

5) A clarification question: In the section "ipv4hint and ipv6hint":

> An empty list of addresses is invalid.

Empty hints will not mean that the record is malformed, i.e. it is not a
fatal error that will make the whole record invalid?

6) Nit:

> As discussed in {{client-behavior}}, clients MUST be able fetch additional
> information that is required to use
>

s/MUST be able fetch/MUST be able to fetch

dragana