On Tue, 17 Jan 2017 18:22:29 +0800, Shane Kerr wrote: 
>Hello,
>
>I'm sorry if it has already been discussed, but has there been any work
>done on using TLS for AXFR/IXFR?
>
>It seems like it should be relatively straightforward, compared to the
>stub-to-resolver and resolver-to-authority links. While it does not
>seem as big of a problem either, obviously somebody cares about hiding
>the contents of zones or everybody wouldn't block zone transfers,
>right? 
>
>There are still some issues to consider, such as what the interaction of
>TSIG and TLS certificates means, as well as what method a master can
>use to signal TLS support (this seems desirable to me, although not
>necessary).
>
>Does this seem like something worth working on? Or is it a distraction
>from the resolver-to-authority work?

That seems like a good idea.

Wouldn't a straightforward signalling method be the same as rfc7858: use
port 853?  Is there some reason that wouldn't work?

>Note also that it might be worthwhile building a new zone transfer
>protocol that can perform better in areas where AXFR and IXFR don't
>work well today (unnecessary data in IXFR of signed zones, inefficiency
>for synchronizing lots of zones, automatic fallback to full zone
>transfer on IXFR failure, and so on). That's not really something for
>DPRIVE, of course, but adding TLS to the protocol could be rolled into
>such an activity.

A more modern prototocol may may not be a good idea, but if just using
port 853 works, then the two should be decoupled.

   -John Heidemann

_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to