Hi all, As promised, here's a draft which describes the alternate approach (alternate to the omniscient, custom-code route that our other document proposes) of using DNAME to extend AS112 service.
<sales pitch> This one has the side-effect of supporting DNSSEC-validatable redirection to AS112 nodes! </sales pitch> :-) Joe Begin forwarded message: > From: "[email protected]" <[email protected]> > Subject: New Version Notification for draft-jabley-dnsop-as112-dname-00.txt > Date: 28 June 2013 18:23:33 EDT > To: Joe Abley <[email protected]>, Brian Dickson > <[email protected]> > > > A new version of I-D, draft-jabley-dnsop-as112-dname-00.txt > has been successfully submitted by Joe Abley and posted to the > IETF repository. > > Filename: draft-jabley-dnsop-as112-dname > Revision: 00 > Title: AS112 Redirection using DNAME > Creation date: 2013-06-28 > Group: Individual Submission > Number of pages: 20 > URL: > http://www.ietf.org/internet-drafts/draft-jabley-dnsop-as112-dname-00.txt > Status: > http://datatracker.ietf.org/doc/draft-jabley-dnsop-as112-dname > Htmlized: http://tools.ietf.org/html/draft-jabley-dnsop-as112-dname-00 > > > 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. > > > > > The IETF Secretariat > _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
