idnits 2.17.1 draft-andrews-6man-dns64-exclude-00.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 private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. == There are 3 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 22, 2019) is 1739 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) -- Looks like a reference, but probably isn't: '1' on line 174 ** Downref: Normative reference to an Experimental RFC: RFC 3123 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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: Standards Track July 22, 2019 5 Expires: January 23, 2020 7 DNS64 Exclusion List RA Option 8 draft-andrews-6man-dns64-exclude-00 10 Abstract 12 To allow automatic device configuration to a DNS64 process behind a 13 IPv6-only link it is necessary to provide AAAA and A record exclusion 14 lists. This document provide such a mechanism. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 23, 2020. 33 Copyright Notice 35 Copyright (c) 2019 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . 2 52 2. DNS64-EXCLUDE Option . . . . . . . . . . . . . . . . . . . . 2 53 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 58 6.2. Informative References . . . . . . . . . . . . . . . . . 4 59 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 62 1. Introduction 64 To allow automatic device configuration to a DNS64 process behind a 65 IPv6-only link it is necessary to provide AAAA and A record exclusion 66 lists. This document provide such a mechanism. 68 When an DNS64 implementation needs to be configured behind DNS64 69 server, for example when performing DNSSEC [RFC4034] validation, the 70 AAAA exclusion list from [RFC6147] needs to be made available. When 71 the DNS64 implementation implementation is also on a local dual-stack 72 network the local A records also need to be excluded from DNS64 73 processing to prevent local traffic being sent to the NAT64. 75 1.1. Reserved Words 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in [RFC2119]. 81 2. DNS64-EXCLUDE Option 83 The DNS64-EXLUDE option (TBA) contains a DNS wire encoded name 84 [RFC1034] which points at 1 or 2 APL records [RFC3123] where the 85 records contain IPv4 and IPv6 exclusions lists which are encoded on a 86 first match basis. If there are multiple records prefixes for a 87 address family MUST NOT be split across multiple records as DNS 88 records are not ordered. 90 The IPv6 prefixes are used to populate the AAAA exclusion list from 91 [RFC6147] Section 5.1.4. 93 The IPv4 prefixes are used to exclude A records from translation to 94 DNS64 mapped AAAA records. 96 0 1 2 3 97 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Type | Length | Lifetime | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 | | 102 ~ DNS Wire Encoded Name ~ 103 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | | Padding | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 3. Examples 109 dns64.example.com. IN APL !1:10.0.0/24 1:10/8 2:64:ff9b::/32 111 Single Record 113 dns64.example.com. IN APL !1:10.0.0/24 1:10/8 114 dns64.example.com. IN APL 2:64:ff9b::/32 116 Multiple Records 118 Exclude 10.0.0.0/8 except for 10.0.0.0/24 from DNS64 processing. 120 Exclude the well known DNS64 prefix 64:ff9b::/32 from DNS64 121 processing. 123 4. IANA Considerations 125 The IANA is requested to assign a new IPv6 Neighbor Discovery Option 126 type for the DNS64-EXCLUDE option defined in this document. 128 +----------------------+-------+ 129 | Option Name | Type | 130 +----------------------+-------+ 131 | DNS64-EXCLUDE option | (TBD) | 132 +----------------------+-------+ 134 The IANA registry for these options is: 136 https://www.iana.org/assignments/icmpv6-parameters [1] 138 5. Security Considerations 140 TBA 142 6. References 144 6.1. Normative References 146 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 147 STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, 148 . 150 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 151 Requirement Levels", BCP 14, RFC 2119, 152 DOI 10.17487/RFC2119, March 1997, 153 . 155 [RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes 156 (APL RR)", RFC 3123, DOI 10.17487/RFC3123, June 2001, 157 . 159 6.2. Informative References 161 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 162 Rose, "Resource Records for the DNS Security Extensions", 163 RFC 4034, DOI 10.17487/RFC4034, March 2005, 164 . 166 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 167 Beijnum, "DNS64: DNS Extensions for Network Address 168 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 169 DOI 10.17487/RFC6147, April 2011, 170 . 172 6.3. URIs 174 [1] https://www.iana.org/assignments/icmpv6-parameters 176 Author's Address 178 M. Andrews 179 Internet Systems Consortium 180 950 Charter Street 181 Redwood City, CA 94063 182 US 184 Email: marka@isc.org