Re: [DNSOP] [[e-mail]: New Version Notification for draft-sullivan-dns-class-useless-01.txt]

[Paul Vixie <[e-mail]>]

Shane Kerr wrote:
> Mark Andrews<[e-mail]>  wrote:
>> There is nothing stopping a second class working.  Absolutely
>> nothing.  You just have to want to set up a parallel heirarchy which
>> does not have to be complete or maintain a lot more top of namespaces.

what's stopping a second $class from working is STD 13, half of which 
says that zones and rrsets span classes, and half of which says that 
each class has its own zone cut hierarchy. we would have to decide, and 
revise.

>>
>> Hesiod worked for those institutions that decided to use it.  They
>> maintained their own top of namespace.  They could have use the TXT
>> record better but it worked.

every hesiod installation maintained its own class=HS root name servers; 
there was never a way to access example2.edu's resources using an 
example1.edu client.

>> Just because we can't think of a good way to use class today is not
>> a good reason to shut down the registry.  It really doesn't cost
>> to maintain a registry that is not being actively updated.
>
> Closing the registry sends a clear message: don't use class. That
> matches the best understanding today.
>
> If someone thinks of a good way to use class tomorrow, the registry can
> be re-opened, right?

i think mark is right-- the cost of this registry is low, and the 
reservations for HS and CHAOS are in use, though interoperability is 
low. we should leave the registry in place until there's some need 
beyond cleanliness to remove it. (for example, if we revise STD 13 in a 
way that makes $class useful.)

-- 
P Vixie