Hi everyone > A new version of I-D, draft-muks-dnsop-dns-catalog-zones-00.txt > has been successfully submitted by Mukund Sivaraman and posted to the > IETF repository. > > Name: draft-muks-dnsop-dns-catalog-zones > Revision: 00 > Title: DNS catalog zones > Document date: 2015-10-18 > Group: Individual Submission > Pages: 20 > URL: > https://www.ietf.org/internet-drafts/draft-muks-dnsop-dns-catalog-zones-00.txt > Status: > https://datatracker.ietf.org/doc/draft-muks-dnsop-dns-catalog-zones/ > Htmlized: > https://tools.ietf.org/html/draft-muks-dnsop-dns-catalog-zones-00 > > > Abstract: > This document describes a method for automatic zone catalog > provisioning and synchronization among DNS primary and secondary > nameservers by storing and transferring the catalogs as regular DNS > zones.
ISC is implementing a zone catalog synchronization method in BIND. This is the first public draft of various ideas and suggestions that were pooled together and is named "DNS catalog zones". Some prelimnary versions of a requirements specification (named "Easy Add Zone requirements") and drafts were shared with DNS operators to gather input. Reviews of this first public draft are requested specifically from DNS implementations and DNS operators. We want it to be adopted across implementations so that operators have an easy time synchronizing catalogs regardless of the implementation. This is why this draft is brought here for discussion so that others can participate in its design. A zone based representation has been attempted and implemented before (see Vixie's Metazones cited in the draft). Catalog zones borrows some ideas from it. We haven't yet settled on a list of zone properties (zone options in BIND terminology) that are to be synchronized across implementations. Comments on suitable zone properties are requested. A list of BIND 9.10 zone options can be found in its administrator reference manual (BIND 9.10 ARM) in section 6.1.25: https://www.isc.org/downloads/bind/doc/bind-9-10/ We request implementations to consider if catalog zones would perform well with your zone data structures (we considered a binary search forest - an RB forest specifically for the BIND case). The draft is currently under-specified. It requires further discussion on open items, more elaborate nameserver behavior specification and several items marked "TBD" to be completed. However at this stage, it is more or less together as a design for public participation and comments. Mukund
signature.asc
Description: PGP signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
