I'd be interested in the cache effects. If the TTL is mapped into cache age, then there is potential for CDN distribution to work more better gooder.
More for entertainment value, since label compression is totally bogus, like carrying forward ASCII only standards documents I mean who does that .. ok sorry But really, if we didn't do label compression, and we did do UTF-8 instead of punycode, would we still be DNS? -G On Wed, Dec 23, 2015 at 1:58 PM, Paul Vixie <[email protected]> wrote: > On Tuesday, December 22, 2015 11:00:22 AM Tony Finch wrote: > > > Paul Vixie <[email protected]> wrote: > > > > On Monday, December 21, 2015 01:13:10 PM Tony Finch wrote: > > > > > The current way to deal with out-of-order responses and head-of-line > > > > > blocking in HTTP is HTTP/2. > > > > > > > > since http/2 is a completely new protocol, i think that's a strange way > > > > to say it. > > > > > > Not completely - it has the same message semantics, they "just" changed > > > how the messages are transported. > > > > > > So another way of phrasing my previous message is that DNS-over-HTTP > ought > > > to be "just" a mapping from DNS messages to HTTP messages. > > > > i agree. the only specification matter is the transform between message > formats. there's no reason to talk about transport at all. > > > > -- > > P Vixie > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop > >
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
