Network Working Group J. Korhonen, Ed.
Request for Comments: 5447 Nokia Siemens Networks
Category: Standards Track J. Bournelle
Orange Labs
H. Tschofenig
Nokia Siemens Networks
C. Perkins
WiChorus
K. Chowdhury
Starent Networks
February 2009
Network Working Group J. Korhonen, Ed.
Request for Comments: 5447 Nokia Siemens Networks
Category: Standards Track J. Bournelle
Orange Labs
H. Tschofenig
Nokia Siemens Networks
C. Perkins
WiChorus
K. Chowdhury
Starent Networks
February 2009
Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction
Diameter移动IPv6：支持网络访问服务器到Diameter服务器的交互
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/ 许可证信息）在本文件发布之日生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Abstract
摘要
A Mobile IPv6 node requires a home agent address, a home address, and a security association with its home agent before it can start utilizing Mobile IPv6. RFC 3775 requires that some or all of these parameters be statically configured. Mobile IPv6 bootstrapping work aims to make this information dynamically available to the mobile node. An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with existing Authentication, Authorization, and Accounting (AAA) infrastructures. This document describes MIPv6 bootstrapping using the Diameter Network Access Server to home AAA server interface.
移动IPv6节点需要一个归属代理地址、归属地址以及与其归属代理的安全关联，然后才能开始使用移动IPv6。RFC 3775要求静态配置部分或所有这些参数。移动IPv6引导工作旨在使这些信息动态地可供移动节点使用。移动IPv6引导解决方案的一个重要方面是支持与现有身份验证、授权和计费（AAA）基础架构的互通。本文档介绍使用Diameter网络访问服务器到家庭AAA服务器接口的MIPv6引导。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Commands, Attribute-Value Pairs, and Advertising
Application Support . . . . . . . . . . . . . . . . . . . . . 6
4.1. Advertising Application Support . . . . . . . . . . . . . 6
4.2. Attribute-Value Pair Definitions . . . . . . . . . . . . . 6
4.2.1. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . 6
4.2.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 7
4.2.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 7
4.2.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 8
4.2.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 8
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 10
5.2. Home Agent Assignment by the Diameter Server . . . . . . . 11
5.3. Home Agent Assignment by the NAS or Diameter Server . . . 11
6. Attribute-Value Pair Occurrence Tables . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7.1. Registration of New AVPs . . . . . . . . . . . . . . . . . 13
7.2. New Registry: Mobility Capability . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Commands, Attribute-Value Pairs, and Advertising
Application Support . . . . . . . . . . . . . . . . . . . . . 6
4.1. Advertising Application Support . . . . . . . . . . . . . 6
4.2. Attribute-Value Pair Definitions . . . . . . . . . . . . . 6
4.2.1. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . 6
4.2.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 7
4.2.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 7
4.2.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 8
4.2.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 8
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 10
5.2. Home Agent Assignment by the Diameter Server . . . . . . . 11
5.3. Home Agent Assignment by the NAS or Diameter Server . . . 11
6. Attribute-Value Pair Occurrence Tables . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7.1. Registration of New AVPs . . . . . . . . . . . . . . . . . 13
7.2. New Registry: Mobility Capability . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15
The Mobile IPv6 (MIPv6) specification [RFC3775] requires a mobile node (MN) to perform registration with a home agent (HA) with information about its current point of attachment (care-of address). The HA creates and maintains the binding between the MN's home address and the MN's care-of address.
移动IPv6（MIPv6）规范[RFC3775]要求移动节点（MN）使用其当前连接点（转交地址）的信息向归属代理（HA）进行注册。HA创建并维护MN的家庭地址和MN的转交地址之间的绑定。
In order to register with an HA, the MN needs to know some information, such as the home link prefix, the HA address, the home address(es), the home link prefix length, and security-association-related information.
为了向HA注册，MN需要知道一些信息，例如归属链路前缀、HA地址、归属地址、归属链路前缀长度和安全关联相关信息。
The aforementioned information may be statically configured. However, static provisioning becomes an administrative burden for an operator. Moreover, it does not address load balancing, failover, opportunistic home link assignment, or assignment of local HAs in close proximity to the MN. Also, the ability to react to sudden environmental or topological changes is minimal. Static provisioning may not be desirable, in light of these limitations.
上述信息可以是静态配置的。但是，静态资源调配成为运营商的管理负担。此外，它不处理负载平衡、故障切换、机会归属链路分配或在MN附近分配本地HAs。此外，对突然的环境或拓扑变化作出反应的能力是最小的。鉴于这些限制，静态资源调配可能不可取。
Dynamic assignment of MIPv6 home registration information is a desirable feature for ease of deployment and network maintenance. For this purpose, the AAA infrastructure, which is used for access authentication, can be leveraged to assign some or all of the necessary parameters. The Diameter server in the Access Service Provider's (ASP's) or Mobility Service Provider's (MSP's) network may return these parameters to the AAA client. Regarding the bootstrapping procedures, the AAA client might either be the Network Access Server, in case of the integrated scenario, or the HA, in case of the split scenario [RFC5026]. The terms "integrated" and "split" are described in the following terminology section and were introduced in [RFC4640] and [AAA].
动态分配MIPv6家庭注册信息是便于部署和网络维护的理想功能。为此，可以利用用于访问身份验证的AAA基础设施来分配一些或所有必要的参数。接入服务提供商（ASP）或移动服务提供商（MSP）网络中的Diameter服务器可以将这些参数返回给AAA客户端。关于引导过程，AAA客户端可能是网络访问服务器（在集成场景中），也可能是HA（在拆分场景中）[RFC5026]。术语“集成”和“拆分”在以下术语部分中描述，并在[RFC4640]和[AAA]中介绍。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
General mobility terminology can be found in [RFC3753]. The following additional terms are either borrowed from [RFC4640] or [RFC5026] or are introduced in this document:
通用机动性术语可在[RFC3753]中找到。以下附加条款从[RFC4640]或[RFC5026]借用，或在本文件中介绍：
Access Service Authorizer (ASA):
访问服务授权人（ASA）：
A network operator that authenticates an MN and establishes the MN's authorization to receive Internet service.
一种网络运营商，对MN进行认证，并建立MN接收Internet服务的授权。
Access Service Provider (ASP):
访问服务提供商（ASP）：
A network operator that provides direct IP packet-forwarding to and from the MN.
一种网络运营商，提供与MN之间的直接IP数据包转发。
Mobility Service Authorizer (MSA):
移动服务授权人（MSA）：
A service provider that authorizes MIPv6 service.
授权MIPv6服务的服务提供商。
Mobility Service Provider (MSP):
移动服务提供商（MSP）：
A service provider that provides MIPv6 service. In order to obtain such service, the MN must be authenticated and authorized to do so.
提供MIPv6服务的服务提供商。为了获得这样的服务，必须对MN进行身份验证和授权。
Split Scenario:
拆分场景：
A scenario where the mobility service and the network access service are authorized by different entities.
移动服务和网络接入服务由不同实体授权的场景。
Integrated Scenario:
综合场景：
A scenario where the mobility service and the network access service are authorized by the same entity.
移动服务和网络接入服务由同一实体授权的场景。
Network Access Server (NAS):
网络访问服务器（NAS）：
A device that provides an access service for a user to a network.
为用户提供网络访问服务的设备。
Home AAA (HAAA):
家庭AAA（HAAA）：
An Authentication, Authorization, and Accounting server located in the user's home network, i.e., in the home realm.
位于用户家庭网络（即家庭域）中的身份验证、授权和记帐服务器。
Local AAA (LAAA):
本地AAA（LAAA）：
An Authentication, Authorization, and Accounting proxy located in the local (ASP) network.
位于本地（ASP）网络中的身份验证、授权和记帐代理。
Visited AAA (VAAA):
访问AAA（VAAA）：
An Authentication, Authorization, and Accounting proxy located in a visited network, i.e., in the visited realm. In a roaming case, the local Diameter proxy has the VAAA role (see Figure 1).
位于访问网络（即访问域）中的身份验证、授权和记帐代理。在漫游情况下，本地Diameter代理具有VAAA角色（参见图1）。
This document addresses the Authentication, Authorization, and Accounting (AAA) functionality required for the MIPv6 bootstrapping solutions outlined in [RFC4640], and focuses on the Diameter-based AAA functionality for the NAS-to-HAAA (home AAA) server communication.
本文档介绍了[RFC4640]中概述的MIPv6引导解决方案所需的身份验证、授权和记帐（AAA）功能，并重点介绍了NAS到HAAA（家庭AAA）服务器通信的基于直径的AAA功能。
In the integrated scenario, MIPv6 bootstrapping is provided as part of the network access authentication procedure. Figure 1 shows the participating entities.
在集成场景中，MIPv6引导作为网络访问身份验证过程的一部分提供。图1显示了参与实体。
+---------------------------+ +-----------------+
|Access Service Provider | |ASA/MSA/(MSP) |
|(Mobility Service Provider)| | |
| | | |
| +--------+ | | +--------+ |
| |Local | Diameter | | |Home | |
| |Diameter|<---------------------->|Diameter| |
| |Proxy | (*) | | |Server | |
| +--------+ | | +--------+ |
| ^ ^ | | ^ |
| | | | | |(+) |
| | | | | | |
| Diameter | | v |
| | |(+) +-------+ | | +-------+ |
| | | |Home | | | |Home | |
| | +-------->|Agent | | | |Agent | |
| (*)| |in ASP | | | |in MSP | |
| v +-------+ | | +-------+ |
+-------+ IEEE | +-----------+ +-------+ | +-----------------+
|Mobile | 802.1X | |NAS/Relay | |DHCPv6 | |
|Node |------------|Diameter |---|Server | |
| | PANA, | |Client |(+)| | |
+-------+ IKEv2, | +-----------+ +-------+ |
DHCP,... +---------------------------+
(+)
+---------------------------+ +-----------------+
|Access Service Provider | |ASA/MSA/(MSP) |
|(Mobility Service Provider)| | |
| | | |
| +--------+ | | +--------+ |
| |Local | Diameter | | |Home | |
| |Diameter|<---------------------->|Diameter| |
| |Proxy | (*) | | |Server | |
| +--------+ | | +--------+ |
| ^ ^ | | ^ |
| | | | | |(+) |
| | | | | | |
| Diameter | | v |
| | |(+) +-------+ | | +-------+ |
| | | |Home | | | |Home | |
| | +-------->|Agent | | | |Agent | |
| (*)| |in ASP | | | |in MSP | |
| v +-------+ | | +-------+ |
+-------+ IEEE | +-----------+ +-------+ | +-----------------+
|Mobile | 802.1X | |NAS/Relay | |DHCPv6 | |
|Node |------------|Diameter |---|Server | |
| | PANA, | |Client |(+)| | |
+-------+ IKEv2, | +-----------+ +-------+ |
DHCP,... +---------------------------+
(+)
Legend: (*): Functionality in scope of this specification. (+): Extensions described in other documents.
图例：（*）：本规范范围内的功能。（+）：其他文档中描述的扩展。
Figure 1: Mobile IPv6 Bootstrapping in the Integrated Scenario
图1：集成场景中的移动IPv6引导
In a typical MIPv6 access scenario, an MN is attached to an ASP's network. During the network attachment procedure, the MN interacts with the NAS/Diameter client. Subsequently, the NAS/Diameter client interacts with the Diameter server over the NAS-to-HAAA interface.
在典型的MIPv6访问场景中，MN连接到ASP的网络。在网络连接过程中，MN与NAS/Diameter客户端交互。随后，NAS/Diameter客户端通过NAS到HAAA接口与Diameter服务器交互。
When the Diameter server performs the authentication and authorization for network access, it also determines whether the user is authorized for the MIPv6 service. Based on the MIPv6 service authorization and the user's policy profile, the Diameter server may return several MIPv6 bootstrapping-related parameters to the NAS. The NAS-to-HAAA interface described in this document is not tied to the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) as the only mechanism to convey MIPv6-related configuration parameters from the NAS/Diameter client to the mobile node.
当Diameter服务器对网络访问执行身份验证和授权时，它还确定用户是否获得MIPv6服务的授权。根据MIPv6服务授权和用户的策略配置文件，Diameter服务器可能会向NAS返回多个与MIPv6引导相关的参数。本文档中描述的NAS到HAAA接口与IPv6的动态主机配置协议（DHCPv6）无关，因为它是将与MIPv6相关的配置参数从NAS/Diameter客户端传送到移动节点的唯一机制。
While this specification addresses the bootstrapping of MIPv6 HA information and possibly the assignment of the home link prefix, it does not address how the Security Association (SA) between the MN and the HA for MIPv6 purposes is created. The creation or the use of the SA between the MN and the HA takes places after the procedures described in this specification, and therefore are out of scope.
虽然本规范解决了MIPv6 HA信息的引导以及可能的归属链路前缀的分配，但它没有解决如何创建用于MIPv6目的的MN和HA之间的安全关联（SA）。MN和HA之间SA的创建或使用发生在本规范中描述的过程之后，因此超出范围。
This document does not define a new application. On the other hand, it defines a number of attribute-value pairs (AVPs) used in the interface between NAS to HAAA for the integrated scenario of MIPv6 bootstrapping. These AVPs can be used with any present and future Diameter applications, where permitted by the command ABNF. The examples using existing applications and their commands in the following sections are for informational purposes only. The examples in this document reuse the Extensible Authentication Protocol (EAP) [RFC4072] application and its respective commands.
本文档未定义新的应用程序。另一方面，它定义了在NAS到HAAA之间的接口中使用的许多属性值对（AVP），用于MIPv6引导的集成场景。如果ABNF命令允许，这些AVP可用于任何当前和未来的直径应用。以下部分中使用现有应用程序及其命令的示例仅供参考。本文档中的示例重用可扩展身份验证协议（EAP）[RFC4072]应用程序及其相应的命令。
The MIP6-Agent-Info AVP (AVP code 486) is of type Grouped and contains necessary information to assign an HA to the MN. When the MIP6-Agent-Info AVP is present in a message, it MUST contain either the MIP-Home-Agent-Address AVP, the MIP-Home-Agent-Host AVP, or both AVPs. The grouped AVP has the following modified ABNF (as defined in [RFC3588]):
MIP6代理信息AVP（AVP代码486）属于分组类型，包含将HA分配给MN所需的信息。当消息中存在MIP6代理信息AVP时，它必须包含MIP Home Agent地址AVP、MIP Home Agent主机AVP或两个AVP。分组的AVP具有以下修改的ABNF（定义见[RFC3588]）：
MIP6-Agent-Info ::= < AVP-Header: 486 >
*2[ MIP-Home-Agent-Address ]
[ MIP-Home-Agent-Host ]
[ MIP6-Home-Link-Prefix ]
* [ AVP ]
MIP6-Agent-Info ::= < AVP-Header: 486 >
*2[ MIP-Home-Agent-Address ]
[ MIP-Home-Agent-Host ]
[ MIP6-Home-Link-Prefix ]
* [ AVP ]
If both the MIP-Home-Agent-Address and MIP-Home-Agent-Host APVs are present in the MIP6-Agent-Info, the MIP-Home-Agent-Address SHOULD have a precedence over the MIP-Home-Agent-Host. The reason for this recommendation is that the MIP-Home-Agent-Address points to a specific home agent, whereas the MIP-Home-Agent-Host may point to a group of HAs located within the same realm. A Diameter client or agent may use the MIP-Home-Agent-Host AVP, for instance, to find out in which realm the HA is located.
如果MIP Home Agent地址和MIP Home Agent主机APV都存在于MIP6 Agent信息中，则MIP Home Agent地址应优先于MIP Home Agent主机。此建议的原因是MIP Home Agent地址指向特定的Home Agent，而MIP Home Agent主机可能指向位于同一领域内的一组HA。例如，Diameter客户端或代理可以使用MIP归属代理主机AVP来找出HA位于哪个领域。
The ABNF allows returning up to two MIPv6 HA addresses. This is a useful feature for deployments where the HA has both IPv6 and IPv4 addresses, and particularly addresses Dual Stack Mobile IPv6 (DSMIPv6) deployment scenarios [DSMIPv6].
ABNF允许返回最多两个MIPv6 HA地址。对于HA同时具有IPv6和IPv4地址的部署，这是一项非常有用的功能，尤其适用于双栈移动IPv6（DSMPv6）部署场景[DSMPv6]。
The MIP6-Agent-Info AVP MAY also be attached by the NAS or by the intermediating Diameter proxies in a request message when sent to the Diameter server as a hint of a locally assigned HA. This AVP MAY also be attached by the intermediating Diameter proxies in a reply message from the Diameter server, if locally assigned HAs are authorized by the Diameter server. There MAY be multiple instances of the MIP6-Agent-Info AVP in Diameter messages, for example, in cases where the NAS receives HA information from an MN's home network and locally allocated HA information from the visited network. See Section 4.2.5 for further discussion on possible scenarios.
当作为本地分配HA的提示发送到Diameter服务器时，MIP6代理信息AVP也可以由NAS或中间Diameter代理在请求消息中附加。如果Diameter服务器授权本地分配的HAs，则中间Diameter代理也可以在Diameter服务器的回复消息中附加此AVP。在Diameter消息中可能存在MIP6代理信息AVP的多个实例，例如，在NAS从MN的家庭网络接收HA信息和从访问的网络接收本地分配的HA信息的情况下。有关可能情况的进一步讨论，请参见第4.2.5节。
The MIP-Home-Agent-Address AVP (AVP Code 334 [RFC4004]) is of type Address and contains the IPv6 or IPv4 address of the MIPv6 HA. The Diameter server MAY decide to assign an HA to the MN that is in close proximity to the point of attachment (e.g., determined by the NAS-Identifier AVP). There may be other reasons for dynamically assigning HAs to the MN, for example, to share the traffic load.
MIP归属代理地址AVP（AVP代码334[RFC4004]）属于Address类型，包含MIPv6 HA的IPv6或IPv4地址。Diameter服务器可以决定将HA分配给靠近连接点的MN（例如，由NAS标识符AVP确定）。动态地将HAs分配给MN可能还有其他原因，例如，为了共享业务负载。
The MIP-Home-Agent-Host AVP (AVP Code 348 [RFC4004]) is of type Grouped and contains the identity of the assigned MIPv6 HA. Both the Destination-Realm and the Destination-Host AVPs of the HA are included in the grouped AVP. The usage of the MIP-Home-Agent-Host AVP is equivalent to the MIP-Home-Agent-Address AVP but offers an additional level of indirection by using the DNS infrastructure. The Destination-Host AVP is used to identify an HA, and the Destination-Realm AVP is used to identify the realm where the HA is located.
MIP归属代理主机AVP（AVP代码348[RFC4004]）属于分组类型，并且包含分配的MIPv6 HA的标识。HA的目标域和目标主机AVP都包含在分组AVP中。MIP归属代理主机AVP的使用相当于MIP归属代理地址AVP，但通过使用DNS基础设施提供了额外的间接级别。目标主机AVP用于标识HA，目标领域AVP用于标识HA所在的领域。
Depending on the actual deployment and DNS configuration, the Destination-Host AVP MAY represent one or more home agents. It is RECOMMENDED that the Destination-Host AVP identifies exactly one HA.
根据实际部署和DNS配置，目标主机AVP可以表示一个或多个归属代理。建议目标主机AVP仅识别一个HA。
It is RECOMMENDED that the MIP-Home-Agent-Host AVP is always included in the MIP6-Agent-Info AVP. In this way, the HA can be associated with the corresponding realm of the Diameter entity that added the MIP6-Agent-Info AVP using the Destination-Realm AVP, which is included in the MIP-Home-Agent-Host AVP.
It is RECOMMENDED that the MIP-Home-Agent-Host AVP is always included in the MIP6-Agent-Info AVP. In this way, the HA can be associated with the corresponding realm of the Diameter entity that added the MIP6-Agent-Info AVP using the Destination-Realm AVP, which is included in the MIP-Home-Agent-Host AVP.translate error, please retry
The MIP6-Home-Link-Prefix AVP (AVP Code 125) is of type OctetString and contains the Mobile IPv6 home network prefix information in a network byte order. The home network prefix MUST be encoded as the 8-bit prefix length information (one octet) followed by the 128-bit field (16 octets) for the available home network prefix. The trailing bits of the IPv6 prefix after the prefix length bits MUST be set to zero (e.g., if the prefix length is 60, then the remaining 68 bits MUST be set to zero).
MIP6家庭链路前缀AVP（AVP代码125）为OctetString类型，并以网络字节顺序包含移动IPv6家庭网络前缀信息。家庭网络前缀必须编码为8位前缀长度信息（一个八位字节），后跟可用家庭网络前缀的128位字段（16个八位字节）。前缀长度位之后的IPv6前缀尾随位必须设置为零（例如，如果前缀长度为60，则剩余的68位必须设置为零）。
The HAAA MAY act as a central entity managing prefixes for MNs. In this case, the HAAA returns to the NAS the prefix allocated to the MN. The NAS/ASP then delivers the home link prefix to the MN using, e.g., mechanisms described in [INTEGRATED]. The NAS/ASP MAY propose to the HAAA a specific prefix to allocate to the MN by including the MIP6-Home-Link-Prefix AVP in the request message. However, the HAAA MAY override the prefix allocation hint proposed by the NAS/ASP and return a different prefix in the response message.
HAAA可以充当管理MNs前缀的中心实体。在这种情况下，HAAA将分配给MN的前缀返回给NAS。然后，NAS/ASP使用[INTEGRATED]中所述的机制将主链路前缀传送到MN。NAS/ASP可以通过在请求消息中包括MIP6归属链路前缀AVP，向HAAA建议分配给MN的特定前缀。但是，HAAA可能会覆盖NAS/ASP提出的前缀分配提示，并在响应消息中返回不同的前缀。
The MIP6-Feature-Vector AVP (AVP Code 124) is of type Unsigned64 and contains a 64-bit flags field of supported capabilities of the NAS/ ASP. Sending and receiving the MIP6-Feature-Vector AVP with value 0 MUST be supported, although that does not provide much guidance about specific needs of bootstrapping.
MIP6功能向量AVP（AVP代码124）的类型为Unsigned64，包含NAS/ASP支持功能的64位标志字段。必须支持发送和接收值为0的MIP6功能向量AVP，尽管这并不能为引导的具体需求提供太多指导。
The NAS MAY include this AVP to indicate capabilities of the NAS/ASP to the Diameter server. For example, the NAS may indicate that a local HA can be provided. Similarly, the Diameter server MAY include this AVP to inform the NAS/ASP about which of the NAS/ASP indicated capabilities are supported or authorized by the ASA/MSA(/MSP).
NAS可能包括此AVP，以向Diameter服务器指示NAS/ASP的功能。例如，NAS可以指示可以提供本地HA。类似地，Diameter服务器可包括该AVP，以通知NAS/ASP关于ASA/MSA（/MSP）支持或授权的NAS/ASP指示功能中的哪些。
The following capabilities are defined in this document:
本文档中定义了以下功能：
MIP6_INTEGRATED (0x0000000000000001)
MIP6_集成（0x0000000000000001）
When this flag is set by the NAS, it means that the Mobile IPv6 integrated scenario bootstrapping functionality is supported by the NAS. When this flag is set by the Diameter server, then the Mobile IPv6 integrated scenario bootstrapping is supported by the Diameter server.
当NAS设置此标志时，表示NAS支持移动IPv6集成方案引导功能。当Diameter服务器设置此标志时，Diameter服务器支持移动IPv6集成方案引导。
LOCAL_HOME_AGENT_ASSIGNMENT (0x0000000000000002)
本地\本地\代理\分配（0x0000000000000002）
When this flag is set in the request message, a local home agent outside the home realm is requested and may be assigned to the MN. When this flag is set by the Diameter server in the answer message, then the assignment of local HAs is authorized by the Diameter server.
当在请求消息中设置此标志时，将请求归属域之外的本地归属代理，并可将其分配给MN。当Diameter服务器在应答消息中设置此标志时，Diameter服务器授权分配本地HAs。
A local HA may be assigned by the NAS, LAAA, or VAAA depending on the network architecture and the deployment.
本地HA可由NAS、LAAA或VAAA分配，具体取决于网络体系结构和部署。
The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT (referred to as LOCAL-bit in the examples) capability and the MIP-Agent-Info AVP (referred to as HA-Info in the examples) are used to assign HAs -- either a local HA (L-HA) or a home network HA (H-HA). Below are examples of request message combinations as seen by the HAAA:
以下示例显示如何使用本地本地本地代理分配（在示例中称为本地位）功能和MIP代理信息AVP（在示例中称为HA信息）来分配HAs——本地HA（L-HA）或家庭网络HA（H-HA）。以下是HAAA看到的请求消息组合示例：
LOCAL-bit HA-Info Meaning
本地位HA信息含义
0 - ASP or [LV]AAA is not able to assign an L-HA. 0 L-HA Same as above. HA-Info must be ignored. 1 - ASP or [LV]AAA can/wishes to assign an L-HA. 1 L-HA Same as above but the ASP or [LV]AAA also provides a hint of the assigned L-HA.
0-ASP或[LV]AAA无法分配L-HA。0 L-HA，同上。必须忽略HA信息。1-ASP或[LV]AAA可以/希望分配L-HA。1 L-HA与上述相同，但ASP或[LV]AAA也提供分配L-HA的提示。
The same as above but for answer message combinations as seen by the NAS:
与上面相同，但对于NAS看到的应答消息组合：
LOCAL-bit HA-Info Meaning
本地位HA信息含义
0 - No HA assignment allowed for HAAA or [LV]AAA. 0 H-HA L-HA is not allowed. HAAA assigns an H-HA. 1 - L-HA is allowed. No HAAA- or [LV]AAA-assigned HA. 1 L-HA L-HA is allowed. [LV]AAA also assigns an L-HA. 1 H-HA L-HA is allowed. HAAA also assigns an HA. 1 H-HA L-HA is allowed. HAAA assigns an H-HA and + L-HA [LV]AAA also assigns an L-HA.
0-HAAA或[LV]AAA不允许HA分配。不允许使用0 H-HA L-HA。HAAA分配一个H-HA。1-L-HA是允许的。没有HAAA-或[LV]AAA分配HA。1个L-HA L-HA是允许的。[LV]AAA还分配一个L-HA。1 H-HA L-HA是允许的。HAAA还分配了一个HA。1 H-HA L-HA是允许的。HAAA分配H-HA，+L-HA[LV]AAA也分配L-HA。
An NAS should expect to receive multiple MIP6-Agent-Info AVPs.
NAS应能接收多个MIP6代理信息AVP。
In this scenario, we consider the case where the NAS wishes to allocate a local HA to the MN. The NAS will also inform the Diameter server about the HA address it has assigned to the visiting MN (e.g., 2001:db8:1:c020::1). The Diameter-EAP-Request message, therefore, has the MIP6-Feature-Vector with the LOCAL_HOME_AGENT_ASSIGNMENT and the MIP6_INTEGRATED set. The MIP6-Agent-Info AVP contains the MIP-Home-Agent-Address AVP with the address of the proposed HA.
在这种情况下，我们考虑的情况下，NAS希望分配一个本地HA到MN。NAS还将通知Diameter服务器其分配给访问MN的HA地址（例如，2001:db8:1:c020:：1）。因此，Diameter EAP请求消息具有MIP6特征向量和本地\本地\代理\分配以及MIP6 \集成集。MIP6代理信息AVP包含MIP Home Agent地址AVP和建议HA的地址。
Diameter
NAS/VAAA Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
| } |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Diameter
NAS/VAAA Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
| } |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Figure 2: Home Agent Assignment by the NAS
图2:NAS的归属代理分配
Depending on the Diameter server's configuration and the user's subscription profile, the Diameter server either accepts or rejects the local HA allocated by the NAS. In our example, the Diameter server accepts the proposal, and the MIP6-Feature-Vector AVP with LOCAL_HOME_AGENT_ASSIGNMENT flag (together with the MIP6_INTEGRATED flag) is set and returned to the NAS.
根据Diameter服务器的配置和用户的订阅配置文件，Diameter服务器接受或拒绝NAS分配的本地HA。在我们的示例中，Diameter服务器接受该建议，并设置MIP6特征向量AVP和LOCAL_HOME_AGENT_分配标志（连同MIP6_INTEGRATED标志）并将其返回NAS。
In this scenario, we consider the case where the NAS supports the Diameter MIPv6 integrated scenario as defined in this document, but does not offer local HA assignment. Hence, the MIP6-Feature-Vector AVP only has the MIP6_INTEGRATED flag set. The Diameter server allocates an HA to the mobile node and conveys the address in the MIP-Home-Agent-Address AVP that is encapsulated in the MIP6-Agent-Info AVP. Additionally, the MIP6-Feature-Vector AVP has the MIP6_INTEGRATED flag set.
在这种情况下，我们考虑的情况下，NAS支持直径MIPv6集成场景中定义的文件，但不提供本地HA分配。因此，MIP6特征向量AVP仅具有MIP6_集成标志集。Diameter服务器将HA分配给移动节点，并传送MIP Home Agent address AVP中的地址，该地址封装在MIP6 Agent Info AVP中。此外，MIP6特征向量AVP具有MIP6_集成标志集。
Diameter
NAS Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(MIP6_INTEGRATED) |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:6000:302::1) |
| } |
| MIP6-Feature-Vector=(MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Diameter
NAS Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(MIP6_INTEGRATED) |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:6000:302::1) |
| } |
| MIP6-Feature-Vector=(MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Figure 3: Home Agent Assignment by the Diameter Server
图3:Diameter服务器的归属代理分配
This section shows another message flow for the MIPv6 integrated scenario bootstrapping where the NAS informs the Diameter server that it is able to locally assign an HA to the MN. The Diameter server is able to provide an HA to the MN but also authorizes the assignment of the local HA. The Diameter server then replies to the NAS with HA-related bootstrapping information.
本节显示了MIPv6集成场景引导的另一个消息流，其中NAS通知Diameter服务器它能够在本地将HA分配给MN。Diameter服务器能够向MN提供HA，但也授权本地HA的分配。然后Diameter服务器使用HA相关的引导信息回复NAS。
Whether the NAS/ASP then offers a locally assigned HA or the Diameter-server-assigned HA to the MN is, in this example, based on the local ASP policy.
在本例中，NAS/ASP随后是否向MN提供本地分配的HA或Diameter服务器分配的HA取决于本地ASP策略。
Diameter
NAS/VAAA Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
| } |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:6000:302::1)} |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Diameter
NAS/VAAA Server
| |
| Diameter-EAP-Request |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:1:c020::1)} |
| } |
| Auth-Request-Type=AUTHORIZE_AUTHENTICATE |
| EAP-Payload(EAP Start) |
|---------------------------------------------------------------->|
| |
| |
: ...more EAP Request/Response pairs... :
| |
| |
| Diameter-EAP-Answer |
| MIP6-Agent-Info{ |
| MIP-Home-Agent-Address(2001:db8:6000:302::1)} |
| MIP6-Feature-Vector=(LOCAL_HOME_AGENT_ASSIGNMENT |
| | MIP6_INTEGRATED) |
| Result-Code=DIAMETER_SUCCESS |
| EAP-Payload(EAP Success) |
| EAP-Master-Session-Key |
| (authorization AVPs) |
| ... |
|<----------------------------------------------------------------|
| |
Figure 4: Home Agent Assignment by the NAS or Diameter Server
图4:NAS或Diameter服务器的归属代理分配
If the Diameter server does not allow the MN to use a locally assigned HA, the Diameter server returns to the MN the MIP6-Feature-Vector AVP with the LOCAL_HOME_AGENT_ASSIGNMENT bit unset and the HA address it allocated.
如果Diameter服务器不允许MN使用本地分配的HA，则Diameter服务器将MIP6特征向量AVP返回给MN，其中本地\u HOME\u AGENT\u分配位未设置，HA地址已分配。
Figure 5 lists the MIPv6 bootstrapping NAS-to-HAAA interface AVPs along with a specification determining how many of each new AVP may be included in a Diameter command. They may be present in any Diameter application request and answer commands, where permitted by the command ABNF.
图5列出了MIPv6引导NAS到HAAA接口AVP的规范，以及确定Diameter命令中可能包含的每个新AVP的数量的规范。在命令ABNF允许的情况下，它们可能出现在任何Diameter应用程序请求和应答命令中。
+-----------+
| Command |
|-----+-----+
Attribute Name | Req | Ans |
-------------------------------|-----+-----|
MIP6-Agent-Info | 0+ | 0+ |
MIP6-Feature-Vector | 0-1 | 0-1 |
+-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | Req | Ans |
-------------------------------|-----+-----|
MIP6-Agent-Info | 0+ | 0+ |
MIP6-Feature-Vector | 0-1 | 0-1 |
+-----+-----+
Figure 5: Generic Request and Answer Commands AVP Table
图5：通用请求和应答命令AVP表
This specification defines the following AVPs that have been allocated from a normal Diameter AVP Code space (values >= 256):
本规范定义了从标准直径AVP代码空间（值>=256）分配的以下AVP：
MIP6-Agent-Info is set to 486
MIP6代理信息设置为486
The following new AVPs are to be allocated from RADIUS Attribute Type space [RFC2865] so that they are RADIUS backward-compatible (AVP Code values between 0-255):
以下新的AVP将从RADIUS属性类型空间[RFC2865]分配，以使其与RADIUS向后兼容（AVP代码值介于0-255之间）：
MIP6-Feature-Vector is set to 124 MIP6-Home-Link-Prefix is set to 125
MIP6特征向量设置为124 MIP6主链接前缀设置为125
IANA has created a new registry for the Mobility Capability as described in Section 4.2.5.
IANA已为第4.2.5节所述的移动能力创建了一个新的注册表。
Token | Value | Description
----------------------------------+---------------------+------------
MIP6_INTEGRATED | 0x0000000000000001 | [RFC5447]
LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC5447]
Available for Assignment via IANA | 2^x |
Token | Value | Description
----------------------------------+---------------------+------------
MIP6_INTEGRATED | 0x0000000000000001 | [RFC5447]
LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC5447]
Available for Assignment via IANA | 2^x |
Allocation rule: Only numeric values that are 2^x (power of two, where x >= 2) are allowed, based on the allocation policy described below.
分配规则：根据下面描述的分配策略，仅允许2^x（二的幂，其中x>=2）的数值。
Following the example policies described in [RFC5226], new values for the Mobility Capability Registry will be assigned based on the "Specification Required" policy. No mechanism to mark entries as "deprecated" is envisioned.
按照[RFC5226]中描述的示例策略，将根据“所需规范”策略为移动性能力注册表分配新值。没有设想将条目标记为“已弃用”的机制。
The security considerations for the Diameter interaction required to accomplish the integrated scenario are described in [INTEGRATED]. Additionally, the security considerations for the Diameter base protocol [RFC3588], the Diameter NASREQ application [RFC4005], and the Diameter EAP application (with respect to network access authentication and the transport of keying material) [RFC4072] are applicable to this document. Developers should insure that special attention is paid to configuring the security associations protecting the messages that enable the global positioning and allocation of home agents, for instance, as outlined in Section 5.
完成集成场景所需的Diameter交互的安全注意事项在[integrated]中描述。此外，Diameter基本协议[RFC3588]、Diameter NASREQ应用程序[RFC4005]和Diameter EAP应用程序（关于网络访问认证和密钥材料传输）[RFC4072]的安全注意事项适用于本文件。开发人员应确保特别注意配置安全关联，以保护消息，从而实现家庭代理的全球定位和分配，例如，如第5节所述。
Furthermore, the Diameter messages may be transported between the NAS and the Diameter server via one or more AAA brokers or Diameter agents (such as proxies). In this case, the AAA communication from the NAS to the Diameter server relies on the security properties of the intermediate AAA brokers and Diameter agents.
此外，Diameter消息可以经由一个或多个AAA代理或Diameter代理（例如代理）在NAS和Diameter服务器之间传输。在这种情况下，从NAS到Diameter服务器的AAA通信依赖于中间AAA代理和Diameter代理的安全属性。
This document is heavily based on the ongoing work for RADIUS MIPv6 interaction. Hence, credits go to respective authors for their work with "RADIUS Mobile IPv6 Support" (November 2008). Furthermore, the authors of this document would like to thank the authors of "Diameter Mobile IPv6 Application" (November 2004) -- Franck Le, Basavaraj Patil, Charles E. Perkins, and Stefano Faccin -- for their work in the context of MIPv6 Diameter interworking. Their work influenced this document. Jouni Korhonen would like to thank the Academy of Finland and TEKES MERCoNe Project for providing funding to work on this document while he was with TeliaSonera. Julien Bournelle would like to thank GET/INT since he began to work on this document while he was in their employ. Authors would also like to acknowledge Raymond Hsu for his valuable feedback on local HA assignment and Wolfgang Fritsche for his thorough review. Additionally, we would like to Domagoj Premec for his review comments.
本文档主要基于正在进行的RADIUS MIPv6交互工作。因此，作者在“RADIUS移动IPv6支持”方面的工作（2008年11月）将获得相应的奖励。此外，本文档的作者要感谢“Diameter移动IPv6应用程序”（2004年11月）的作者Franck Le、Basavaraj Patil、Charles E.Perkins和Stefano Faccin在MIPv6 Diameter互通环境中所做的工作。他们的工作影响了这份文件。Jouni Korhonen感谢芬兰科学院和TEKES MERCoNe项目在他任职TeliaSonera期间为编写本文件提供资金。Julien Bournelle要感谢GET/INT，因为他在受雇于他们期间开始编写此文档。作者还想感谢Raymond Hsu对当地医管局任务的宝贵反馈，以及Wolfgang Fritsche的全面审查。此外，我们还想向Domagoj Premec咨询他的审查意见。
Finally, we would like to thank Alper Yegin, Robert Marks, and David Frascone for their comments at the second WG Last Call.
最后，我们要感谢阿尔珀·耶金、罗伯特·马克斯和大卫·弗雷斯科在第二次工作组最后一次电话会议上发表的评论。
[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月。
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000.
[RFC2865]Rigney，C.，Willens，S.，Rubens，A.，和W.Simpson，“远程认证拨入用户服务（RADIUS）”，RFC 28652000年6月。
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3588]Calhoun，P.，Loughney，J.，Guttman，E.，Zorn，G.，和J.Arkko，“直径基础协议”，RFC 3588，2003年9月。
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004.
[RFC3775]Johnson，D.，Perkins，C.，和J.Arkko，“IPv6中的移动支持”，RFC 37752004年6月。
[RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, August 2005.
[RFC4004]Calhoun，P.，Johansson，T.，Perkins，C.，Hiller，T.，和P.McCann，“Diameter移动IPv4应用”，RFC 40042005年8月。
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005.translate error, please retry
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible Authentication Protocol (EAP) Application", RFC 4072, August 2005.
[RFC4072]Eronen，P.，Hiller，T.，和G.Zorn，“直径可扩展认证协议（EAP）应用”，RFC 4072，2005年8月。
[AAA] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. Lopez, "AAA Goals for Mobile IPv6", Work in Progress, May 2008.
[AAA]Giaretta，G.，Guardini，I.，Demaria，E.，Bournelle，J.，和R.Lopez，“移动IPv6的AAA目标”，正在进行的工作，2008年5月。
[DSMIPv6] Solimand, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6)", Work in Progress, December 2008.
[DSMIV6]Solimand，H.，“双栈主机和路由器的移动IPv6支持（DSMIV6）”，正在进行的工作，2008年12月。
[INTEGRATED] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the Integrated Scenario", Work in Progress, April 2008.
[集成]Chowdhury，K.和A.Yegin，“集成场景的MIP6引导”，正在进行的工作，2008年4月。
[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月。
[RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 Bootstrapping in Split Scenario", RFC 5026, October 2007.
[RFC5026]Giaretta，G.，Kempf，J.，和V.Devarapalli，“拆分场景中的移动IPv6引导”，RFC 5026，2007年10月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
Authors' Addresses
作者地址
Jouni Korhonen (editor) Nokia Siemens Networks Linnoitustie 6 Espoo FIN-02600 Finland
Jouni Korhonen（编辑）诺基亚西门子网络公司Linnoitustie 6 Espoo FIN-02600芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com
Julien Bournelle Orange Labs 38-4O rue du general Leclerc Issy-Les-Moulineaux 92794 France
Julien Bournelle Orange实验室法国莱克勒将军大道38-4O号
EMail: julien.bournelle@orange-ftgroup.com
EMail: julien.bournelle@orange-ftgroup.com
Hannes Tschofenig Nokia Siemens Networks Linnoitustie 6 Espoo 02600 Finland
Hannes Tschofenig诺基亚西门子网络公司芬兰Linnoitustie 6 Espoo 02600
EMail: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.priv.at
EMail: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.priv.at
Charles E. Perkins WiChorus Inc. 3590 North First St., Suite 300 San Jose, CA 95134 US
Charles E.Perkins WiChorus Inc.美国加利福尼亚州圣何塞北第一街3590号300室，邮编95134
EMail: charliep@wichorus.com
EMail: charliep@wichorus.com
Kuntal Chowdhury Starent Networks 30 International Place Tewksbury, MA 01876 US
Kuntal Chowdhury Starent Networks美国马萨诸塞州托克斯伯里国际广场30号01876
EMail: kchowdhury@starentnetworks.com
EMail: kchowdhury@starentnetworks.com