idnits 2.17.1 draft-donley-dhc-cer-id-option-01.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 : ---------------------------------------------------------------------------- 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 (September 6, 2012) is 4221 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Donley 3 Internet-Draft C. Grundemann 4 Intended status: Informational CableLabs 5 Expires: March 10, 2013 September 6, 2012 7 Customer Edge Router Identification Option 8 draft-donley-dhc-cer-id-option-01 10 Abstract 12 Several addressing mechanisms supporting DHCPv6 Prefix Delegation in 13 home networks require identification of the customer edge router 14 (CER) as the demarcation between the customer network and the service 15 provider network. This document reserves a DHCPv6 option to identify 16 the CER. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on March 10, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 54 2. CER Identification Option . . . . . . . . . . . . . . . . . . . 3 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 60 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 63 1. Introduction 65 Several addressing mechanisms supporting DHCPv6 Prefix Delegation in 66 home networks such as [I-D.gmann-homenet-relay-autoconf] require 67 identification of the customer edge router as the demarcation between 68 the customer network and the service provider network. For prefix 69 delegation purposes, it is desirable for other routers within the 70 home to know which device is the CER so that the customer nome 71 network only requests a single prefix from the ISP DHCPv6 server, and 72 efficiently distributes this prefix within the home. This document 73 reserves a DHCPv6 option to be used to identify the CER. 75 1.1. Requirements Language 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 RFC 2119 [RFC2119]. 81 2. CER Identification Option 83 A CER sets the CER_ID to the IPv6 address of its LAN interface. If 84 it has more than one LAN IPv6 address, it selects one of its LAN or 85 loopback IPv6 addresses to be used in the CER_ID. An ISP server does 86 not respond with the CER_ID or sets the CER_ID to ::. Such a 87 response or lack of response indicates to the DHCPv6 client that it 88 is the CER. 90 The format of the CER Identification option is: 92 0 1 2 3 93 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 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 | option-code | option-len | 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | | 98 | CER_ID | 99 | | 100 | | 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 option-code OPTION_CER_ID (TBD). 103 option-len 16 104 CER_ID value IPv6 address of CER or :: 106 Figure 1. 108 A DHCPv6 client SHOULD include the CER Identification option code in 109 an Option Request option [RFC3315] in its DHCP Solicit messages. The 110 DHCPv6 server MAY include the CER Identification option in any 111 response it sends to a client that has included the CER 112 Identification option code in an Option Request option. The CER 113 Identification option is sent in the main body of the message to 114 client, not as a sub-option in, e.g., an IA_NA, IA_TA 115 [RFC3315]option. When sending the CER Identification option, the 116 DHCPv6 server MUST set the CER_ID value to either one of its IPv6 117 addresses or ::. If a device does not receive the CER Identification 118 Option or receives a CER ID of :: from the DHCPv6 server, it MUST 119 include one of its Globally Unique IPv6 address(es) in the CER_ID 120 value in response to DHCPv6 messages received by its DHCPv6 server 121 that contains the CER Identification option code in an Option Request 122 option. If the device has only one LAN interface, it SHOULD use its 123 LAN IPv6 address as the CER_ID value. If the device has more than 124 one LAN interface, it SHOULD use the lowest Globally Unique address 125 not assigned to its WAN interface. 127 3. IANA Considerations 129 IANA is requested to assign an option code from the "DHCP Option 130 Codes" Registry for OPTION_CER_ID. 132 4. Security Considerations 134 TBD 136 5. Acknowledgements 138 6. References 140 6.1. Normative References 142 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 143 Requirement Levels", BCP 14, RFC 2119, March 1997. 145 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 146 and M. Carney, "Dynamic Host Configuration Protocol for 147 IPv6 (DHCPv6)", RFC 3315, July 2003. 149 6.2. Informative References 151 [I-D.gmann-homenet-relay-autoconf] 152 Grundemann, C. and C. Donley, "Home Network 153 Autoconfiguration via DHCPv6 Relay", 154 draft-gmann-homenet-relay-autoconf-01 (work in progress), 155 March 2012. 157 Authors' Addresses 159 Chris Donley 160 CableLabs 161 858 Coal Creek Cir. 162 Louisville, CO 80027 163 US 165 Email: c.donley@cablelabs.com 167 Chris Grundemann 168 CableLabs 169 858 Coal Creek Cir. 170 Louisville, CO 80027 171 US 173 Email: c.grundemann@cablelabs.com