On Mon, May 11, 2020 at 1:42 PM Tim Wicinski <tjw.i...@gmail.com> wrote:
> > All, > > As we stated in the meeting and in our chairs actions, we're going to run > regular call for adoptions over next few months. > We are looking for *explicit* support for adoption. > > > This starts a Call for Adoption for draft-toorop-dnsop-dns-catalog-zones > > The draft is available here: > https://datatracker.ietf.org/doc/draft-toorop-dnsop-dns-catalog-zones/ > > Please review this draft to see if you think it is suitable for adoption > by DNSOP, and comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends: 25 May 2020 > > Thanks, > tim wicinski > DNSOP co-chair > > I support adoption and will review. "3. Description An implementation of catalog zones MAY allow the catalog to contain other catalog zones as member zones." It seems ok to me to allow catalog zones to include other catalog zones as future feature, although I cannot figure out yet how that would work, but it might conflict with: "6.1. Implementation Notes Catalog zones on secondary nameservers would have to be setup manually" -- Bob Harold
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
