Re: [DNSOP] Fwd: [EXT] New Version Notification for draft-toorop-dnsop-dns-catalog-zones-01.txt

Bob Harold <rharolde@umich.edu> Thu, 16 April 2020 12:38 UTC

MIME-Version: 1.0
References: <6f0fe035-eb4b-9aaf-77ae-9f3e8be62079@nlnetlabs.nl>
In-Reply-To: <6f0fe035-eb4b-9aaf-77ae-9f3e8be62079@nlnetlabs.nl>
From: Bob Harold <rharolde@umich.edu>
Date: Thu, 16 Apr 2020 08:37:44 -0400
Message-ID: <CA+nkc8B2z7dap=Jod2mv_4E2EuWNp3NjddxGpYNZTSzW2eBnPg@mail.gmail.com>
To: Willem Toorop <willem@nlnetlabs.nl>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b7536c05a367b3aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FOXBhEiGcdcIBmGXtU2n8L2zWfI>
Subject: Re: [DNSOP] Fwd: [EXT] New Version Notification for draft-toorop-dnsop-dns-catalog-zones-01.txt
Precedence: list

On Wed, Apr 15, 2020 at 5:27 AM Willem Toorop <willem@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-drafts@ietf.org
> Aan: Ondrej Sury <ondrej@isc.org> <ondrej@isc.org>, Libor Peltan
> <libor.peltan@nic.cz> <libor.peltan@nic.cz>, Peter van Dijk
> <peter.van.dijk@powerdns.com> <peter.van.dijk@powerdns.com>, Willem
> Toorop <willem@nlnetlabs.nl> <willem@nlnetlabs.nl>, Leo Vandewoestijne
> <leo@dns.company> <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?

-- 
Bob Harold

[DNSOP] Fwd: [EXT] New Version Notification for d… Willem Toorop
Re: [DNSOP] Fwd: [EXT] New Version Notification f… Bob Harold
Re: [DNSOP] Fwd: [EXT] New Version Notification f… Willem Toorop
Re: [DNSOP] Fwd: [EXT] New Version Notification f… Richard Gibson
Re: [DNSOP] Fwd: [EXT] New Version Notification f… Willem Toorop