I think you missed the point John. Its a manifesto, and it can take
radical positions. If you read Shanes markup its clear a lot of things
which are implicit in 'UDP/EDNS0' are up for grabs.
I for one, would welcome versioning models closer to HTTP. I'd also
welcome client-capability signalling and negotiation, another thing
which won't happen in my lifetime on port 53.
I agree that a protocol that had versioning and signalling and negotiation
and other stuff would be cool, but it wouldn't be DNS. With respect to
the stuff in the manifesto, I think it needs to take another step back and
figure out what problem(s) the DNS is supposed to solve, which affects
questions like whether wildcards are a good idea.
The DNS was originally mostly a way to map names to IP addresses, but even
at the beginning it had other stuff like MX and HINFO and TXT. In its
current incarnation it's a tree structured database with weak searching
(just terminal wildcards) where you can put whatever you want so long as
the records aren't more than a few K each. DANE has done a little of that
with TLSA, but you can go way beyond that.
A while back I wrote a draft that put a B-tree in the DNS, for fairly
efficient prefix matches for lookups, with the intended application being
IPv6 DNSBLs. Last year I wrote a draft that put a state machine for a DFA
for regular expressions in the DNS, to do more general string pattern
matching, with the intended application being e-mail address local parts.
Or look at the DBOUND drafts that Casey Deccio and I wrote, that use
wildcards in parallel subdomains to publish boundary info sort of like the
PSL.
Even if the main application is still finding addresses for host names,
I'd want to push what SRV does into the protocol so I can say I want to
find the web server or the mail server for foo.example, and it'd tell me
the IP addresses and the ports and some hints about what sort of
connection to make, TLS over TCP or whatever.
We already have a draft for DNS over HTTP. Perhaps we can bootstrap from
there once we understand what we're trying to do.
Regards,
John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
