On 7 Jul 2026, at 4:02, Jan Schaumann wrote: > Perhaps it would be useful to include in the draft a > brief description why that is insufficient and whether > the anticipation is that browsers will (eventually) > _not_ race HTTPS and A/AAAA lookups but _only_ use > HTTPS lookups (or use those as blocking prior to any > A/AAAA lookups).
This. Besides, I wonder whether the proposal offers any new semantics beyond what is already possible by omitting the "ipv4hint" parameter while providing the "ipv6hint" one. For emphasis, one might set the "mandatory" parameter to include "ipv6hint", and reference the IPv4 endpoint in a separate SVCB-compatible RR with relatively unfavourable SvcPriority. Modulo my syntax errors, here is an example of what I have in mind. ``` $ORIGIN example.com ;; or whatever info HTTPS 5 . mandatory=ipv6hint ipv6hint=2001:db8::5 info HTTPS 5000 . ;; fallback to default info AAAA 2001:db8::5 info A 192.0.2.5 ``` ATB, Niall
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
