idnits 2.17.1 draft-ietf-dnsop-rfc6598-rfc6303-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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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 12: '... [100.64.0.0/10] MUST NOT be forwarded...' RFC 2119 keyword, line 65: '... [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 (Oct 2014) is 3480 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (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 (~~), 3 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 Expires: April 4, 2015 Oct 2014 6 Add 100.64.0.0/10 prefixes to IPv4 Locally-Served DNS Zones Registry. 7 draft-ietf-dnsop-rfc6598-rfc6303-02 9 Abstract 11 RFC6598 specified that: "Reverse DNS queries for Shared Address Space 12 addresses [100.64.0.0/10] MUST NOT be forwarded to the global DNS 13 infrastructure." 15 This document formally directs IANA to add the associated zones to 16 the "IPv4 Locally-Served DNS Zones Registry" to prevent such queries 17 accidently leaking to the global DNS infrastructure. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 4, 2015. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Changes to IPv4 Locally-Served DNS Zones Registry . . . . . . . 3 55 2.1. RFC6598 Zones . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 58 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 59 6. Normative References . . . . . . . . . . . . . . . . . . . . . 5 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 1. Introduction 64 [RFC6598] specified that: "Reverse DNS queries for Shared Address 65 Space addresses [100.64.0.0/10] MUST NOT be forwarded to the global 66 DNS infrastructure." [RFC6303] provides guidance on handling such 67 queries. 69 This document directs the IANA to add the IPv4 reverse zones 70 corresponding to 100.64.0.0/10, a netblock reserved in [RFC6598], to 71 the IPv4 Locally-Served DNS Zone Registry established in [RFC6303]. 73 Unlike [RFC1918] address, which are not expected to be seen by other 74 parties, the addresses from [RFC6598] are expected to be seen by 75 parties other than those deploying the addresses, so it is more 76 crucial that recursive nameservers default to serving these zones 77 locally. 79 2. Changes to IPv4 Locally-Served DNS Zones Registry 81 To add the following zone listed in RFC6598 Zones (Section 2.1) to 82 the "IPv4 Locally-Served DNS Zone Registry". 84 2.1. RFC6598 Zones 86 64.100.IN-ADDR.ARPA 87 65.100.IN-ADDR.ARPA 88 66.100.IN-ADDR.ARPA 89 67.100.IN-ADDR.ARPA 90 68.100.IN-ADDR.ARPA 91 69.100.IN-ADDR.ARPA 92 70.100.IN-ADDR.ARPA 93 71.100.IN-ADDR.ARPA 94 72.100.IN-ADDR.ARPA 95 73.100.IN-ADDR.ARPA 96 74.100.IN-ADDR.ARPA 97 75.100.IN-ADDR.ARPA 98 76.100.IN-ADDR.ARPA 99 77.100.IN-ADDR.ARPA 100 78.100.IN-ADDR.ARPA 101 79.100.IN-ADDR.ARPA 102 80.100.IN-ADDR.ARPA 103 81.100.IN-ADDR.ARPA 104 82.100.IN-ADDR.ARPA 105 83.100.IN-ADDR.ARPA 106 84.100.IN-ADDR.ARPA 107 85.100.IN-ADDR.ARPA 108 86.100.IN-ADDR.ARPA 109 87.100.IN-ADDR.ARPA 110 88.100.IN-ADDR.ARPA 111 89.100.IN-ADDR.ARPA 112 90.100.IN-ADDR.ARPA 113 91.100.IN-ADDR.ARPA 114 92.100.IN-ADDR.ARPA 115 93.100.IN-ADDR.ARPA 116 94.100.IN-ADDR.ARPA 117 95.100.IN-ADDR.ARPA 118 96.100.IN-ADDR.ARPA 119 97.100.IN-ADDR.ARPA 120 98.100.IN-ADDR.ARPA 121 99.100.IN-ADDR.ARPA 122 100.100.IN-ADDR.ARPA 123 101.100.IN-ADDR.ARPA 124 102.100.IN-ADDR.ARPA 125 103.100.IN-ADDR.ARPA 126 104.100.IN-ADDR.ARPA 127 105.100.IN-ADDR.ARPA 128 106.100.IN-ADDR.ARPA 129 107.100.IN-ADDR.ARPA 130 108.100.IN-ADDR.ARPA 131 109.100.IN-ADDR.ARPA 132 110.100.IN-ADDR.ARPA 133 111.100.IN-ADDR.ARPA 134 112.100.IN-ADDR.ARPA 135 113.100.IN-ADDR.ARPA 136 114.100.IN-ADDR.ARPA 137 115.100.IN-ADDR.ARPA 138 116.100.IN-ADDR.ARPA 139 117.100.IN-ADDR.ARPA 140 118.100.IN-ADDR.ARPA 141 119.100.IN-ADDR.ARPA 142 120.100.IN-ADDR.ARPA 143 121.100.IN-ADDR.ARPA 144 122.100.IN-ADDR.ARPA 145 123.100.IN-ADDR.ARPA 146 124.100.IN-ADDR.ARPA 147 125.100.IN-ADDR.ARPA 148 126.100.IN-ADDR.ARPA 149 127.100.IN-ADDR.ARPA 151 3. IANA Considerations 153 This document directs IANA to add the zones listed in RFC6598 Zones 154 (Section 2.1) to the "IPv4 Locally-Served DNS Zone Registry". 156 IANA is reminded that a insecure delegation for these zones is 157 required for compliance with [RFC6598] to break the DNSSEC chain of 158 trust. 160 4. Security Considerations 162 This document is thought to present no additional security risks to 163 the Internet. 165 5. Acknowledgements 167 I would like to thank Joe Abley for his review comments. 169 6. Normative References 171 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 172 E. Lear, "Address Allocation for Private Internets", 173 BCP 5, RFC 1918, February 1996. 175 [RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163, 176 RFC 6303, July 2011. 178 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 179 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 180 Space", BCP 153, RFC 6598, April 2012. 182 Author's Address 184 M. Andrews 185 Internet Systems Consortium 186 950 Charter Street 187 Redwood City, CA 94063 188 US 190 Email: marka@isc.org