Op 16-04-2020 om 14:37 schreef Bob Harold: > On Wed, Apr 15, 2020 at 5:27 AM Willem Toorop <wil...@nlnetlabs.nl > <mailto:wil...@nlnetlabs.nl>> wrote: > > Dear all, > > This is the new catalog zones draft as presented yesterday at the > DNSOP WG Interim meeting. The idea of catalog zones is to establish > automatic zone provisioning along existing primary/secondary > relationships. > > This is an earlier idea which was previously worked on by ISC > authors. The editor's pen has been picked up by authors from > different DNS Software implementations with the aim to create a > cross-implementation compatible version of catalog zones. > Most prominent modifications to earlier versions are: > > 1. There are descriptions nor definitions of zone properties anymore > 2. A zone is required to reset state when its unique label changes > 3. The version TXT RR now can be a RRset to allow for versions that > are backwards compatible with earlier versions. > > Willem > > -------- Doorgestuurd bericht -------- > Onderwerp: [EXT] New Version Notification for > draft-toorop-dnsop-dns-catalog-zones-01.txt > Datum: Tue, 14 Apr 2020 04:02:23 -0700 > Van: internet-dra...@ietf.org <mailto:internet-dra...@ietf.org> > Aan: Ondrej Sury <ond...@isc.org> <mailto:ond...@isc.org>, Libor > Peltan <libor.pel...@nic.cz> <mailto:libor.pel...@nic.cz>, Peter van > Dijk <peter.van.d...@powerdns.com> > <mailto:peter.van.d...@powerdns.com>, Willem Toorop > <wil...@nlnetlabs.nl> <mailto:wil...@nlnetlabs.nl>, Leo > Vandewoestijne <leo@dns.company> <mailto:leo@dns.company> > > > > A new version of I-D, draft-toorop-dnsop-dns-catalog-zones-01.txt > has been successfully submitted by Willem Toorop and posted to the > IETF repository. > > Name: draft-toorop-dnsop-dns-catalog-zones > Revision: 01 > Title: DNS Catalog Zones > Document date: 2020-04-14 > Group: Individual Submission > Pages: 11 > URL: > > https://www.ietf.org/internet-drafts/draft-toorop-dnsop-dns-catalog-zones-01.txt > Status: > https://datatracker.ietf.org/doc/draft-toorop-dnsop-dns-catalog-zones/ > Htmlized: > https://tools.ietf.org/html/draft-toorop-dnsop-dns-catalog-zones-01 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-toorop-dnsop-dns-catalog-zones > Diff: > https://www.ietf.org/rfcdiff?url2=draft-toorop-dnsop-dns-catalog-zones-01 > > Abstract: > This document describes a method for automatic DNS zone provisioning > among DNS primary and secondary nameservers by storing and > transferring the catalog of zones to be provisioned as one or more > regular DNS zones. > > > 5.1.. General Requirements > > If there is a clash between an existing member zone's name and an > incoming member zone's name (via transfer or update), the new > instance of the zone MUST be ignored and an error SHOULD be logged. > > -- I do not understand. Can you give an example?
An authoritative nameserver might have two or more catalog zones, each associated with their own set of configuration. In that case, the member zone that was configured first (and associated with the settings of the particular catalog zone it was a member of) will keep that association, regardless of it being a member zone of other catalog zones as well. -- Willem > > -- > Bob Harold > > > _______________________________________________ > 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
