idnits 2.17.1 draft-ietf-dnsop-rfc6598-rfc6303-05.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: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 13: '... [100.64.0.0/10] MUST NOT be forwarded...' RFC 2119 keyword, line 66: '... [100.64.0.0/10] MUST NOT be forwarded...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 11, 2015) is 3120 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Andrews 3 Internet-Draft ISC 4 Intended status: Best Current Practice October 11, 2015 5 Expires: April 13, 2016 7 Add 100.64.0.0/10 prefixes to IPv4 Locally-Served DNS Zones Registry. 8 draft-ietf-dnsop-rfc6598-rfc6303-05 10 Abstract 12 RFC6598 specified that: "Reverse DNS queries for Shared Address Space 13 addresses [100.64.0.0/10] MUST NOT be forwarded to the global DNS 14 infrastructure." 16 This document formally directs IANA to add the associated zones to 17 the "IPv4 Locally-Served DNS Zones Registry" to prevent such queries 18 accidently leaking to the global DNS infrastructure. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 13, 2016. 37 Copyright Notice 39 Copyright (c) 2015 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Changes to IPv4 Locally-Served DNS Zones Registry . . . . . . 2 56 2.1. RFC6598 Zones . . . . . . . . . . . . . . . . . . . . . . 2 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 60 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 63 1. Introduction 65 [RFC6598] specified that: "Reverse DNS queries for Shared Address 66 Space addresses [100.64.0.0/10] MUST NOT be forwarded to the global 67 DNS infrastructure." [RFC6303] provides guidance on handling such 68 queries. 70 This document directs the IANA to add the IPv4 reverse zones 71 corresponding to 100.64.0.0/10, a netblock reserved in [RFC6598], to 72 the IPv4 Locally-Served DNS Zone Registry established in [RFC6303]. 74 Unlike [RFC1918] address, which are not expected to be seen by other 75 parties, the addresses from [RFC6598] are expected to be seen by 76 parties other than those deploying the addresses, so it is more 77 crucial that recursive nameservers default to serving these zones 78 locally. 80 2. Changes to IPv4 Locally-Served DNS Zones Registry 82 To add the following zone listed in RFC6598 Zones (Section 2.1) to 83 the "IPv4 Locally-Served DNS Zone Registry". 85 2.1. RFC6598 Zones 87 64.100.IN-ADDR.ARPA 89 65.100.IN-ADDR.ARPA 91 66.100.IN-ADDR.ARPA 93 67.100.IN-ADDR.ARPA 95 68.100.IN-ADDR.ARPA 96 69.100.IN-ADDR.ARPA 98 70.100.IN-ADDR.ARPA 100 71.100.IN-ADDR.ARPA 102 72.100.IN-ADDR.ARPA 104 73.100.IN-ADDR.ARPA 106 74.100.IN-ADDR.ARPA 108 75.100.IN-ADDR.ARPA 110 76.100.IN-ADDR.ARPA 112 77.100.IN-ADDR.ARPA 114 78.100.IN-ADDR.ARPA 116 79.100.IN-ADDR.ARPA 118 80.100.IN-ADDR.ARPA 120 81.100.IN-ADDR.ARPA 122 82.100.IN-ADDR.ARPA 124 83.100.IN-ADDR.ARPA 126 84.100.IN-ADDR.ARPA 128 85.100.IN-ADDR.ARPA 130 86.100.IN-ADDR.ARPA 132 87.100.IN-ADDR.ARPA 134 88.100.IN-ADDR.ARPA 136 89.100.IN-ADDR.ARPA 138 90.100.IN-ADDR.ARPA 140 91.100.IN-ADDR.ARPA 142 92.100.IN-ADDR.ARPA 143 93.100.IN-ADDR.ARPA 145 94.100.IN-ADDR.ARPA 147 95.100.IN-ADDR.ARPA 149 96.100.IN-ADDR.ARPA 151 97.100.IN-ADDR.ARPA 153 98.100.IN-ADDR.ARPA 155 99.100.IN-ADDR.ARPA 157 100.100.IN-ADDR.ARPA 159 101.100.IN-ADDR.ARPA 161 102.100.IN-ADDR.ARPA 163 103.100.IN-ADDR.ARPA 165 104.100.IN-ADDR.ARPA 167 105.100.IN-ADDR.ARPA 169 106.100.IN-ADDR.ARPA 171 107.100.IN-ADDR.ARPA 173 108.100.IN-ADDR.ARPA 175 109.100.IN-ADDR.ARPA 177 110.100.IN-ADDR.ARPA 179 111.100.IN-ADDR.ARPA 181 112.100.IN-ADDR.ARPA 183 113.100.IN-ADDR.ARPA 185 114.100.IN-ADDR.ARPA 187 115.100.IN-ADDR.ARPA 189 116.100.IN-ADDR.ARPA 190 117.100.IN-ADDR.ARPA 192 118.100.IN-ADDR.ARPA 194 119.100.IN-ADDR.ARPA 196 120.100.IN-ADDR.ARPA 198 121.100.IN-ADDR.ARPA 200 122.100.IN-ADDR.ARPA 202 123.100.IN-ADDR.ARPA 204 124.100.IN-ADDR.ARPA 206 125.100.IN-ADDR.ARPA 208 126.100.IN-ADDR.ARPA 210 127.100.IN-ADDR.ARPA 212 3. IANA Considerations 214 This document directs IANA to add the zones listed in RFC6598 Zones 215 (Section 2.1) to the "IPv4 Locally-Served DNS Zone Registry". 217 IANA is reminded that an insecure delegation for these zones is 218 required for compliance with [RFC6598] to break the DNSSEC chain of 219 trust. 221 4. Security Considerations 223 This document is thought to present no additional security risks to 224 the Internet. 226 5. Acknowledgements 228 I would like to thank Joe Abley for his review comments. 230 6. Normative References 232 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 233 and E. Lear, "Address Allocation for Private Internets", 234 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 235 . 237 [RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163, RFC 238 6303, DOI 10.17487/RFC6303, July 2011, 239 . 241 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 242 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 243 Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April 244 2012, . 246 Author's Address 248 M. Andrews 249 Internet Systems Consortium 250 950 Charter Street 251 Redwood City, CA 94063 252 US 254 Email: marka@isc.org