Internet Engineering Task Force (IETF) X. Zhou
Request for Comments: 7148 ZTE Corporation
Category: Standards Track J. Korhonen
ISSN: 2070-1721 Broadcom
C. Williams
Consultant
S. Gundavelli
Cisco
CJ. Bernardos
UC3M
March 2014
Internet Engineering Task Force (IETF) X. Zhou
Request for Comments: 7148 ZTE Corporation
Category: Standards Track J. Korhonen
ISSN: 2070-1721 Broadcom
C. Williams
Consultant
S. Gundavelli
Cisco
CJ. Bernardos
UC3M
March 2014
Prefix Delegation Support for Proxy Mobile IPv6
代理移动IPv6的前缀委派支持
Abstract
摘要
This specification defines extensions to the Proxy Mobile IPv6 protocol for allowing a mobile router in a Proxy Mobile IPv6 domain to obtain IP prefixes for its attached mobile networks using DHCPv6 prefix delegation. Network-based mobility management support is provided for those delegated IP prefixes just as it is provided for the mobile node's home address. Even if the mobile router performs a handoff and changes its network point of attachment, mobility support is ensured for all the delegated IP prefixes and for all the IP nodes in the mobile network that use IP address configuration from those delegated IP prefixes.
本规范定义了代理移动IPv6协议的扩展，以允许代理移动IPv6域中的移动路由器使用DHCPv6前缀委派为其连接的移动网络获取IP前缀。基于网络的移动性管理支持是为那些委派的IP前缀提供的，就像它是为移动节点的家庭地址提供的一样。即使移动路由器执行切换并更改其网络连接点，移动网络中的所有委派IP前缀以及使用这些委派IP前缀的IP地址配置的所有IP节点的移动性支持也会得到保证。
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/rfc7148.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7148.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 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 .....................................................6
3. Solution Overview ...............................................7
3.1. Stated Assumptions .........................................7
3.2. Deployment Models ..........................................8
3.2.1. Delegating Router Co-located with Mobile
Access Gateway ......................................8
3.2.2. Delegating Router Co-located with Local
Mobility Anchor .....................................9
3.2.3. Static Configuration of Delegated Mobile
Network Prefixes ...................................12
4. Message Formats ................................................12
4.1. Delegated Mobile Network Prefix Option ....................12
4.2. Status Codes ..............................................14
5. Operational Details ............................................14
5.1. MAG Considerations ........................................14
5.1.1. Extension to Binding Update List Entry Data
Structure ..........................................14
5.1.2. Signaling Considerations ...........................14
5.1.3. DHCP -- MAG Interactions ...........................16
5.1.3.1. Delegating Router Co-located with
Mobile Access Gateway .....................17
5.1.3.2. Delegating Router Co-Located with
Local Mobility Anchor .....................18
5.1.4. Packet Forwarding ..................................19
5.2. LMA Considerations ........................................20
5.2.1. Extensions to Binding Cache Entry Data Structure ...20
5.2.2. Signaling Considerations ...........................20
5.2.3. Packet Forwarding ..................................22
5.3. Security Policy Database (SPD) Example Entries ............22
6. Security Considerations ........................................23
7. IANA Considerations ............................................24
8. Acknowledgements ...............................................24
9. References .....................................................25
9.1. Normative References ......................................25
9.2. Informative References ....................................26
1. Introduction ....................................................4
2. Terminology .....................................................6
3. Solution Overview ...............................................7
3.1. Stated Assumptions .........................................7
3.2. Deployment Models ..........................................8
3.2.1. Delegating Router Co-located with Mobile
Access Gateway ......................................8
3.2.2. Delegating Router Co-located with Local
Mobility Anchor .....................................9
3.2.3. Static Configuration of Delegated Mobile
Network Prefixes ...................................12
4. Message Formats ................................................12
4.1. Delegated Mobile Network Prefix Option ....................12
4.2. Status Codes ..............................................14
5. Operational Details ............................................14
5.1. MAG Considerations ........................................14
5.1.1. Extension to Binding Update List Entry Data
Structure ..........................................14
5.1.2. Signaling Considerations ...........................14
5.1.3. DHCP -- MAG Interactions ...........................16
5.1.3.1. Delegating Router Co-located with
Mobile Access Gateway .....................17
5.1.3.2. Delegating Router Co-Located with
Local Mobility Anchor .....................18
5.1.4. Packet Forwarding ..................................19
5.2. LMA Considerations ........................................20
5.2.1. Extensions to Binding Cache Entry Data Structure ...20
5.2.2. Signaling Considerations ...........................20
5.2.3. Packet Forwarding ..................................22
5.3. Security Policy Database (SPD) Example Entries ............22
6. Security Considerations ........................................23
7. IANA Considerations ............................................24
8. Acknowledgements ...............................................24
9. References .....................................................25
9.1. Normative References ......................................25
9.2. Informative References ....................................26
Proxy Mobile IPv6 [RFC5213] enables network-based mobility management support for an IP host without requiring its participation in any IP mobility signaling. In Proxy Mobile IPv6 (PMIPv6), the mobile access gateway (MAG) performs the mobility management function on behalf of the mobile node (MN). The local mobility anchor (LMA) is the home agent for the MN and the topological anchor point. The mobility elements (LMA and MAGs) in the network allow an IP host to obtain an IPv4 address and/or a set of IPv6 addresses and be able to obtain IP mobility support for those IP address(es) within the Proxy Mobile IPv6 domain. In this context, the mobility management support is enabled for an individual IP host, which is the mobile node. The IPv4 home address or the IPv6 home network prefixes are logically bound to the link shared between the mobile access gateway and the mobile node, and only the mobile node can use those IP address(es) by configuring them on the interface attached to that link. Currently, there is no mobility support for the mobile networks attached to a mobile router (MR) in a Proxy Mobile IPv6 domain.
代理移动IPv6[RFC5213]为IP主机提供基于网络的移动性管理支持，而无需参与任何IP移动性信令。在代理移动IPv6（PMIPv6）中，移动接入网关（MAG）代表移动节点（MN）执行移动性管理功能。局部移动锚（LMA）是MN和拓扑锚点的归属代理。网络中的移动元件（LMA和mag）允许IP主机获得IPv4地址和/或一组IPv6地址，并且能够在代理移动IPv6域内获得这些IP地址的IP移动支持。在该上下文中，为作为移动节点的单个IP主机启用移动性管理支持。IPv4家庭地址或IPv6家庭网络前缀在逻辑上绑定到移动接入网关和移动节点之间共享的链路，并且只有移动节点可以通过在连接到该链路的接口上配置这些IP地址来使用这些IP地址。目前，在代理移动IPv6域中，没有对连接到移动路由器（MR）的移动网络的移动支持。
This specification defines extensions to the Proxy Mobile IPv6 protocol for allowing mobility support to the mobile networks attached to a mobile router. These extension include definition of a new mobility option that can be exchanged in the signaling messages between the mobile access gateway and the local mobility anchor. The mobile router can request the mobility entities in the Proxy Mobile IPv6 domain for delegated IP prefix(es) using DHCP prefix delegation extensions [RFC3633], static configuration of the prefixes, or mechanisms specific to the access technology. The mobility entities in the PMIPv6 network provide network-based mobility management support for those delegated prefixes just as it is supported for a home address. The delegated prefixes are hosted in the mobile network attached to the mobile router. IP mobility is ensured for all the IP nodes in the mobile network, even as the mobile router performs a handoff by changing its point of network attachment within the Proxy Mobile IPv6 domain. The local mobility anchor in the Proxy Mobile IPv6 domain will not track the individual IP nodes in the mobile network; it only tracks a single mobile router session that is hosting the mobile network and associates the delegated IP prefixes with that session. Although the protocol solution defined in this specification also allows signaling IPv4 subnets between the mobile access gateway and the local mobility anchor, the delegation of IPv4 subnets to the mobile router is out of the scope of this specification.
本规范定义了代理移动IPv6协议的扩展，以支持连接到移动路由器的移动网络的移动性。这些扩展包括可在移动接入网关和本地移动锚之间的信令消息中交换的新移动选项的定义。移动路由器可以使用DHCP前缀委派扩展[RFC3633]、前缀的静态配置或特定于接入技术的机制，请求代理移动IPv6域中的移动实体委派IP前缀。PMIPv6网络中的移动性实体为这些委派前缀提供基于网络的移动性管理支持，就像支持家庭地址一样。委托前缀托管在连接到移动路由器的移动网络中。即使移动路由器通过改变其在代理移动IPv6域内的网络连接点来执行切换，移动网络中的所有IP节点的IP移动性也得到了保证。代理移动IPv6域中的本地移动锚不会跟踪移动网络中的单个IP节点；它只跟踪承载移动网络的单个移动路由器会话，并将委派的IP前缀与该会话关联。尽管本规范中定义的协议解决方案还允许在移动接入网关和本地移动锚之间发送IPv4子网信令，但将IPv4子网委托给移动路由器不在本规范的范围之内。
_----_
+-------+ _( )_
| |---( Internet )
| LMA | (_ _)
| | '----'
+-------+
|
=== === ===
== Proxy ==
== Mobile IPv6 ==
== Domain ==
=== === ===
___________|___________
| |
+-------+ +-------+
| MAG | | MAG |
+-------+ +-------+
.
.
- - - - - - - -
| +------+ |
| | MR | |
| +------+ |
| | |
| ------- |
| | | |
| LFN LFN |
- - - - - - - -
_----_
+-------+ _( )_
| |---( Internet )
| LMA | (_ _)
| | '----'
+-------+
|
=== === ===
== Proxy ==
== Mobile IPv6 ==
== Domain ==
=== === ===
___________|___________
| |
+-------+ +-------+
| MAG | | MAG |
+-------+ +-------+
.
.
- - - - - - - -
| +------+ |
| | MR | |
| +------+ |
| | |
| ------- |
| | | |
| LFN LFN |
- - - - - - - -
Figure 1: Mobile Router in Proxy Mobile IPv6 Domain
图1：代理移动IPv6域中的移动路由器
Within the context of this document, the definition of a mobile router extends the definition of a mobile node from [RFC5213] by adding routing capability between the mobile network and the point of attachment of the mobile router. Local fixed nodes (LFNs) are IP nodes in the mobile network; LFNs all move with the mobile router as a single cluster. As the mobile router moves, the LFNs are not aware of the mobility of the MR to a new point of attachment. Figure 1 illustrates a mobile router in a Proxy Mobile IPv6 domain.
在本文件的上下文中，移动路由器的定义通过在移动网络和移动路由器的连接点之间添加路由能力，从[RFC5213]扩展了移动节点的定义。本地固定节点（LFN）是移动网络中的IP节点；LFN都作为单个集群随移动路由器移动。当移动路由器移动时，lfn不知道MR移动到新的连接点。图1显示了代理移动IPv6域中的移动路由器。
The rest of this document identifies the protocol extensions and the operational details of the local mobility anchor and mobile access gateway for realizing prefix delegation support for Proxy Mobile IPv6.
本文档的其余部分确定了本地移动锚和移动访问网关的协议扩展和操作细节，以实现对代理移动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 Proxy Mobile IPv6 specifications [RFC5213] and [RFC5844]. All the DHCP-related terms are to be interpreted as defined in DHCPv6 Prefix Delegation for Network Mobility (NEMO) [RFC6276], DHCPv6 Prefix Delegation (DHCPv6PD) [RFC3633], and Subnet Allocation Option for DHCPv4 [RFC6656]. This document also provides a context-specific explanation of the following terms used here and originally defined in the Mobile Network terminology document [RFC4885].
本文档中使用的所有移动相关术语应按照代理移动IPv6规范[RFC5213]和[RFC5844]中的定义进行解释。所有与DHCP相关的术语均应按照网络移动性（NEMO）的DHCPv6前缀委派[RFC6276]、DHCPv6前缀委派（DHCPv6PD）[RFC3633]和DHCPv4的子网分配选项[RFC6656]中的定义进行解释。本文档还提供了以下术语的上下文特定解释，这些术语在此处使用，最初在移动网络术语文档[RFC4885]中定义。
Mobile Router (MR)
移动路由器（MR）
The term "mobile router" is used to refer to an IP router whose mobility is managed by the network while being attached to a Proxy Mobile IPv6 domain. The mobile router is a mobile node as defined in [RFC5213] but with additional capabilities for supporting an attached mobile network. The MR's interface used for attachment to the mobile access gateway is referred to as the "egress interface". Any MR's interface used for attachment to the mobile network is referred to as the "ingress interface". The mobility entities in the Proxy Mobile IPv6 domain provide mobility for the IPv4/IPv6 address(es) assigned to the mobile node's egress link and also mobility support to the network prefixes hosted in the network attached to the mobile router.
术语“移动路由器”用于指当连接到代理移动IPv6域时由网络管理其移动性的IP路由器。移动路由器是[RFC5213]中定义的移动节点，但具有支持连接的移动网络的附加功能。用于连接到移动接入网关的MR接口被称为“出口接口”。用于连接到移动网络的任何MR接口称为“入口接口”。代理移动IPv6域中的移动实体为分配给移动节点的出口链路的IPv4/IPv6地址提供移动，并且还为连接到移动路由器的网络中承载的网络前缀提供移动支持。
Mobile Network
移动网络
A mobile network is an IP network attached to a mobile router. There can be many IP nodes in this IP network. The mobile router is a gateway for these IP nodes for reaching other IP networks or the Internet. The mobile router and the attached IP networks move as a single cluster.
移动网络是连接到移动路由器的IP网络。此IP网络中可能有许多IP节点。移动路由器是这些IP节点到达其他IP网络或Internet的网关。移动路由器和连接的IP网络作为单个集群移动。
Delegated Mobile Network Prefix (DMNP)
授权移动网络前缀（DMNP）
The Delegated Mobile Network Prefix is an IPv4/IPv6 prefix delegated to a mobile router and is hosted in the mobile network. The IP nodes in the mobile network will be able to obtain IP address configuration from the DMNP and will have IP mobility support for that address configuration. The DMNP is topologically anchored on the local mobility anchor, and the mobility elements
委派的移动网络前缀是委派给移动路由器的IPv4/IPv6前缀，托管在移动网络中。移动网络中的IP节点将能够从DMNP获得IP地址配置，并且将具有该地址配置的IP移动性支持。DMNP拓扑锚定在局部移动性锚上，移动性元素
in the Proxy Mobile IPv6 domain provide IP mobility support for the prefix by forwarding the mobile network traffic to the mobile router.
在代理移动IPv6域中，通过将移动网络流量转发到移动路由器，为前缀提供IP移动支持。
Local Fixed Node (LFN)
本地固定节点（LFN）
A local fixed node is an IP node in the mobile network. As the mobile router performs a handoff and changes its network point of attachment, the local fixed node moves along with the mobile router.
本地固定节点是移动网络中的IP节点。当移动路由器执行切换并更改其网络连接点时，本地固定节点随移动路由器移动。
This section lists the stated assumptions and provides an overview of the operation of this specification. This document references three different deployment scenarios and explains the protocol operation.
本节列出了所述假设，并概述了本规范的操作。本文档参考了三种不同的部署场景，并解释了协议操作。
o The mobile router is a mobile node as defined in [RFC5213] but with additional capabilities for routing IP packets between its egress interface (interface used for attachment to the mobile access gateway) and any of its ingress interfaces (interfaces used for attachment to the mobile network).
o 移动路由器是[RFC5213]中定义的移动节点，但具有在其出口接口（用于连接到移动接入网关的接口）和任何入口接口（用于连接到移动网络的接口）之间路由IP数据包的附加功能。
o This specification assumes that a mobile router is an IPv4 and/or IPv6 router without any capability for mobility management.
o 本规范假设移动路由器是IPv4和/或IPv6路由器，没有任何移动性管理功能。
o The mobile router can obtain the delegated IP prefix(es) for its attached mobile networks using DHCPv6 prefix delegation, static configuration, or mechanisms specific to access technology. This document assumes DHCPv6 prefix delegation [RFC3633] in conjunction with the Prefix Exclude Option [RFC6603] as the default mechanism for prefix assignment to the mobile node. It defines an interworking between the mobility entities and the DHCPv6 functional elements in a non-normative way. The mechanism that delegates IPv4 subnets to a mobile router is out of the scope of this specification.
o 移动路由器可以使用DHCPv6前缀委派、静态配置或特定于接入技术的机制来获得其连接的移动网络的委派IP前缀。本文档假设DHCPv6前缀委派[RFC3633]与前缀排除选项[RFC6603]一起作为向移动节点分配前缀的默认机制。它以非规范的方式定义了移动实体和DHCPv6功能元素之间的互通。将IPv4子网委托给移动路由器的机制不在本规范的范围内。
o The mobile router obtains the IP address configuration for its egress roaming interface as specified in [RFC5213] and [RFC5844]. The mobile router, along with its mobile networks, will be able to perform handoff, change its point of attachment in the network, and retain IP mobility support.
o 移动路由器获得[RFC5213]和[RFC5844]中规定的其出口漫游接口的IP地址配置。移动路由器及其移动网络将能够执行切换，更改其在网络中的连接点，并保留IP移动性支持。
o When using DHCPv6 prefix delegation, this document assumes that the mobile router uses its egress interface when making DHCPv6 requests.
o 当使用DHCPv6前缀委派时，本文档假设移动路由器在发出DHCPv6请求时使用其出口接口。
This section explains the protocol operation used to support prefix delegation in Proxy Mobile IPv6 for the following three deployment models: i) delegating router co-located with mobile access gateway, ii) delegating router co-located with local mobility anchor, and iii) static configuration of delegated prefixes. High-level message call flows between the mobile router, mobile access gateway, and the local mobility anchor are presented while explaining the protocol operation.
本节介绍了在代理移动IPv6中用于支持以下三种部署模型的前缀委派的协议操作：i）委派与移动访问网关位于同一位置的路由器，ii）委派与本地移动锚位于同一位置的路由器，以及iii）委派前缀的静态配置。在解释协议操作的同时，给出了移动路由器、移动接入网关和本地移动锚之间的高级消息呼叫流。
In this deployment scenario, the delegating router (DR) function, as specified in [RFC3633], is co-located with the mobile access gateway, and a requesting router (RR) function is enabled on the mobile router.
在此部署场景中，[RFC3633]中规定的委托路由器（DR）功能与移动接入网关位于同一位置，并且在移动路由器上启用请求路由器（RR）功能。
Figure 2 shows the high-level message call flow for this case. The mobile router attaches to the mobile access gateway, which triggers the Proxy Mobile IPv6 signaling between the mobile access gateway and the local mobility anchor, setting up the bidirectional tunnel between them (regular Proxy Mobile IPv6 registration). After that, the DHCPv6 requesting router function running on the mobile router sends a Solicit message requesting a prefix. This message is received by the DHCPv6 delegating router function running on the mobile access gateway. The mobile access gateway then sends a Proxy Binding Update message including a Delegated Mobile Network Prefix (DMNP) option carrying the ALL_ZERO value [RFC5213]. This serves as a request for the local mobility anchor to allocate a set of delegated prefixes, conveyed back in one or more DMNP options in a Proxy Binding Acknowledgement message. The DHCPv6-PD procedure is then completed as described in [RFC3633], ending with the delegating router sending a Reply message conveying the delegated prefixes. If the requesting router includes a Rapid Commit option in its Solicit message, it is preferable that the MAG respond directly with a Reply message rather than with an Advertise message, as described in [RFC3315], Section 17.2.3.
图2显示了这种情况下的高级消息调用流。移动路由器连接到移动接入网关，从而触发移动接入网关和本地移动锚之间的代理移动IPv6信令，在它们之间建立双向隧道（常规代理移动IPv6注册）。之后，在移动路由器上运行的DHCPv6请求路由器功能发送请求前缀的请求消息。此消息由运行在移动访问网关上的DHCPv6委托路由器功能接收。然后，移动接入网关发送一个代理绑定更新消息，该消息包括一个带有ALL_零值的委托移动网络前缀（DMNP）选项[RFC5213]。这用作本地移动锚分配一组委派前缀的请求，在代理绑定确认消息中以一个或多个DMNP选项传回。然后，如[RFC3633]所述完成DHCPv6 PD过程，最终由授权路由器发送一条回复消息，传达授权前缀。如[RFC3315]第17.2.3节所述，如果请求路由器在其请求消息中包括快速提交选项，则MAG最好直接使用回复消息而不是广告消息进行响应。
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
|(RR) | | (DR)| | |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
| |--Proxy Binding Update----->|
| | |
| |<-------Proxy Binding Ack.--|
| | |
| |o==========================o|
2) | | PMIPv6 tunnel |
| |o==========================o|
3) |--Solicit for---->| |
| delegated prefix | |
4) | |--Proxy Binding Update----->|
| | |
5) | |<--Proxy Binding Ack.(DMNP)-|
| | |
- -<---+ |
6) |<------Advertise--| | |
| | | |
7) |--Request-------->| Optional |
| | | |
- -<---+ |
8) |<---Reply (DMNP)--| |
| | |
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
|(RR) | | (DR)| | |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
| |--Proxy Binding Update----->|
| | |
| |<-------Proxy Binding Ack.--|
| | |
| |o==========================o|
2) | | PMIPv6 tunnel |
| |o==========================o|
3) |--Solicit for---->| |
| delegated prefix | |
4) | |--Proxy Binding Update----->|
| | |
5) | |<--Proxy Binding Ack.(DMNP)-|
| | |
- -<---+ |
6) |<------Advertise--| | |
| | | |
7) |--Request-------->| Optional |
| | | |
- -<---+ |
8) |<---Reply (DMNP)--| |
| | |
Figure 2: Delegating Router Co-located with Mobile Access Gateway
图2：委托路由器与移动接入网关位于同一位置
From an operational point of view, this is the simplest deployment option, as it keeps a single protocol interface between the mobile access gateway and the local mobility anchor.
从操作的角度来看，这是最简单的部署选项，因为它在移动接入网关和本地移动锚之间保持单一协议接口。
In this deployment scenario, the delegating router (DR) function, as
specified in [RFC3633], is co-located with the local mobility anchor;
the requesting router (RR) function is enabled on the mobile router;
and a DHCPv6 relay agent (DRA) function is co-located on the mobile
access gateway.
In this deployment scenario, the delegating router (DR) function, as
specified in [RFC3633], is co-located with the local mobility anchor;
the requesting router (RR) function is enabled on the mobile router;
and a DHCPv6 relay agent (DRA) function is co-located on the mobile
access gateway.
Figure 3 shows the high-level message call flow for this case. The mobile router attaches to the mobile access gateway, which triggers the Proxy Mobile IPv6 signaling between the mobile access gateway and the local mobility anchor, setting up the bidirectional tunnel between them (regular Proxy Mobile IPv6 registration). After that, the DHCPv6 requesting router function running on the mobile router requests a prefix by sending a Solicit message. This message is
图3显示了这种情况下的高级消息调用流。移动路由器连接到移动接入网关，从而触发移动接入网关和本地移动锚之间的代理移动IPv6信令，在它们之间建立双向隧道（常规代理移动IPv6注册）。之后，在移动路由器上运行的DHCPv6请求路由器功能通过发送请求消息来请求前缀。此消息是
received by the DHCPv6 relay agent function running on the mobile access gateway, which then completes the DHCPv6 signaling, according to [RFC3315]. The relay agent function SHOULD include the relay agent remote-id option [RFC4649] into Relay-forward messages with appropriate identity information to enable correlation of mobile router identities used over DHCPv6 and PMIPv6.
由移动接入网关上运行的DHCPv6中继代理功能接收，然后根据[RFC3315]完成DHCPv6信令。中继代理功能应将中继代理远程id选项[RFC4649]包括在具有适当身份信息的中继转发消息中，以实现通过DHCPv6和PMIPv6使用的移动路由器身份的关联。
Once the mobile access gateway gets the set of delegated prefixes from the delegating router function running on the local mobility anchor, the MAG conveys the delegated prefixes in a Proxy Binding Update. This ensures that the local mobility anchor properly routes the traffic addressed to the delegated prefixes via the PMIPv6 tunnel established with the mobile access gateway and that mobility is provided to these prefixes while the mobile router roams within the PMIPv6 domain. Note that the relay agent function in the mobile access gateway has to queue the Reply message for the duration of the PMIPv6 signaling (steps 10 and 11) before forwarding the Reply message to the requesting router. While this does not change anything from the DHCPv6-PD protocol's point of view, implementations will need to account for interactions between the timing of PMIPv6 signaling and the DHCPv6 timeout/retry logic.
一旦移动接入网关从本地移动锚上运行的委托路由器功能获得委托前缀集，MAG将在代理绑定更新中传送委托前缀。这确保本地移动性锚点通过与移动接入网关建立的PMIPv6隧道正确地路由寻址到委托前缀的流量，并且在移动路由器在PMIPv6域内漫游时向这些前缀提供移动性。注意，在将应答消息转发到请求路由器之前，移动接入网关中的中继代理功能必须在PMIPv6信令期间（步骤10和11）对应答消息排队。虽然这不会改变DHCPv6 PD协议的观点，但实现需要考虑PMIPv6信令的定时和DHCPv6超时/重试逻辑之间的交互。
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
|(RR) | |(DRA)| |(DR) |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
| |--------- PBU ----------->|
| | |
| |<-------- PBA ------------|
| | |
| |o========================o|
2) | | PMIPv6 tunnel |
| |o========================o|
3) |-- Solicit for -->| |
| delegated prefix | |
4) | |--- Solicit ------------->|
- - - <---+
5) | |<-- Advertise ------------| |
| | | |
6) |<- Advertise -----| | |
| | | Optional
7) |-- Request ------>| | |
| | | |
8) | |--- Request ------------->| |
- - - <---+
9) | |<-- Reply (DMNP) ---------|
| | |
10) | |----------PBU (DMNP)----->|
| | |
11) | |<---------PBA (DMNP)------|
| | |
12) |<-- Reply (DMNP) -| |
| | |
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
|(RR) | |(DRA)| |(DR) |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
| |--------- PBU ----------->|
| | |
| |<-------- PBA ------------|
| | |
| |o========================o|
2) | | PMIPv6 tunnel |
| |o========================o|
3) |-- Solicit for -->| |
| delegated prefix | |
4) | |--- Solicit ------------->|
- - - <---+
5) | |<-- Advertise ------------| |
| | | |
6) |<- Advertise -----| | |
| | | Optional
7) |-- Request ------>| | |
| | | |
8) | |--- Request ------------->| |
- - - <---+
9) | |<-- Reply (DMNP) ---------|
| | |
10) | |----------PBU (DMNP)----->|
| | |
11) | |<---------PBA (DMNP)------|
| | |
12) |<-- Reply (DMNP) -| |
| | |
Figure 3: Delegating Router Co-located with Local Mobility Anchor
图3：授权路由器与本地移动锚共同定位
The DR function can also be located in other entities of the home network aside from the LMA. This deployment model requires some interworking between the DR and the LMA and is out of the scope of this specification. Note that this additional interworking would have no impact on the protocol between the LMA and MAG defined in this document.
DR功能还可以位于除LMA之外的家庭网络的其他实体中。此部署模型需要DR和LMA之间进行一些互通，不在本规范的范围内。注意，这种额外的互通不会影响本文件中定义的LMA和MAG之间的协议。
In this deployment scenario, the DMNPs of the mobile router are statically configured in the mobile node's policy profile [RFC5213]. The DMNPs are statically configured in the mobile network attached to the mobile router. The mobile router is the default-router for the mobile networks.
在此部署场景中，移动路由器的DMNPs在移动节点的策略配置文件[RFC5213]中静态配置。DMNPs在连接到移动路由器的移动网络中静态配置。移动路由器是移动网络的默认路由器。
Figure 4 shows a high-level message call flow for this example. The mobile access gateway obtains statically configured mobile network prefixes from the policy profile and registers them with the local mobility anchor using the extensions specified in this document, that is, the use of the Delegated Mobile Network Prefix (DMNP) option in the Proxy Mobile IPv6 signaling. There is no explicit trigger from the mobile router for registering or de-registering those prefixes. As long as there is a mobility session for the mobile router's home address, the local mobility anchor enables mobility support for the mobile network prefixes.
图4显示了此示例的高级消息调用流。移动接入网关从策略配置文件获取静态配置的移动网络前缀，并使用本文档中指定的扩展，即在代理移动IPv6信令中使用委派移动网络前缀（DMNP）选项，向本地移动锚注册这些前缀。移动路由器没有明确的触发器来注册或取消注册这些前缀。只要移动路由器的家庭地址存在移动性会话，本地移动性锚就能够支持移动网络前缀的移动性。
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
| | | | | |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
2) | - (Policy Profile) |
| | |
3) | |--------- PBU (DMNP) ---->|
| | |
4) | |<-------- PBA (DMNP) -----|
| | |
| |o========================o|
5) | | PMIPv6 tunnel |
| |o========================o|
| | |
+-----+ +-----+ +-----+
| MR | | MAG | | LMA |
| | | | | |
+-----+ +-----+ +-----+
1) |-- MN Attach -----| |
2) | - (Policy Profile) |
| | |
3) | |--------- PBU (DMNP) ---->|
| | |
4) | |<-------- PBA (DMNP) -----|
| | |
| |o========================o|
5) | | PMIPv6 tunnel |
| |o========================o|
| | |
Figure 4: Static Configuration of Delegated Mobile Network Prefixes
图4：委托移动网络前缀的静态配置
This section defines extensions to Proxy Mobile IPv6 [RFC5213] protocol messages.
本节定义了代理移动IPv6[RFC5213]协议消息的扩展。
A new mobility header option, the Delegated Mobile Network Prefix option, is defined for use with Proxy Binding Update and Proxy Binding Acknowledgement messages exchanged between a local mobility anchor and a mobile access gateway. This option is used for
定义了一个新的移动报头选项，即委托移动网络前缀选项，用于在本地移动锚和移动接入网关之间交换代理绑定更新和代理绑定确认消息。此选项用于
exchanging the mobile router's IPv4/IPv6 DMNP. There can be multiple instances of the Delegated Mobile Network Prefix option present in a message.
交换移动路由器的IPv4/IPv6 DMNP。消息中可能存在多个代理移动网络前缀选项的实例。
The Delegated Mobile Network Prefix option has an alignment requirement of 8n+2. Its format is as follows:
委派的移动网络前缀选项的对齐要求为8n+2。其格式如下：
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 |V| Reserved | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
. .
+ IPv4 or IPv6 Delegated Mobile Network Prefix +
| (DMNP) |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |V| Reserved | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
. .
+ IPv4 or IPv6 Delegated Mobile Network Prefix +
| (DMNP) |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
类型
55
55
Length
长
8-bit unsigned integer indicating the length of the option in octets, excluding the Type and Length fields.
8位无符号整数，以八位字节表示选项的长度，不包括类型和长度字段。
IPv4 Prefix (V)
IPv4前缀（V）
If the IPv4 Prefix (V) flag is set to a value of (1), then it indicates that the prefix that is included in the DMNP field is an IPv4 prefix. If the IPv4 Prefix (V) flag is set to a value of (0), then it indicates that the prefix that is included in the DMNP field is an IPv6 prefix.
如果IPv4前缀（V）标志设置为值（1），则表示DMNP字段中包含的前缀是IPv4前缀。如果IPv4前缀（V）标志设置为值（0），则表示DMNP字段中包含的前缀是IPv6前缀。
Reserved
含蓄的
This field is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
Prefix Length
前缀长度
8-bit unsigned integer indicating the number of leftmost bits covering the network part of the address contained in the Prefix field.
8位无符号整数，表示包含在前缀字段中的地址网络部分的最左端位数。
Delegated Mobile Network Prefix
代理移动网络前缀
Contains a mobile router's 4-byte IPv4 or a 16-byte IPv6 Delegated Mobile Network Prefix.
包含移动路由器的4字节IPv4或16字节IPv6代理移动网络前缀。
This document defines the following new status code values for use in the Proxy Binding Acknowledgement message. These values have been allocated from the same number space as defined in Section 6.1.8 of [RFC6275].
本文档定义了以下在代理绑定确认消息中使用的新状态代码值。这些值是从[RFC6275]第6.1.8节定义的相同数字空间分配的。
NOT_AUTHORIZED_FOR_DELEGATED_MNP: 177
未经授权的授权的授权的MNP:177
Not authorized for DMNP
未授权使用DMNP
REQUESTED_DMNP_IN_USE: 178
使用中请求的DMNP：178
Requested DMNP is in use
请求的DMNP正在使用中
In order to support this specification, the conceptual Binding Update List Entry (BULE) data structure [RFC5213] needs to be extended to include a Delegated Mobile Network Prefix (DMNP) list. Each entry in the list is used for storing an IPv4/IPv6 mobile network prefix delegated to the mobile router.
为了支持此规范，需要扩展概念绑定更新列表条目（BULE）数据结构[RFC5213]，以包括委派移动网络前缀（DMNP）列表。列表中的每个条目用于存储委派给移动路由器的IPv4/IPv6移动网络前缀。
During the mobile router's initial attachment procedure, the mobile access gateway obtains the mobile router's policy profile, as per the procedures defined in [RFC5213]. The mobile node's policy profile defined in [RFC5213] is extended to include a parameter that indicates Delegated Prefix support. If the policy profile indicates that the mobile router is authorized for Delegated Prefix support, then the considerations described next apply.
在移动路由器的初始连接过程中，移动接入网关根据[RFC5213]中定义的过程获取移动路由器的策略配置文件。[RFC5213]中定义的移动节点的策略配置文件被扩展，以包括一个指示委派前缀支持的参数。如果策略配置文件指示移动路由器被授权进行委派前缀支持，则下面描述的注意事项适用。
The mobile access gateway MUST include one or more Delegated Mobile Network Prefix (DMNP) options in the Proxy Binding Update message in order to request the local mobility anchor to allocate DMNP(s) for the mobile router.
移动接入网关必须在代理绑定更新消息中包括一个或多个委托移动网络前缀（DMNP）选项，以便请求本地移动锚为移动路由器分配DMNP。
If the mobile access gateway requests the local mobility anchor to perform the prefix assignment, then:
如果移动接入网关请求本地移动锚执行前缀分配，则：
o There MUST be exactly one instance of the Delegated Mobile Network Prefix option with an ALL_ZERO value and with the (V) flag set to a value of (0). This serves as a request to the local mobility anchor to allocate a set of IPv6 DMNPs.
o 委托移动网络前缀选项必须只有一个实例的ALL_值为零，且（V）标志的值设置为（0）。这用作对本地移动锚的请求，以分配一组IPv6 DMNPs。
o There MUST be exactly one instance of the Delegated Mobile Network Prefix option with an ALL_ZERO value and with the (V) flag set to a value of (1). This serves as a request to the local mobility anchor to allocate a set of IPv4 DMNP.
o “委派移动网络前缀”选项必须只有一个实例的ALL_值为零值且（V）标志的值设置为（1）。这用作对本地移动锚的请求，以分配一组IPv4 DMNP。
o If the received Proxy Binding Acknowledgement message has the status field value set to NOT_AUTHORIZED_FOR_DELEGATED_MNP (not authorized for DMNP), the mobile access gateway MUST NOT enable mobility support for any of the prefixes in the mobile network, and prefix delegation support has to be disabled.
o 如果收到的代理绑定确认消息的状态字段值设置为NOT_AUTHORIZED_FOR_DELEGATED_MNP（NOT AUTHORIZED FOR DMNP），则移动接入网关不得为移动网络中的任何前缀启用移动性支持，并且必须禁用前缀委派支持。
o If the received Proxy Binding Acknowledgement message has the status field value set to REQUESTED_DMNP_IN_USE (Requested DMNP is in use), the mobile access gateway MUST NOT enable mobility support for the requested prefixes. The mobile access gateway MAY choose to send Proxy Binding Update message requesting the local mobility anchor to perform the prefix assignment.
o 如果收到的代理绑定确认消息的状态字段值设置为REQUESTED_DMNP_IN_USE（REQUESTED DMNP IN USE），则移动接入网关不得为请求的前缀启用移动性支持。移动接入网关可以选择发送代理绑定更新消息，请求本地移动锚执行前缀分配。
If the mobile access gateway provides the local mobility anchor with the prefix(es) to be allocated, then:
如果移动接入网关向本地移动锚提供要分配的前缀，则：
o There MUST be exactly one instance of the Delegated Mobile Network Prefix option with NON_ZERO prefix value [RFC5213] for each of the mobile network prefixes that the mobile access gateway is requesting the local mobility anchor to allocate. The prefix value in the option is the prefix that is either statically configured for that mobile router in the mobile node's policy profile or obtained via interactions with the DHCP PD functions. This serves as a request to the local mobility anchor to allocate the requested IPv4/IPv6 prefix.
o 对于移动接入网关正在请求本地移动锚分配的每个移动网络前缀，必须正好有一个具有非零前缀值[RFC5213]的委托移动网络前缀选项实例。选项中的前缀值是在移动节点的策略配置文件中为该移动路由器静态配置的前缀，或通过与DHCP PD功能的交互获得的前缀。这用作对本地移动锚的请求，以分配请求的IPv4/IPv6前缀。
If the received Proxy Binding Acknowledgement message has the status field value set to 0 (Proxy Binding Update accepted), the mobile access gateway has to apply the following considerations.
如果收到的代理绑定确认消息的状态字段值设置为0（接受代理绑定更新），则移动接入网关必须应用以下注意事项。
o The Delegated Mobile Network Prefix (DMNP) list in the mobile router's Binding Update List entry has to be updated with the allocated prefix(es). However, if the received message was in response to a de-registration request with a lifetime value of (0), then the DMNP list has to be removed along with the Binding Update List entry.
o 移动路由器绑定更新列表条目中的委托移动网络前缀（DMNP）列表必须使用分配的前缀进行更新。但是，如果收到的消息响应的是生存期值为（0）的注销请求，则必须将DMNP列表与绑定更新列表条目一起删除。
o The mobile access gateway has to set up a policy-based route for forwarding the IP packets received from the mobile network (with the source IP address from any of the IPv4/IPv6 DMNPs) through the bidirectional tunnel set up for that mobile router. However, if the received message was in response to a de-registration request with a lifetime value of (0), then the created forwarding state has to be removed.
o 移动接入网关必须设置基于策略的路由，以便通过为该移动路由器设置的双向隧道转发从移动网络接收的IP数据包（源IP地址来自任何IPv4/IPv6 DMNPs）。但是，如果收到的消息响应的是生存期值为（0）的取消注册请求，则必须删除创建的转发状态。
This specification assumes that all the mobile access gateways of a PMIPv6 domain support the same prefix delegation mechanism. Any differences will result in DMNPs getting de-registered and the mobile network losing the prefix(es). This would result in the attached local fixed nodes losing the assigned IP addresses. The mobile router MAY explicitly deprecate these prefixes. Alternatively, the lifetime of the addresses may expire.
本规范假设PMIPv6域的所有移动访问网关都支持相同的前缀委派机制。任何差异都将导致DMNPs取消注册，移动网络丢失前缀。这将导致连接的本地固定节点丢失分配的IP地址。移动路由器可能会明确拒绝使用这些前缀。或者，地址的生存期可能会到期。
This section describes the interactions between the DHCP and PMIPv6 logical entities running on the mobile access gateway. This section is applicable only for deployments that use DHCPv6-based prefix delegation (i.e., it does not apply if static configuration is used). As described next, these interactions vary slightly depending on the considered deployment model at the mobile access gateway (described in Section 3.2).
本节描述在移动访问网关上运行的DHCP和PMIPv6逻辑实体之间的交互。本节仅适用于使用基于DHCPv6的前缀委派的部署（即，如果使用静态配置，则不适用）。如下文所述，根据移动接入网关（第3.2节所述）所考虑的部署模型，这些交互略有不同。
The mobile router, acting as a requesting router as described in [RFC3633], sends a Solicit message including one or more IA_PD option(s) to the delegating router / DHCPv6 relay agent co-located on the mobile access gateway. This message provides the needed trigger for the mobile access gateway to request the local mobility anchor to enable DMNP support for that mobility session. We next describe the subsequent interactions depending on the deployment model.
移动路由器充当[RFC3633]中所述的请求路由器，将包括一个或多个IA_PD选项的请求消息发送到位于移动接入网关上的委托路由器/DHCPv6中继代理。该消息为移动接入网关提供所需的触发器，以请求本地移动锚，从而为该移动会话启用DMNP支持。接下来，我们将根据部署模型描述后续交互。
The mobile access gateway applies the considerations in Section 5.1.2 for requesting the local mobility anchor to enable delegated prefix support. For example, if the mobile router is soliciting an IPv4 prefix, the mobile access gateway includes in the Proxy Binding Update signaling a Delegated Mobile Network Prefix option with an ALL_ZERO value and with the (V) flag set to a value of (1).
移动接入网关应用第5.1.2节中的注意事项来请求本地移动锚以启用委托前缀支持。例如，如果移动路由器请求IPv4前缀，则移动接入网关在代理绑定更新信令中包括具有ALL_零值且（V）标志设置为值（1）的委托移动网络前缀选项。
The mobile access gateway, upon successfully completing the Proxy Binding Update signaling with the local mobility anchor (following the considerations described in Section 5.1.2), adds the DMNPs to the Binding Update List. Then, the mobile access gateway provides the obtained prefixes to the DHCPv6 delegating router for prefix assignment. The way in which these prefixes are passed to the DHCPv6 delegating router function is beyond the scope of this document.
移动接入网关在使用本地移动锚成功完成代理绑定更新信令后（遵循第5.1.2节中描述的注意事项），将DMNPs添加到绑定更新列表中。然后，移动接入网关将获得的前缀提供给DHCPv6委托路由器进行前缀分配。这些前缀传递给DHCPv6委托路由器功能的方式超出了本文档的范围。
o In case the Proxy Binding Update signaling with the local mobility anchor is not completed successfully, for example, because the local mobility anchor is not authorized for DMNP or the requested prefix is in use, the DHCPv6 delegating router will send a Reply message to the requesting router with no IA_PREFIX suboptions and with a Status Code option as described in [RFC3633], Section 11.2.
o 在与本地移动性锚的代理绑定更新信令未成功完成的情况下，例如，因为本地移动性锚未被授权用于DMNP或请求的前缀正在使用，DHCPv6委托路由器将向请求路由器发送一条回复消息，该消息不包含IA_前缀子选项，且带有[RFC3633]第11.2节所述的状态代码选项。
The standard DHCPv6 considerations will be applied with respect to the interactions between the delegating router and the requesting router. The requesting router is provided with the delegated prefix(es), which can then be then advertised in the mobile network and therefore used by the local fixed nodes to autoconfigure IP addresses, allowing them to gain access to the Internet.
标准DHCPv6注意事项将应用于授权路由器和请求路由器之间的交互。向请求路由器提供委托前缀，然后可以在移动网络中公布该前缀，并因此被本地固定节点用于自动配置IP地址，从而允许它们访问互联网。
Any time the requesting router releases the delegated prefixes, the delegating router removes the assigned prefixes. To do so, the mobile access gateway will send an Updated Proxy Binding Update following the considerations described in Section 5.1.2 for de-registering those prefixes. The way in which the DHCPv6 delegating router triggers the mobile access gateway in order to de-register the prefixes is beyond the scope of this document.
每当请求路由器释放委派前缀时，委派路由器都会删除指派的前缀。为此，移动接入网关将按照第5.1.2节中描述的取消注册这些前缀的注意事项发送更新的代理绑定更新。DHCPv6委托路由器触发移动访问网关以注销前缀的方式超出了本文档的范围。
In case the mobile router performs a handover and attaches to a different mobile access gateway, the following cases are possible:
如果移动路由器执行切换并连接到不同的移动接入网关，则可能出现以下情况：
o The new mobile access gateway does not support the delegation of mobile network prefixes described in this specification. In this case, forwarding of the previously DMNPs is no longer performed.
o 新的移动接入网关不支持本规范中描述的移动网络前缀的委派。在这种情况下，不再执行先前dmnp的转发。
o The new mobile access gateway supports the delegation of mobile network prefixes described in this specification. There are two possible cases upon the reception of the Solicit message by the delegating router. If the MAG already knows the DMNPs, it conveys them in a DMNP option included in the Proxy Binding Update sent to the local mobility anchor, which then authorizes them based on: a) the content of the associated Binding Cache entry (if one exists), b) the user profile (if the allocation is static), or c) checking that the DMNPs are not already allocated. On the other hand, if the mobile access gateway is not aware of the DMNPs, it will include 0.0.0.0 / :: in a DMNP option included in the Proxy Binding Update sent to the LMA, which will provide the right prefixes back in the Proxy Binding Acknowledgement based on a) the content of the associated Binding Cache entry (if one exits), b) the profile (if static allocation is used), or c) dynamic assignment.
o 新的移动接入网关支持本规范中描述的移动网络前缀的委托。在委托路由器接收到请求消息时，有两种可能的情况。如果MAG已经知道DMNP，它将在发送给本地移动锚的代理绑定更新中包含的DMNP选项中传送它们，然后本地移动锚基于以下内容对它们进行授权：a）相关绑定缓存项的内容（如果存在），b）用户配置文件（如果分配是静态的），或c）检查DMNPs是否尚未分配。另一方面，如果移动接入网关不知道DMNP，则它将在发送到LMA的代理绑定更新中包括的DMNP选项中包括0.0.0.0/：：该DMNP选项将基于a）相关联的绑定缓存条目的内容（如果存在），b）概要文件在代理绑定确认中提供正确的前缀（如果使用静态分配），或c）动态分配。
A DHCPv6 relay agent function running on the mobile access gateway will forward the DHCP messages to the local mobility anchor that has the co-located delegating router function. The requesting router and the delegating router complete the DHCP messages related to prefix delegation.
在移动接入网关上运行的DHCPv6中继代理功能将DHCP消息转发到本地移动锚，该本地移动锚具有共同定位的委托路由器功能。请求路由器和委派路由器完成与前缀委派相关的DHCP消息。
During the DHCPv6 exchange, the standard DHCPv6 considerations apply with respect to the interactions between the delegating router, DHCPv6 relay agent, and requesting router.
在DHCPv6交换期间，标准DHCPv6注意事项适用于委托路由器、DHCPv6中继代理和请求路由器之间的交互。
The mobile access gateway learns from the co-located DHCPv6 relay agent the prefixes allocated by the delegating router. The way in which the mobile access gateway obtains this information from the DHCPv6 relay agent function is beyond the scope of this document.
移动接入网关从位于同一位置的DHCPv6中继代理学习由委派路由器分配的前缀。移动接入网关从DHCPv6中继代理功能获取此信息的方式超出了本文档的范围。
The mobile access gateway will apply the considerations in Section 5.1.2 for requesting the local mobility anchor to enable delegated prefix support. The mobile access gateway will include exactly one instance of the Delegated Mobile Network Prefix option with NON_ZERO prefix value for each of the mobile network prefixes that the mobile access gateway is requesting the local mobility anchor to allocate. The prefix value(s) in the option will be the prefix(es) obtained via DHCP prefix delegation.
移动接入网关将应用第5.1.2节中的注意事项来请求本地移动锚以启用委托前缀支持。移动接入网关将包括委托移动网络前缀选项的恰好一个实例，对于移动接入网关正在请求本地移动锚分配的每个移动网络前缀，具有非零前缀值。选项中的前缀值将是通过DHCP前缀委派获得的前缀。
The mobile access gateway, upon successfully completing the Proxy Binding Update signaling with the local mobility anchor, will provide the obtained prefixes to the DHCPv6 relay agent for prefix assignment. The delegating router is provided with the delegated prefix(es) completing the standard DHCPv6 signaling. These prefixes
移动接入网关在成功完成与本地移动锚的代理绑定更新信令后，将向DHCPv6中继代理提供获得的前缀以进行前缀分配。委托路由器具有完成标准DHCPv6信令的委托前缀。这些前缀
can then be advertised in the mobile network and therefore used by the local fixed nodes to autoconfigure IP addresses, allowing them to gain access to the Internet.
然后可以在移动网络中进行广告，从而被本地固定节点用于自动配置IP地址，从而允许他们访问互联网。
o In case the Proxy Binding Update signaling with the local mobility anchor is not completed successfully, for example, because the local mobility anchor is not authorized for DMNP, the requested prefix is in use, or the delegated prefix(es) do not match the ones allocated by DHCP prefix delegation, the DHCPv6 relay agent MAY send a Reply message to the requesting router with no IA_PREFIX suboptions and with a Status Code option as described in [RFC3633], Section 11.2.
o 如果与本地移动锚的代理绑定更新信令未成功完成，例如，因为本地移动锚未被授权用于DMNP，请求的前缀正在使用，或者委托的前缀与DHCP前缀委托分配的前缀不匹配，DHCPv6中继代理可以向请求路由器发送回复消息，该消息不包含IA_前缀子选项，并且具有[RFC3633]第11.2节所述的状态代码选项。
In case the mobile router performs a handover and attaches to a different mobile access gateway, the following cases are possible:
如果移动路由器执行切换并连接到不同的移动接入网关，则可能出现以下情况：
o The new mobile access gateway does not support the delegation of mobile network prefixes described in this specification. In this case, forwarding of the previously delegated mobile network prefixes is no longer performed.
o 新的移动接入网关不支持本规范中描述的移动网络前缀的委派。在这种情况下，不再执行先前委派的移动网络前缀的转发。
o The new mobile access gateway supports the delegation of mobile network prefixes described in this specification. There are two possible cases upon the reception of the Solicit message by the DHCPv6 relay agent. If the MAG already knows the DMNPs, it conveys them in a DMNP option included in the Proxy Binding Update sent to the local mobility anchor, which then authorizes them based on: a) the content of the associated Binding Cache entry (if one exists), b) the user profile (if the allocation is static), or c) checking that the DMNPs are not already allocated. On the other hand, if the mobile access gateway is not aware of the DMNPs, it will include 0.0.0.0 / :: in a DMNP option included in the Proxy Binding Update sent to the LMA, which will provide the right prefixes back in the Proxy Binding Acknowledgement based on a) the content of the associated Binding Cache entry (if one exits), b) the profile (if static allocation is used), or c) dynamic assignment.
o 新的移动接入网关支持本规范中描述的移动网络前缀的委托。在DHCPv6中继代理接收到请求消息时，有两种可能的情况。如果MAG已经知道DMNP，它将在发送给本地移动锚的代理绑定更新中包含的DMNP选项中传送它们，然后本地移动锚基于以下内容对它们进行授权：a）相关绑定缓存项的内容（如果存在），b）用户配置文件（如果分配是静态的），或c）检查DMNPs是否尚未分配。另一方面，如果移动接入网关不知道DMNP，则它将在发送到LMA的代理绑定更新中包括的DMNP选项中包括0.0.0.0/：：该DMNP选项将基于a）相关联的绑定缓存条目的内容（如果存在），b）概要文件在代理绑定确认中提供正确的前缀（如果使用静态分配），或c）动态分配。
On receiving an IP packet from a mobile router, the mobile access gateway MUST ensure, before tunneling the packet to the local mobility anchor, that there is an established binding for the mobile router and that the source IP address of the packet is a prefix delegated to that mobile router. If the source address of the received IP packet is not part of the DMNP, then the mobile access gateway MUST NOT tunnel the packet to the local mobility anchor.
在从移动路由器接收到IP分组时，移动接入网关必须在将分组隧道传输到本地移动锚之前确保移动路由器存在已建立的绑定，并且分组的源IP地址是委托给该移动路由器的前缀。如果接收到的IP分组的源地址不是DMNP的一部分，则移动接入网关不得将分组隧道到本地移动锚。
On receiving an IP packet from the bidirectional tunnel established with the local mobility anchor, the mobile access gateway MUST first decapsulate the packet (remove the outer header) and then use the destination address of the (inner) packet to forward it on the interface through which the mobile router is reachable.
在从使用本地移动性锚建立的双向隧道接收到IP分组时，移动接入网关必须首先解除分组的封装（移除外部报头），然后使用（内部）分组的目的地地址在可通过其到达移动路由器的接口上转发它。
The above forwarding considerations are not applicable to the IP traffic sent/received to/from the mobile router's home address (IPv4 HoA / Home Network Prefix (HNP)). For the mobile router's home address traffic, forwarding considerations from [RFC5213] and [RFC5844] continue to apply.
上述转发注意事项不适用于发送/接收到/来自移动路由器的家庭地址（IPv4 HoA/家庭网络前缀（HNP））的IP流量。对于移动路由器的家庭地址通信，来自[RFC5213]和[RFC5844]的转发注意事项继续适用。
In order to support this specification, the conceptual Binding Cache entry (BCE) data structure [RFC5213] needs to be extended to include the Delegated Mobile Network Prefix (DMNP) list. Each entry in the list represents a DMNP.
为了支持此规范，需要扩展概念绑定缓存项（BCE）数据结构[RFC5213]，以包括委派移动网络前缀（DMNP）列表。列表中的每个条目代表一个DMNP。
If the Proxy Binding Update message does not include any Delegated Mobile Network Prefix option(s) (Section 4.1), then the local mobility anchor MUST NOT enable Delegated Prefix support for the mobility session, and the Proxy Binding Acknowledgement message that is sent in response MUST NOT contain any Delegated Mobile Network Prefix option(s).
如果代理绑定更新消息不包括任何代理移动网络前缀选项（第4.1节），则本地移动锚不得为移动会话启用代理前缀支持，并且作为响应发送的代理绑定确认消息不得包含任何代理移动网络前缀选项。
If the Proxy Binding Update message includes one or more Delegated Mobile Network Prefix options, but the local mobility anchor is not configured with Delegated Prefix support, then the local mobility anchor will ignore the option(s) and process the rest of the option as specified in [RFC5213]. This would have no effect on the operation of the rest of the protocol. The Proxy Binding Acknowledgement message that is sent in response will not include any Delegated Mobile Network Prefix option(s).
如果代理绑定更新消息包括一个或多个委派移动网络前缀选项，但本地移动锚未配置委派前缀支持，则本地移动锚将忽略该选项，并按照[RFC5213]中的规定处理该选项的其余部分。这对协议其余部分的操作没有影响。作为响应发送的代理绑定确认消息将不包括任何委派的移动网络前缀选项。
If the Proxy Binding Update message has the Delegated Mobile Network Prefix option(s) and if the local mobility anchor is configured for Delegated Prefix support, then the local mobility anchor MUST enable the Delegated Mobile Network Prefix option for that mobility session. The Proxy Binding Acknowledgement message that is sent in response MUST include the Delegated Mobile Network Prefix option(s). The following considerations apply.
如果代理绑定更新消息具有委派移动网络前缀选项，并且如果本地移动锚配置为委派前缀支持，则本地移动锚必须为该移动会话启用委派移动网络前缀选项。作为响应发送的代理绑定确认消息必须包括委派的移动网络前缀选项。以下注意事项适用。
o If there is at least one instance of the Delegated Mobile Network Prefix option with an ALL_ZERO [RFC5213] prefix value, then this serves as a request for the local mobility anchor to perform the assignment of one or more DMNPs.
o 如果存在至少一个具有全零[RFC5213]前缀值的委托移动网络前缀选项实例，则这将用作本地移动锚执行一个或多个DMNPs的分配的请求。
* A Delegated Mobile Network option with an ALL_ZERO value and with the (V) flag set to a value of (0) is a request for the local mobility anchor to allocate one or more IPv6 prefixes.
* 具有ALL_零值且（V）标志设置为（0）值的委托移动网络选项是本地移动锚分配一个或多个IPv6前缀的请求。
* A Delegated Mobile Network option with an ALL_ZERO value and with the (V) flag set to a value of (1) is a request for the local mobility anchor to allocate one or more IPv4 prefixes.
* 具有ALL_零值且（V）标志设置为值（1）的委托移动网络选项是本地移动锚分配一个或多个IPv4前缀的请求。
* Inclusion of multiple instances of Delegated Mobile Network options with ALL_ZERO values, one with the (V) flag set to a value of (1) and another instance with the (V) flag set to a value of (0), is a request to allocate both IPv4 and IPv6 prefixes.
* 包含多个具有所有_零值的委派移动网络选项实例（一个实例的（V）标志设置为（1）值，另一个实例的（V）标志设置为（0）值）是分配IPv4和IPv6前缀的请求。
o If there are no instances of the Delegated Mobile Network Prefix option present in the request with an ALL_ZERO value but a specific prefix value exists, then this serves as a request for the local mobility anchor to perform the allocation of the requested prefix(es).
o 如果请求中不存在具有ALL_零值但存在特定前缀值的委托移动网络前缀选项的实例，则这将用作本地移动锚执行所请求前缀的分配的请求。
* If any one of the requested prefixes are assigned to some other mobility node, or not from an authorized pool that the local mobility can allocate for that mobility session, then the Proxy Binding Update MUST be rejected by sending a Proxy Binding Acknowledgement message with the Status field set to REQUESTED_DMNP_IN_USE (Requested DMNP is in use).
* 如果请求的前缀中的任何一个被分配给某个其他移动节点，或者不是从本地移动可以为该移动会话分配的授权池分配的，则必须通过发送状态字段设置为requested_DMNP_IN_USE（请求的DMNP正在使用）的代理绑定确认消息来拒绝代理绑定更新.
Upon accepting the Proxy Binding Update, the local mobility anchor MUST send a Proxy Binding Acknowledgement message with the Status field set to 0 (Proxy Binding Update accepted).
在接受代理绑定更新后，本地移动锚必须发送状态字段设置为0（代理绑定更新已接受）的代理绑定确认消息。
o The message MUST include one instance of the Delegated Mobile Network Prefix option for each of the allocated IPv4/IPv6 DMNPs.
o 消息必须包括每个已分配IPv4/IPv6 DMNPs的委派移动网络前缀选项的一个实例。
o The Delegated Mobile Network Prefix (DMNP) list in the mobile router's Binding Cache entry has to be updated with the allocated prefix(es). However, if the request is a de-registration request with a lifetime value of (0), the DMNP list has to be removed along with the Binding Cache entry.
o 移动路由器绑定缓存条目中的委托移动网络前缀（DMNP）列表必须使用分配的前缀进行更新。但是，如果请求是生存期值为（0）的注销请求，则必须将DMNP列表与绑定缓存项一起删除。
o A route (or a platform-specific equivalent function that sets up the forwarding) for each of the allocated prefixes over the tunnel has to be added. However, if the request is a de-registration request, with a lifetime value of (0), all the IPv4/IPv6 delegated prefix routes created for that session have to be removed.
o 必须为隧道上分配的每个前缀添加路由（或设置转发的特定于平台的等效功能）。但是，如果请求是取消注册请求，且生存期值为（0），则必须删除为该会话创建的所有IPv4/IPv6委派前缀路由。
The local mobility anchor MUST advertise a connected route into the routing infrastructure for the IP prefixes delegated to all of the mobile routers that it is serving. This step essentially enables the local mobility anchor to be a routing anchor for those IP prefixes and be able to intercept IP packets sent to those mobile networks.
本地移动性锚点必须将连接的路由播发到路由基础设施中，以获得委派给它所服务的所有移动路由器的IP前缀。该步骤基本上使本地移动锚成为那些IP前缀的路由锚，并且能够截获发送到那些移动网络的IP分组。
On receiving a packet from a correspondent node with the destination address matching any of the mobile router's DMNPs, the local mobility anchor MUST forward the packet through the bidirectional tunnel set up with the mobile access gateway where the mobile router is attached.
当从通信节点接收到目的地址与移动路由器的任何dmnp匹配的分组时，本地移动锚必须通过与移动路由器连接的移动接入网关建立的双向隧道转发该分组。
On receiving an IP packet from the bidirectional tunnel established with the mobile access gateway, the local mobility anchor MUST first decapsulate the packet (remove the outer header) and then use the destination address of the (inner) packet for forwarding decisions. The local mobility anchor MUST ensure that there is an established binding for the mobile router and that the source IP address of the packet is a prefix delegated to a mobile router reachable over that bidirectional tunnel.
在从使用移动接入网关建立的双向隧道接收到IP分组时，本地移动锚必须首先解除分组的封装（移除外部报头），然后使用（内部）分组的目的地地址进行转发决策。本地移动性锚必须确保为移动路由器建立了绑定，并且分组的源IP地址是委派给可通过该双向隧道到达的移动路由器的前缀。
The above forwarding considerations are not applicable to the IP traffic sent/received to/from the mobile router's home address (IPv4 HoA/HNP). For the mobile router's home address traffic, forwarding considerations from [RFC5213] and [RFC5844] continue to apply.
上述转发注意事项不适用于发送/接收到/来自移动路由器的家庭地址（IPv4 HoA/HNP）的IP流量。对于移动路由器的家庭地址通信，来自[RFC5213]和[RFC5844]的转发注意事项继续适用。
The use of DHCPv6, as described in this document, requires message integrity protection and source authentication. The IPsec security mechanism used by Proxy Mobile IPv6 [RFC5213] for securing the signaling messages between the mobile access gateway and the local mobility anchor can be used for securing the DHCP signaling between the mobile access gateway and the local mobility anchor.
如本文档所述，使用DHCPv6需要消息完整性保护和源身份验证。代理移动IPv6[RFC5213]用于保护移动接入网关和本地移动锚之间的信令消息的IPsec安全机制可用于保护移动接入网关和本地移动锚之间的DHCP信令。
The Security Policy Database (SPD) and Security Association Database (SAD) entries necessary to protect the DHCP signaling is specified below. The format of these entries is based on [RFC4877] conventions. The SPD and SAD entries are only example configurations. A particular implementation of mobile access gateway
下面指定了保护DHCP信令所需的安全策略数据库（SPD）和安全关联数据库（SAD）条目。这些条目的格式基于[RFC4877]约定。SPD和SAD条目只是示例配置。移动接入网关的一种特殊实现
and local mobility anchor implementation can configure different SPD and SAD entries as long as they provide the required security for protecting DHCP signaling messages.
本地移动锚实现可以配置不同的SPD和SAD条目，只要它们提供保护DHCP信令消息所需的安全性。
For the examples described in this document, a mobile access gateway with address "mag_address_1" and a local mobility anchor with address "lma_address_1" are assumed.
对于本文档中描述的示例，假设具有地址“mag_address_1”的移动接入网关和具有地址“lma_address_1”的本地移动锚。
mobile access gateway SPD-S:
- IF local_address = mag_address_1 &
remote_address = lma_address_1 & proto = UDP &
local_port = any & remote_port = DHCP
Then use SA1 (OUT) and SA2 (IN)
mobile access gateway SPD-S:
- IF local_address = mag_address_1 &
remote_address = lma_address_1 & proto = UDP &
local_port = any & remote_port = DHCP
Then use SA1 (OUT) and SA2 (IN)
mobile access gateway SAD:
- SA1(OUT, spi_a, lma_address_1, ESP, TRANSPORT):
local_address = mag_address_1 &
remote_address = lma_address_1 &
proto = UDP & remote_port = DHCP
- SA2(IN, spi_b, mag_address_1, ESP, TRANSPORT):
local_address = lma_address_1 &
remote_address = mag_address_1 &
proto = UDP & local_port = DHCP
mobile access gateway SAD:
- SA1(OUT, spi_a, lma_address_1, ESP, TRANSPORT):
local_address = mag_address_1 &
remote_address = lma_address_1 &
proto = UDP & remote_port = DHCP
- SA2(IN, spi_b, mag_address_1, ESP, TRANSPORT):
local_address = lma_address_1 &
remote_address = mag_address_1 &
proto = UDP & local_port = DHCP
local mobility anchor SPD-S:
- IF local_address = lma_address_1 &
remote_address = mag_address_1 & proto = UDP &
local_port = DHCP & remote_port = any
Then use SA2 (OUT) and SA1 (IN)
local mobility anchor SPD-S:
- IF local_address = lma_address_1 &
remote_address = mag_address_1 & proto = UDP &
local_port = DHCP & remote_port = any
Then use SA2 (OUT) and SA1 (IN)
local mobility anchor SAD:
- SA2(OUT, spi_b, mag_address_1, ESP, TRANSPORT):
local_address = lma_address_1 &
remote_address = mag_address_1 &
proto = UDP & local_port = DHCP
- SA1(IN, spi_a, lma_address_1, ESP, TRANSPORT):
local_address = mag_address_1 &
remote_address = lma_address_1 &
proto = UDP & remote_port = DHCP
local mobility anchor SAD:
- SA2(OUT, spi_b, mag_address_1, ESP, TRANSPORT):
local_address = lma_address_1 &
remote_address = mag_address_1 &
proto = UDP & local_port = DHCP
- SA1(IN, spi_a, lma_address_1, ESP, TRANSPORT):
local_address = mag_address_1 &
remote_address = lma_address_1 &
proto = UDP & remote_port = DHCP
The Delegated Mobile Network Prefix option defined in this specification is for use in Proxy Binding Update and Proxy Binding Acknowledgement messages. This option is carried like any other mobility header option as specified in [RFC5213]. Therefore, it inherits from [RFC5213] its security guidelines and does not require any additional security considerations.
本规范中定义的委托移动网络前缀选项用于代理绑定更新和代理绑定确认消息。该选项与[RFC5213]中规定的任何其他移动报头选项相同。因此，它继承了[RFC5213]的安全准则，不需要任何额外的安全考虑。
The use of DHCPv6 in this specification is as defined in the DHCPv6 base specification [RFC3315] and DHCPv6 prefix delegation specification [RFC3633]. The security considerations specified in those specifications apply to this document.
本规范中DHCPv6的使用如DHCPv6基本规范[RFC3315]和DHCPv6前缀委派规范[RFC3633]中所定义。这些规范中规定的安全注意事项适用于本文件。
If IPsec is used, the IPsec security association that is used for protecting the Proxy Binding Update and Proxy Binding Acknowledgement also needs to be used for protecting the DHCPv6 signaling between the mobile access gateway and the local mobility anchor. Considerations specified in Section 5.3 identify the extensions to security policy entries [RFC4301]
如果使用IPsec，则用于保护代理绑定更新和代理绑定确认的IPsec安全关联也需要用于保护移动接入网关和本地移动锚之间的DHCPv6信令。第5.3节中规定的注意事项确定了安全策略条目的扩展[RFC4301]
o This specification defines a new mobility header option, the Delegated Mobile Network Prefix option. This mobility option is described in Section 4.1. The type value 55 for this message has been allocated from the "Mobility Options" registry at http:// www.iana.org/assignments/mobility-parameters.
o 该规范定义了一个新的移动报头选项，即委派移动网络前缀选项。第4.1节描述了该移动性选项。此消息的类型值55已从http://www.iana.org/assignments/Mobility-parameters上的“移动选项”注册表中分配。
o This document also defines two new status code values for use in the Proxy Binding Acknowledgement message, as described in Section 4.2. These status codes are NOT_AUTHORIZED_FOR_DELEGATED_MNP (not authorized for DMNP) with a status code value of 177 and REQUESTED_DMNP_IN_USE (Requested DMNP is in use) with a status code value of 178. These values have been assigned from the same number space as allocated for other status codes [RFC6275].
o 如第4.2节所述，本文件还定义了两个新的状态码值，用于代理绑定确认消息。这些状态代码未授权用于状态代码值为177的授权MNP（未授权用于DMNP）和状态代码值为178的请求DMNP正在使用（请求DMNP正在使用）。这些值是从与分配给其他状态代码相同的数字空间分配的[RFC6275]。
The authors would like to acknowledge Ryuji Wakikawa, Alexandru Petrescu, Behcet Sarikaya, Seil Jeon, Basavaraj Patil, Brian Haberman, and Michal Hoeft for all the discussions and reviews of this document.
作者感谢Wakikawa Ryuji、Alexandru Petrescu、Behcet Sarikaya、Seil Jeon、Basavaraj Patil、Brian Haberman和Michal Hoeft对本文件的所有讨论和评论。
The work of Carlos J. Bernardos has also been partially supported by the European Community's Seventh Framework Programme (FP7-ICT-2009-5) under grant agreement n. 258053 (MEDIEVAL project) and by the Ministry of Science and Innovation of Spain under the QUARTET project (TIN2009-13992-C02-01).
Carlos J.Bernardos的工作也得到了欧洲共同体第七个框架计划（FP7-ICT-2009-5）的部分支持，该计划是根据《赠款协议n》制定的。258053（中世纪项目）和西班牙科学和创新部根据四重奏项目（TIN2009-13992-C02-01）。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3315]Droms，R.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003.
[RFC3633]Troan，O.和R.Droms，“动态主机配置协议（DHCP）版本6的IPv6前缀选项”，RFC 3633，2003年12月。
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005.
[RFC4301]Kent，S.和K.Seo，“互联网协议的安全架构”，RFC 43012005年12月。
[RFC4649] Volz, B., "Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option", RFC 4649, August 2006.
[RFC4649]Volz，B.，“IPv6（DHCPv6）中继代理远程ID选项的动态主机配置协议”，RFC 4649，2006年8月。
[RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture", RFC 4877, April 2007.
[RFC4877]Devarapalli，V.和F.Dupont，“使用IKEv2的移动IPv6操作和修订的IPsec架构”，RFC 4877，2007年4月。
[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月。
[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月。
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, July 2011.
[RFC6275]Perkins，C.，Johnson，D.，和J.Arkko，“IPv6中的移动支持”，RFC 62752011年7月。
[RFC6276] Droms, R., Thubert, P., Dupont, F., Haddad, W., and C. Bernardos, "DHCPv6 Prefix Delegation for Network Mobility (NEMO)", RFC 6276, July 2011.
[RFC6276]Droms，R.，Thubert，P.，Dupont，F.，Haddad，W.，和C.Bernardos，“网络移动（NEMO）的DHCPv6前缀授权”，RFC 62762011年7月。
[RFC6603] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, "Prefix Exclude Option for DHCPv6-based Prefix Delegation", RFC 6603, May 2012.
[RFC6603]Korhonen，J.，Savolainen，T.，Krishnan，S.，和O.Troan，“基于DHCPv6的前缀委托的前缀排除选项”，RFC 6603，2012年5月。
[RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support Terminology", RFC 4885, July 2007.
[RFC4885]Ernst，T.和H-Y.Lach，“网络移动性支持术语”，RFC 48852007年7月。
[RFC6656] Johnson, R., Kinnear, K., and M. Stapp, "Description of Cisco Systems' Subnet Allocation Option for DHCPv4", RFC 6656, July 2012.
[RFC6656]Johnson，R.，Kinnear，K.和M.Stapp，“思科系统DHCPv4子网分配选项的说明”，RFC 66562012年7月。
Authors' Addresses
作者地址
Xingyue Zhou ZTE Corporation No.50 Software Avenue, Yuhuatai District Nanjing China
中国南京市雨花台区软件大道50号星月周中兴通讯公司
Phone: +86-25-8801-4634
EMail: zhou.xingyue@zte.com.cn
Phone: +86-25-8801-4634
EMail: zhou.xingyue@zte.com.cn
Jouni Korhonen Broadcom Porkkalankatu 24 Helsinki FIN-00180 Finland
Jouni Korhonen Broadcom Porkkalankatu 24赫尔辛基FIN-00180芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com
Carl Williams Consultant San Jose, CA USA
美国加利福尼亚州圣何塞市卡尔·威廉姆斯顾问公司
EMail: carlw@mcsr-labs.org
EMail: carlw@mcsr-labs.org
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Carlos J. Bernardos Universidad Carlos III de Madrid Av. Universidad, 30 Leganes, Madrid 28911 Spain
卡洛斯·J·贝尔纳多斯大学卡洛斯三世马德里大道。西班牙马德里勒冈30号大学28911
Phone: +34 91624 6236
EMail: cjbc@it.uc3m.es
URI: http://www.it.uc3m.es/cjbc/
Phone: +34 91624 6236
EMail: cjbc@it.uc3m.es
URI: http://www.it.uc3m.es/cjbc/