The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'AS112 Redirection using DNAME' <draft-ietf-dnsop-as112-dname-04.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-10-08. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Subsequent to the IETF Last call on this document. questions arose as to wether the implications of using dname and therefore allowing zones other than those described by the draft and previously served by the as112 project to be served by as112 project nameservers was fully considered. We have requested an additional last call to address this question. The mechanism specified in 3.2 can be employed in practice by the managers of a zone without coordination with as112 server operators. This facilitates the deployment of additional zones for the purposes of authoritative negative answers. http://tools.ietf.org/html/draft-ietf-dnsop-as112-dname-04#section-3.2 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 file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/ballot/ No IPR declarations have been submitted directly on this I-D.
