actually, the ICANN bylaws agree with your more liberal (RFC 2181-style) understanding…
"In particular, all sub domains shall be allowed to operate their own domain name servers, providing in them whatever information the sub domain manager sees fit (as long as it is true and correct).” manning bmann...@karoshi.com PO Box 12317 Marina del Rey, CA 90295 310.322.8102 On 17May2015Sunday, at 16:59, Paul Hoffman <paul.hoff...@vpnc.org> wrote: > On May 15, 2015, at 1:40 AM, Tony Finch <d...@dotat.at> wrote: >> Another item for section 7: >> >> DNS operator -- an entity responsible for running DNS servers. For a zone's >> authoritative servers, the registrant may act as their own DNS operator, or >> their registrar may do it on their behalf, or they may use a third-party >> operator. > > It was pointed out to me offline that I was taking the term "DNS operator" > too far, and that this is really part of the registration model. (I found it > in RFC 2181 in the general sense, but that seems to be a one-short use of the > term). > > So, I'm OK with the above definition if other folks here are. > > --Paul Hoffman > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
