idnits 2.17.1 draft-andrews-dnsop-pd-reverse-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 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 16, 2013) is 3817 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) ** Obsolete normative reference: RFC 2845 (Obsoleted by RFC 8945) ** Obsolete normative reference: RFC 3633 (Obsoleted by RFC 8415) Summary: 2 errors (**), 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 Expires: April 19, 2014 October 16, 2013 6 Automatic Delegation of IP6.ARPA reverse zones with PD 7 draft-andrews-dnsop-pd-reverse-00 9 Abstract 11 This document describes a method to automate the delegation of 12 IPv6.ARPA reverse zones when performing Prefix Delegations. 14 Status of this Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on April 19, 2014. 31 Copyright Notice 33 Copyright (c) 2013 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 52 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 53 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 1. Introduction 57 This document describes a method to automate the delegation of 58 IPv6.ARPA reverse zones when performing Prefix Delegations. 60 This will allow home users and small businesses to have IPv6.ARPA 61 zones without manual intervention on the part of the ISP. 63 2. Method 65 CPE generates a RSA key pair and stores this in non-volatile memory. 67 CPE generates DHCPv6 Prefix Delegation [RFC3633] request which 68 includes a KEY-RDATA option (code point TBA) which contains a the 69 rdata of a DNS KEY record containing a RSASHA256 key using the public 70 components of the previously generated RSA key pair. 72 DHCP server updates DNS server based on the prefix it is delegating 73 and the KEY-RDATA using TSIG [RFC2845] for authentication and 74 responds with prefix. If this is a new prefix delegation it will 75 clear out all the old DNS records as part of the delegation processs. 76 If there are multiple prefixes being delegated the ISP's DNS server 77 will be updated for all of them. 79 The CPE device configures the nameserver built in to it to server the 80 reverse of the delegated prefixes. Alternatively it may configure 81 other nameservers to server these zones however the method to do that 82 is out of scope for this document. 84 CPE device generates DNS UPDATE [RFC2136] which delegates the reverse 85 name space to itself and others if they have been configured. The 86 CPE uses SIG(0) [RFC2931] to sign the request with owner name 87 matching the reverse of the delegated prefix. 89 The ISP's DNS server is configured to accept self signed requests 90 (the owner name used in the SIG(0) signature matches the owner name 91 of the data to be updated). It examines the request. Looks at the 92 KEY record added by the DHCPv6 server and decides the request is 93 valid. 95 3. IANA Considerations 97 Allocate a DHCPv6 code point for KEY-RDATA. 99 4. Security Considerations 101 The UPDATE requests are all signed. This is a proven method for 102 securing UPDATE requests in the DNS. 104 As a RSA key is being used there is no issue with the key material 105 being in the clear. 107 Only the CPE device and the ISP itself is capable of creating, 108 updating or destroying the delegation. 110 5. Normative References 112 [RFC2136] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound, 113 "Dynamic Updates in the Domain Name System (DNS UPDATE)", 114 RFC 2136, April 1997. 116 [RFC2845] Vixie, P., Gudmundsson, O., Eastlake, D., and B. 117 Wellington, "Secret Key Transaction Authentication for DNS 118 (TSIG)", RFC 2845, May 2000. 120 [RFC2931] Eastlake, D., "Secret Key Transaction Authentication for 121 DNS (TSIG)", RFC 2931, September 2000. 123 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 124 Host Configuration Protocol (DHCP) version 6", RFC 3633, 125 December 2003. 127 Author's Address 129 M. Andrews 130 Internet Systems Consortium 131 950 Charter Street 132 Redwood City, CA 94063 133 US 135 Email: marka@isc.org