6440
PROPOSED STANDARD
The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
Authors: G. Zorn, Q. Wu, Y. Wang
Date: December 2011
Area: sec
Working Group: hokey
Stream: IETF
Abstract
In order to derive a Domain-Specific Root Key (DSRK) from the Extended Master Session Key (EMSK) generated as a side effect of an Extensible Authentication Protocol (EAP) method, the EAP peer must discover the name of the domain to which it is attached.
This document specifies a Dynamic Host Configuration Protocol Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform clients using the EAP Re-authentication Protocol (ERP) EAP method of the name of the local domain for ERP. [STANDARDS-TRACK]
RFC 6440
PROPOSED STANDARD
Internet Engineering Task Force (IETF) G. Zorn
Request for Comments: 6440 Network Zen
Category: Standards Track Q. Wu
ISSN: 2070-1721 Y. Wang
Huawei
December 2011
The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
Abstract
In order to derive a Domain-Specific Root Key (DSRK) from the
Extended Master Session Key (EMSK) generated as a side effect of an
Extensible Authentication Protocol (EAP) method, the EAP peer must
discover the name of the domain to which it is attached.
This document specifies a Dynamic Host Configuration Protocol
Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform
clients using the EAP Re-authentication Protocol (ERP) EAP method of
the name of the local domain for ERP.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6440">http://www.rfc-editor.org/info/rfc6440</a>.
<span class="grey">Zorn, et al. Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6440">RFC 6440</a> The ERP Local Domain Name DHCPv6 Option December 2011</span>
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Standards Language .........................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Acronyms ...................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Option Format ...................................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. DHCPv6 ERP Local Domain Name Option ........................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Client Behavior .................................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. Relay Agent Behavior ............................................<a href="#page-4">4</a>
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-4">4</a>
<a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-4">4</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The EAP Re-authentication Protocol (ERP) [<a href="./rfc5296" title=""EAP Extensions for EAP Re-authentication Protocol (ERP)"">RFC5296</a>] is designed to
allow faster re-authentication of a mobile device that was previously
authenticated by means of the Extensible Authentication Protocol
[<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>]. Given that the local root key (e.g., a DSRK, as described
in <a href="./rfc5295">RFC 5295</a> [<a href="./rfc5295" title=""Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)"">RFC5295</a>]) is generated using the local domain name
(LDN), LDN discovery is an important part of re-authentication. As
described in <a href="./rfc5296">RFC 5296</a> [<a href="./rfc5296" title=""EAP Extensions for EAP Re-authentication Protocol (ERP)"">RFC5296</a>], the LDN to be used in ERP can be
learned by the mobile device through the ERP exchange or via a lower-
layer mechanism. However, no lower-layer mechanisms for LDN
discovery have yet been defined.
This document specifies an extension to DHCPv6 for LDN to be used
in ERP.
<span class="grey">Zorn, et al. Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6440">RFC 6440</a> The ERP Local Domain Name DHCPv6 Option December 2011</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Standards Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Acronyms</span>
o FQDN: Fully Qualified Domain Name
o AAA: Authentication, Authorization, and Accounting
o DSRK: Domain-Specific Root Key
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Option Format</span>
In DHCPv6-based local domain name discovery, the LDN option is used
by the DHCPv6 client to obtain the local domain name from the DHCPv6
server after full EAP authentication has taken place.
The contents of the ERP Local Domain Name option are intended only
for use with ERP and do not represent the name of a local domain for
any other purposes.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. DHCPv6 ERP Local Domain Name Option</span>
The format of this option is:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_ERP_LOCAL_DOMAIN_NAME| option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| erp-local-domain-name...
+-+-+-+-+-+-+-+-+-+-+-+-+-
option code
OPTION_ERP_LOCAL_DOMAIN_NAME (65)
option-length
Length of the erp-local-domain-name field, in octets
<span class="grey">Zorn, et al. Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6440">RFC 6440</a> The ERP Local Domain Name DHCPv6 Option December 2011</span>
erp-local-domain-name
This field contains the name of the local ERP domain and MUST be
encoded as specified in <a href="./rfc3315#section-8">Section 8 of RFC 3315</a> [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]. Note
that this encoding does enable the use of internationalized domain
names, but only as a set of A-labels [<a href="./rfc5890" title=""Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"">RFC5890</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Client Behavior</span>
If a DHCPv6 client doesn't know the ERP LDN and requires the DHCPv6
server to provide the DHCPv6 ERP LDN option, it MUST include an
Option Request option requesting the DHCPv6 ERP Local Domain Name
option, as described in <a href="./rfc3315#section-22.7">Section 22.7 of RFC 3315</a> [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>].
When the DHCPv6 client receives an ERP Local Domain Name option with
the ERP LDN present in it, it MUST verify that the option length is
no more than 256 octets (the maximum length of a single fully
qualified domain name (FQDN) allowed by the DNS), and that the local
domain name is a properly encoded single FQDN, as specified in
<a href="./rfc3315#section-8">Section 8 of RFC 3315</a> ("Representation and Use of Domain Names")
[<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Relay Agent Behavior</span>
If a DHCPv6 relay agent has pre-existing knowledge of the ERP local
domain name for a client (for example, from a previous AAA exchange),
it SHOULD include it in an instance of the DHCPv6 ERP Local Domain
Name option and forward to the DHCPv6 server as a suboption of the
Relay-Supplied Options option [<a href="./rfc6422" title=""Relay-Supplied DHCP Options"">RFC6422</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The communication between the DHCPv6 client and the DHCPv6 server for
the exchange of local domain name information is security sensitive
and requires server authentication and integrity protection. DHCPv6
security as described in [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] can be used for this purpose.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
IANA has added the name "OPTION_ERP_LOCAL_DOMAIN_NAME" to the
registry titled "Options Permitted in the Relay-Supplied Options
Option" maintained at <a href="http://www.iana.org/">http://www.iana.org/</a>.
IANA has assigned one new option code to the registry titled "DHCP
Option Codes" maintained at <a href="http://www.iana.org/">http://www.iana.org/</a>, referencing this
document.
<span class="grey">Zorn, et al. Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6440">RFC 6440</a> The ERP Local Domain Name DHCPv6 Option December 2011</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
[<a id="ref-RFC5295">RFC5295</a>] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri,
"Specification for the Derivation of Root Keys from an
Extended Master Session Key (EMSK)", <a href="./rfc5295">RFC 5295</a>,
August 2008.
[<a id="ref-RFC5296">RFC5296</a>] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP
Re-authentication Protocol (ERP)", <a href="./rfc5296">RFC 5296</a>, August 2008.
[<a id="ref-RFC6422">RFC6422</a>] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options",
<a href="./rfc6422">RFC 6422</a>, December 2011.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC3748">RFC3748</a>] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
Levkowetz, Ed., "Extensible Authentication Protocol
(EAP)", <a href="./rfc3748">RFC 3748</a>, June 2004.
[<a id="ref-RFC5890">RFC5890</a>] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
<a href="./rfc5890">RFC 5890</a>, August 2010.
<span class="grey">Zorn, et al. Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6440">RFC 6440</a> The ERP Local Domain Name DHCPv6 Option December 2011</span>
Authors' Addresses
Glen Zorn
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 87-040-4617
EMail: [email protected]
Qin Wu
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Phone: +86-25-56623633
EMail: [email protected]
Yungui Wang
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Phone: +86-25-56624545
EMail: [email protected]
Zorn, et al. Standards Track [Page 6]
Annotations
Select text to annotate