I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. A DNS zone is used to host the DNS records for a particular domain. This draft describes a method for automatic DNS zone provisioning by treating the catalog of zones to be provisioned as itself a DNS zone, called here a “catalog zone.” The draft gives methods for storing information in these catalogs, as well as how to handle issues such as change of ownership. The security considerations section gives a number of reasonable authentication and privacy requirements, but does stops short of the use of the word MUST. Is MUST avoided because it is not yet practical? Nits: There are a lot of unexplained acronyms, especially at the beginning: RR, SOA, NS RR, RDATA, PTR, and so on. These should be spelled out the first time they are used at the document. It would also help to have the more important ones described in more detail in the terminology section.