On Wed, Jan 18, 2017 at 06:53:44AM +0530, Mukund Sivaraman wrote: > On Tue, Jan 17, 2017 at 07:54:45AM -0800, Paul Hoffman wrote: > > > On a side note, because any encryption will require a change to the DNS > > > protocol (i.e., putting things into a crypto box which isn't backwards > > > compatible) IMO it would be worthwhile to consider revisiting the DNS > > > message format. > > > > Shane was talking about wrapping the DNS traffic in TLS. This does not > > "require a change to the DNS protocol", as we have already seen in this WG. > > It does. It won't work on port 53 with an existing client.
BTW, the email I sent wasn't exactly a follow-up to Shane's DNS over TLS
for AXFR email. My mail was about the resolver -> auth communications.
Maybe it was not clear from the original mail: when a different
mechanism (port and related protocol change) is being introduced for
encrypted traffic which current implementations cannot use without
changes to them, it would be good to consider revisiting the DNS message
format. The reasons for this have been given, and some of these are
things we have recently had performance or filtering issues with with in
the implementation I work on. After a point, no amount of tweaking the
implementation is going to help an inferior format.
Mukund
signature.asc
Description: PGP signature
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
