Re: [DNSOP] Question on RRtypes in RFC 4034 Section 6.2

[Mark Andrews <[e-mail]>]

In message <[e-mail]>, 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]