idnits 2.17.1 draft-ietf-hokey-ldn-discovery-08.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 (April 19, 2011) is 4753 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 information found for draft-ietf-dhc-dhcpv6-relay-supplied-options - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-dhc-dhcpv6-relay-supplied-options' ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 5296 (Obsoleted by RFC 6696) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: Standards Track Q. Wu 5 Expires: October 21, 2011 Y. Wang 6 Huawei 7 April 19, 2011 9 The ERP Local Domain Name DHCPv6 Option 10 draft-ietf-hokey-ldn-discovery-08 12 Abstract 14 In order to derive a Domain-Specific Root Key (DSRK) from the 15 Extended Master Session Key (EMSK) generated as a side-effect of an 16 Extensible Authentication Protocol (EAP) method, the EAP peer must 17 discover the name of the domain to which it is attached. 19 This document specifies a Dynamic Host Configuration Protocol Version 20 6 (DHCPv6) option designed to allow a DHCPv6 server to inform clients 21 using the EAP Re-authentication Protocol (ERP) EAP method of the name 22 of the local domain. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on October 21, 2011. 41 Copyright Notice 43 Copyright (c) 2011 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 61 2.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. Option Format . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3.1. DHCPv6 ERP Local Domain Name Option . . . . . . . . . . . . 3 64 4. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 4 65 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 4 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 67 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . . 4 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 72 1. Introduction 74 The EAP Re-authentication Protocol (ERP) [RFC5296] is designed to 75 allow faster re-authentication of a mobile device which was 76 previously authenticated by means of the Extensible Authentication 77 Protocol [RFC3748]. Given that the local root key (e.g., DSRK RFC 78 5295 [RFC5295]) is generated using the local domain name (LDN), LDN 79 discovery is an important part of re-authentication. As described in 80 RFC 5296 [RFC5296], the local domain name can be learned by the 81 mobile device through the ERP exchange or via a lower-layer 82 mechanism. However, no lower-layer mechanisms for LDN discovery have 83 yet been defined. 85 This document specifies an extension to DHCPv6 for local domain name 86 discovery by ERP peers. 88 2. Terminology 90 2.1. Standards Language 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in [RFC2119]. 96 2.2. Acronyms 98 FQDN Fully Qualified Domain Name 100 AAA Authentication, Authorization and Accounting 102 DSRK Domain-Specific Root Key 104 3. Option Format 106 In DHCPv6-based local domain name discovery, the LDN option is used 107 by the DHCPv6 client to obtain the local domain name from the DHCPv6 108 Server after full EAP authentication has taken place. 110 3.1. DHCPv6 ERP Local Domain Name Option 112 The format of this option is: 114 0 1 2 3 115 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 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | OPTION_LOCAL_DOMAIN_NAME | option-length | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | local-domain-name... 121 +-+-+-+-+-+-+-+-+-+-+-+ 123 option code 124 OPTION_ERP_LOCAL_DOMAIN_NAME (TBD) 126 option-length 127 Length of the local-domain-name field, in octets 129 local-domain-name 130 This field contains the name of the local domain and MUST be 131 encoded as specified in Section 8 of RFC 3315 [RFC3315] note that 132 this encoding does enable the use of internationalized domain 133 names, but only as a set of A-labels [RFC5890]. 135 4. Client Behavior 137 If a DHCPv6 client doesn't know the local domain name and requires 138 the DHCPv6 Server to provide the DHCPv6 LDN option, it MUST include 139 an Option Request option requesting the DHCPv6 LDN option, as 140 described in Section 22.7 of RFC 3315 [RFC3315]. 142 When the DHCPv6 client recieves a LDN option with the local domain 143 name present in it, it MUST verify that the option length is no more 144 than 256 octets (the maximum length of a single fully-qualified 145 domain name (FQDN) allowed by the DNS), and that the local domain 146 name is a properly encoded single FQDN, as specified in Section 8, 147 "Representation and Use of Domain Names" of RFC3315 [RFC3315]. 149 5. Relay Agent Behavior 151 If a DHCPv6 relay agent has pre-existing knowledge of the local 152 domain name (for example, from a previous AAA exchange), it SHOULD 153 include it in an instance of the DHCPv6 LDN option and forward to the 154 DHCPv6 server as a suboption of the Relay-Supplied Options option 155 [I-D.ietf-dhc-dhcpv6-relay-supplied-options]. 157 6. Security Considerations 159 The communication between the DHCPv6 client and the DHCPv6 server for 160 the exchange of local domain name information is security sensitive 161 and requires server authentication and integrity protection. DHCPv6 162 security [RFC3315] can be used for this purpose. 164 7. IANA considerations 166 IANA is requested to assign one new option code from the registry of 167 DHCP Option Codes maintained at 168 http://www.iana.org/assignments/dhcpv6-parameters, referencing this 169 document. 171 8. References 173 8.1. Normative References 175 [I-D.ietf-dhc-dhcpv6-relay-supplied-options] Lemon, T. and W. Wu, 176 "Relay-Supplied DHCP 177 Options", draft-ietf- 178 dhc-dhcpv6-relay- 179 supplied-options-04 180 (work in progress), 181 October 2010. 183 [RFC2119] Bradner, S., "Key words 184 for use in RFCs to 185 Indicate Requirement 186 Levels", BCP 14, 187 RFC 2119, March 1997. 189 [RFC3315] Droms, R., Bound, J., 190 Volz, B., Lemon, T., 191 Perkins, C., and M. 192 Carney, "Dynamic Host 193 Configuration Protocol 194 for IPv6 (DHCPv6)", 195 RFC 3315, July 2003. 197 [RFC5295] Salowey, J., Dondeti, 198 L., Narayanan, V., and 199 M. Nakhjiri, 200 "Specification for the 201 Derivation of Root Keys 202 from an Extended Master 203 Session Key (EMSK)", 204 RFC 5295, August 2008. 206 [RFC5296] Narayanan, V. and L. 207 Dondeti, "EAP 208 Extensions for EAP Re- 209 authentication Protocol 210 (ERP)", RFC 5296, 211 August 2008. 213 8.2. Informative References 215 [RFC3748] Aboba, B., Blunk, L., 216 Vollbrecht, J., 217 Carlson, J., and H. 218 Levkowetz, "Extensible 219 Authentication Protocol 220 (EAP)", RFC 3748, 221 June 2004. 223 [RFC5890] Klensin, J., 224 "Internationalized 225 Domain Names for 226 Applications (IDNA): 227 Definitions and 228 Document Framework", 229 RFC 5890, August 2010. 231 Authors' Addresses 233 Glen Zorn 234 Network Zen 235 227/358 Thanon Sanphawut 236 Bang Na, Bangkok 10260 237 Thailand 239 Phone: +66 (0) 87-040-4617 240 EMail: gwz@net-zen.net 242 Qin Wu 243 Huawei Technologies Co., Ltd. 244 101 Software Avenue, Yuhua District 245 Nanjing, Jiangsu 21001 246 China 248 Phone: +86-25-84565892 249 EMail: sunseawq@huawei.com 251 Yungui Wang 252 Huawei Technologies Co., Ltd. 253 Site B, Floor 10, HuiHong Mansion, No.91 BaiXia Rd. 254 Nanjing, Jiangsu 210001 255 P.R. China 257 Phone: +86 25 84565893 258 EMail: w52006@huawei.com