Actually it is. A master file is a zone transfer mechanism. Mark
> On 4 Sep 2018, at 2:29 pm, StJohns, Michael <m...@nthpermutation.com> wrote: > > Actually, 5.2 suggests that a master file (not zone) should contain a single > class and single SOA record. That’s not the same thing as limiting a zone to > a single class AFAICT. > > Mike > > > On Mon, Sep 3, 2018 at 18:49 Mark Andrews <ma...@isc.org> wrote: > RFC 1035 Section 5.2 limits a zone to be single class. > > > On 4 Sep 2018, at 1:34 am, Paul Vixie <p...@redbarn.org> wrote: > > > > > > > > Suzanne Woolf wrote: > >> Hi all, > >> > >> During the IESG review, Adam Roach noticed that > >> draft-ietf-dnsop-terminology-bis talked about “class" but never defined > >> it. This seemed to the authors and chairs like a reasonable thing to > >> fix. It’s also important enough that we want WG review, but not > >> extensive enough to require a new LC. > >> > >> 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. > >> > >> 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..." > > > > -- > > P Vixie > > > > _______________________________________________ > > 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 -- 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
