(The history of SMTP is, I think, a good poster child for this, with MX, A, AAAA, plus DNSSEC and TLSA support in the clients, which are email transport things, not merely DNS things.)
Not really. MX and A mean different things, and it is useful and common for an SMTP server to be pointed to via MX and A with different names.
The SVCB parameters' wire format is an extremely simple TLV arrangement; I don't think "a complex parser" is required. It's also far from a novel design for DNS; in fact, it's identical to the widely implemented OPT RR RDATA format from 1999 [1][2].
Having written some DNS parsers, I agree. Parsing the fields out of the wire format is easy. I have reservations about SVCB but the encoding is not one of them.
Regards, John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
