Internet Engineering Task Force (IETF) H. Jang
Request for Comments: 6610 KISTI
Category: Standards Track A. Yegin
ISSN: 2070-1721 Samsung
K. Chowdhury
Radio Mobile Access, Inc.
J. Choi
Samsung
T. Lemon
Nominum
May 2012
Internet Engineering Task Force (IETF) H. Jang
Request for Comments: 6610 KISTI
Category: Standards Track A. Yegin
ISSN: 2070-1721 Samsung
K. Chowdhury
Radio Mobile Access, Inc.
J. Choi
Samsung
T. Lemon
Nominum
May 2012
DHCP Options for Home Information Discovery in Mobile IPv6 (MIPv6)
移动IPv6（MIPv6）中家庭信息发现的DHCP选项
Abstract
摘要
This document defines a DHCP-based scheme to enable dynamic discovery of Mobile IPv6 home network information. New DHCP options are defined that allow a mobile node to request the home agent IP address, Fully Qualified Domain Name (FQDN), or home network prefix and obtain it via the DHCP response.
本文档定义了一个基于DHCP的方案，以支持移动IPv6家庭网络信息的动态发现。定义了新的DHCP选项，允许移动节点请求归属代理IP地址、完全限定域名（FQDN）或归属网络前缀，并通过DHCP响应获取。
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/rfc6610.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6610.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从该文档中提取的代码组件必须
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.
包括信托法律条款第4.e节中所述的简化BSD许可证文本，且不提供简化BSD许可证中所述的担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction ....................................................3
2. Terminology .....................................................3
3. DHCP Options for Home Network/Agent Dynamic Discovery ...........4
3.1. MIPv6 Home Network ID FQDN Option ..........................4
3.2. Home Network Information Options ...........................5
3.2.1. MIPv6 Visited Home Network Information Option .......5
3.2.2. MIPv6 Identified Home Network Information Option ....6
3.2.3. MIPv6 Unrestricted Home Network Information Option ..6
3.3. MIPv6 Home Network Prefix Option ...........................7
3.4. MIPv6 Home Agent Address Option ............................7
3.5. MIPv6 Home Agent FQDN Option ...............................8
4. Option Usage ....................................................9
4.1. Mobile Node Behavior .......................................9
4.1.1. Requesting MIPv6 Configuration ......................9
4.1.2. Processing MIPv6 Configuration Information .........10
4.2. Relay Agent Behavior ......................................11
4.3. DHCP Server Behavior ......................................12
4.4. Home Agent Discovery Using a Network Access Server ........12
5. Security Considerations ........................................13
6. IANA Considerations ............................................14
7. Acknowledgments ................................................14
8. References .....................................................14
8.1. Normative References ......................................14
8.2. Informative References ....................................15
1. Introduction ....................................................3
2. Terminology .....................................................3
3. DHCP Options for Home Network/Agent Dynamic Discovery ...........4
3.1. MIPv6 Home Network ID FQDN Option ..........................4
3.2. Home Network Information Options ...........................5
3.2.1. MIPv6 Visited Home Network Information Option .......5
3.2.2. MIPv6 Identified Home Network Information Option ....6
3.2.3. MIPv6 Unrestricted Home Network Information Option ..6
3.3. MIPv6 Home Network Prefix Option ...........................7
3.4. MIPv6 Home Agent Address Option ............................7
3.5. MIPv6 Home Agent FQDN Option ...............................8
4. Option Usage ....................................................9
4.1. Mobile Node Behavior .......................................9
4.1.1. Requesting MIPv6 Configuration ......................9
4.1.2. Processing MIPv6 Configuration Information .........10
4.2. Relay Agent Behavior ......................................11
4.3. DHCP Server Behavior ......................................12
4.4. Home Agent Discovery Using a Network Access Server ........12
5. Security Considerations ........................................13
6. IANA Considerations ............................................14
7. Acknowledgments ................................................14
8. References .....................................................14
8.1. Normative References ......................................14
8.2. Informative References ....................................15
Before a mobile node can engage in Mobile IPv6 signaling with a home agent, it should either know the IP address of the home agent via pre-configuration or dynamically discover it. The Mobile IPv6 specification [RFC6275] describes how home agents can be dynamically discovered by mobile nodes that know the home network prefix. This scheme does not work when prefix information is not already available to the mobile node. This document specifies extensions to DHCPv6 [RFC3736] [RFC3315] to deliver the home agent information to the mobile node in the form of the IP address of the home agent or the Fully Qualified Domain Name (FQDN) [RFC1035] of the home agent. The information delivered to the mobile node may also include the home prefix for the mobile node. The solution involves defining new DHCP options to carry home network prefixes, home agent IP addresses, and FQDN information. The mobile node MAY also use the home prefix to discover the list of home agents serving the home prefix using the Dynamic Home Agent Address Discovery mechanism specified in [RFC6275].
在移动节点可以与归属代理进行移动IPv6信令之前，它应该通过预配置知道归属代理的IP地址，或者动态地发现它。移动IPv6规范[RFC6275]描述了知道家庭网络前缀的移动节点如何动态发现家庭代理。当前缀信息对移动节点不可用时，此方案不起作用。本文档指定对DHCPv6[RFC3736][RFC3315]的扩展，以归属代理的IP地址或归属代理的完全限定域名（FQDN）[RFC1035]的形式将归属代理信息传递给移动节点。交付给移动节点的信息还可以包括移动节点的归属前缀。解决方案包括定义新的DHCP选项以携带家庭网络前缀、家庭代理IP地址和FQDN信息。移动节点还可以使用归属前缀来使用在[RFC6275]中指定的动态归属代理地址发现机制来发现服务于归属前缀的归属代理的列表。
As part of configuring the initial TCP/IP parameters, a mobile node can find itself a suitable home agent. Such a home agent might reside in the access network to which the mobile node connects or in a home network with which the mobile node is associated. A mobile node can indicate its home network identity when roaming to a visited network in order to obtain the MIPv6 bootstrap parameters from the home network. As an example, the visited network may determine the home network of the mobile node based on the realm portion of the NAI (Network Access Identifier) [RFC4282] used in access authentication [RFC5447].
作为配置初始TCP/IP参数的一部分，移动节点可以找到自己合适的归属代理。这样的归属代理可以驻留在移动节点所连接的接入网络中，或者驻留在移动节点所关联的归属网络中。移动节点可以在漫游到到访网络时指示其归属网络标识，以便从归属网络获取MIPv6引导参数。例如，到访网络可以基于在接入认证[RFC5447]中使用的NAI（网络接入标识符）[RFC4282]的领域部分来确定移动节点的归属网络。
The mobile node may or may not be connected to the "home" network when it attempts to learn Mobile IPv6 home network information. This allows operators to centrally deploy home agents while being able to bootstrap mobile nodes that are already roaming. This scenario also occurs when Hierarchical Mobile IPv6 (HMIPv6) [RFC5380] is used, where the mobile node is required to discover the MAP (a special home agent) that is located multiple hops away from the mobile node's attachment point.
当移动节点尝试学习移动IPv6家庭网络信息时，它可以连接到“家庭”网络，也可以不连接到“家庭”网络。这允许运营商集中部署归属代理，同时能够引导已经漫游的移动节点。当使用分层移动IPv6（HMIPv6）[RFC5380]时，这种情况也会发生，其中移动节点需要发现距离移动节点的连接点多个跃点的MAP（特殊归属代理）。
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]中所述进行解释。
General mobility terminology can be found in [RFC3753]. The following additional terms, as defined in [RFC4640], are used in this document:
通用机动性术语可在[RFC3753]中找到。本文件中使用了[RFC4640]中定义的以下附加术语：
Access Service Provider (ASP): A network operator that provides direct IP packet forwarding to and from the mobile node.
接入服务提供商（ASP）：一家网络运营商，提供与移动节点之间的直接IP数据包转发。
Mobility Service Provider (MSP): A service provider that provides Mobile IPv6 service. In order to obtain such service, the mobile node must be authenticated and authorized to use the Mobile IPv6 service.
移动服务提供商（MSP）：提供移动IPv6服务的服务提供商。为了获得这种服务，必须对移动节点进行身份验证并授权其使用移动IPv6服务。
Mobility Service Authorizer (MSA): A service provider that authorizes Mobile IPv6 service.
移动服务授权人（MSA）：授权移动IPv6服务的服务提供商。
This section introduces new DHCP options that are used for dynamic discovery of the home agent's IPv6 address, IPv6 home network prefix, or FQDN information in Mobile IPv6. Transport to a home agent over IPv4 is also supported by specifying an IPv4-Embedded IPv6 address. The detailed procedures are described in Section 2.3.2 of "Mobile IPv6 Support for Dual Stack Hosts and Routers" [RFC5555].
本节介绍用于在移动IPv6中动态发现归属代理的IPv6地址、IPv6归属网络前缀或FQDN信息的新DHCP选项。通过指定IPv4嵌入IPv6地址，还支持通过IPv4传输到归属代理。详细程序见“双栈主机和路由器的移动IPv6支持”[RFC5555]的第2.3.2节。
The names of options listed in this section all start with MIPv6, in order to differentiate them from other DHCP options that might have similar names. However, throughout the rest of this document, the options are referred to by name without the MIPv6 prefix, for brevity.
本节中列出的选项名称均以MIPv6开头，以区别于其他可能具有类似名称的DHCP选项。但是，为了简洁起见，在本文档的其余部分中，这些选项都是按名称引用的，没有MIPv6前缀。
This option is used by mobile nodes to communicate to the DHCP server an FQDN that identifies the target home network for which the client is requesting configuration information. When the mobile node requests configuration for more than one target home network, this option is also used by the server to identify the target home network for each Identified Home Network Information option returned.
移动节点使用此选项与DHCP服务器通信FQDN，该FQDN标识客户端请求配置信息的目标家庭网络。当移动节点请求配置多个目标家庭网络时，服务器还使用此选项为返回的每个已识别家庭网络信息选项识别目标家庭网络。
When a mobile node sends this option to request information about a specific home network, the option is simply included in the DHCP message from the mobile node. When a server responds with an Identified Home Network Information option, this option MUST be encapsulated in the Identified Home Network Information option that it identifies.
当移动节点发送此选项以请求有关特定家庭网络的信息时，该选项仅包含在来自移动节点的DHCP消息中。当服务器响应标识的家庭网络信息选项时，此选项必须封装在其标识的标识的家庭网络信息选项中。
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_MIP6_HNIDF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Home Network Identifier FQDN |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_HNIDF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Home Network Identifier FQDN |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_HNIDF (49)
选项代码：选项MIP6\U HNIDF（49）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Home Network Identifier FQDN: A Fully Qualified Domain Name (FQDN) that identifies a mobile IP home network for which the client is seeking configuration information. This is encoded in accordance with RFC 3315, Section 8, "Representation and Use of Domain Names".
家庭网络标识符FQDN：一个完全限定的域名（FQDN），用于标识客户端正在查找其配置信息的移动IP家庭网络。这是根据RFC 3315第8节“域名的表示和使用”进行编码的。
There are three different options that specify home network information. Which of these options is used depends on what kind of home network information the client needs. Each of these options is used to encapsulate options containing prefix and home agent information about the home network for which configuration information was requested.
有三种不同的选项指定家庭网络信息。使用哪种选项取决于客户端需要哪种家庭网络信息。这些选项中的每一个都用于封装包含有关请求配置信息的家庭网络的前缀和家庭代理信息的选项。
This option is used by relay agents and DHCP servers to provide information about the local home network.
中继代理和DHCP服务器使用此选项提供有关本地家庭网络的信息。
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_MIP6_VDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_VDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_VDINF (50)
选项代码：选项MIP6\U VDINF（50）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Options: One or more options, specifying information about the local ASP (visited domain).
选项：一个或多个选项，指定有关本地ASP（已访问域）的信息。
This option is used by relay agents and DHCP servers to provide information about the home network identified by a Home Network Identifier FQDN option.
中继代理和DHCP服务器使用此选项提供有关由家庭网络标识符FQDN选项标识的家庭网络的信息。
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_MIP6_IDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_IDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_IDINF (69)
选项代码：选项MIP6\U IDIF（69）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Options: One or more options, specifying information about the home network identified by a Home Network Identifier FQDN option sent by a mobile node.
选项：一个或多个选项，指定有关由移动节点发送的家庭网络标识符FQDN选项标识的家庭网络的信息。
This option is used by relay agents and DHCP servers to provide information about the a home network specified by the DHCP server administrator.
中继代理和DHCP服务器使用此选项提供有关DHCP服务器管理员指定的家庭网络的信息。
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_MIP6_UDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_UDINF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Options |
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_UDINF (70)
选项代码：选项6乌迪夫（70）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Options: One or more options, specifying information about some home network as specified by the DHCP server administrator.
选项：一个或多个选项，指定DHCP服务器管理员指定的有关某个家庭网络的信息。
This option is used by DHCP servers and relay agents to define the prefix for a home network. This option should only appear in one of the Home Network Information options.
DHCP服务器和中继代理使用此选项定义家庭网络的前缀。此选项应仅出现在一个家庭网络信息选项中。
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_MIP6_HNP | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix-len | |
+-+-+-+-+-+-+-+-+ +
| |
| Prefix |
| |
| +-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_HNP | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix-len | |
+-+-+-+-+-+-+-+-+ +
| |
| Prefix |
| |
| +-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_HNP (71)
期权代码：期权MIP6\U HNP（71）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Prefix-len: Length of prefix
前缀len：前缀的长度
Prefix: Home Network Prefix
前缀：家庭网络前缀
This option is used by DHCP servers and relay agents to specify the home agent IP address. In cases where the home agent must be contacted over an IPv4-only infrastructure, the IPv4 address is specified as an IPv4-Embedded IPv6 address using the "Well-Known Prefix" [RFC6052]. This option should only appear in one of the Home Network Information options.
DHCP服务器和中继代理使用此选项指定归属代理IP地址。如果必须通过仅IPv4的基础结构联系归属代理，则IPv4地址将使用“已知前缀”[RFC6052]指定为IPv4嵌入式IPv6地址。此选项应仅出现在一个家庭网络信息选项中。
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_MIP6_HAA | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_HAA | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_HAA (72)
选项代码：选项MIP6\U HAA（72）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Address: IP Address of home agent
地址：本地代理的IP地址
This option is used by DHCP servers and relay agents to specify the home agent FQDN. This FQDN is used to look up one or more A or AAAA records containing IPv4 or IPv6 addresses for the home agent, as needed. This option should only appear in one of the Home Network Information options.
DHCP服务器和中继代理使用此选项指定归属代理FQDN。此FQDN用于根据需要查找包含归属代理的IPv4或IPv6地址的一个或多个A或AAAA记录。此选项应仅出现在一个家庭网络信息选项中。
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_MIP6_HAF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| FQDN |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_MIP6_HAF | Option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| FQDN |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-code: OPTION_MIP6_HAF (73)
选项代码：选项MIP6\U HAF（73）
Option-len: Length of option, per RFC 3315
选项长度：选项长度，根据RFC 3315
Address: FQDN resolving to one or more IPv4 and/or IPv6 addresses for the home agent. This is encoded in accordance with RFC 3315, Section 8, "Representation and Use of Domain Names".
地址：解析为归属代理的一个或多个IPv4和/或IPv6地址的FQDN。这是根据RFC 3315第8节“域名的表示和使用”进行编码的。
The requesting and sending of the proposed DHCP options follow the rules for DHCPv6 options in [RFC3315].
建议的DHCP选项的请求和发送遵循[RFC3315]中DHCPv6选项的规则。
Mobile nodes MAY obtain MIPv6 configuration information during either a stateful configuration exchange [RFC3315] or a stateless configuration exchange [RFC3736].
移动节点可在有状态配置交换[RFC3315]或无状态配置交换[RFC3736]期间获取MIPv6配置信息。
Mobile nodes that obtain MIPv6 configuration information using a stateful configuration exchange SHOULD include the same options in every message they send to the DHCP server.
使用有状态配置交换获取MIPv6配置信息的移动节点应在发送到DHCP服务器的每条消息中包含相同的选项。
Mobile nodes that obtain MIPv6 configuration using a stateless exchange MAY omit MIPv6 configuration from some exchanges, but SHOULD reconfigure whenever a change in the attached network is detected. If the DHCP server responds to a MIPv6-related stateless configuration request with an Information Request Timer option, the mobile node SHOULD attempt to reconfigure when the IRT expires.
使用无状态交换获取MIPv6配置的移动节点可能会从某些交换中忽略MIPv6配置，但在检测到连接的网络发生更改时，应该重新配置。如果DHCP服务器使用信息请求计时器选项响应与MIPv6相关的无状态配置请求，则移动节点应在IRT过期时尝试重新配置。
A mobile node using stateless configuration may try to perform home network information discovery when it lacks home network information for MIPv6 or needs to change the home agent for some reason. For example, this may be necessary to recover from the failure of an existing home agent or to use the local home agent located in the network where the mobile node is currently attached. Note that despite the home information discovery procedure, the mobile node may continue to use the old home agent, in order to avoid losing current sessions.
使用无状态配置的移动节点在缺少MIPv6的家庭网络信息或出于某种原因需要更改家庭代理时，可能会尝试执行家庭网络信息发现。例如，这对于从现有归属代理的故障中恢复或使用位于移动节点当前连接的网络中的本地归属代理可能是必需的。注意，尽管有归属信息发现过程，移动节点可以继续使用旧的归属代理，以避免丢失当前会话。
Mobile nodes signal that they are interested in being configured with MIPv6 home agent information by requesting one or more of the three Home Network Information options: the Visited Home Network Information option, the Identified Home Network Information option, or the Unrestricted Home Network Information option. To request these options, the client lists them in the Option Request Option (ORO). A client that requests any of these three options in the ORO MUST also request the Home Network Identifier FQDN option, the Home Network Prefix option, the Home Agent Address option, and the Home Agent FQDN option.
移动节点通过请求三个家庭网络信息选项（到访家庭网络信息选项、标识的家庭网络信息选项或不受限制的家庭网络信息选项）中的一个或多个来表示他们有兴趣配置MIPv6家庭代理信息。要请求这些选项，客户端会在选项请求选项（ORO）中列出它们。请求ORO中这三个选项中任何一个选项的客户端还必须请求家庭网络标识符FQDN选项、家庭网络前缀选项、家庭代理地址选项和家庭代理FQDN选项。
If the mobile node requests the Visited Home Network Information option, this indicates that it is interested in learning the home
如果移动节点请求访问的家庭网络信息选项，这表示它有兴趣学习家庭信息
network information that pertains to the currently visited network. This type can be used to discover local home agents in the local ASP.
与当前访问的网络相关的网络信息。此类型可用于在本地ASP.NET中发现本地主代理。
If the mobile node requests the Identified Home Network Information option, this indicates that it is interested in learning the home network information that pertains to a specified realm. This type can be used to discover home agents that are hosted by a user's home domain or by any target domain. A mobile node requesting the Identified Home Network Information option MUST include a Client Home Network ID FQDN option identifying the MSP being identified. The target MSP can be a mobile node's home MSP or any MSP that has a trusted roaming relationship with the mobile node's MSA.
如果移动节点请求识别的家庭网络信息选项，则这表示它有兴趣学习属于指定领域的家庭网络信息。此类型可用于发现由用户的主域或任何目标域承载的主代理。请求标识的家庭网络信息选项的移动节点必须包括标识正在标识的MSP的客户端家庭网络ID FQDN选项。目标MSP可以是移动节点的主MSP或与移动节点的MSA具有可信漫游关系的任何MSP。
If the mobile node has no preference as to the home network with which it should be configured, it SHOULD request the Unrestricted Home Network Information option, and SHOULD NOT request either the Visited Home Network Information option or the Identified Home Network Information option.
如果移动节点对其应配置的家庭网络没有偏好，则其应请求无限制家庭网络信息选项，并且不应请求访问的家庭网络信息选项或识别的家庭网络信息选项。
A client that wishes to be configured with both the Visited Home Network Information option and the Identified Home Network Information option may request both options in the Option Request Option. A client may request information about more than one identified domain by requesting the Identified Home Network Information option in the ORO and including more than one Home Network ID FQDN option. A client that sends more than one Home Network ID FQDN option MUST request the Home Network ID option in the ORO.
希望同时配置到访家庭网络信息选项和识别的家庭网络信息选项的客户端可以在选项请求选项中请求这两个选项。客户端可以通过请求ORO中的已识别家庭网络信息选项并包括多个家庭网络ID FQDN选项来请求关于多个已识别域的信息。发送多个家庭网络ID FQDN选项的客户端必须在ORO中请求家庭网络ID选项。
DHCP Clients on mobile nodes should be prepared to receive any MIPv6 Home Network Information options they request. If more than one Home Network ID FQDN option was sent, the client should be prepared to handle zero or more Identified Home Network Information options in response; the DHCP server may not have configuration information for all targeted domains, or, indeed, for any. If a misconfigured server returns an Identified Home Network Information option that does not contain a Home Network ID FQDN option corresponding to one that the client requested, the client MUST silently discard that Identified Home Network Information option.
移动节点上的DHCP客户端应准备好接收其请求的任何MIPv6家庭网络信息选项。如果发送了多个家庭网络ID FQDN选项，则客户端应准备处理零个或多个已识别的家庭网络信息选项作为响应；DHCP服务器可能没有所有目标域的配置信息，或者实际上没有任何目标域的配置信息。如果配置错误的服务器返回的标识的家庭网络信息选项不包含与客户端请求的家庭网络ID FQDN选项相对应的家庭网络ID FQDN选项，则客户端必须以静默方式放弃该标识的家庭网络信息选项。
If any of the three Home Network Information options is returned, configuration information will be included within it. The client must be prepared to handle home agent addresses in the form of either the Home Agent Address option or the Home Agent FQDN option.
如果返回三个家庭网络信息选项中的任何一个，配置信息将包含在其中。客户端必须准备好以home agent Address选项或home agent FQDN选项的形式处理home agent地址。
If the client finds an IPv4-Embedded IPv6 address in a Home Agent Address option, it may only use this address to communicate over IPv4. If a Home Network Information option does not contain complete configuration information, the client MUST silently discard that Home Network Information option.
如果客户端在归属代理地址选项中找到IPv4嵌入IPv6地址，则它可能仅使用此地址通过IPv4进行通信。如果家庭网络信息选项不包含完整的配置信息，则客户端必须以静默方式放弃该家庭网络信息选项。
If the client receives any Home Network ID FQDN options, Home Network Prefix options, Home Agent Address options, or Home Agent FQDN options that are not encapsulated in one of the three types of Home Network Information options, it MUST silently discard these options.
如果客户端收到未封装在三种家庭网络信息选项之一中的任何家庭网络ID FQDN选项、家庭网络前缀选项、家庭代理地址选项或家庭代理FQDN选项，则必须以静默方式放弃这些选项。
The DHCP client must pass whatever configuration information it receives to the appropriate mobile IP implementation on the mobile node. How this is done, and what the mobile IP implementation on the mobile node does with this information, is outside the scope of this document.
DHCP客户端必须将其接收到的任何配置信息传递给移动节点上的相应移动IP实现。如何做到这一点，以及移动节点上的移动IP实现如何利用这些信息，超出了本文档的范围。
As described later in this section, servers may provide more than one Home Network Information option or multiple Home Agent Prefix, Home Agent Address, or Home Agent FQDN options. When provided with multiple Visited Home Network Information options or Unrestricted Home Network Information options of the same type, or with multiple sub-options within such an option, the mobile node SHOULD choose the first one that it can employ.
如本节后面所述，服务器可以提供多个家庭网络信息选项或多个家庭代理前缀、家庭代理地址或家庭代理FQDN选项。当向移动节点提供多个到访家庭网络信息选项或相同类型的不受限制的家庭网络信息选项时，或者在该选项中提供多个子选项时，移动节点应选择其可以使用的第一个选项。
If the DHCP client on a mobile node receives any Home Network Prefix options, Home Agent Address option, or Home Agent FQDN option that are not contained within Home Network Information options, the DHCP client MUST silently discard these options.
如果移动节点上的DHCP客户端接收到家庭网络信息选项中未包含的任何家庭网络前缀选项、家庭代理地址选项或家庭代理FQDN选项，则DHCP客户端必须以静默方式放弃这些选项。
In some cases, DHCP relay agents may have access to configuration information for the mobile node. In such cases, relay agents MAY send Visited Home Network Information options, Identified Home Network Information options, and/or Unrestricted Home Network Information options to the DHCP server. To do so, the relay agent MUST encapsulate these options in a Relay-Supplied Options option [RFC6422]. If the DHCP relay agent includes any Identified Home Network Information options, these options MUST correspond to home networks identified in Home Network ID FQDN options in the client request. In addition, each Identified Home Network Information option must contain a Home Network ID FQDN option identical to the one sent by the client, to identify the network to the client.
在某些情况下，DHCP中继代理可以访问移动节点的配置信息。在这种情况下，中继代理可以向DHCP服务器发送到访家庭网络信息选项、识别的家庭网络信息选项和/或不受限制的家庭网络信息选项。为此，中继代理必须将这些选项封装在中继提供的选项[RFC6422]中。如果DHCP中继代理包括任何标识的家庭网络信息选项，则这些选项必须对应于客户端请求中的家庭网络ID FQDN选项中标识的家庭网络。此外，每个已标识的家庭网络信息选项必须包含与客户端发送的相同的家庭网络ID FQDN选项，以便向客户端标识网络。
No special handling is required when processing relay-reply messages.
处理中继回复消息时不需要特殊处理。
Generally, DHCP servers can simply be configured with Visited Home Network Information options, Identified Home Network Information options, and Unrestricted Home Network Information options. In the case of Visited Home Network Information options and Unrestricted Home Network Information options, which clients get what options depends on operator configuration.
通常，DHCP服务器可以简单地配置访问的家庭网络信息选项、已识别的家庭网络信息选项和不受限制的家庭网络信息选项。在访问家庭网络信息选项和不受限制的家庭网络信息选项的情况下，哪些客户端获得什么选项取决于运营商配置。
A DHCP server MAY maintain a table of Home Network ID FQDNs. For each such FQDN, a server that maintains such a table SHOULD include an Identified Home Network Information option. Such a server would look up the FQDN from any Home Network ID FQDN options provided by the client in its table, and for each match, include the Identified Home Network Information option configured in the table entry for that FQDN.
DHCP服务器可以维护家庭网络ID FQDNs表。对于每个这样的FQDN，维护这样一个表的服务器应该包括一个标识的家庭网络信息选项。这样的服务器将从客户机在其表中提供的任何家庭网络ID FQDN选项中查找FQDN，并且对于每个匹配项，包括在该FQDN的表条目中配置的已标识家庭网络信息选项。
If a DHCP server does not implement the Home Network ID FQDN table, or some similar functionality, it is an error for the operator to configure it with any Identified Home Network Information options. These options could be erroneously forwarded to the client, which would have no use for them, and is required to discard them.
如果DHCP服务器未实现家庭网络ID FQDN表或某些类似功能，则操作员使用任何已识别的家庭网络信息选项对其进行配置是错误的。这些选项可能会被错误地转发给客户机，而客户机对这些选项没有任何用处，因此需要放弃这些选项。
DHCP servers that implement the Home Network ID FQDN table must, when sending an Identified Home Network Information option to the client, include a Home Network ID option within the Identified Home Network Information option that identifies the home network for which configuration information is being sent.
在向客户端发送标识的家庭网络信息选项时，实现家庭网络ID FQDN表的DHCP服务器必须在标识的家庭网络信息选项中包含一个家庭网络ID选项，该选项标识要为其发送配置信息的家庭网络。
Aside from the Home Network ID FQDN table, the actual behavior of the DHCP server with respect to MIPv6 configuration is simply in accordance with the DHCPv6 protocol specification [RFC3315] and depends on operator configuration. No special processing is required for Visited Home Network Information options or Unrestricted Home Network Information options.
除了家庭网络ID FQDN表之外，DHCP服务器关于MIPv6配置的实际行为仅符合DHCPv6协议规范[RFC3315]，并取决于操作员配置。访问的家庭网络信息选项或不受限制的家庭网络信息选项不需要特殊处理。
[RFC5447] describes the complete procedure for home agent assignment among the mobile node, NAS (Network Access Server), DHCP, and Authentication, Authorization, and Accounting (AAA) entities for the bootstrapping procedure in the integrated scenario.
[RFC5447]描述了集成场景中引导过程的移动节点、NAS（网络访问服务器）、DHCP和身份验证、授权和计费（AAA）实体之间归属代理分配的完整过程。
A NAS is assumed to be co-located with a DHCP relay agent or a DHCP server in this solution. In a network where the NAS is not co-located with a DHCP relay or a server, the server may not be provided with the home network information from the NAS; therefore,
在此解决方案中，假定NAS与DHCP中继代理或DHCP服务器位于同一位置。在NAS与DHCP中继或服务器不位于同一位置的网络中，可以不向服务器提供来自NAS的家庭网络信息；因此
it may either fail to provide information or provide home information that has been pre-configured by the administrator or that is acquired through a mechanism that is not described in this document.
它可能无法提供管理员预先配置的信息或通过本文档中未描述的机制获取的主页信息。
Secure delivery of home agent and home network information from a DHCP server to the mobile node (DHCP client) relies on the same security as DHCP. The particular option defined in this document does not have additional impact on DHCP security.
从DHCP服务器到移动节点（DHCP客户端）的归属代理和归属网络信息的安全传递依赖于与DHCP相同的安全性。本文档中定义的特定选项对DHCP安全性没有其他影响。
Aside from the DHCP client-to-server interaction, an operator must also ensure secure delivery of mobile IP information to the DHCP server. This is outside the scope of DHCP and the newly defined options.
除了DHCP客户端到服务器的交互之外，运营商还必须确保将移动IP信息安全地传送到DHCP服务器。这超出了DHCP和新定义的选项的范围。
The mechanisms in this specification could be used by attackers to learn the addresses of home agents in the home network or to feed incorrect information to mobile nodes.
攻击者可利用本规范中的机制了解家庭网络中家庭代理的地址，或向移动节点提供不正确的信息。
The ability to learn addresses of nodes may be useful to attackers because brute-force scanning of the address space is not practical with IPv6. Thus, they could benefit from any means that make mapping the networks easier. For example, if a security threat targeted at routers or even home agents is discovered, having a simple mechanism to easily find out possible targets may prove to be an additional security risk.
学习节点地址的能力可能对攻击者有用，因为对地址空间进行暴力扫描在IPv6中不实用。因此，他们可以从任何使网络映射更容易的方法中获益。例如，如果发现针对路由器甚至家庭代理的安全威胁，那么使用简单的机制轻松找到可能的目标可能会带来额外的安全风险。
Apart from discovering the address(es) of home agents, attackers will not be able to learn much from this information, and mobile nodes cannot be tricked into using wrong home agents, as the actual communication with the home agents employs mutual authentication.
除了发现归属代理的地址外，攻击者将无法从该信息中了解更多信息，并且移动节点也不会被诱骗使用错误的归属代理，因为与归属代理的实际通信采用了相互认证。
The mechanisms from this specification may also leak interesting information about network topology and prefixes to attackers, and where there is no security to protect DHCP, even modify this information. Again, the mobile nodes and home agents employ end-to-end security when they communicate with each other. The authentic source of all information is that communication, not the information from DHCP.
此规范中的机制还可能向攻击者泄漏有关网络拓扑和前缀的有趣信息，并且在没有安全保护DHCP的情况下，甚至可以修改此信息。同样，移动节点和归属代理在彼此通信时采用端到端安全性。所有信息的真实来源是通信，而不是来自DHCP的信息。
However, attacks against the information carried in DHCP may lead to denial of service if mobile nodes are unable to connect to any home agent, or choose a home agent that is not the most preferred one.
但是，如果移动节点无法连接到任何归属代理，或者选择一个不是最首选的归属代理，那么针对DHCP中携带的信息的攻击可能会导致拒绝服务。
IANA has assigned the following new DHCPv6 Option Codes in the registry maintained in
IANA在中维护的注册表中分配了以下新的DHCPv6选项代码：
http://www.iana.org/assignments/dhcpv6-parameters:
http://www.iana.org/assignments/dhcpv6-parameters:
49: OPTION_MIP6_HNIDF for the Home Network ID FQDN option
49：家庭网络ID FQDN选项的选项\u MIP6\u HNIDF
50: OPTION_MIP6_VDINF for the Visited Home Network Information option
50：访问家庭网络信息选项的选项\u MIP6\u VDINF
69: OPTION_MIP6_IDINF for the Identified Home Network Information option
69：已识别家庭网络信息选项的选项\u MIP6\u idif
70: OPTION_MIP6_UDINF for the Unrestricted Home Network Information option
70：无限制家庭网络信息选项的选项
71: OPTION_MIP6_HNP for the Home Network Prefix option
71：家庭网络前缀选项的选项\u MIP6\u HNP
72: OPTION_MIP6_HAA for the Home Agent Address option
72：Home Agent Address选项的选项\u MIP6\u HAA
73: OPTION_MIP6_HAF for the Home Agent FQDN option
73：归属代理FQDN选项的选项\u MIP6\u HAF
The authors would like to thank Kilian Weniger, Domagoj Premec, Basavaraj Patil, Vijay Devarapalli, Gerardo Giaretta, Bernie Volz, David W. Hankins, Behcet Sarikaya, Vidya Narayanan, Francis Dupont, Sam Weiler, Jari Arkko, Alfred Hoenes, Suresh Krishnan, and Miguel A. Diaz for their valuable feedback.
作者要感谢Kilian Weniger、Domagoj Premec、Basavaraj Patil、Vijay Devarapalli、Gerardo Giaretta、Bernie Volz、David W.Hankins、Behcet Sarikaya、Vidya Narayan、Francis Dupont、Sam Weiler、Jari Arkko、Alfred Hoenes、Suresh Krishnan和Miguel A.Diaz的宝贵反馈。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[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., 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.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6", RFC 3736, April 2004.
[RFC3736]Droms，R.，“IPv6的无状态动态主机配置协议（DHCP）服务”，RFC 3736，2004年4月。
[RFC4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The Network Access Identifier", RFC 4282, December 2005.
[RFC4282]Aboba，B.，Beadles，M.，Arkko，J.，和P.Erenen，“网络访问标识符”，RFC 42822005年12月。
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers", RFC 5555, June 2009.
[RFC5555]Soliman，H.，“双栈主机和路由器的移动IPv6支持”，RFC 55552009年6月。
[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, October 2010.
[RFC6052]Bao，C.，Huitema，C.，Bagnulo，M.，Boucadair，M.，和X.Li，“IPv4/IPv6转换器的IPv6寻址”，RFC 6052010年10月。
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, July 2011.
[RFC6275]Perkins，C.，Johnson，D.，和J.Arkko，“IPv6中的移动支持”，RFC 62752011年7月。
[RFC6422] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", RFC 6422, December 2011.
[RFC6422]Lemon，T.和Q.Wu，“继电器提供的DHCP选项”，RFC 6422，2011年12月。
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", RFC 3753, June 2004.
[RFC3753]Way，J.和M.Kojo，“机动性相关术语”，RFC 3753，2004年6月。
[RFC4640] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[RFC4640]Patel，A.和G.Giaretta，“引导移动IPv6（MIPv6）的问题陈述”，RFC 46402006年9月。
[RFC5380] Soliman, H., Castelluccia, C., ElMalki, K., and L. Bellier, "Hierarchical Mobile IPv6 (HMIPv6) Mobility Management", RFC 5380, October 2008.
[RFC5380]Soliman，H.，Castelluccia，C.，ElMalki，K.，和L.Bellier，“分层移动IPv6（HMIPv6）移动性管理”，RFC 53802008年10月。
[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction", RFC 5447, February 2009.
[RFC5447]Korhonen，J.，Bournelle，J.，Tschofenig，H.，Perkins，C.，和K.Chowdhury，“Diameter移动IPv6：支持网络访问服务器到Diameter服务器的交互”，RFC 5447，2009年2月。
Authors' Addresses
作者地址
Heejin Jang Korea Institute of Science and Technology Information (KISTI) 245 Daehak-ro, Yuseong-gu Daejeon 305-806 Korea
Heejin Jang韩国科学技术信息研究所（KISTI）韩国大田余城大河245号305-806
EMail: heejin.jang@gmail.com
EMail: heejin.jang@gmail.com
Alper E. Yegin Samsung Electronics Istanbul Turkey
阿尔珀·E·耶金三星电子土耳其伊斯坦布尔
EMail: alper.yegin@yegin.org
EMail: alper.yegin@yegin.org
Kuntal Chowdhury Radio Mobile Access, Inc. 100 Ames Pond Dr. Tewksbury, MA 01876 US
Kuntal Chowdhury无线电移动接入有限公司美国马萨诸塞州特克斯伯里艾姆斯池塘100号，邮编01876
EMail: kc@radiomobiles.com
EMail: kc@radiomobiles.com
JinHyeock Choi Samsung Advanced Institute of Technology P.O. Box 111 Suwon 440-600 Korea
韩国三星高级技术研究院韩国水原440-600邮政信箱111
EMail: jinchoe@gmail.com
EMail: jinchoe@gmail.com
Ted Lemon Nominum 2000 Seaport Blvd Redwood City, CA 94063 USA
美国加利福尼亚州红木市海港大道2000号Ted Lemon Nominum 94063
Phone: +1 650 381 6000
EMail: Ted.Lemon@nominum.com
Phone: +1 650 381 6000
EMail: Ted.Lemon@nominum.com