> Yes, and catching COVID on Friday didn't help. Will attempt to send a
> pull request for just the $QNAME fix shortly.
Making a pull request does not preclude also Cc'ing the list. Which
is what I'm doing now and was planning to do in any case:
https://github.com/MikeBishop/dns-alt-svc/pull/399/files
--- a/draft-ietf-dnsop-svcb-https.md
+++ b/draft-ietf-dnsop-svcb-https.md
@@ -532,12 +532,13 @@ noted in {{client-failures}} and {{ech-client-behavior}}).
SVCB-optional clients SHOULD issue in parallel any other DNS queries that might
be needed for connection establishment if the SVCB record is absent, in order
to minimize delay
in that case and enable the optimizations discussed in {{optimizations}}.
Once SVCB resolution has concluded, whether successful or not,
+if at least one AliasMode record was processed,
SVCB-optional clients SHALL append to the priority list an
endpoint consisting of the final value of $QNAME, the authority
endpoint's port number, and no SvcParams. (This endpoint will be
attempted before falling back to non-SVCB connection modes. This ensures that
SVCB-optional clients will make use of an AliasMode record whose TargetName has
A and/or AAAA records but no SVCB records.)
--
VIktor.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
