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
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
EAP重新认证协议（ERP）本地域名DHCPv6选项
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.
为了从作为可扩展身份验证协议（EAP）方法的副作用而生成的扩展主会话密钥（EMSK）派生特定于域的根密钥（DSRK），EAP对等方必须发现其所连接的域的名称。
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.
本文档指定了动态主机配置协议版本6（DHCPv6）选项，该选项旨在允许DHCPv6服务器使用EAP重新认证协议（ERP）EAP方法通知客户端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 Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6440.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6440.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Terminology .....................................................3
2.1. Standards Language .........................................3
2.2. Acronyms ...................................................3
3. Option Format ...................................................3
3.1. DHCPv6 ERP Local Domain Name Option ........................3
4. Client Behavior .................................................4
5. Relay Agent Behavior ............................................4
6. Security Considerations .........................................4
7. IANA Considerations .............................................4
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................5
1. Introduction ....................................................2
2. Terminology .....................................................3
2.1. Standards Language .........................................3
2.2. Acronyms ...................................................3
3. Option Format ...................................................3
3.1. DHCPv6 ERP Local Domain Name Option ........................3
4. Client Behavior .................................................4
5. Relay Agent Behavior ............................................4
6. Security Considerations .........................................4
7. IANA Considerations .............................................4
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................5
The EAP Re-authentication Protocol (ERP) [RFC5296] is designed to allow faster re-authentication of a mobile device that was previously authenticated by means of the Extensible Authentication Protocol [RFC3748]. Given that the local root key (e.g., a DSRK, as described in RFC 5295 [RFC5295]) is generated using the local domain name (LDN), LDN discovery is an important part of re-authentication. As described in RFC 5296 [RFC5296], 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.
EAP重新认证协议（ERP）[RFC5296]旨在允许对之前通过可扩展认证协议[RFC3748]进行认证的移动设备进行更快的重新认证。鉴于本地根密钥（如RFC 5295[RFC5295]中所述的DSRK）是使用本地域名（LDN）生成的，LDN发现是重新认证的一个重要部分。如RFC 5296[RFC5296]所述，移动设备可通过ERP交换或通过较低层机制学习ERP中使用的LDN。然而，尚未定义LDN发现的较低层机制。
This document specifies an extension to DHCPv6 for LDN to be used in ERP.
本文档指定了用于ERP的LDN对DHCPv6的扩展。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
o FQDN: Fully Qualified Domain Name
o FQDN：完全限定域名
o AAA: Authentication, Authorization, and Accounting
o AAA：身份验证、授权和记帐
o DSRK: Domain-Specific Root Key
o DSRK：特定于域的根密钥
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.
在基于DHCPv6的本地域名发现中，DHCPv6客户端使用LDN选项在进行完全EAP身份验证后从DHCPv6服务器获取本地域名。
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.
“ERP本地域名”选项的内容仅用于ERP，不代表用于任何其他目的的本地域名。
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...
+-+-+-+-+-+-+-+-+-+-+-+-+-
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)
选项代码选项\u ERP\u本地\u域名（65）
option-length Length of the erp-local-domain-name field, in octets
选项长度erp本地域名字段的长度，以八位字节为单位
erp-local-domain-name This field contains the name of the local ERP domain and MUST be encoded as specified in Section 8 of RFC 3315 [RFC3315]. Note that this encoding does enable the use of internationalized domain names, but only as a set of A-labels [RFC5890].
erp本地域名此字段包含本地erp域的名称，必须按照RFC 3315[RFC3315]第8节的规定进行编码。注意，这种编码允许使用国际化域名，但只能作为一组a标签[RFC5890]。
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 Section 22.7 of RFC 3315 [RFC3315].
如果DHCPv6客户端不知道ERP LDN并要求DHCPv6服务器提供DHCPv6 ERP LDN选项，则必须包括一个选项请求选项，请求DHCPv6 ERP本地域名选项，如RFC 3315[RFC3315]第22.7节所述。
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 Section 8 of RFC 3315 ("Representation and Use of Domain Names") [RFC3315].
当DHCPv6客户端接收到ERP本地域名选项且其中包含ERP LDN时，它必须验证该选项长度不超过256个八位字节（DNS允许的单个完全限定域名（FQDN）的最大长度），并且本地域名是正确编码的单个FQDN，按照RFC 3315第8节（“域名的表示和使用”）[RFC3315]的规定。
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 [RFC6422].
如果DHCPv6中继代理预先知道客户端的ERP本地域名（例如，从以前的AAA交换中），则应将其包含在DHCPv6 ERP本地域名选项的实例中，并作为中继提供的选项的子选项[RFC6422]转发到DHCPv6服务器。
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 [RFC3315] can be used for this purpose.
DHCPv6客户端和DHCPv6服务器之间用于交换本地域名信息的通信是安全敏感的，需要服务器身份验证和完整性保护。[RFC3315]中所述的DHCPv6安全性可用于此目的。
IANA has added the name "OPTION_ERP_LOCAL_DOMAIN_NAME" to the registry titled "Options Permitted in the Relay-Supplied Options Option" maintained at http://www.iana.org/.
IANA已将名称“OPTION_ERP_LOCAL_DOMAIN_name”添加到名为“继电器提供的选项中允许的选项”的注册表中，该注册表保存在http://www.iana.org/.
IANA has assigned one new option code to the registry titled "DHCP Option Codes" maintained at http://www.iana.org/, referencing this document.
IANA已将一个名为“DHCP选项代码”的新选项代码分配给位于http://www.iana.org/，参考本文件。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3315]Droms，R.，Ed.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri, "Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)", RFC 5295, August 2008.
[RFC5295]Salowey，J.，Dondeti，L.，Narayanan，V.，和M.Nakhjiri，“从扩展主会话密钥（EMSK）派生根密钥的规范”，RFC 52952008年8月。
[RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re-authentication Protocol (ERP)", RFC 5296, August 2008.
[RFC5296]Narayanan，V.和L.Dondeti，“EAP再认证协议（ERP）的EAP扩展”，RFC 52962008年8月。
[RFC6422] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", RFC 6422, December 2011.
[RFC6422]Lemon，T.和Q.Wu，“继电器提供的DHCP选项”，RFC 6422，2011年12月。
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. Levkowetz, Ed., "Extensible Authentication Protocol (EAP)", RFC 3748, June 2004.
[RFC3748]Aboba，B.，Blunk，L.，Vollbrecht，J.，Carlson，J.，和H.Levkowetz，Ed.，“可扩展认证协议（EAP）”，RFC 3748，2004年6月。
[RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010.
[RFC5890]Klensin，J.，“应用程序的国际化域名（IDNA）：定义和文档框架”，RFC 58902010年8月。
Authors' Addresses
作者地址
Glen Zorn Network Zen 227/358 Thanon Sanphawut Bang Na, Bangkok 10260 Thailand
格伦佐恩网络禅宗227/358泰国曼谷Thanon Sanphawut Bang Na 10260
Phone: +66 (0) 87-040-4617
EMail: glenzorn@gmail.com
Phone: +66 (0) 87-040-4617
EMail: glenzorn@gmail.com
Qin Wu Huawei Technologies Co., Ltd. 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
中国江苏省南京市雨花区软件大道101号秦武华为技术有限公司210012
Phone: +86-25-56623633
EMail: sunseawq@huawei.com
Phone: +86-25-56623633
EMail: sunseawq@huawei.com
Yungui Wang Huawei Technologies Co., Ltd. 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
中国江苏省南京市雨花区软件大道101号王云贵华为技术有限公司210012
Phone: +86-25-56624545
EMail: w52006@huawei.com
Phone: +86-25-56624545
EMail: w52006@huawei.com