draft-sitw-dnsop-metazones-01.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-sitw-dnsop-metazones-01" submissionType="independent" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="false">

<front>
<title abbrev="metazones">DNS Metazones</title><seriesInfo value="draft-sitw-dnsop-metazones-01" stream="independent" status="informational" name="Internet-Draft"></seriesInfo>
<author role="editor" initials="S." surname="Instenes" fullname="Shawn Instenes"><organization></organization><address><postal><street></street>
</postal><email>shawn@instenes.com </email>
</address></author><author role="editor" initials="T." surname="Wicinski" fullname="Tim Wicinski"><organization></organization><address><postal><street></street>
<city>Elkins</city>
<code>26241</code>
<country>USA</country>
<region>WV</region>
</postal><email>tjw.ietf@gmail.com</email>
</address></author><date/>
<area></area>
<workgroup>DNSOP</workgroup>

<abstract>
<t>This document describes a method for zone catalog
 provisioning and updating among DNS primary and secondary
 nameservers by storing and transferring the catalogs as regular DNS
 zones.</t>
</abstract>

</front>

<middle>

<section anchor="introduction"><name>Introduction</name>
<t>[RFC1035] describes a &quot;catalog&quot; as a data structure that lists the zones
  and where the zone data can be located. DNS zone data is currently
  synchronize between primary and secondary nameservers using existing DNS
  protocols AXFR [RFC5936] and IXFR [RFC1995].  The configuration of these
  synchronization methods currently happen outside of the DNS and involve
  adhoc processes.</t>
<t>A method for managing zone catalog provisioning and synchronization in a
 similiar method as DNS zone data, can be useful to administrators.
 While the initial concept of a catalog is a list of zones, and zone data pointers,
 nameserver deployments have grown more complex over time. There is a need to
 manage multiple &quot;catlogs&quot; of distinct zones, as well as describing individual
 properties of a zone, such as allowing zone transfers, queries, etc.</t>
<t>This document describes one such method, in which this management information
 is represented as a regular DNS zone called a &quot;metazone&quot;, and
 transferred using DNS zone transfers.  The representation of this data
 within DNS zones is specified and nameserver requirements are listed.</t>
</section>

<section anchor="metazones"><name>Metazones</name>

<section anchor="description"><name>Description</name>
<t>[Start here with describing zone data]</t>
</section>

<section anchor="resource-records"><name>Resource Records</name>

<section anchor="apl"><name>APL</name>
</section>

<section anchor="ptr"><name>PTR</name>
<t>Used for attributes</t>
</section>

<section anchor="use-of-dname"><name>Use of DNAME</name>
<t>Example:</t>

<artwork>    version.west 3600 IN CNAME version.metazone.local.
    masters.west 3600 IN APL 1:228.9.219.253/32
    allow-query.west 3600 IN APL 1:10.1.0.0/16 1:10.2.0.0/16
    90.105.235.189 3600 IN DNAME west.metazone.local.
    121.141.185.129 3600 IN DNAME west.metazone.local.
    54.235.179.68 3600 IN DNAME west.metazone.local.
    159.228.89.78 3600 IN DNAME west.metazone.local.
    zone-list.west 3600 IN TXT &quot;zones bridge_zones edge_zones&quot;
    default-forward.west 3600 IN TXT &quot;True&quot;
    default-forward-list.west 3600 IN APL 1:10.115.35.242/32 1:63.26.3.163/32 1:97.167.62.214/32 1:66.193.84.92/32
    notify.west 3600 IN TXT &quot;True&quot;
    also-notify-list.west 3600 IN APL 1:10.115.35.242/32 1:63.26.3.163/32 1:97.167.62.214/32 1:66.193.84.92/32
    local-bridge.west 3600 IN APL 1:126.90.129.146/32
</artwork>
</section>
</section>
</section>

</middle>

<back>

</back>

</rfc>