idnits 2.17.1 draft-michaelson-as112-ipv6-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 2) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([RFC6304]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 07, 2011) is 4608 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 3152 (Obsoleted by RFC 3596) -- Obsolete informational reference (is this intentional?): RFC 6304 (Obsoleted by RFC 7534) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual Submission G. Michaelson 3 Internet-Draft G. Huston 4 Intended status: Best Current Practice APNIC 5 Expires: March 14, 2012 J. Abley 6 ICANN 7 W. Sotomayor 8 NRC 9 September 07, 2011 11 AS112 Nameserver Delegations for IPv6 12 draft-michaelson-as112-ipv6-02 14 Abstract 16 To reduce longterm traffic to the DNS root servers and the IP6.ARPA 17 authoritative servers, the IAB is requested to instruct the IANA to 18 delegate a set of sub-domains of IP6.ARPA to the AS112 Project 19 [RFC6304]. These domains represent IPv6 address prefixes that are 20 not conventionally populated in the global reverse-DNS, including 21 IPv6 prefixes that are not globally scoped and certain prefixes used 22 in an anycast context. 24 The reverse DNS query load associated with these IPv6 address 25 prefixes appear to have unacceptable scaling consequences as IPv6 26 uptake increases. By delegating these sub-domains to the AS112 27 project, the DNS query load can be passed to a distributed sink, 28 reducing the query load on the root servers and the IP6.ARPA 29 authoritative servers. 31 Status of this Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on March 14, 2012. 48 Copyright Notice 49 Copyright (c) 2011 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents (http://trustee.ietf.org/ 54 license-info) in effect on the date of publication of this document. 55 Please review these documents carefully, as they describe your rights 56 and restrictions with respect to this document. Code Components 57 extracted from this document must include Simplified BSD License text 58 as described in Section 4.e of the Trust Legal Provisions and are 59 provided without warranty as described in the Simplified BSD License. 61 Table of Contents 63 1. Reverse DNS Delegation and Local-Use Addresses . . . . . . . . 2 64 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 65 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 66 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 67 5. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 5.1. Changes since the -00 draft . . . . . . . . . . . . . . . 4 69 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 71 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 74 1. Reverse DNS Delegation and Local-Use Addresses 76 The IPv6 Addressing Architecture [RFC4291] and Unique Local IPv6 77 Unicast Addresses [RFC4193] includes certain address prefixes that 78 are not intended to be uniquely used in the global network as 79 globally-scoped unicast addresses. Such addresses include locally- 80 scoped addresses, certain anycast addresses, and loopback addresses. 82 While such addresses are not intended to be used in the same context 83 as globally-scoped unicast addresses, their use in various local and 84 global contexts is seen to trigger Domain Name System (DNS) [RFC1034] 85 queries (of the form of "reverse lookups") corresponding to these 86 addresses. Since the addresses concerned generally have local rather 87 than global significance, it is good practice for site administrators 88 to ensure that such queries are answered locally [RFC6303]. However, 89 it is not uncommon for such queries to follow the normal delegation 90 path in the public DNS instead of being answered within the site. It 91 is not possible for public DNS servers to give useful answers to such 92 queries, and the response to such reverse lookup queries from the 93 global DNS is the "Name Error" RCODE described in [RFC1035], commonly 94 termed "NXDOMAIN". 96 When the reverse-DNS infrastructure receives a request for un- 97 delegated sub-domains, the point of delegation of the last matched 98 label along the name path to the root receives the query. In the 99 case of the IPv6 reverse delegation structure, this implies that the 100 IP6.ARPA authoritative servers will receive the query load. Because 101 the sub-domain is not delegated, the server is obliged to answer with 102 an NXDOMAIN response. A large number of these DNS queries are 103 repeated, further increasing the DNS query load imposed on the DNS 104 root servers and the IP6.ARPA authoritative servers. 106 This query load appears to have unacceptable scaling consequences as 107 IPv6 uptake increases. By delegating these sub-domains to the AS112 108 project [RFC6304], the DNS query load can be passed off to a 109 distributed dedicated server set, reducing the load through the DNS 110 root and on the IP6.ARPA authoritative servers. 112 2. IANA Considerations 114 As per the provisions of [RFC3152], this document recommends the IAB 115 to direct IANA to delegate the following IP6.ARPA reverse DNS zones 116 to the AS112 project [RFC6304]: 118 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa (Unspecified) 119 8.e.f.ip6.arpa (Link-Local Scope) 120 9.e.f.ip6.arpa (Link-Local Scope) 121 a.e.f.ip6.arpa (Link-Local Scope) 122 b.e.f.ip6.arpa (Link-Local Scope) 123 c.e.f.ip6.arpa (Site-Local Scope) 124 d.e.f.ip6.arpa (Site-Local Scope) 125 e.e.f.ip6.arpa (Site-Local Scope) 126 f.e.f.ip6.arpa (Site-Local Scope) 127 1.0.f.f.ip6.arpa (Interface-Local multicast scope) 128 2.0.f.f.ip6.arpa (Link-Local multicast scope) 129 4.0.f.f.ip6.arpa (Admin-Local multicast scope) 130 5.0.f.f.ip6.arpa (Site-Local multicast scope) 131 8.0.f.f.ip6.arpa (Organization-Local multicast scope) 132 0.0.0.0.1.0.0.2.ip6.arpa (Teredo) 133 8.B.D.0.1.0.0.2.ip6.arpa (Documentation Prefix) 135 AS112 project servers should add these zones to their configuration, 136 and terminate queries efficiently inside their service 137 infrastructure. 139 This delegation instruction is subject to further direction in the 140 future from the IAB to IANA, as per the provisions of [RFC3152]. 142 3. Security Considerations 144 The Security Considerations described in [RFC6304] also apply to 145 local-use IPv6 addresses, and should be considered in the context of 146 the use of these addresses. 148 DNS queries may well identify the location of deployment of IPv6 149 enabled equipment in private contexts, particularly when the reverse 150 queries relate to local-use IPv6 addresses. While operators of the 151 DNS reverse servers should respect the privacy of data relating to 152 individual queries made to these reverse address servers, the 153 unintentional leakage of information beyond its intended scope of use 154 and circulation represents a potential threat to the security of a 155 local private network. This direction to delegate these local-use 156 IPv6 reverse address sub-domains does not substantially change the 157 security risks of information leakage from private environments. 159 4. Acknowledgments 160 The authors acknowledge the work of Joe Abley and William Maton and 161 the DNSOPS Working Group in preparing the AS112 framework document 162 for delegation of the private use address blocks in IPv4, and have 163 used parts of their AS112 document as a template for these AS112 164 delegation instructions in IPv6. John Mann also provided much useful 165 feedback. 167 5. Changes 169 [Note: This section is not for publication.] 171 5.1. Changes since the -00 draft 173 The multicast ranges were stripped back to the subset of scopes which 174 do not have future specific applicability for a reverse-DNS registry 175 under consideration by the multicast community of interest. 177 mis-labelled Site-Local addresses were renamed (john mann) 179 6. References 181 6.1. Normative References 183 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 184 STD 13, RFC 1034, November 1987. 186 6.2. Informative References 188 [RFC1035] Mockapetris, P., "Domain names - implementation and 189 specification", STD 13, RFC 1035, November 1987. 191 [RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152, 192 August 2001. 194 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 195 Addresses", RFC 4193, October 2005. 197 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 198 Architecture", RFC 4291, February 2006. 200 [RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163, RFC 201 6303, July 2011. 203 [RFC6304] Abley, J. and W. Maton, "AS112 Nameserver Operations", RFC 204 6304, July 2011. 206 Authors' Addresses 208 George Michaelson 209 APNIC 211 Email: ggm@apnic.net 212 URI: http://www.apnic.net 213 Geoff Huston 214 APNIC 216 Email: gih@apnic.net 217 URI: http://www.apnic.net 219 Joe Abley 220 ICANN 222 Email: joe.abley@icann.org 224 William F. Maton Sotomayor 225 NRC 227 Email: wmaton@ryouko.imsb.nrc.ca