I support adopting 3) draft-hzhwm-dprive-start-tls-for-dns. It may not be in shipping shape, but I think it is a worthy path to pursue and can be tweaked further along. In particular, I think it would be a good idea to consider pushing documents for DNS-over-TCP/TLS and DNS-over-UDP/DTLS at the same time, with harmonized authentication language.
Re 1 and 2, I don't understand what advantage they would give compared to DNS-over-TLS, DNS-over-DTLS, or DNSCurve. I believe a strong justification is necessary to motivate adoption. Frankly, I would prefer DNSCurve over both 1 and 2. /Simon Warren Kumari <[email protected]> writes: > Hi all, > > So, the big day has finally arrived -- we are initiating calls for > adoption on the three documents. < http://i.imgur.com/SKX3P8J.gif > > > For *each* of the below documents, please **clearly** state if you > would like DPRIVE to adopt it, or if you think that it will be a > distraction / not helpful. > > 1) Confidential DNS: > https://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns/ > > 2) Private-DNS: https://datatracker.ietf.org/doc/draft-hallambaker-privatedns/ > > 3) TLS for DNS: Initiation and Performance Considerations: > http://datatracker.ietf.org/doc/draft-hzhwm-dprive-start-tls-for-dns/ > > > This call for adoption will be wrapping up on April 30th. > At that point we will decide on one or multiple of the documents.... > > W
signature.asc
Description: PGP signature
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
