Paul Vixie wrote: > Suzanne Woolf wrote: > > > > Here's the definition that the authors would like to add to the > > document: > > > > > > Class: > > A class "identifies a protocol family or instance of a protocol" > > (Quoted from [RFC1034], Section 3.6). "The DNS tags all data > > with a class as well as the type, so that we can allow parallel use > > of different formats for data of type address." (Quoted from > > [RFC1034], Section 2.2). In practice, the class for nearly every > > query is "IN". There are some queries for "CH", but they are > > usually for the purposes of information about the server itself > > rather than for a different type of address.
I think I would call out here more clearly that CH has been "hijacked" by name server vendors for server status information and that one cannot expect regular DNS name resolution to be performed for queries with this class. > > > > Please let us know your opinions yea or nay by Monday, Sept. 10, > > midnight UTC. > > i don't think this def'n serves the need. we need to speak more truth: > > "The Class tag was weakly defined, such that either a zone can have > data in multiple classes, or each class can have its own zone cut > hierarchy, and so neither interpretation can be relied upon by DNS > protocol implementers." > > then go on to "in practice..." RFC 1034, section 4.2 seems pretty clear that each class has its own hierarchy. It also says that cuts are made within each class's hierarchy separately. My reading is that each class has its own zones, but that indeed isn't called out explicitly in that section. Kind regards, Martin _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
