Hi all, In Berlin, Warren and I presented two approaches to expanding the AS112 project beyond that currently deployed (and described in RFC6304) with the primary goal of making it practical to add and remove zones from the system without requiring fine-grained management of a system that is only loosely-coordinated.
Our preference was to use DNAME, as described in draft-jabley-dnsop-as112-dname-00. We suggested to the room that what remained was to run some experiments to determine whether DNAME support was adequate for the purpose; if it turned out DNAME was not practical, our fallback plan was draft-wkumari-dnsop-omniscient-as112-03. Geoff Huston and George Michaelson were kind enough to run an initial experiment this week to try and find problems with DNAME support in the wild. They did not find any; DNAME support (for the purposes of AS112) seems more than adequate. This document (below) includes a description of the experiment and the results. We request that the chairs poll the working group and identify consensus (or not) to adopt this document. Note that this document also recommends an update to 6304 (details of the proposed updates are included in an appendix). The authors are waiting on the reaction of the working group to this plan before preparing a candidate 6304bis (which I do not expect would take much time). Thanks all, Joe Begin forwarded message: > From: "[email protected]" <[email protected]> > Subject: New Version Notification for draft-jabley-dnsop-as112-dname-01.txt > Date: 12 October 2013 17:26:28 EDT > To: George Michaelson <[email protected]>, "George G. Michaelson" > <[email protected]>, Joe Abley <[email protected]>, Brian Dickson > <[email protected]>, Warren Kumari <[email protected]> > > > A new version of I-D, draft-jabley-dnsop-as112-dname-01.txt > has been successfully submitted by Joe Abley and posted to the > IETF repository. > > Filename: draft-jabley-dnsop-as112-dname > Revision: 01 > Title: AS112 Redirection using DNAME > Creation date: 2013-10-12 > Group: Individual Submission > Number of pages: 23 > URL: > http://www.ietf.org/internet-drafts/draft-jabley-dnsop-as112-dname-01.txt > Status: > http://datatracker.ietf.org/doc/draft-jabley-dnsop-as112-dname > Htmlized: http://tools.ietf.org/html/draft-jabley-dnsop-as112-dname-01 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-jabley-dnsop-as112-dname-01 > > Abstract: > Many sites connected to the Internet make use of IPv4 addresses that > are not globally unique. Examples are the addresses designated in > RFC 1918 for private use within individual sites. > > Devices in such environments may occasionally originate Domain Name > System (DNS) queries (so-called "reverse lookups") corresponding to > those private-use addresses. Since the addresses concerned have only > local significance, it is good practice for site administrators to > ensure that such queries are answered locally. However, it is not > uncommon for such queries to follow the normal delegation path in the > public DNS instead of being answered within the site. > > It is not possible for public DNS servers to give useful answers to > such queries. In addition, due to the wide deployment of private-use > addresses and the continuing growth of the Internet, the volume of > such queries is large and growing. The AS112 project aims to provide > a distributed sink for such queries in order to reduce the load on > the IN-ADDR.ARPA authoritative servers. The AS112 project is named > after the Autonomous System Number (ASN) that was assigned to it. > > The AS112 project does not accommodate the addition and removal of > DNS zones elegantly. Since additional zones of definitively local > significance are known to exist, this presents a problem. This > document describes modifications to the deployment and use of AS112 > infrastructure that will allow zones to be added and dropped much > more easily. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
