In message <dbb262ae-2f0e-4c63-a202-b53e0a6c9...@fugue.com>, Ted Lemon writes: > > On Dec 21, 2016, at 3:31 PM, Stephane Bortzmeyer <bortzme...@nic.fr> > wrote: > > What did we publish on classes? If you refer to > > draft-sullivan-dns-class-useless, it was never published (which is > > bad). > > Thatâs what I was referring to. It was so obviously the right thing > that it never occurred to me that it hadnât been published.
Truely there is nothing in draft-sullivan-dns-class-useless which says we should abandon the ability to use classes in the future. The only thing we need to do now is to stop making type allocations type independent by default. Everything else is addressable in the future when we decide we need to use a new class. By default all new type allocations are IN only. You need to make the case that a type needs to be class independent or a class other than IN. A simple update to IANA's instructions on type allocations would fix that. In reality we have allocated a very small percentage of types and having a few being class independent which didn't need to be shouldn't be a reason to break future use of classes. Just because we have not used classes much, because there has been no need to date, doesn't mean that we should abandon the ability. Mark -- 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
