Pushing text processing onto the client does not reduce the complexity; it
just moves it to people who are less likely to be reading DNSOP. Notably,
it moves that responsibility to a place where typical text processing
errors are far more dangerous, and malicious inputs are far more likely.
I suppose, but it also moves it to people who are more likely to care.
I don't know if you've looked at the state of DNS provisioning software,
but it is pretty bad. While I'm sure that bind and nsd and powerdns can
handle anything, I', also sure that approximately nobody outside of a few
large sophisticated sites will use SVCB because their local DNS
provisioning crudware doesn't support it. If you can say it's easy, it's
a couple of numbers and strings, they might. If they have to parse and
sort and dedup and look up code numbers, uh, sure, maybe later. Much,
much, later.
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
