Internet Engineering Task Force (IETF) F. Xia
Request for Comments: 6572 B. Sarikaya
Category: Standards Track Huawei USA
ISSN: 2070-1721 J. Korhonen, Ed.
Nokia Siemens Networks
S. Gundavelli
Cisco
D. Damic
Siemens
June 2012
Internet Engineering Task Force (IETF) F. Xia
Request for Comments: 6572 B. Sarikaya
Category: Standards Track Huawei USA
ISSN: 2070-1721 J. Korhonen, Ed.
Nokia Siemens Networks
S. Gundavelli
Cisco
D. Damic
Siemens
June 2012
RADIUS Support for Proxy Mobile IPv6
RADIUS支持代理移动IPv6
Abstract
摘要
This document defines new attributes to facilitate Proxy Mobile IPv6 operations using the RADIUS infrastructure. The protocol defined in this document uses RADIUS-based interfaces of the mobile access gateway and the local mobility anchor with the AAA server for authentication, authorization, and policy functions. The RADIUS interactions between the mobile access gateway and the RADIUS-based AAA server take place when the mobile node (MN) attaches, authenticates, and authorizes to a Proxy Mobile IPv6 domain. Furthermore, this document defines the RADIUS-based interface between the local mobility anchor and the AAA RADIUS server for authorizing received Proxy Binding Update messages for the mobile node's mobility session. In addition to the interactions related to mobility session setup, this document defines the baseline for the mobile access gateway and the local mobility anchor generated accounting.
本文档定义了新属性，以便于使用RADIUS基础架构执行代理移动IPv6操作。本文档中定义的协议使用基于RADIUS的移动接入网关接口和本地移动锚与AAA服务器的接口来实现身份验证、授权和策略功能。移动接入网关和基于RADIUS的AAA服务器之间的RADIUS交互在移动节点（MN）连接、认证和授权到代理移动IPv6域时发生。此外，本文档定义了本地移动锚和AAA RADIUS服务器之间基于RADIUS的接口，用于为移动节点的移动会话授权接收到的代理绑定更新消息。除了与移动会话设置相关的交互之外，本文档还定义了移动接入网关和本地移动锚生成的记帐的基线。
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/rfc6572.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6572.
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 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 ....................................................4
2. Terminology .....................................................4
3. Solution Overview ...............................................5
4. Attribute Definitions ...........................................9
4.1. MIP6-Feature-Vector ........................................9
4.2. Mobile-Node-Identifier ....................................11
4.3. Service-Selection .........................................12
4.4. PMIP6-Home-LMA-IPv6-Address ...............................12
4.5. PMIP6-Visited-LMA-IPv6-Address ............................13
4.6. PMIP6-Home-LMA-IPv4-Address ...............................14
4.7. PMIP6-Visited-LMA-IPv4-Address ............................15
4.8. PMIP6-Home-HN-Prefix ......................................15
4.9. PMIP6-Visited-HN-Prefix ...................................16
4.10. PMIP6-Home-Interface-ID ..................................18
4.11. PMIP6-Visited-Interface-ID ...............................18
4.12. PMIP6-Home-IPv4-HoA ......................................19
4.13. PMIP6-Visited-IPv4-HoA ...................................20
4.14. PMIP6-Home-DHCP4-Server-Address ..........................21
4.15. PMIP6-Visited-DHCP4-Server-Address .......................22
4.16. PMIP6-Home-DHCP6-Server-Address ..........................22
4.17. PMIP6-Visited-DHCP6-Server-Address .......................23
4.18. Calling-Station-Id .......................................24
4.19. Chargeable-User-Identity .................................24
4.20. PMIP6-Home-IPv4-Gateway ..................................25
4.21. PMIP6-Visited-IPv4-Gateway ...............................25
5. MAG to RADIUS AAA Interface ....................................26
5.1. Interface Operations ......................................26
5.2. Table of Attributes .......................................27
6. LMA to RADIUS AAA Interface ....................................28
6.1. Interface Operations ......................................28
6.2. Table of Attributes .......................................30
7. Accounting .....................................................31
7.1. Accounting at LMA .........................................31
7.2. Accounting at MAG .........................................32
7.3. Table of Attributes .......................................32
8. Security Considerations ........................................32
9. IANA Consideration .............................................33
9.1. Attribute Type Codes ......................................33
9.2. Namespaces ................................................33
10. Acknowledgements ..............................................34
11. References ....................................................34
11.1. Normative References .....................................34
11.2. Informative References ...................................35
1. Introduction ....................................................4
2. Terminology .....................................................4
3. Solution Overview ...............................................5
4. Attribute Definitions ...........................................9
4.1. MIP6-Feature-Vector ........................................9
4.2. Mobile-Node-Identifier ....................................11
4.3. Service-Selection .........................................12
4.4. PMIP6-Home-LMA-IPv6-Address ...............................12
4.5. PMIP6-Visited-LMA-IPv6-Address ............................13
4.6. PMIP6-Home-LMA-IPv4-Address ...............................14
4.7. PMIP6-Visited-LMA-IPv4-Address ............................15
4.8. PMIP6-Home-HN-Prefix ......................................15
4.9. PMIP6-Visited-HN-Prefix ...................................16
4.10. PMIP6-Home-Interface-ID ..................................18
4.11. PMIP6-Visited-Interface-ID ...............................18
4.12. PMIP6-Home-IPv4-HoA ......................................19
4.13. PMIP6-Visited-IPv4-HoA ...................................20
4.14. PMIP6-Home-DHCP4-Server-Address ..........................21
4.15. PMIP6-Visited-DHCP4-Server-Address .......................22
4.16. PMIP6-Home-DHCP6-Server-Address ..........................22
4.17. PMIP6-Visited-DHCP6-Server-Address .......................23
4.18. Calling-Station-Id .......................................24
4.19. Chargeable-User-Identity .................................24
4.20. PMIP6-Home-IPv4-Gateway ..................................25
4.21. PMIP6-Visited-IPv4-Gateway ...............................25
5. MAG to RADIUS AAA Interface ....................................26
5.1. Interface Operations ......................................26
5.2. Table of Attributes .......................................27
6. LMA to RADIUS AAA Interface ....................................28
6.1. Interface Operations ......................................28
6.2. Table of Attributes .......................................30
7. Accounting .....................................................31
7.1. Accounting at LMA .........................................31
7.2. Accounting at MAG .........................................32
7.3. Table of Attributes .......................................32
8. Security Considerations ........................................32
9. IANA Consideration .............................................33
9.1. Attribute Type Codes ......................................33
9.2. Namespaces ................................................33
10. Acknowledgements ..............................................34
11. References ....................................................34
11.1. Normative References .....................................34
11.2. Informative References ...................................35
Proxy Mobile IPv6 (PMIPv6) [RFC5213] is a network-based mobility management protocol that allows IP mobility support for a mobile node without requiring the mobile node's participation in any mobility-related signaling. The mobile management elements in the network, the mobile access gateway (MAG) and the local mobility anchor (LMA), are the two key functions in this network-based mobility system. The mobile access gateway is responsible for detecting the mobile node's movements in the network and for initiating the needed mobility management signaling with the local mobility anchor (LMA). Both the mobility management agents make use of the AAA infrastructure to retrieve the mobile node's policy profile and for performing service authorization.
代理移动IPv6（PMIPv6）[RFC5213]是一种基于网络的移动性管理协议，它允许在不要求移动节点参与任何移动性相关信令的情况下为移动节点提供IP移动性支持。网络中的移动管理元件，即移动接入网关（MAG）和本地移动锚（LMA），是基于网络的移动系统中的两个关键功能。移动接入网关负责检测移动节点在网络中的移动，并使用本地移动锚（LMA）发起所需的移动管理信令。这两个移动性管理代理都使用AAA基础设施来检索移动节点的策略配置文件并执行服务授权。
This document defines a RADIUS-based [RFC2865] profile and corresponding attributes to be used on the AAA interface between the MAG and the AAA RADIUS server. This interface is used to carry the per-MN policy profile from the remote policy store to the MAG. Furthermore, this document also defines a RADIUS-based interface between the LMA and the AAA RADIUS server for authorization of the received Proxy Mobile IPv6 signaling messages. The AAA procedures defined in this document cover the following two scenarios:
本文档定义了一个基于RADIUS的[RFC2865]配置文件和相应的属性，用于MAG和AAA RADIUS服务器之间的AAA接口。此接口用于将每MN策略配置文件从远程策略存储传送到MAG。此外，本文档还定义了LMA和AAA RADIUS服务器之间基于RADIUS的接口，用于对接收到的代理移动IPv6信令消息进行授权。本文件中定义的AAA程序包括以下两种情况：
o a mobile node connects to the Proxy Mobile IPv6 domain from the home network
o 移动节点从家庭网络连接到代理移动IPv6域
o a mobile node connects to the Proxy Mobile IPv6 domain from a visited network
o 移动节点从访问的网络连接到代理移动IPv6域
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]中所述进行解释。
All the mobility-related terms used in this document are to be interpreted as defined in the Proxy Mobile IPv6 specifications [RFC5213] and [RFC5844]. Additionally, this document uses the following abbreviations:
本文件中使用的所有移动相关术语应按照代理移动IPv6规范[RFC5213]和[RFC5844]中的定义进行解释。此外，本文件使用以下缩写：
Network Access Server (NAS):
网络访问服务器（NAS）：
A function that provides authorization services for a device/user access to the network as defined in [RFC2865]. This document makes an assumption that the NAS function is co-located with the
为设备/用户访问[RFC2865]中定义的网络提供授权服务的功能。本文档假设NAS功能与
MAG. In scenarios where the NAS function and MAG are decoupled, the messaging interface needed between them for the operation of PMIP6 is beyond the scope of this document.
MAG。在NAS功能和MAG分离的场景中，PMIP6运行所需的NAS功能和MAG之间的消息传递接口超出了本文档的范围。
Home AAA (HAAA):
家庭AAA（HAAA）：
An Authentication, Authorization, and Accounting (AAA) server located in the MN's home network. This sever has access to the mobile node's policy profiles.
位于MN的家庭网络中的身份验证、授权和计费（AAA）服务器。此服务器可以访问移动节点的策略配置文件。
Visited AAA (VAAA):
访问AAA（VAAA）：
An Authentication, Authorization, and Accounting (AAA) server located in the MN's visited network. The VAAA server takes the role of a proxy-server, forwarding the received AAA service request to the HAAA server in the mobile node's home network and relaying the response to the requesting node, after applying any local access network policies.
位于MN的访问网络中的身份验证、授权和计费（AAA）服务器。VAAA服务器扮演代理服务器的角色，在应用任何本地接入网络策略之后，将接收到的AAA服务请求转发给移动节点的家庭网络中的HAAA服务器，并将响应转发给请求节点。
Local AAA (LAAA):
本地AAA（LAAA）：
An Authentication, Authorization, and Accounting proxy located in the local network. In a roaming case, the local AAAA has the visited AAA role.
位于本地网络中的身份验证、授权和记帐代理。在漫游情况下，本地AAAA具有已访问的AAA角色。
This document defines the RADIUS-based AAA interactions with the two mobility management elements in the Proxy Mobile IPv6 domain.
本文档定义了基于RADIUS的AAA与代理移动IPv6域中的两个移动管理元素的交互。
o Interactions between a MAG and a RADIUS-based AAA server
o MAG和基于RADIUS的AAA服务器之间的交互
o Interactions between a LMA and a RADIUS-based AAA server
o LMA和基于RADIUS的AAA服务器之间的交互
The mobile node's policy profile [RFC5213] is present in a policy store and is needed by the PMIPv6 mobility management elements for authorizing the mobile node for mobility management service and for obtaining various service-related parameters. This policy store could be locally co-located with the mobility management agents enabling direct local access or could be available from a AAA server through a RADIUS-based AAA interface.
移动节点的策略简档[RFC5213]存在于策略存储中，并且PMIPv6移动性管理元件需要该策略简档来授权移动节点进行移动性管理服务以及获取各种与服务相关的参数。此策略存储可以与移动管理代理在本地共存，从而实现直接本地访问，也可以通过基于RADIUS的AAA接口从AAA服务器获得。
When a mobile node attaches to an access network, the NAS on that access network may activate the network access authentication procedure. The choice of the authentication mechanism is specific to the access network deployment; however, it is typically based on the Extensible Authentication Protocol (EAP) [RFC3748]. The NAS performs the network access authentication and queries the HAAA using AAA
当移动节点连接到接入网络时，该接入网络上的NAS可激活网络接入认证过程。认证机制的选择取决于接入网的部署；然而，它通常基于可扩展身份验证协议（EAP）[RFC3748]。NAS执行网络访问身份验证，并使用AAA查询HAAA
protocol, such as RADIUS. If the network access authentication succeeds, the MN's policy profile is obtained as part of the RADIUS message exchange with the AAA server.
协议，例如RADIUS。如果网络访问身份验证成功，MN的策略配置文件将作为与AAA服务器进行RADIUS消息交换的一部分获得。
The mobile node may be an IPv4-only node, IPv6-only node, or a dual-stack (IPv4/v6) node. Based on the policy specified in the policy profile, the network access authentication procedure SHOULD provide the unambiguous indication of the type of address(es) to be assigned for the MN in the network and with all other service-related and policy parameters relevant to the mobility service.
移动节点可以是仅IPv4节点、仅IPv6节点或双栈（IPv4/v6）节点。基于策略概要文件中指定的策略，网络接入认证过程应提供要为网络中的MN分配的地址类型的明确指示，以及与移动性服务相关的所有其他服务相关和策略参数。
After the successful network access authentication and obtaining the mobile node's policy profile, the MAG sends a Proxy Binding Update (PBU) to the LMA. Upon receiving the PBU, the LMA interacts with the HAAA to obtain the mobile node's policy profile, which is required for authorizing and activating mobility service.
在成功的网络接入认证和获得移动节点的策略简档之后，MAG向LMA发送代理绑定更新（PBU）。在接收到PBU时，LMA与HAAA交互以获得移动节点的策略简档，该策略简档是授权和激活移动服务所必需的。
This document adds support for three distinct PMIPv6 mobility use cases, taking into account the administrative domains to which the MAG and the LMA belong. The following are the three relevant deployment models.
考虑到MAG和LMA所属的管理领域，本文档添加了对三种不同的PMIPv6移动性用例的支持。以下是三种相关的部署模型。
1. the MAG and LMA are both in the home network,
1. MAG和LMA都在家庭网络中，
2. the MAG and LMA are both in the visited network,
2. MAG和LMA都在访问网络中，
3. the MAG is in the visited network while the LMA is in the home network.
3. MAG在访问网络中，而LMA在家庭网络中。
Figure 1 shows participating network entities for the PMIPv6 mobility session, which is located in the home network. The MAG and LMA interact only with the HAAA.
图1显示了位于家庭网络中的PMIPv6移动会话的参与网络实体。MAG和LMA仅与HAAA相互作用。
+--------+
| HAAA & | RADIUS +-----+
| Policy |<-------->| LMA |
| Profile| +-----+
+--------+ | <--- LMA-Address
^ |
| // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
| |
MN1 MN2
+--------+
| HAAA & | RADIUS +-----+
| Policy |<-------->| LMA |
| Profile| +-----+
+--------+ | <--- LMA-Address
^ |
| // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
| |
MN1 MN2
Figure 1: The MAG and LMA Are Both in the Home Network
图1:MAG和LMA都在家庭网络中
Figure 2 shows both the LMA and MAG are in the visited network. The MAG and LMA exchange signaling with the HAAA through the VAAA, which acts as a Proxy. The visited network may append additional information to the HAAA replies in order to reflect the local policy.
图2显示了LMA和MAG都在访问的网络中。MAG和LMA通过充当代理的VAAA与HAAA交换信令。受访网络可在HAAA回复中附加附加信息，以反映当地政策。
+---------------+
| HAAA & |
+----------| Policy Profile|
| +---------------+
|
+---------+
|[VL]AAA &| RADIUS +-----+
| Policy |<------->| LMA |
| Profile | +-----+
+---------+ | <--- LMA-Address
^ // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
MN1 MN2
+---------------+
| HAAA & |
+----------| Policy Profile|
| +---------------+
|
+---------+
|[VL]AAA &| RADIUS +-----+
| Policy |<------->| LMA |
| Profile | +-----+
+---------+ | <--- LMA-Address
^ // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
MN1 MN2
Figure 2: The MAG and LMA Are Both in the Visited/Local Network
图2:MAG和LMA都在访问/本地网络中
Figure 3 illustrates a topology where the MAG resides in the visited network while the associated LMA is in MN's home network. Any message between the MAG and the HAAA passes through the VAAA, which acts as a Proxy. During the network authentication, the visited network's specific policy may also be propagated from the VAAA to the MAG. The LMA has a direct access to the HAAA.
图3说明了一种拓扑结构，其中MAG位于访问网络中，而相关LMA位于MN的家庭网络中。MAG和HAAA之间的任何消息都将通过充当代理的VAAA传递。在网络认证期间，访问网络的特定策略也可以从VAAA传播到MAG。LMA可以直接访问HAAA。
+---------------+
| HAAA & |
+----------| Policy Profile|
| +---------------+
| |
| RADIUS
+---------+ |
|[VL]AAA &| +-----+
| Policy | | LMA |
| Profile | +-----+
+---------+ | <--- LMA-Address
^ // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
MN1 MN2
+---------------+
| HAAA & |
+----------| Policy Profile|
| +---------------+
| |
| RADIUS
+---------+ |
|[VL]AAA &| +-----+
| Policy | | LMA |
| Profile | +-----+
+---------+ | <--- LMA-Address
^ // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
RADIUS // <- Tunnel1 \\ <- Tunnel2
| // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
MN1 MN2
Figure 3: Visited MAG and Home LMA Topology
图3：访问MAG和家庭LMA拓扑
Diameter [RFC3588] reserves AVP Code space 1-255 as RADIUS attribute compatibility space. The MIP6-Feature-Vector attribute (Type value 124) defined in [RFC5447] is of type OctetString and contains a 64-bit flags field of supported mobility capabilities. This document reserves two new capability bits according to the rules in [RFC5447], and reuses the PMIPv6 capability bits defined by [RFC5779]. The following capability flag bits are used or defined in this document:
Diameter[RFC3588]保留AVP代码空间1-255作为RADIUS属性兼容空间。[RFC5447]中定义的MIP6特征向量属性（类型值124）为OctetString类型，包含支持的移动能力的64位标志字段。本文档根据[RFC5447]中的规则保留两个新的能力位，并重用[RFC5779]中定义的PMIPv6能力位。本文件中使用或定义了以下能力标志位：
PMIP6_SUPPORTED (0x0000010000000000)
支持的PMIP6_（0x000001000000000）
This capability bit is used as defined in [RFC5779].
此能力位的使用如[RFC5779]中所定义。
IP4_HOA_SUPPORTED (0x0000020000000000)
支持IP4_-HOA_（0x000002000000000）
This capability bit is used as defined in [RFC5779]. Assignment of the IPv4-HoA (Home Address) is defined by [RFC5844].
此能力位的使用如[RFC5779]中所定义。IPv4 HoA（家庭地址）的分配由[RFC5844]定义。
LOCAL_MAG_ROUTING_SUPPORTED (0x0000040000000000)
支持本地磁盘路由（0x00004000000000）
This capability bit is used as defined in [RFC5779].
此能力位的使用如[RFC5779]中所定义。
IP4_TRANSPORT_SUPPORTED (0x0000800000000000)
支持IP4_传输_（0x0000080000000000）
This capability bit is used for negotiation of the IPv4 transport support between the MAG and AAA. When the MAG sets this flag bit in the MIP6-Feature-Vector, it indicates the ability of the MAG to provide IPv4 transport (i.e., IPv4-based encapsulation) for carrying IP traffic between the MAG and the LMA. If this flag bit is unset in the returned MIP6-Feature-Vector attribute, the AAA does not authorize the use of IPv4 transport on the MAG-to-LMA tunnel.
此功能位用于在MAG和AAA之间协商IPv4传输支持。当MAG在MIP6特征向量中设置该标志位时，它指示MAG提供IPv4传输（即，基于IPv4的封装）以在MAG和LMA之间承载IP流量的能力。如果此标志位在返回的MIP6特征向量属性中未设置，则AAA不会授权在MAG到LMA隧道上使用IPv4传输。
IP4_HOA_ONLY_SUPPORTED (0x0001000000000000)
仅支持IP4_-HOA_（0x00010000000000）
This capability bit is used for determination of the authorized PMIPv6 mobility mode. When this bit is set by the AAA, it indicates PMIPv6 mobility with IPv4 support has only been authorized for the MN. As a result, the RADIUS Access-Accept SHOULD NOT carry the IPv6 Home Network Prefix (IPv6 HNP). When this bit is set, the PMIP6_SUPPORTED flag MUST also be set and the IP4_HOA_SUPPORTED flag MUST NOT be set.
该能力位用于确定授权PMIPv6移动模式。当该位由AAA设置时，表示仅为MN授权了支持IPv4的PMIPv6移动性。因此，RADIUS访问接受不应带有IPv6家庭网络前缀（IPv6 HNP）。设置此位时，还必须设置PMIP6_支持标志，且不得设置IP4_HOA_支持标志。
To summarize the use of the MIP6-Feature-Vector the following capability bit combination settings mean:
总结MIP6特征向量的使用，以下能力位组合设置意味着：
PMIP6-SUPPORTED bit set - only IPv6 mobility is supported and authorized.
PMIP6支持的位集-仅支持和授权IPv6移动。
PMIP6-SUPPORTED and IP4-ONLY-HOA-SUPPORTED bits set - only IPv4 mobility is supported and authorized.
支持PMIP6和仅支持IP4-HOA的位集-仅支持和授权IPv4移动。
PMIP6-SUPPORTED and IP4-HOA-SUPPORTED bits set - both IPv6 and IPv4 mobility are supported and authorized.
支持PMIP6和支持IP4-HOA的位集-支持并授权IPv6和IPv4移动性。
The MIP6-Feature-Vector attribute is also used on the LMA to the RADIUS AAA interface. This capability announcement attribute enables direct capability negotiation between the LMA and the AAA. The capabilities that are announced by both parties in the MIP6-Feature-Vector are known to be mutually supported. The LMA may use this mechanism during authorization of the received PBU against the AAA to check individual PMIPv6 feature permissions for a particular MN.
MIP6特征向量属性也用于LMA到RADIUS AAA接口。此能力公告属性支持LMA和AAA之间的直接能力协商。双方在MIP6特征向量中宣布的功能已知是相互支持的。LMA可以在针对AAA对接收到的PBU进行授权期间使用该机制来检查特定MN的单个PMIPv6特性许可。
If the RADIUS Access-Accept contains a contradicting combination of the capability flag bits such as both the IP4_HOA_ONLY_SUPPORTED and the IP4_HOA_SUPPORTED flags being set, then the RADIUS client MUST
如果RADIUS Access Accept包含能力标志位的矛盾组合，例如支持的IP4_HOA_ONLY_和设置的支持的IP4_HOA_标志，则RADIUS客户端必须
treat the Access-Accept as an Access-Reject and SHOULD log the event. Similarly, if the RADIUS Access-Request contains a contradicting combination of the capability flag bits, then the RADIUS server MUST reply with an Access-Reject message and SHOULD log the event.
将访问接受视为访问拒绝，并应记录事件。类似地，如果RADIUS访问请求包含能力标志位的矛盾组合，则RADIUS服务器必须使用访问拒绝消息进行回复，并应记录事件。
The Mobile-Node-Identifier attribute (Type value 145) is of type String and contains the mobile node identifier (MN-Identifier), see [RFC5213], in a form of a Network Access Identifier (NAI) [RFC4282]. This identifier and the identifier used for access authentication may be different; however, there needs to be a mapping between the two identities as specified in Section 6.6 of [RFC5213]. This attribute is used on the interface between the MAG and the AAA server. The Mobile-Node-Identifier attribute is designed for deployments where the identity used during network access authentication and the identity used for mobility management is decoupled. It may also be the case where the MAG does not have means to find out the MN identity that could be used in subsequent PBU and Proxy Binding Acknowledgement (PBA) exchanges (e.g., due to identity hiding during the network access authentication) or when the HAAA wants to assign periodically changing identities to the MN.
移动节点标识符属性（类型值145）为字符串类型，包含移动节点标识符（MN标识符），参见[RFC5213]，其形式为网络接入标识符（NAI）[RFC4282]。该标识符和用于访问认证的标识符可以不同；但是，需要在[RFC5213]第6.6节中规定的两个身份之间进行映射。此属性用于MAG和AAA服务器之间的接口。“移动节点标识符”属性设计用于网络访问身份验证期间使用的标识与用于移动性管理的标识解耦的部署。也可能是这样的情况，即MAG没有手段找出可在随后的PBU和代理绑定确认（PBA）交换中使用的MN身份（例如，由于在网络接入认证期间的身份隐藏），或者当HAAA想要向MN分配周期性改变的身份时。
The Mobile-Node-Identifier attribute MAY be returned by the HAAA in the RADIUS Access-Accept message that completes a successful authentication and authorization exchange between the MAG and the HAAA. The MAG MUST use the received MN-Identifier.
移动节点标识符属性可由HAAA在RADIUS接入接受消息中返回，该消息完成MAG和HAAA之间的成功认证和授权交换。MAG必须使用接收到的MN标识符。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Mobile Node Identifier... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Mobile Node Identifier... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Mobile-Node-Identifier 145.
类型：移动节点标识符145。
Length: In octets, including Type and Length fields (>= 3).
长度：以八位字节为单位，包括类型和长度字段（>=3）。
Mobile Node Identifier: This field is of type String and contains the MN-Identifier of the MN to be used in the PBU/PBA exchange.
移动节点标识符：该字段为字符串类型，包含PBU/PBA交换中使用的MN的MN标识符。
The Service-Selection attribute (Type value 146) is of type UTF-8 text and contains the name of the service or the external network with which the mobility service for the particular MN SHOULD be associated [RFC5149]. The identifier MUST be unique within the PMIPv6 Domain when normalized using the selected normalization form [UNF] for the particular PMIPv6 Domain deployment. For instance, [RFC5149] uses the Normalization Form KC (NFKC).
服务选择属性（类型值146）为UTF-8文本类型，包含服务或外部网络的名称，特定MN的移动服务应与之关联[RFC5149]。当使用为特定PMIPv6域部署选择的规范化表单[UNF]进行规范化时，该标识符在PMIPv6域中必须是唯一的。例如，[RFC5149]使用规范化形式KC（NFKC）。
The MAG MUST include the Service-Selection attribute in the Access-Request sent to the AAA if the information was acquired, e.g., by operator-specific configuration. The AAA MAY include the Service-Selection attribute in the Access-Accept response message to the MAG even if it was not included in the Access-Request as a means of indicating the MN's default service.
MAG必须在发送给AAA的访问请求中包含服务选择属性（如果信息是通过特定于操作员的配置获取的）。AAA可以在对MAG的访问接受响应消息中包括服务选择属性，即使该属性没有包括在访问请求中，作为指示MN的默认服务的手段。
The Service Selection mobility option defined in [RFC5149] can be used in PBU/PBA messages between the MAG and LMA. On the LMA-to-AAA interface, the LMA MAY populate the Service-Selection attribute in the Access-Request message using the service information found in the received PBU, if such a mobility option were included. The Service-Selection identifier should be used to assist the PBU authorization, the assignment of the MN-HNP, and the IPv4-MN-HoA as described in [RFC5149] and [RFC5779].
[RFC5149]中定义的服务选择移动选项可用于MAG和LMA之间的PBU/PBA消息中。在LMA到AAA接口上，如果包括这样的移动性选项，则LMA可以使用在接收到的PBU中找到的服务信息来填充接入请求消息中的服务选择属性。如[RFC5149]和[RFC5779]所述，服务选择标识符应用于协助PBU授权、MN-HNP分配和IPv4 MN HoA。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Service Identifier... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Service Identifier... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Service-Selection 146.
类型：服务选择146。
Length: In octets, including Type and Length fields (>= 3).
长度：以八位字节为单位，包括类型和长度字段（>=3）。
Text: This field is of type UTF-8 text and contains the Service Identifier with which the MN is associated.
Text：此字段的类型为UTF-8 Text，包含与MN关联的服务标识符。
The PMIP6-Home-LMA-IPv6-Address attribute (Type value 147) is of type IPv6 address and is used to deliver the IPv6 address of the LMA located in the home network.
PMIP6-Home-LMA-IPv6-Address属性（类型值147）属于IPv6地址类型，用于传递位于家庭网络中的LMA的IPv6地址。
Before the MAG can initiate Proxy Mobile IPv6 signaling, it must be aware of the LMA's IP address.
在MAG可以启动代理移动IPv6信令之前，它必须知道LMA的IP地址。
When the LMA is assigned to the MN from the home network, this attribute MAY be sent by the HAAA to the MAG in the RADIUS Access-Accept message.
当LMA从家庭网络分配给MN时，HAAA可以在RADIUS接入接受消息中将该属性发送给MAG。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv6 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-LMA-IPv6-Address 147.
类型：PMIP6-Home-LMA-IPv6-Address 147。
Length: = 18 octets
长度：=18个八位字节
Home LMA IPv6 address: 128-bit IPv6 address of the assigned home LMA IPv6 address.
家庭LMA IPv6地址：分配的家庭LMA IPv6地址的128位IPv6地址。
The PMIP6-Visited-LMA-IPv6-Address attribute (Type value 148) is of type IPv6 address and is used to propose a particular LMA in the visited network and to authorize the use of the LMA in the visited/ local network.
PMIP6-visted-LMA-IPv6-Address属性（类型值148）是IPv6-Address类型，用于在到访网络中提出特定LMA，并授权在到访/本地网络中使用LMA。
PMIP6-Visited-LMA-IPv6-Address attribute MAY be included by the MAG in the RADIUS Access-Request message. The LMA in the visited/local network may be assigned by the [VL]AAA as the result of retrieved policy profile. If included by the [VL]AAA in the RADIUS Access-Accept sent to the MAG, the use of the LMA in the visited/local network is authorized and the attribute SHALL carry the IPv6 address of the LMA assigned for the particular MN. See Section 4.2.5 of [RFC5447] how the MIP6-Feature-Vector attribute and LOCAL_HOME_AGENT_ASSIGNMENT capability flag is used with the LMA (Home Agent) assignment.
MAG可以在RADIUS访问请求消息中包括PMIP6-Visited-LMA-IPv6-Address属性。作为检索到的策略简档的结果，[VL]AAA可以分配到访/本地网络中的LMA。如果[VL]AAA在发送给MAG的RADIUS访问接受中包括LMA，则授权在访问/本地网络中使用LMA，并且该属性应携带分配给特定MN的LMA的IPv6地址。请参阅[RFC5447]第4.2.5节，了解MIP6特征向量属性和本地_HOME_AGENT_分配能力标志如何与LMA（归属代理）分配一起使用。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv6 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-LMA-IPv6-Address 148.
类型：PMIP6-visted-LMA-IPv6-Address 148。
Length: = 18 octets
长度：=18个八位字节
Visited LMA IPv6 address: 128-bit IPv6 address of the assigned visited LMA IPv6 address.
已访问LMA IPv6地址：分配的已访问LMA IPv6地址的128位IPv6地址。
The PMIP6-Home-LMA-IPv4-Address attribute (Type value 149) is of type IPv4 address and contains the IPv4 address of the LMA assigned by the HAAA. The [RFC5844] supports Proxy Mobile IPv6 signaling exchange between MAG and LMA using the IPv4 transport.
PMIP6-Home-LMA-IPv4-Address属性（类型值149）属于IPv4地址类型，包含HAAA分配的LMA的IPv4地址。[RFC5844]支持使用IPv4传输在MAG和LMA之间进行代理移动IPv6信令交换。
When the LMA is located in the home network, this attribute MAY be sent by the HAAA to the MAG in the RADIUS Access-Accept message.
当LMA位于家庭网络中时，该属性可由HAAA在RADIUS接入接受消息中发送给MAG。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home LMA IPv4 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv4 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home LMA IPv4 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home LMA IPv4 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-LMA-IPv4-Address 149.
类型：PMIP6-Home-LMA-IPv4-Address 149。
Length: = 6 octets
长度：=6个八位字节
Home LMA IPv4 address: 32-bit IPv4 address of the assigned LMA.
主LMA IPv4地址：分配的LMA的32位IPv4地址。
The PMIP6-Visited-LMA-IPv4-Address attribute (Type value 150) is of type IPv4 address and is used to propose a particular LMA in the visited network and to authorize the use of the LMA in the visited network.
PMIP6-visted-LMA-IPv4-Address属性（类型值150）是IPv4地址类型，用于在到访网络中提出特定LMA并授权在到访网络中使用LMA。
PMIP6-Visited-LMA-IPv4-Address attribute MAY be included by the MAG in the RADIUS Access-Request message. The LMA in the visited/local network may be assigned by the [VL]AAA as the result of retrieved policy profile. If included by the [VL]AAA in the RADIUS Access-Accept sent to the MAG, the use of the LMA in the visited/local network is authorized and the attribute SHALL carry the IPv4 address of the LMA assigned for the particular MN. See Section 4.2.5 of [RFC5447] how the MIP6-Feature-Vector attribute and LOCAL_HOME_AGENT_ASSIGNMENT capability flag is used with the LMA (Home Agent) assignment.
MAG可以在RADIUS访问请求消息中包括PMIP6-Visited-LMA-IPv4-Address属性。作为检索到的策略简档的结果，[VL]AAA可以分配到访/本地网络中的LMA。如果[VL]AAA在发送给MAG的RADIUS访问接受中包括LMA，则授权在访问/本地网络中使用LMA，并且该属性应携带分配给特定MN的LMA的IPv4地址。请参阅[RFC5447]第4.2.5节，了解MIP6特征向量属性和本地_HOME_AGENT_分配能力标志如何与LMA（归属代理）分配一起使用。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited LMA IPv4 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv4 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited LMA IPv4 address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited LMA IPv4 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-LMA-IPv4-Address 150.
类型：PMIP6-visted-LMA-IPv4-Address 150。
Length: = 6 octets
长度：=6个八位字节
IPv4 LMA address: 32-bit IPv4 address of the assigned LMA.
IPv4 LMA地址：分配的LMA的32位IPv4地址。
The PMIP6-Home-HN-Prefix attribute (Type value 151) is of type IPv6 prefix. It contains the Mobile Node - Home Network Prefix (MN-HNP), which is the IPv6 prefix assigned to the link between the MN and the MAG. The MN configures its IP interface from its home network prefix(es). When the LMA is located in the home network, the PMIP6- Home-HN-Prefix attribute is used to deliver the MN-HNP from the HAAA to the MAG.
PMIP6 Home HN Prefix属性（类型值151）的类型为IPv6 Prefix。它包含移动节点-家庭网络前缀（MN-HNP），这是分配给MN和MAG之间链路的IPv6前缀。MN根据其家庭网络前缀配置其IP接口。当LMA位于家庭网络中时，PMIP6-home HN Prefix属性用于将MN-HNP从HAAA传送到MAG。
The PMIP6-Home-HN-Prefix attribute is also used on the LMA-to-HAAA interface containing the prefix assigned to the MN. If the LMA delegates the MN-HNP assignment to the HAAA, the attribute MUST contain all zeroes in the address of (i.e., '::') the Access-Request message. The attribute MUST be present in the RADIUS Access-Accept message if the prior request already included one and SHOULD carry the MN-HNP the HAAA assigned to the MN.
PMIP6 Home HN Prefix属性也用于包含分配给MN的前缀的LMA到HAAA接口。如果LMA将MN-HNP分配委托给HAAA，则该属性必须在访问请求消息的地址（即“：”）中包含所有零。如果先前的请求已经包含一个属性，那么该属性必须出现在RADIUS访问接受消息中，并且应该携带分配给MN的MN-HNP和HAAA。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home MN-HNP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-HN-Prefix 151.
类型：PMIP6 Home HN前缀151。
Length: = at least 4 and no larger than 20.
长度：=至少4且不大于20。
Reserved: Reserved for future use. The bits MUST be set to zero by the sender and MUST be ignored by the receiver.
保留：保留供将来使用。发送方必须将位设置为零，接收方必须忽略位。
Prefix-Length: The 8-bit unsigned integer indicating the prefix length of the home network prefix (at least 0 and no larger than 128). If the home network prefix contains an address of all zeroes (i.e., '::'), then the Prefix-Length MUST be set to 128.
前缀长度：表示家庭网络前缀前缀长度的8位无符号整数（至少为0且不大于128）。如果家庭网络前缀包含全零地址（即“：：”），则前缀长度必须设置为128。
Home Network Prefix: The home network prefix for the MN's IPv6 address configuration. The Prefix field is up to 16 octets in length. Bits outside of the Prefix-Length, if included, must be zero.
家庭网络前缀：MN的IPv6地址配置的家庭网络前缀。前缀字段的长度最多为16个八位字节。前缀长度之外的位（如果包括）必须为零。
The PMIP6-Visited-HN-Prefix attribute (Type value 152) is of type IPv6 prefix. It contains the Mobile Node - Home Network Prefix (MN-HNP), which is the IPv6 prefix assigned to the link between the MN
PMIP6前缀属性（类型值152）的类型为IPv6前缀。它包含移动节点-家庭网络前缀（MN-HNP），这是分配给MN之间链路的IPv6前缀
and the MAG. The MN configures its IP interface from its home network prefix(es). When the LMA is located in the visited network, the PMIP6-Visited-HN-Prefix attribute is used to deliver the MN-HNP from the VAAA to the MAG.
MN根据其家庭网络前缀（es）配置其IP接口。当LMA位于到访网络中时，PMIP6到访HN前缀属性用于将MN-HNP从VAAA传送到MAG。
The PMIP6-Visited-HN-Prefix attribute is also used on the LMA-to-VAAA interface containing the IPv6 prefix assigned to the MN. If the LMA delegates the assignment of the MN-HNP to the VAAA, the attribute MUST contain an address of all zeroes (i.e., '::') in the RADIUS Access-Request message. The attribute MUST be present in Access-Accept message if the prior request already included one and SHOULD carry the MN-HNP the VAAA assigned to the MN.
在包含分配给MN的IPv6前缀的LMA到VAAA接口上，也使用PMIP6访问的HN前缀属性。如果LMA将MN-HNP的分配委托给VAAA，则该属性在RADIUS访问请求消息中必须包含一个全零地址（即“：”）。如果先前的请求已经包含一个属性，则该属性必须存在于Access Accept消息中，并且应该携带分配给MN的MN-HNP和VAAA。
The attribute SHOULD NOT be included if the use of LMA in the home network is authorized (the PMIP6-Home-HN-Prefix and/or PMIP6-Home-LMA-IPv6-Address attributes are already present). However, if the VAAA local policy allows both home and visited LMA addresses to be delivered to the MAG, then this attribute MAY also be included.
如果授权在家庭网络中使用LMA，则不应包括该属性（PMIP6 home HN前缀和/或PMIP6-home-LMA-IPv6-Address属性已经存在）。但是，如果VAAA本地策略允许将家庭和访问的LMA地址发送到MAG，则该属性也可以包括在内。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited MN-HNP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-HN-Prefix 152.
类型：PMIP6，前缀为152。
Length: = at least 4 and no larger than 20.
长度：=至少4且不大于20。
Reserved: Reserved for future use. The bits MUST be set to zero by the sender and MUST be ignored by the receiver.
保留：保留供将来使用。发送方必须将位设置为零，接收方必须忽略位。
Prefix-Length: The 8-bit unsigned integer indicating the prefix length of the Visited MN-HNP (at least 0 and no larger than 128). If the visited home network prefix contains an address of all zeroes (i.e., '::'), then the Prefix-Length MUST be set to 128.
前缀长度：表示访问的MN-HNP的前缀长度的8位无符号整数（至少为0且不大于128）。如果到访家庭网络前缀包含全零地址（即“：：”），则前缀长度必须设置为128。
Visited Home Network Prefix: The home network prefix for the MN's IPv6 address configuration. The Prefix field is up to 16 octets in length. Bits outside of the Prefix-Length, if included, must be zero.
到访家庭网络前缀：MN IPv6地址配置的家庭网络前缀。前缀字段的长度最多为16个八位字节。前缀长度之外的位（如果包括）必须为零。
The PMIP6-Home-Interface-ID attribute (Type value 153) is of type String and contains the MN's interface identifier. The selection of the interface identifier SHOULD NOT allow the tracking of individual MNs or users between PMIPv6 mobility sessions for privacy reasons. This attribute is applicable in network systems and link technologies, where the network explicitly delivers an interface identifier to the MN during the link setup. Third Generation Partnership Project (3GPP) and PPP link technologies are examples of such.
PMIP6主接口ID属性（类型值153）为字符串类型，包含MN的接口标识符。出于隐私原因，接口标识符的选择不应允许在PMIPv6移动会话之间跟踪单个MN或用户。此属性适用于网络系统和链路技术，其中网络在链路设置期间显式地向MN传递接口标识符。第三代合作伙伴关系项目（3GPP）和PPP链路技术就是这样的例子。
This attribute MAY be sent by the LMA or the MAG to the HAAA in the RADIUS Access-Request packet as a proposal. This attribute MAY be sent by the HAAA to the LMA or to the MAG in an Access-Accept packet; however, it MUST be present if the prior request already included one.
该属性可作为建议由LMA或MAG发送到RADIUS接入请求分组中的HAAA。该属性可由HAAA在接入接受分组中发送到LMA或MAG；但是，如果先前的请求中已经包含了一项，则必须提供该请求。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-Interface-ID 153.
类型：PMIP6主接口ID 153。
Length: = 10 octets.
长度：=10个八位字节。
Home Interface Identifier: The 64-bit long interface identifier (8 octets).
主接口标识符：64位长的接口标识符（8个八位字节）。
The PMIP6-Visited-Interface-ID attribute (Type value 154) is of type String and contains the MN's interface identifier. The selection of the interface identifier SHOULD NOT allow the tracking of individual MNs or users between PMIPv6 mobility session for privacy reasons.
PMIP6访问接口ID属性（类型值154）为字符串类型，包含MN的接口标识符。出于隐私原因，接口标识符的选择不应允许在PMIPv6移动会话之间跟踪单个MN或用户。
This attribute is applicable in network systems and link technologies, where the network explicitly delivers an interface identifier to the MN during the link setup. 3GPP and PPP link technologies are examples of such.
此属性适用于网络系统和链路技术，其中网络在链路设置期间显式地向MN传递接口标识符。3GPP和PPP链路技术就是这样的例子。
This attribute MAY be sent by the LMA or the MAG to the VAAA in the RADIUS Access-Request packet as a proposal. This attribute MAY be sent by the VAAA to the LMA or to the MAG in an Access-Accept packet; however, it MUST be present if the prior request already included one.
该属性可以由LMA或MAG作为建议发送到RADIUS接入请求分组中的VAAA。该属性可由VAAA在接入接受分组中发送到LMA或MAG；但是，如果先前的请求中已经包含了一项，则必须提供该请求。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited Interface Identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-Interface-ID 154.
类型：PMIP6访问接口ID 154。
Length: = 10 octets.
长度：=10个八位字节。
Visited Interface Identifier: The 64-bit long interface identifier (8 octets).
访问接口标识符：64位长的接口标识符（8个八位字节）。
[RFC5844] specifies extensions to Proxy Mobile IPv6 protocol that enable IPv4 home address mobility support to the MN. The PMIP6-Home-IPv4-HoA attribute (Type value 155) is of type Address and contains the IPv4 Home Address of the MN. The primary use of this attribute is to deliver the assigned IPv4-HoA from HAAA to the MAG.
[RFC5844]指定代理移动IPv6协议的扩展，该协议支持MN的IPv4家庭地址移动。PMIP6-Home-IPv4-HoA属性（类型值155）的类型为Address，包含MN的IPv4主地址。此属性的主要用途是将分配的IPv4 HoA从HAAA传递到MAG。
The PMIP6-Home-IPv4-HoA is also used on the LMA-to-HAAA interface. If the LMA in the home network delegates the assignment of the IPv4-HoA to the HAAA, the attribute MUST contain an address of all zeroes (i.e., 0.0.0.0) in the Access-Request message. The attribute MUST be included in by HAAA in the Access-Accept message if the previous request included it, and it contains the IPv4-HoA assigned to the MN.
PMIP6-Home-IPv4-HoA也用于LMA到HAAA接口。如果家庭网络中的LMA将IPv4 HoA的分配委托给HAAA，则该属性在访问请求消息中必须包含全零地址（即0.0.0.0）。如果上一个请求包含该属性，并且该属性包含分配给MN的IPv4 HoA，则该属性必须由HAAA包含在Access Accept消息中。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |Prefix-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home IPv4 HoA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |Prefix-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home IPv4 HoA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-IPv4-HoA 155.
类型：PMIP6-Home-IPv4-HoA 155。
Length: = 8 octets
长度：=8个八位字节
Reserved The 10-bit field reserved for future use. The value MUST be initialized to zero by sender and MUST be ignored by the receiver.
保留保留供将来使用的10位字段。发送方必须将该值初始化为零，接收方必须忽略该值。
Prefix-Len The 6-bit unsigned integer indicating the prefix length of the IPv4 HoA. If the Home IPv4 HoA contains an address of all zeroes (i.e., '0.0.0.0'), then the Prefix-Len MUST be set to 32.
Prefix Len表示IPv4 HoA前缀长度的6位无符号整数。如果主IPv4 HoA包含全零地址（即“0.0.0.0”），则前缀Len必须设置为32。
Home IPv4 HoA: This field is of type Address and contains the IPv4 home address of the MN in the home network.
家庭IPv4 HoA：此字段的类型为Address，包含家庭网络中MN的IPv4家庭地址。
When both the MAG and the LMA are in the visited network, the PMIP6- Visited-IPv4-HoA attribute (Type value 156) is of type Address and is used to exchange information between the VAAA and the MAG on the assignment of the IPv4 Home Address to the MN being present in the visited network.
当MAG和LMA都在访问的网络中时，PMIP6-访问的-IPv4-HoA属性（类型值156）的类型为Address，用于在VAAA和MAG之间交换关于将IPv4家庭地址分配给访问的网络中存在的MN的信息。
The PMIP6-Visited-IPv4-HoA is also used on the LMA-to-VAAA interface. If the LMA delegates the assignment of the IPv4-HoA to the VAAA, the attribute MUST contain an address of all zeroes (i.e., 0.0.0.0) in the RADIUS Access-Request message. The Access-Accept message MUST have the attribute present if the prior request to the VAAA already included one.
PMIP6-IPv4-HoA也用于LMA到VAAA接口。如果LMA将IPv4 HoA的分配委托给VAAA，则该属性在RADIUS访问请求消息中必须包含一个全零地址（即0.0.0.0）。如果先前对VAAA的请求已包含属性，则Access Accept消息必须具有该属性。
The attribute SHOULD NOT be included if the use of the LMA in the home network is authorized (the PMIP6-Home-IPv4-HoA and/or PMIP6- Home-LMA-IPv4-Address attributes are already present). However, if the VAAA local policy allows both home and visited LMA addresses to be delivered to the MAG, then this attribute MAY also be included.
如果授权在家庭网络中使用LMA，则不应包括该属性（PMIP6-home-IPv4-HoA和/或PMIP6-home-LMA-IPv4-Address属性已经存在）。但是，如果VAAA本地策略允许将家庭和访问的LMA地址发送到MAG，则该属性也可以包括在内。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |Prefix-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Visited IPv4 HoA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |Prefix-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Visited IPv4 HoA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-IPv4-HoA 156.
类型：PMIP6-IPv4-hoa156。
Length: = 8 octets
长度：=8个八位字节
Reserved: The 10-bit field reserved for future use. The value MUST be initialized to zero by the sender and MUST be ignored by the receiver.
保留：保留供将来使用的10位字段。发送方必须将该值初始化为零，接收方必须忽略该值。
Prefix-Len: 6-bit unsigned integer indicating the prefix length of the IPv4 HoA. If the Visited IPv4 HoA contains an address of all zeroes (i.e., '0.0.0.0'), then the Prefix-Len MUST be set to 32.
前缀Len:6位无符号整数，表示IPv4 HoA的前缀长度。如果访问的IPv4 HoA包含全零地址（即“0.0.0.0”），则前缀Len必须设置为32。
Visited IPv4 HoA: This field is of type Address and contains the IPv4 home address of the MN in the visited network.
已访问IPv4 HoA：此字段的类型为Address，包含已访问网络中MN的IPv4家庭地址。
The PMIP6-Home-DHCP4-Server-Address (Type value 157) is of type Address and contains the IPv4 address of the DHCPv4 server in the home network. The particular DHCP server address is indicated to the MAG that serves the concerning MN. The HAAA MAY assign a DHCP server to the MAG in deployments where the MAG acts as a DHCP Relay, as defined in [RFC5844].
PMIP6-Home-DHCP4-Server-Address（类型值157）属于Address类型，包含家庭网络中DHCPv4服务器的IPv4地址。特定的DHCP服务器地址指示给服务于相关MN的MAG。HAAA可以在MAG充当DHCP中继的部署中为MAG分配DHCP服务器，如[RFC5844]中所定义。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home DHCPv4 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv4 server 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home DHCPv4 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv4 server address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-DHCP4-Server-Address 157.
类型：PMIP6-Home-DHCP4-Server-Address 157。
Length: = 6 octets.
长度：=6个八位字节。
Home DHCPv4 server address: This field is of type Address and contains a 4-octet IPv4 address of the DHCP server.
主DHCPv4服务器地址：此字段的类型为address，包含DHCP服务器的4个八位IPv4地址。
The PMIP6-Visited-DHCP4-Server-Address attribute (Type value 158) is of type Address and delivers the IPv4 address of the DHCPv4 server from the visited network to the MAG. When both the MAG and the LMA are in the visited network, the VAAA MAY assign a DHCPv4 server to the MAG in deployments where the MAG acts as a DHCP Relay, as defined in [RFC5844].
PMIP6-VISISTED-DHCP4-Server-Address属性（类型值158）为Address类型，将DHCPv4服务器的IPv4地址从受访网络传送到MAG。当MAG和LMA都在受访网络中时，VAAA可以在MAG充当DHCP中继的部署中为MAG分配DHCPv4服务器，如中所定义[RFC5844]。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited DHCPv4 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv4 server 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited DHCPv4 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv4 server address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-DHCP4-Server-Address 158.
类型：PMIP6-visted-DHCP4-Server-Address 158。
Length: = 6 octets
长度：=6个八位字节
Visited DHCPv4 server address: This field is of type Address and contains a 4-octet IPv4 address of the DHCPv4 server.
已访问的DHCPv4服务器地址：此字段的类型为address，包含DHCPv4服务器的4字节IPv4地址。
The PMIP6-Home-DHCP6-Server-Address (Type value 159) is of type IPv6 address and contains the IPv6 address of the DHCPv6 server in the home network indicated by the HAAA to the MAG that serves the MN. The HAAA MAY assign a DHCPv6 server to the MAG in deployments where the MAG acts as a DHCP Relay, as defined in [RFC5213].
PMIP6-Home-DHCP6-Server-Address（类型值159）属于IPv6地址类型，并且包含由HAAA向为MN服务的MAG指示的家庭网络中DHCPv6服务器的IPv6地址。在MAG充当DHCP中继的部署中，HAAA可将DHCPv6服务器分配给MAG，如[RFC5213]中所定义。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Home DHCPv6 server address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-DHCP6-Server-Address 159.
类型：PMIP6-Home-DHCP6-Server-Address 159。
Length: = 18 octets
长度：=18个八位字节
Home DHCPv6 server address: This field is of type Address and contains 16-octet IPv6 address of the DHCPv6 server.
主DHCPv6服务器地址：此字段为address类型，包含DHCPv6服务器的16个八位IPv6地址。
The PMIP6-Visited-DHCP6-Server-Address attribute (Type value 160) is of type IPv6 address and contains the IPv6 address of the DHCPv6 server in the visited network indicated by the VAAA to the MAG that serves the MN. When both MAG and the LMA are located in the visited network, the VAAA MAY assign a DHCPv6 server to the MAG in deployments where the MAG acts as a DHCP Relay, as defined in [RFC5213].
PMIP6-VISTER-DHCP6-Server-Address属性（类型值160）为IPv6地址类型，包含VAAA向为MN服务的MAG指示的访问网络中DHCPv6服务器的IPv6地址。当MAG和LMA都位于访问的网络中时，VAAA可以在MAG充当DHCP中继的部署中为MAG分配DHCPv6服务器，如[RFC5213]中所定义。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Visited DHCPv6 server address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-DHCP6-Server-Address 160.
类型：PMIP6-visted-DHCP6-Server-Address 160。
Length: = 18 octets
长度：=18个八位字节
Visited DHCPv6 server address: This field is of type Address and contains the 16-octet IPv6 address of the DHCPv6 server.
已访问的DHCPv6服务器地址：此字段的类型为address，包含DHCPv6服务器的16个八位IPv6地址。
The Calling-Station-Id attribute (Type value 31) is of type String. When used within PMIPv6 deployments, the attribute contains the MN Link-Layer Identifier option of the MN as defined in [RFC5213], Sections 2.2 and 8.6.
呼叫站Id属性（类型值31）的类型为字符串。在PMIPv6部署中使用时，该属性包含[RFC5213]第2.2和8.6节中定义的MN的MN链路层标识符选项。
The Chargeable-User-Identity attribute, or CUI, (Type value 89) is a unique, temporary handle used as means to, for example, correlate authentication, accounting, and bill post-processing for a particular chargeable subscriber. The CUI format and use follows guidelines defined by [RFC4372].
计费用户标识属性或CUI（类型值89）是一个唯一的临时句柄，用作关联特定计费订户的身份验证、记帐和账单后处理的手段。CUI格式和使用遵循[RFC4372]定义的准则。
In the scope of this document, the CUI attribute MAY be present in the Access-Request. The CUI MAY also be present in the Access-Accept. The CUI MUST be present in the Access-Accept if it was present in the Access-Request. If the use of the Chargeable-User-Identity attribute is supported, then the MAG and/or the LMA commits to include the Chargeable-User-Identity attribute in all subsequent RADIUS Accounting packets they send for the given user.
在本文档的范围内，CUI属性可能存在于访问请求中。CUI也可能出现在Access Accept中。如果CUI存在于访问请求中，则它必须存在于访问接受中。如果支持使用计费用户标识属性，则MAG和/或LMA承诺将计费用户标识属性包括在其为给定用户发送的所有后续RADIUS计费数据包中。
[RFC5844] specifies extensions to Proxy Mobile IPv6 protocol that enable IPv4 home address mobility support to the MN. The PMIP6-Home-IPv4-Gateway attribute (Type value 161) is of type Address and contains the default gateway IPv4 address for the MN. This address is populated into the PMIPv6 IPv4 Default-Router Address Option [RFC5844]. The address MUST belong to the subnet defined in the PMIP6-Home-IPv4-HoA attribute.
[RFC5844]指定代理移动IPv6协议的扩展，该协议支持MN的IPv4家庭地址移动。PMIP6-Home-IPv4-Gateway属性（类型值161）的类型为Address，包含MN的默认网关IPv4地址。此地址填充到PMIPv6 IPv4默认路由器地址选项[RFC5844]中。地址必须属于PMIP6-Home-IPv4-HoA属性中定义的子网。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home IPv4 default gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Home IPv4 default gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Home-IPv4-Gateway 161.
类型：PMIP6-Home-IPv4-Gateway 161。
Length: = 6 octets
长度：=6个八位字节
Home IPv4 default gateway address: This field is of type Address and contains a 4-octet IPv4 default gateway address.
家庭IPv4默认网关地址：此字段的类型为address，包含4个八位组的IPv4默认网关地址。
[RFC5844] specifies extensions to Proxy Mobile IPv6 protocol that enable IPv4 home address mobility support to the MN. The PMIP6- Visited-IPv4-Gateway attribute (Type value 162) is of type Address and contains the default gateway IPv4 address for the MN. This address is populated into the PMIPv6 IPv4 Default-Router Address Option [RFC5844]. The address MUST belong to the subnet defined in the PMIP6-Visited-IPv4-HoA attribute.
[RFC5844]指定代理移动IPv6协议的扩展，该协议支持MN的IPv4家庭地址移动。PMIP6-visitored-IPv4-Gateway属性（类型值162）的类型为Address，包含MN的默认网关IPv4地址。此地址填充到PMIPv6 IPv4默认路由器地址选项[RFC5844]中。该地址必须属于PMIP6-VITED-IPv4-HoA属性中定义的子网。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited IPv4 default gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Visited IPv4 default gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: PMIP6-Visited-IPv4-Gateway 162.
类型：PMIP6-IPv4-Gateway 162。
Length: = 6 octets
长度：=6个八位字节
Visited IPv4 default gateway address: This field is of type Address and contains a 4-octet IPv4 default gateway address.
已访问IPv4默认网关地址：此字段的类型为address，包含4个八位组的IPv4默认网关地址。
The MAG to the AAA RADIUS server interface is used for retrieval of the policy profile when an MN tries to attach, authenticate, and authorize to a PMIPv6 domain. Depending on the policies and network capabilities, the MAG may retrieve different sets of PMIPv6-session-related parameters:
AAA RADIUS服务器接口的MAG用于在MN尝试连接、验证和授权到PMIPv6域时检索策略配置文件。根据策略和网络能力，MAG可以检索不同的PMIPv6会话相关参数集：
o Configuration attributes for home or visited network access scenario, depending on the location and attachment point of the MN,
o 家庭或访问网络访问场景的配置属性，取决于MN的位置和连接点，
o The IPv6 or IPv4 address of the designated LMA, depending on the access network's actual IP topology,
o 指定LMA的IPv6或IPv4地址，取决于接入网络的实际IP拓扑，
o The IPv6 or IPv4 configuration parameters for the MN, depending on the utilized IP configuration method and individual MN's service Policy,
o MN的IPv6或IPv4配置参数，取决于使用的IP配置方法和单个MN的服务策略，
o The DHCP Relay support attributes (IPv4 or IPv6) in case such functionality is supported in the network.
o DHCP中继支持属性（IPv4或IPv6），以防网络中支持此类功能。
In addition to PMIPv6-specific attributes, other RADIUS attributes are to be used on the MAG-to-AAA interface.
除PMIPv6特定属性外，MAG至AAA接口上还将使用其他RADIUS属性。
The User-Name attribute MUST be present in the Access-Request. It MUST carry a correctly formed identifier that SHOULD correspond to an MN identity unless the identity is being suppressed for policy reasons, for example, when identity hiding is in effect. The MN identity, if available, MUST be in Network Access Identifier (NAI) [RFC4282] format. At minimum, the home realm of the MN MUST be available at the MAG when the network access authentication takes place. Otherwise, the MAG is not able to route RADIUS request messages towards the correct HAAA. The MN identity used on the MAG-to-HAAA interface and in the User-Name attribute MAY entirely be related to the network access authentication and, therefore, not be suitable to be used as the MN-Identifier mobility option value in the subsequent PBU/PBA messages. In this case, the HAAA MUST provide the MN-Identifier for PBU/PBA messages using the Mobile-Node-Identifier attribute (see Section 4.2).
访问请求中必须存在用户名属性。它必须携带一个格式正确的标识符，该标识符应与MN标识相对应，除非该标识因策略原因而被抑制，例如，当标识隐藏生效时。MN标识（如果可用）必须采用网络访问标识符（NAI）[RFC4282]格式。至少，当网络访问认证发生时，MN的主域必须在MAG上可用。否则，MAG无法将RADIUS请求消息路由到正确的HAAA。在MAG到HAAA接口上和用户名属性中使用的MN标识可能完全与网络接入认证相关，因此，不适合在后续PBU/PBA消息中用作MN标识符移动选项值。在这种情况下，HAAA必须使用移动节点标识符属性为PBU/PBA消息提供MN标识符（参见第4.2节）。
At least one of the NAS-IP-Address, NAS-IPv6-Address, or NAS-Identifier attributes MUST be present in the Access-Request. The Service-Type attribute SHOULD be set to value 1 (Login) and the NAS-Port-Type attribute SHOULD be present in the Access-Request.
访问请求中必须至少存在一个NAS IP地址、NAS-IPv6-Address或NAS标识符属性。服务类型属性应设置为值1（登录），NAS端口类型属性应出现在访问请求中。
The following table provides a guide to attributes that may be found in authentication and authorization RADIUS messages between the MAG and the AAA server.
下表提供了在MAG和AAA服务器之间的身份验证和授权RADIUS消息中可以找到的属性指南。
Request Accept Reject Challenge # Attribute
请求接受拒绝质询#属性
1 0-1 0 0 1 User-Name 0-1 0 0 0 4 NAS-IP-Address 0-1 0-1 0 0 5 NAS-Port 0-1 0-1 0 0 6 Service-Type 0-1 0-1 0 0-1 24 State 0 0-1 0 0 25 Class 0 0-1 0 0-1 27 Session-Timeout 0-1 0 0 0 31 Calling-Station-Id 0-1 0 0 0 32 NAS-Identifier 0+ 0+ 0+ 0+ 33 Proxy-State 0-1 0 0 0 69 NAS-Port-Type 0+ 0+ 0+ 0+ 79 EAP-Message 1 1 1 1 80 Message-Authenticator 0-1 0-1 0 0 89 Chargeable-User-Identity 0-1 0 0 0 95 NAS-IPv6-Address 0-1 0-1 0 0 124 MIP6-Feature-Vector 0 1 0 0 145 Mobile-Node-Identifier 0-1 0-1 0 0 146 Service-Selection 0 0-1 0 0 147 PMIP6-Home-LMA-IPv6-Address 0-1 0-1 0 0 148 PMIP6-Visited-LMA-IPv6-Address 0 0-1 0 0 149 PMIP6-Home-LMA-IPv4-Address 0-1 0-1 0 0 150 PMIP6-Visited-LMA-IPv4-Address 0 0+ 0 0 151 PMIP6-Home-HN-Prefix 0 0+ 0 0 152 PMIP6-Visited-HN-Prefix 0 0-1 0 0 153 PMIP6-Home-Interface-ID 0 0-1 0 0 154 PMIP6-Visited-Interface-ID 0 0-1 0 0 155 PMIP6-Home-IPv4-HoA 0 0-1 0 0 156 PMIP6-Visited-IPv4-HoA 0 0-1 0 0 157 PMIP6-Home-DHCP4-Server-Address 0 0-1 0 0 158 PMIP6-Visited-DHCP4-Server-Address 0 0-1 0 0 159 PMIP6-Home-DHCP6-Server-Address 0 0-1 0 0 160 PMIP6-Visited-DHCP6-Server-Address 0 0-1 0 0 161 PMIP6-Home-IPv4-Gateway 0 0-1 0 0 162 PMIP6-Visited-IPv4-Gateway
1 0-1 0 0 0 1用户名0-1 0 0 0 0 4 NAS IP地址0-1 0-1 0 0 0 5 NAS端口0-1 0-1 0 0 6服务类型0-1 0-1 0-1 0-1 0-1 0-1 0 0 25类0 0-1 0 0-1 0 0-1 27会话超时0-1 0 0 0 0 31呼叫站Id 0-1 0 0 0 0 0 0 0 32 NAS标识符0+0+0 0+33代理状态0-1 0 0 0 0 0 0 0 0 69 NAS端口类型0+0+0+0+0 0 0 0 0+79 EAP消息1 180消息验证器0-10-1 0 0 89计费用户标识0-1 0 0 0 0 95 NAS-IPv6-Address 0-1 0-1 0 124 MIP6特征向量0 1 0 0 145移动节点标识符0-1 0-1 0 0 146服务选择0-1 0 147 PMIP6-Home-LMA-IPv6-Address 0-1 0-1 0 148 PMIP6-Visited-LMA-IPv6-Address 0-1 0 0-0 0 149 PMIP6-Home-LMA-IPv4-Address 0-1 0-1 0-1 0-150 PMIP6-Visited-LMA-IPv4-Address0 0+0 0 151 PMIP6 Home HN前缀0+0 0 152 PMIP6已访问HN前缀0-1 0 153 PMIP6 Home接口ID 0-1 0 154 PMIP6已访问接口ID 0-1 0 0 0 0 155 PMIP6-Home-IPv4-HoA 0-1 0 0 156 PMIP6-VISTED-IPv4-HoA 0 0-1 0 157 PMIP6-Home-DHCP4-Server-Address 0-1 0-0-0-0-0-0 158 PMIP6-VISTED-DHCP4-SER-Address 0-0-0-0-0PMIP6-Home-DHCP6-Server-Address 0-1 0 160 PMIP6-visted-DHCP6-Server-Address 0-1 0 161 PMIP6-Home-IPv4-Gateway 0-1 0 0 162 PMIP6-visted-IPv4-Gateway
The LMA-to-HAAA interface may be used for multiple purposes. These include the authorization of the incoming PBU, updating the LMA address to the HAAA, delegating the assignment of the MN-HNP or the IPv4-HoA to the HAAA, and accounting and PMIPv6 session management. The primary purpose of this interface is to update the HAAA with the
LMA到HAAA接口可用于多种用途。这些包括对传入PBU的授权、将LMA地址更新到HAAA、将MN-HNP或IPv4 HoA的分配委托给HAAA以及记帐和PMIPv6会话管理。此接口的主要目的是使用
LMA address information in case of dynamically assigned LMA and to exchange the MN address assignment information between the LMA and the HAAA.
在动态分配LMA的情况下，LMA地址信息以及在LMA和HAAA之间交换MN地址分配信息。
Whenever the LMA sends an Access-Request message to the HAAA, the User-Name attribute SHOULD contain the MN's identity. The LMA-provided identity in the User-Name attribute is strongly RECOMMENDED to be the same as the MN's identity information in the PBU MN-Identifier mobility option. The identity SHOULD also be the same as used on the MAG-to-HAAA interface; however, in case those identities differ, the HAAA MUST have a mechanism of mapping the MN identity used on the MAG-to-HAAA interface to the identity used on the LMA-to-HAAA interface.
每当LMA向HAAA发送访问请求消息时，用户名属性应包含MN的标识。强烈建议用户名属性中LMA提供的标识与PBU MN标识符移动选项中MN的标识信息相同。标识还应与MAG至HAAA接口上使用的标识相同；然而，如果这些身份不同，HAAA必须具有将MAG到HAAA接口上使用的MN身份映射到LMA到HAAA接口上使用的身份的机制。
If the PBU contains the MN Link-Layer Identifier option, the Calling-Station-Id attribute SHOULD be included in the request message containing the received MN Link-Layer Identifier option. Furthermore, if the PBU contains the Service Selection mobility option [RFC5149], the Service-Selection attribute SHOULD be included in the request message containing the received service identifier. Both the MN Link-Layer Identifier option and the service selection can be used to provide more information for the PBU authorization step in the HAAA.
如果PBU包含MN链路层标识符选项，则包含接收到的MN链路层标识符选项的请求消息中应包含呼叫站Id属性。此外，如果PBU包含服务选择移动性选项[RFC5149]，则服务选择属性应包含在包含所接收服务标识符的请求消息中。MN链路层标识符选项和服务选择都可用于为HAAA中的PBU授权步骤提供更多信息。
The Service-Type attribute MUST be set to the value 17 (Authorize Only). If the HAAA is not able to authorize the subscriber's mobility service session, then the Access-Reject message to the LMA MAY contain the Reply-Message attribute describing the reason for rejecting the authorization. A failed authorization obviously results in a rejection of the PBU, and a PBA with an appropriate error Status Value MUST be sent back to the MAG.
服务类型属性必须设置为值17（仅授权）。如果HAAA不能授权订户的移动服务会话，则对LMA的访问拒绝消息可以包含描述拒绝授权的原因的应答消息属性。授权失败显然会导致PBU被拒绝，具有适当错误状态值的PBA必须发送回MAG。
The authorization step MUST be performed at least for the initial PBU session up to a mobility session, when the LMA-to-HAAA interface is deployed. For the subsequent re-registration and handover of PBUs, the authorization step MAY be repeated (in this case, the LMA-to-HAAA interface should also maintain an authorization session state).
当部署LMA到HAAA接口时，必须至少对初始PBU会话到移动会话执行授权步骤。对于随后的pbu的重新注册和切换，可以重复授权步骤（在这种情况下，LMA到HAAA接口也应该保持授权会话状态）。
In case of a dynamic LMA discovery and assignment [RFC6097], the HAAA and the remote policy store may need to be updated with the selected LMA address information. The update can be done during the PBU authorization step using the LMA-to-HAAA interface. This specification uses the PMIP6-*-LMA-*-Address attribute for carrying the LMA's address information from the LMA to the HAAA. The LMA address information in the request message MUST contain the IP address of the LMA, the Fully Qualified Domain Name (FQDN) uniquely
在动态LMA发现和分配[RFC6097]的情况下，可能需要使用所选LMA地址信息更新HAAA和远程策略存储。可以在PBU授权步骤中使用LMA到HAAA接口进行更新。本规范使用PMIP6-*-LMA-*-Address属性将LMA的地址信息从LMA传送到HAAA。请求消息中的LMA地址信息必须包含LMA的IP地址，即唯一的完全限定域名（FQDN）
identifying the LMA, or both. The LMA address information refers to the PMIPv6 part of the LMA, not necessarily the LMA part interfacing with the AAA infrastructure.
识别LMA，或两者兼而有之。LMA地址信息指LMA的PMIPv6部分，不一定指与AAA基础设施接口的LMA部分。
The LMA and the HAAA use the PMIP6-Home-HN-Prefix/ PMIP6-Visited-HN-Prefix attributes to exchange the MN-HNP when appropriate. Similarly, the LMA and the HAAA use the PMIP6-Home-IPv4-HoA/PMIP6-Visited-IPv4-HoA attributes to exchange the IPv4-MN-HoA when appropriate. The MN address information exchange is again done during the PBU authorization step. The HAAA MAY also use the LMA-provided MN address information as a part of the information used to authorize the PBU.
LMA和HAAA在适当时使用PMIP6 Home HN前缀/PMIP6 VISTER HN前缀属性来交换MN-HNP。类似地，LMA和HAAA在适当时使用PMIP6-Home-IPv4-HoA/PMIP6-visted-IPv4-HoA属性来交换IPv4-MN-HoA。MN地址信息交换在PBU授权步骤中再次完成。HAAA还可以使用LMA提供的MN地址信息作为用于授权PBU的信息的一部分。
Which entity is actually responsible for the address management is deployment specific within the PMIPv6 Domain and MUST be pre-agreed on per deployment basis. When the LMA is responsible for the address management, the PMIP6-*-HN-Prefix/PMIP6-*-IPv4-HoA attributes are used to inform the HAAA and the remote policy store of the MN-HNP/ IPv4-MN-HoA assigned to the MN. It is also possible that the LMA delegates the address management to the HAAA. In this case, the MN-HNP/IPv4-MN-HoA are set to undefined addresses in the Access-Request message sent from the LMA to the HAAA. The LMA expects to receive the HAAA assigned HNP/IPv4-MN-HoA in the corresponding Access-Accept message.
哪个实体实际负责地址管理是PMIPv6域中特定于部署的，并且必须根据每个部署预先商定。当LMA负责地址管理时，PMIP6-*-HN前缀/PMIP6-*-IPv4 HoA属性用于通知HAAA和远程策略存储分配给MN的MN-HNP/IPv4 MN HoA。LMA也可能将地址管理委托给HAAA。在这种情况下，在从LMA发送到HAAA的访问请求消息中，MN-HNP/IPv4 MN-HoA被设置为未定义的地址。LMA期望在相应的访问接受消息中接收HAAA分配的HNP/IPv4 MN HoA。
The following table provides a guide to which attributes may be found in authorization process between LMA and the AAA.
下表提供了在LMA和AAA之间的授权过程中可以找到哪些属性的指南。
Request Accept Reject Challenge # Attribute
请求接受拒绝质询#属性
1 0-1 0 0 1 User-Name 0-1 0-1 0 0 4 NAS-IP-Address 0-1 0-1 0 0 5 NAS-Port 1 0-1 0 0 6 Service-Type 0 0-1 0 0 25 Class 0 0-1 0 0-1 27 Session-Timeout 0-1 0 0 0 31 Calling-Station-Id 1 0 0 0 32 NAS-Identifier 0+ 0+ 0+ 0+ 33 Proxy-State 1 0 0 0 69 NAS-Port-Type 1 1 1 1 80 Message-Authenticator 0-1 0-1 0 0 89 Chargeable-User-Identity 0-1 0-1 0 0 95 NAS-IPv6-Address 0-1 0-1 0 0 124 MIP6-Feature-Vector 1 0 0 0 145 Mobile-Node-Identifier 0-1 0-1 0 0 146 Service-Selection 0-1 0 0 0 147 PMIP6-Home-LMA-IPv6-Address 0-1 0 0 0 148 PMIP6-Visited-LMA-IPv6-Address 0-1 0 0 0 149 PMIP6-Home-LMA-IPv4-Address 0-1 0 0 0 150 PMIP6-Visited-LMA-IPv4-Address 0+ 0+ 0 0 151 PMIP6-Home-HN-Prefix 0+ 0+ 0 0 152 PMIP6-Visited-HN-Prefix 0-1 0-1 0 0 153 PMIP6-Home-Interface-ID 0-1 0-1 0 0 154 PMIP6-Visited-Interface-ID 0-1 0-1 0 0 155 PMIP6-Home-IPv4-HoA 0-1 0-1 0 0 156 PMIP6-Visited-IPv4-HoA 0-1 0-1 0 0 161 PMIP6-Home-IPv4-Gateway 0-1 0-1 0 0 162 PMIP6-Visited-IPv4-Gateway
1 0-1 0 0 1用户名0-1 0-1 0 0 4 NAS IP地址0-1 0-1 0 0 0 5 NAS端口1 0-1 0 0 6服务类型0-1 0 0 0 25类0 0-1 0 0 0-1 27会话超时0-1 0 0 0 0 0 31呼叫站Id 1 0 0 0 32 NAS标识符0+0+0+0+33代理状态1 0 0 0 0 69 NAS端口类型1 1 1 1 1 80消息验证器0-1 0 0-1 0 89计费用户标识0-1 0 0 0 95NAS-IPv6-Address 0-1 0-1 0 124 MIP6特征向量1 0 0 0 0 145移动节点标识符0-1 0-1 0 0 146服务选择0-1 0 0 147 PMIP6-Home-LMA-IPv6-Address 0-1 0 0 148 PMIP6-Visited-LMA-IPv6-Address 0-1 0 0 149 PMIP6-Home-LMA-IPv4-Address 0-1 0 0 0 0 0 150 PMIP6-Visited-LMA-IPv4-Address 0+0 0 0 0+0 0 0 151 PMIP6-Home HN前缀0+0+0PMIP6访问过的HN前缀0-10-1 0 0 153 PMIP6家庭接口ID 0-1 0-1 0 154 PMIP6访问过的接口ID 0-1 0-1 0 0 155 PMIP6-Home-IPv4-HoA 0-1 0-1 0 0 0 156 PMIP6-VISTED-IPv4-HoA 0-1 0-1 0-1 0 161 PMIP6-Home-IPv4-Gateway 0-1 0-1 0-1 0 0 0-0 162 PMIP6-VISTED-IPv4-Gateway
Radius-based interfaces at the MAG and LMA with the AAA server enables the metering of traffic associated with the MN, commonly called "accounting". If accounting is turned on in the mobile node's policy profile, the local routing SHOULD NOT be enabled [RFC5213].
MAG和LMA与AAA服务器之间基于Radius的接口能够计量与MN相关的流量，通常称为“计费”。如果在移动节点的策略配置文件中启用了记帐，则不应启用本地路由[RFC5213]。
The accounting at the LMA to AAA server interface is based on [RFC2865] and [RFC2866]. This interface MUST support the transfer of accounting records needed for service control and charging. These records should include (but may not be limited to) the following: time of binding cache entry creation and deletion, number of the octets sent and received by the MN over the bi-directional tunnel, etc.
LMA到AAA服务器接口的记帐基于[RFC2865]和[RFC2866]。此接口必须支持传输服务控制和收费所需的会计记录。这些记录应包括（但不限于）以下内容：绑定缓存项创建和删除的时间、MN通过双向隧道发送和接收的八位字节数等。
The accounting at the MAG to AAA server interface is based on [RFC2865] and [RFC2866]. The interface MUST also support the transfer of accounting records that should include the following: time of binding cache entry creation and deletion, number of the octets sent and received by the MN over the bi-directional tunnel, etc.
MAG到AAA服务器接口的记帐基于[RFC2865]和[RFC2866]。接口还必须支持会计记录的传输，该记录应包括以下内容：绑定缓存项创建和删除的时间、MN通过双向隧道发送和接收的八位字节数等。
If there is data traffic between a visiting MN and a correspondent node that is locally attached to an access link connected to the same MAG, the mobile access gateway MAY optimize on the delivery efforts by locally routing the packets instead of using reverse tunneling to the mobile node's LMA. In this case, the local data traffic too MUST be reported to AAA Accounting servers by means of RADIUS protocol.
如果在访问MN和本地连接到连接到同一MAG的接入链路的对应节点之间存在数据业务，则移动接入网关可以通过本地路由分组而不是使用到移动节点的LMA的反向隧道来优化递送努力。在这种情况下，本地数据流量也必须通过RADIUS协议报告给AAA计费服务器。
The following table provides a list of attributes that may be included in the RADIUS Accounting messages. These attributes are to complement the set of accounting attributes already required by [RFC2866] and [RFC2869].
下表提供了RADIUS记帐消息中可能包含的属性列表。这些属性是对[RFC2866]和[RFC2869]已经要求的会计属性集的补充。
Accounting Request # Attribute
会计请求#属性
0-1 145 Mobile-Node-Identifier 0-1 146 Service-Selection 0-1 147 PMIP6-Home-LMA-IPv6-Address 0-1 148 PMIP6-Visited-LMA-IPv6-Address 0-1 149 PMIP6-Home-LMA-IPv4-Address 0-1 150 PMIP6-Visited-LMA-IPv4-Address 0+ 151 PMIP6-Home-HN-Prefix 0+ 152 PMIP6-Visited-HN-Prefix 0-1 155 PMIP6-Home-IPv4-HoA 0-1 156 PMIP6-Visited-IPv4-HoA 0-1 31 Calling-Station-Id 0-1 80 Message-Authenticator 0-1 89 Chargeable-User-Identity 0-1 124 MIP6-Feature-Vector
0-1 145移动节点标识符0-1 146服务选择0-1 147 PMIP6-Home-LMA-IPv6-Address 0-1 148 PMIP6-visted-LMA-IPv6-Address 0-1 149 PMIP6-Home-LMA-IPv4-Address 0-1 150 PMIP6-visted-LMA-IPv4-Address 0+151 PMIP6-Home-HN前缀0+152 PMIP6-visted-HN前缀0-1 155 PMIP6-Home-IPv4-HoA-0-1 156 PMIP6-visted-IPv4-HoA-0-1 31呼叫站Id 0-1 80消息验证器0-1 89计费用户标识0-1 124 MIP6特征向量
The RADIUS messages may be transported between the MAG and/or the LMA to the RADIUS server via one or more AAA brokers or RADIUS proxies. In this case, the communication between the LMA and the RADIUS AAA server relies on the security properties of the intermediate AAA brokers and RADIUS proxies.
RADIUS消息可以通过一个或多个AAA代理或RADIUS代理在MAG和/或LMA之间传输到RADIUS服务器。在这种情况下，LMA和RADIUS AAA服务器之间的通信依赖于中间AAA代理和RADIUS代理的安全属性。
Regarding the privacy threats associated with sending MN-specific information between the MAG and AAA server and between the LMA and AAA server, considerations of the RADIUS Base protocol [RFC2865], RADIUS Accounting [RFC2866], and the RADIUS EAP application [RFC3579] are applicable to this document. The MAG, LMA, and AAA server SHOULD avoid including attributes containing personally identifying information such as a MN's Interface ID, link-layer address, or NAI, except as needed and SHOULD pay special attention if identity hiding is desired.
关于与在MAG和AAA服务器之间以及LMA和AAA服务器之间发送MN特定信息相关的隐私威胁，RADIUS基本协议[RFC2865]、RADIUS记帐[RFC2866]和RADIUS EAP应用程序[RFC3579]的注意事项适用于本文档。MAG、LMA和AAA服务器应避免包括包含个人识别信息的属性，如MN的接口ID、链路层地址或NAI，除非需要，并且如果需要身份隐藏，应特别注意。
This specification defines the following new RADIUS attribute type values:
本规范定义了以下新的半径属性类型值：
Mobile-Node-Identifier 145 Service-Selection 146 PMIP6-Home-LMA-IPv6-Address 147 PMIP6-Visited-LMA-IPv6-Address 148 PMIP6-Home-LMA-IPv4-Address 149 PMIP6-Visited-LMA-IPv4-Address 150 PMIP6-Home-HN-Prefix 151 PMIP6-Visited-HN-Prefix 152 PMIP6-Home-Interface-ID 153 PMIP6-Visited-Interface-ID 154 PMIP6-Home-IPv4-HoA 155 PMIP6-Visited-IPv4-HoA 156 PMIP6-Home-DHCP4-Server-Address 157 PMIP6-Visited-DHCP4-Server-Address 158 PMIP6-Home-DHCP6-Server-Address 159 PMIP6-Visited-DHCP6-Server-Address 160 PMIP6-Home-IPv4-Gateway 161 PMIP6-Visited-IPv4-Gateway 162
移动节点标识符145服务选择146 PMIP6-Home-LMA-IPv6-Address 147 PMIP6-visted-LMA-IPv6-Address 148 PMIP6-Home-LMA-IPv4-Address 149 PMIP6-visted-LMA-IPv4-Address 150 PMIP6-Home-HN前缀151 PMIP6-visted-HN前缀152 PMIP6-Home接口ID 153 PMIP6-visted接口ID 154 PMIP6-Home-IPv4-HoA 155 PMIP6-visted-ip6-IPv4-HoA 156PMIP6-Home-DHCP4-Server-Address 157 PMIP6-visted-DHCP4-Server-Address 158 PMIP6-Home-DHCP6-Server-Address 159 PMIP6-visted-DHCP6-Server-Address 160 PMIP6-Home-IPv4-Gateway 161 PMIP6-visted-IPv4-Gateway 162
This specification defines new values to the Mobility Capability registry (see [RFC5447]) for use with the MIP6-Feature-Vector AVP:
本规范定义了移动能力注册表的新值（参见[RFC5447]），用于MIP6特征向量AVP：
Token | Value
----------------------------------+--------------------
IP4_TRANSPORT_SUPPORTED | 0x0000800000000000
IP4_HOA_ONLY_SUPPORTED | 0x0001000000000000
Token | Value
----------------------------------+--------------------
IP4_TRANSPORT_SUPPORTED | 0x0000800000000000
IP4_HOA_ONLY_SUPPORTED | 0x0001000000000000
First of all, the authors would like to acknowledge the standardization work and people of the WiMAX Forum that have set the foundation for this document.
首先，作者想承认WiMAX论坛的标准化工作和人员，为这个文件奠定了基础。
The authors would like to thank Basavaraj Patil, Glen Zorn, Avi Lior, Alan DeKok, Dhananjay Patki and Pete McCann for reviewing the document and providing valuable input. The authors also thank Elwyn Davies, Pete Resnick, Bernard Aboba, Jari Arkko, and Stephen Farrell for their reviews on the document during the IESG process.
作者感谢Basavaraj Patil、Glen Zorn、Avi Lior、Alan DeKok、Dhananjay Patki和Pete McCann审阅了该文件并提供了宝贵的意见。作者还感谢Elwyn Davies、Pete Resnick、Bernard Aboba、Jari Arkko和Stephen Farrell在IESG过程中对该文件的审查。
The authors would also like to thank the authors of [RFC5779] as this document reuses some procedural ideas of that specification.
作者还想感谢[RFC5779]的作者，因为本文档重用了该规范的一些程序思想。
[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月。
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5213]Gundavelli，S.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，2008年8月。
[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月。
[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月。
[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月。
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, May 2010.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，2010年5月。
[RFC5779] Korhonen, J., Bournelle, J., Chowdhury, K., Muhanna, A., and U. Meyer, "Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server", RFC 5779, February 2010.
[RFC5779]Korhonen，J.，Bournelle，J.，Chowdhury，K.，Muhanna，A.，和U.Meyer，“Diameter代理移动IPv6：移动接入网关和本地移动锚与Diameter服务器的交互”，RFC 5779，2010年2月。
[RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, "Chargeable User Identity", RFC 4372, January 2006.
[RFC4372]Adrangi，F.，Lior，A.，Korhonen，J.，和J.Loughney，“收费用户身份”，RFC 4372，2006年1月。
[RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)", RFC 3579, September 2003.
[RFC3579]Aboba，B.和P.Calhoun，“RADIUS（远程认证拨入用户服务）对可扩展认证协议（EAP）的支持”，RFC 3579，2003年9月。
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
[RFC2866]Rigney，C.，“半径会计”，RFC 28662000年6月。
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS Extensions", RFC 2869, June 2000.
[RFC2869]Rigney，C.，Willats，W.，和P.Calhoun，“半径延伸”，RFC 2869，2000年6月。
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 3748, June 2004.
[RFC3748]Aboba，B.，Blunk，L.，Vollbrecht，J.，Carlson，J.，和H.Levkowetz，“可扩展身份验证协议（EAP）”，RFC 3748，2004年6月。
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service Selection for Mobile IPv6", RFC 5149, February 2008.
[RFC5149]Korhonen，J.，Nilsson，U.，和V.Devarapalli，“移动IPv6的服务选择”，RFC 5149，2008年2月。
[RFC6097] Korhonen, J. and V. Devarapalli, "Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6", RFC 6097, February 2011.
[RFC6097]Korhonen，J.和V.Devarapalli，“代理移动IPv6的本地移动锚（LMA）发现”，RFC 60972011年2月。
[UNF] Davis, M., Ed. and K. Whistler, Ed., "Unicode Standard Annex #15: Unicode Normalization Forms", January 2012, <http://www.unicode.org/reports/tr15/>.
[UNF]Davis，M.，Ed.和K.Whistler，Ed.，“Unicode标准附录#15：Unicode规范化格式”，2012年1月<http://www.unicode.org/reports/tr15/>.
Authors' Addresses
作者地址
Frank Xia Huawei USA 1700 Alma Dr., Suite 500 Plano, TX 75075
Frank Xia华为美国1700阿尔玛博士，德克萨斯州普莱诺500室75075
Phone: +1 972-509-5599
EMail: xiayangsong@huawei.com
Phone: +1 972-509-5599
EMail: xiayangsong@huawei.com
Behcet Sarikaya Huawei USA 1700 Alma Dr., Suite 500 Plano, TX 75075
Behcet Sarikaya Huawei USA 1700 Alma Dr.，德克萨斯州普莱诺500号套房75075
Phone: +1 972-509-5599
EMail: sarikaya@ieee.org
Phone: +1 972-509-5599
EMail: sarikaya@ieee.org
Jouni Korhonen (editor) Nokia Siemens Networks Linnoitustie 6 Espoo FI-02600 Finland
Jouni Korhonen（编辑）诺基亚西门子网络公司Linnoitustie 6 Espoo FI-02600芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134
斯里·冈达维利思科170西塔斯曼大道圣何塞，加利福尼亚州95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Damjan Damic Siemens Heinzelova 70a Zagreb 10000 Croatia
达姆扬达米奇西门子海因泽洛娃70a萨格勒布10000克罗地亚
EMail: damjan.damic@siemens.com
EMail: damjan.damic@siemens.com