On Wed, Nov 19, 2014 at 8:09 PM, John Heidemann <[email protected]> wrote: > On Wed, 19 Nov 2014 22:33:14 +0000, "Mankin, Allison" wrote:
> One small addition. That's an our older tech report, and that link is > now broken. > > The current version is TR-693, at > > http://www.isi.edu/publications/trpublic/files/tr-693.pdf > > (the old version is now > http://www.isi.edu/publications/trpublic/files/tr-688.pdf > for folks who want to wax nostolgic about where DNS-over-TCP and TLS was > back in Feb. 2014 :-). Referring to table 7 in the report. This is giving average time for a DNS transaction but as I explained to Alison, the issue for browser providers is how fast their page loads. Any chance you could run the numbers and identify the times for the first load? Even on those numbers, one round trip 62% of the time is not the same as one round trip 97% of the time. I do however strongly agree with Alison that we are going to need more than one protocol because we have to achieve 100% connectivity. And that means being able to bypass hotel and coffee shop DNS. That means either DNS over TLS or HTTP with encrypted content (or both). What I like about DNS over TLS is that we get the ability to use multiple records. I think that is an important feature. _______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
