We'd end up adding stuff to a response in order to make it shorter. Is there a clear benefit (shorter responses)? Can you show me a few real world examples?
Thanks Roy > On 8 Dec 2015, at 20:37, Mark Andrews <ma...@isc.org> wrote: > > > In message <alpine.lfd.2.20.1512081440270.27...@bofh.nohats.ca>, Paul Wouters > wr > ites: >> >>> Subject: Re: [DNSOP] Question on RRtypes in RFC 4034 Section 6.2 >> >> Thanks everyone for the useful comments. It's all clear to me now. >> >> Paul > > Additionally if we ever wanted to enable compression for new types > we could use EDNS to signal that the client understands a expand > set of types and one could use case sensitive compression to preserve > the original case of the name in the rdata which would allow DNSSEC > to work to work on the expanded names without having to update every > client in the world first. > > e.g. > EDNS(1) could indicate the client understands the rdata > for all the types allocated as of 12:00 Dec 8, 2016. > > EDNS(2) could indicate the client understands the rdata > for all the types allocated as of 12:00 Dec 8, 2020. > > We all should be doing case sensitive compression already as that > really is part and parcel of preserving the original case as required > by RFC 103[45]. > > I'm actually tempted to say we should do this just to get rid of > the stupid firewalls that think that it is a good idea to drop EDNS > != EDNS(0) requests. > >> _______________________________________________ >> DNSOP mailing list >> DNSOP@ietf.org >> https://www.ietf.org/mailman/listinfo/dnsop > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
