Internet Engineering Task Force (IETF) F. Abinader, Ed.
Request for Comments: 6602 Instituto Nokia de Tecnologia
Category: Standards Track S. Gundavelli, Ed.
ISSN: 2070-1721 K. Leung
Cisco
S. Krishnan
Ericsson
D. Premec
Unaffiliated
May 2012
Internet Engineering Task Force (IETF) F. Abinader, Ed.
Request for Comments: 6602 Instituto Nokia de Tecnologia
Category: Standards Track S. Gundavelli, Ed.
ISSN: 2070-1721 K. Leung
Cisco
S. Krishnan
Ericsson
D. Premec
Unaffiliated
May 2012
Bulk Binding Update Support for Proxy Mobile IPv6
代理移动IPv6的批量绑定更新支持
Abstract
摘要
For extending the lifetime of a mobility session, the Proxy Mobile IPv6 specification requires the mobile access gateway to send a Proxy Binding Update message to the local mobility anchor on a per-session basis. In the absence of signaling semantics for performing operations with group-specific scope, this results in a significant amount of signaling traffic on a periodic basis between a given mobile access gateway and a local mobility anchor. This document defines optimizations to the binding update and revocation operations in Proxy Mobile IPv6 for performing operations with group-specific scope with the use of a group identifier.
为了延长移动会话的生存期，代理移动IPv6规范要求移动接入网关在每个会话的基础上向本地移动锚发送代理绑定更新消息。在缺乏用于执行具有组特定作用域的操作的信令语义的情况下，这导致在给定移动接入网关和本地移动性锚之间周期性地产生大量信令业务。本文档定义了对代理移动IPv6中绑定更新和撤销操作的优化，以使用组标识符执行具有组特定作用域的操作。
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/rfc6602.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6602.
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 ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................4
3. Bulk Binding Update Overview ....................................4
3.1. Motivation .................................................4
3.2. General Operation ..........................................5
4. Message Formats .................................................8
4.1. Extensions to Proxy Binding Update Message .................9
4.2. Extensions to Proxy Binding Acknowledgement Message .......10
4.3. Mobile Node Group Identifier Option .......................10
4.4. Status Codes ..............................................11
5. Protocol Considerations ........................................12
5.1. MAG Considerations ........................................12
5.1.1. Extensions to Binding Update List Entry
Data Structure .....................................12
5.1.2. Requesting Bulk Binding Update Support for
a Mobility Session .................................12
5.1.3. Supporting Bulk Binding Updates ....................14
5.2. LMA Considerations ........................................15
5.2.1. Extensions to Binding Cache Entry Data Structure ...15
5.2.2. Enabling Bulk Binding Update Support for a
Mobility Session ...................................16
5.2.3. Supporting Bulk Binding Updates ....................18
6. Protocol Configuration Variables ...............................20
6.1. Local Mobility Anchor - Configuration Variables ...........20
6.2. Mobile Access Gateway - Configuration Variables ...........20
7. IANA Considerations ............................................20
8. Security Considerations ........................................21
9. Acknowledgements ...............................................21
10. References ....................................................22
10.1. Normative References .....................................22
10.2. Informative References ...................................22
1. Introduction ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................4
3. Bulk Binding Update Overview ....................................4
3.1. Motivation .................................................4
3.2. General Operation ..........................................5
4. Message Formats .................................................8
4.1. Extensions to Proxy Binding Update Message .................9
4.2. Extensions to Proxy Binding Acknowledgement Message .......10
4.3. Mobile Node Group Identifier Option .......................10
4.4. Status Codes ..............................................11
5. Protocol Considerations ........................................12
5.1. MAG Considerations ........................................12
5.1.1. Extensions to Binding Update List Entry
Data Structure .....................................12
5.1.2. Requesting Bulk Binding Update Support for
a Mobility Session .................................12
5.1.3. Supporting Bulk Binding Updates ....................14
5.2. LMA Considerations ........................................15
5.2.1. Extensions to Binding Cache Entry Data Structure ...15
5.2.2. Enabling Bulk Binding Update Support for a
Mobility Session ...................................16
5.2.3. Supporting Bulk Binding Updates ....................18
6. Protocol Configuration Variables ...............................20
6.1. Local Mobility Anchor - Configuration Variables ...........20
6.2. Mobile Access Gateway - Configuration Variables ...........20
7. IANA Considerations ............................................20
8. Security Considerations ........................................21
9. Acknowledgements ...............................................21
10. References ....................................................22
10.1. Normative References .....................................22
10.2. Informative References ...................................22
The Proxy Mobile IPv6 base specification [RFC5213] requires the Mobile Node Identifier option to be present in the mobility signaling messages, such as in the Proxy Binding Update (PBU) and Proxy Binding Acknowledgement (PBA) messages. It essentially limits the operational scope of the binding update operation to a single mobility session. These signaling messages lack the capability to identify a group of mobility sessions, so the operations related to binding update and revocation can be performed on all the mobility sessions that are part of that group.
代理移动IPv6基本规范[RFC5213]要求移动节点标识符选项出现在移动信令消息中，例如在代理绑定更新（PBU）和代理绑定确认（PBA）消息中。它本质上将绑定更新操作的操作范围限制为单个移动会话。这些信令消息缺乏识别一组移动会话的能力，因此可以在属于该组的所有移动会话上执行与绑定更新和撤销相关的操作。
There is a need to have semantics for associating a group identity to a mobility session, so the scope of the operations related to binding update and revocation can be extended to all the mobility sessions identified by the group identifier. The group identifier therefore provides a considerably improved mechanism for protocol operations that would otherwise require multiple atomic transactions on a per-mobility-session basis. Following are some of the use cases where the group identifier can be used.
需要具有将组标识关联到移动会话的语义，因此与绑定更新和撤销相关的操作的范围可以扩展到由组标识符标识的所有移动会话。因此，组标识符为协议操作提供了一种大大改进的机制，否则在每个移动会话的基础上需要多个原子事务。下面是一些可以使用组标识符的用例。
o For extending the lifetime of a mobility session, the mobile access gateway (MAG) periodically sends a Proxy Binding Update message to the local mobility anchor (LMA) on a per-session basis. This process can be optimized by allowing the mobile access gateway to send a single Proxy Binding Update [RFC5213] message for a group of mobility sessions identified by a group identifier. Upon accepting the request, the local mobility anchor can update the lifetime of all the mobility sessions that are part of that group.
o 为了延长移动会话的生存期，移动接入网关（MAG）基于每个会话周期性地向本地移动锚（LMA）发送代理绑定更新消息。可以通过允许移动接入网关为由组标识符标识的移动会话组发送单个代理绑定更新[RFC5213]消息来优化该过程。在接受请求时，本地移动锚可以更新属于该组的所有移动会话的生存期。
o On detecting the failure of a specific service card, a local mobility anchor, or a mobile access gateway service hosted on blade architecture system, can potentially request the peer to revoke all the sessions identified by a common group identifier that are hosted on that service card. Potentially, a single Binding Revocation Indication [RFC5846] message carrying the group identifier can be used to revoke all the sessions hosted on that service card, which otherwise needs to be handled on a per-session basis.
o 在检测到特定服务卡的故障时，本地移动锚或刀片体系结构系统上承载的移动访问网关服务可能会请求对等方撤销由该服务卡上承载的公共组标识符标识的所有会话。可能，携带组标识符的单个绑定撤销指示[RFC5846]消息可用于撤销该服务卡上承载的所有会话，否则需要按会话处理。
This document defines a new mobility option, the Mobile Node Group Identifier option, and the extensions to procedures related to binding update and binding revocation for performing binding operations with group-specific scope.
本文档定义了一个新的移动选项，移动节点组标识符选项，以及与绑定更新和绑定撤销相关的过程的扩展，用于执行特定于组的绑定操作。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
All the mobility-related terms used in this document are to be interpreted as defined in the base Proxy Mobile IPv6 specifications [RFC5213] and [RFC5844]. Additionally, this document uses the following terms:
本文档中使用的所有移动相关术语应按照基本代理移动IPv6规范[RFC5213]和[RFC5844]中的定义进行解释。此外，本文件使用以下术语：
Bulk Binding Update
批量绑定更新
A binding update operation that has group-specific scope. A binding operation is associated with a specific mobility session. However, a bulk binding update operation is associated with multiple mobility sessions. This operation is not relevant for new mobility session creation.
具有组特定作用域的绑定更新操作。绑定操作与特定移动会话相关联。但是，批量绑定更新操作与多个移动会话相关联。此操作与新移动会话创建无关。
Bulk Binding Update Group
批量绑定更新组
A group of mobility sessions that are part of the same logical group and therefore share a common group identifier. This group is the bulk binding update group. This bulk binding update group is maintained by both the mobile access gateway and the local mobility anchor, and the grouping logic is local to that node. A mobility session can therefore be identified by two bulk binding update group identifiers, one specific group created by the mobile access gateway and the other specific group created by the local mobility anchor. The bulk binding update group identifiers are exchanged as part of the initial mobility session creation. The mobility entities thereafter can perform operations related to binding update such as lifetime extension and revocation operations on an entire bulk binding update group identified by the group identifier.
属于同一逻辑组的一组移动会话，因此共享一个公共组标识符。此组是大容量绑定更新组。该批量绑定更新组由移动接入网关和本地移动锚维护，分组逻辑是该节点的本地逻辑。因此，可以通过两个批量绑定更新组标识符来识别移动会话，一个特定组由移动接入网关创建，另一个特定组由本地移动锚创建。批量绑定更新组标识符作为初始移动会话创建的一部分进行交换。此后，移动实体可以对由组标识符标识的整个批量绑定更新组执行与绑定更新相关的操作，例如生存期扩展和撤销操作。
In a typical Proxy Mobile IPv6 domain, a local mobility anchor serves multiple mobile access gateways, and the capacity of that node with respect to the number of mobility sessions that it can host is quite high, typically in the order of a few millions. As the number of
在典型的代理移动IPv6域中，本地移动锚服务于多个移动接入网关，并且该节点相对于其可以承载的移动会话数量的容量相当高，通常在数百万左右。作为
mobility sessions hosted by a local mobility anchor goes up, so does the amount of signaling traffic related to periodic binding update traffic.
由本地移动锚承载的移动会话增加，与定期绑定更新通信相关的信令通信量也增加。
The currently specified approach of the binding update procedure for extending the lifetimes of multiple mobility sessions (where the mobile access gateway is required to send a unique binding update message for each mobility session even when there is no change to the session state) is inefficient or sub-optimal. These periodic binding update messages consume a significant amount of network resources at both the peers, in terms of processing power and network bandwidth. There is an opportunity to optimize the signaling procedures by allowing the local mobility anchor and the mobile access gateway to perform bulk binding update operations. This document specifies extensions to Proxy Mobile IPv6 signaling for performing binding update and revocation operations on a group of mobility sessions. These extensions do not take away the existing functionality of performing binding operations on a single mobility session.
当前指定的用于延长多个移动会话的生存期的绑定更新过程的方法（其中移动接入网关被要求为每个移动会话发送唯一的绑定更新消息，即使会话状态没有改变）是低效的或次优的。就处理能力和网络带宽而言，这些定期绑定更新消息在两个对等点上都会消耗大量的网络资源。有机会通过允许本地移动锚和移动接入网关执行批量绑定更新操作来优化信令过程。本文档指定了代理移动IPv6信令的扩展，用于在一组移动会话上执行绑定更新和撤销操作。这些扩展不会取消在单个移动会话上执行绑定操作的现有功能。
The bulk binding update mechanism specified in this document allows the mobile access gateway and the local mobility anchor to perform binding update and revocation operations on a group of mobility sessions. As part of the initial signaling during mobility session establishment, the local mobility anchor and the mobile access gateway exchange the respective bulk binding update group identifiers for that mobility session. Subsequently, both the peers can perform bulk operations on those groups by presenting the bulk binding update group identifier in the signaling messages.
本文档中指定的批量绑定更新机制允许移动接入网关和本地移动锚对一组移动会话执行绑定更新和撤销操作。作为移动会话建立期间初始信令的一部分，本地移动锚和移动接入网关交换该移动会话的相应批量绑定更新组标识符。随后，两个对等方可以通过在信令消息中呈现批量绑定更新组标识符来对这些组执行批量操作。
When sending a Proxy Binding Update message after detecting a new mobile node on its access link, a mobile access gateway can request the local mobility anchor to assign a bulk binding update group identifier for the mobile node's mobility session. This is indicated by setting the (B) flag in the Proxy Binding Update to a value of (1). The mobile access gateway will also assign a bulk binding update group identifier (or it may assign a default bulk binding update group - ALL-SESSIONS) and include that in the Mobile Node Group Identifier option.
当在其接入链路上检测到新的移动节点之后发送代理绑定更新消息时，移动接入网关可以请求本地移动锚为移动节点的移动会话分配批量绑定更新组标识符。这通过将代理绑定更新中的（B）标志设置为（1）值来表示。移动接入网关还将分配批量绑定更新组标识符（或者它可以分配默认批量绑定更新组-所有会话），并将其包括在移动节点组标识符选项中。
Upon accepting the request, the local mobility anchor will group the mobility session to a specific bulk binding update group (or it may assign it to the default bulk binding update group - ALL-SESSIONS) and return this bulk binding update group identifier in a Proxy Binding Acknowledgement message. It will also set the (B) flag in
在接受请求后，本地移动锚将移动会话分组到特定的批量绑定更新组（或者它可以将其分配到默认批量绑定更新组-所有会话），并在代理绑定确认消息中返回该批量绑定更新组标识符。它还将在中设置（B）标志
the Proxy Binding Acknowledgement message to a value of (1). The bulk binding update group identifier is carried in the Mobile Node Group Identifier option, described in Section 4.3.
代理绑定确认消息的值为（1）。批量绑定更新组标识符包含在移动节点组标识符选项中，如第4.3节所述。
Once the bulk binding update group identifiers are exchanged, the local mobility anchor and the mobile access gateway can perform binding operations on those entire groups, by including the bulk binding update group identifier in the signaling messages. For example, the mobile access gateway can extend the lifetime of all the mobility sessions that are part of a group by sending a single Proxy Binding Update message with that bulk binding update group identifier. Similarly, the local mobility anchor can revoke all the mobility sessions that are part of a group by including that group identifier in the Proxy Binding Revocation message. When initiating bulk binding update operations on a group of mobility sessions, the group identifier that is carried in the Mobile Node Group Identifier option is always the identifier of the local group, and not the identifier of the group on the peer.
一旦交换了批量绑定更新组标识符，本地移动锚和移动接入网关就可以通过在信令消息中包括批量绑定更新组标识符来对这些整个组执行绑定操作。例如，移动接入网关可以通过发送具有该批量绑定更新组标识符的单个代理绑定更新消息来延长作为组的一部分的所有移动会话的生存期。类似地，本地移动锚可以通过在代理绑定撤销消息中包括该组标识符来撤销作为组的一部分的所有移动会话。在移动会话组上启动批量绑定更新操作时，移动节点组标识符选项中携带的组标识符始终是本地组的标识符，而不是对等方上的组标识符。
Figure 1 explains the operational sequence of the bulk binding update and revocation operations on a group of mobile nodes (MN1, MN2, and MN3).
图1解释了一组移动节点（MN1、MN2和MN3）上的批量绑定更新和撤销操作的操作顺序。
MAG LMA
(1) | |
MN1-------| (2) PBU |
|--------------------------->|
| * (3)
| (4) PBA |
|<---------------------------|
* (5) |
(6) | |
MN2-------| |
* (7)........................|
(8) | |
MN3-------| |
* (9)........................|
| |
| (10) PBU |
|--------------------------->|
| * (11)
| (12) PBA |
|<---------------------------|
* (13)
| |
| (14) BRI |
|<---------------------------|
| * (15)
| (16) BRA |
|--------------------------->|
* (17) |
| |
MAG LMA
(1) | |
MN1-------| (2) PBU |
|--------------------------->|
| * (3)
| (4) PBA |
|<---------------------------|
* (5) |
(6) | |
MN2-------| |
* (7)........................|
(8) | |
MN3-------| |
* (9)........................|
| |
| (10) PBU |
|--------------------------->|
| * (11)
| (12) PBA |
|<---------------------------|
* (13)
| |
| (14) BRI |
|<---------------------------|
| * (15)
| (16) BRA |
|--------------------------->|
* (17) |
| |
Figure 1: Exchange of Group Identifier
图1：组标识符的交换
o (1) to (2): The MAG detects the mobile node's (MN1) attachment to the access link. The MAG groups the mobile node to a specific bulk binding update group, (M1). The MAG notifies this group identifier to the LMA by including it in the Mobile Node Group Identifier option of the PBU message.
o （1） to（2）：MAG检测移动节点（MN1）与接入链路的连接。MAG将移动节点分组到特定的批量绑定更新组（M1）。MAG通过将该组标识符包括在PBU消息的移动节点组标识符选项中来通知LMA。
o (3): Upon accepting the PBU, the LMA creates a mobility session and groups the mobility session to a specific bulk binding update group, (L1). The LMA updates the mobile node's Binding Cache entry to include the bulk binding update group identifier, (L1), and the bulk binding update group identifier presented by the MAG, (M1). The LMA also notifies the MAG about the bulk binding update group identifier (L1), by including it in the PBA.
o （3） ：在接受PBU时，LMA创建移动会话并将移动会话分组到特定的批量绑定更新组（L1）。LMA更新移动节点的绑定缓存条目以包括由MAG呈现的批量绑定更新组标识符（L1）和批量绑定更新组标识符（M1）。LMA还通过将其包括在PBA中来通知MAG关于批量绑定更新组标识符（L1）。
o (4) to (5): Upon receiving the PBA, the MAG updates the Binding Update List entry for that mobility session to include the bulk binding update group identifiers (L1) and (M1). At this point, both the LMA and MAG are aware of the mobile node's bulk binding update group identifiers assigned by the peers.
o （4） 至（5）：在接收到PBA时，MAG更新该移动性会话的绑定更新列表条目以包括批量绑定更新组标识符（L1）和（M1）。此时，LMA和MAG都知道由对等方分配的移动节点的批量绑定更新组标识符。
o (6) to (9): The above steps (1 through 5) are repeated here for MN2 and MN3; details are omitted. At the end of step (9), the MAG completes the signaling with the LMA. The MAG assigns the mobile nodes MN2 and MN3 to bulk binding update groups (M1) and (M2) respectively, while the LMA assigns them both to the same bulk binding update group, (L1).
o （6） 至（9）：此处对MN2和MN3重复上述步骤（1至5）；细节被省略。在步骤（9）的末尾，MAG完成与LMA的信令。MAG将移动节点MN2和MN3分别分配给批量绑定更新组（M1）和（M2），而LMA将它们分配给相同的批量绑定更新组（L1）。
o At this point, LMA has assigned MN1, MN2, and MN3 to the bulk binding update group (L1), while the MAG has assigned MN1 and MN2 to group (M1) and MN3 to group (M2). Both peers can now perform binding operations on a group of mobility sessions identified by the respective bulk binding update group identifier.
o 此时，LMA已将MN1、MN2和MN3分配给批量绑定更新组（L1），而MAG已将MN1和MN2分配给组（M1），将MN3分配给组（M2）。两个对等方现在都可以对由各自的批量绑定更新组标识符标识的移动会话组执行绑定操作。
o (10) to (13): The MAG sends a Proxy Binding Update message for extending the lifetime of all the mobility sessions that are part of the bulk binding update group (M1). It includes the bulk binding update group identifier (M1) in the PBU. Upon accepting the PBU, the LMA extends the lifetime of both MN1 and MN2, which are part of the group (M1).
o （10） to（13）：MAG发送代理绑定更新消息，以延长作为批量绑定更新组（M1）一部分的所有移动会话的生存期。它包括PBU中的批量绑定更新组标识符（M1）。一旦接受PBU，LMA将延长MN1和MN2的寿命，这两个组都是组（M1）的一部分。
o (14) to (17): The LMA decides to revoke all the sessions that are part of bulk binding update group (L1). The LMA sends a Binding Revocation Indication (BRI) message with the bulk binding update group identifier (L1). Upon accepting the BRI message, the MAG revokes all the MN1, MN2, and MN3 mobility sessions, which are part of that bulk binding update group (L1), and sends a Binding Revocation Acknowledgement (BRA) [RFC5846] message.
o （14） to（17）：LMA决定撤销属于批量绑定更新组（L1）的所有会话。LMA发送带有批量绑定更新组标识符（L1）的绑定撤销指示（BRI）消息。在接受BRI消息后，MAG撤销属于该批量绑定更新组（L1）的所有MN1、MN2和MN3移动会话，并发送绑定撤销确认（BRA）[RFC5846]消息。
This section identifies the extensions to Proxy Mobile IPv6 signaling messages that are required for supporting this specification.
本节确定了支持本规范所需的代理移动IPv6信令消息的扩展。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|H|L|K|M|R|P|F|T|B| Reserved | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|H|L|K|M|R|P|F|T|B| Reserved | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Extensions to Proxy Binding Update Message
图2：代理绑定更新消息的扩展
A new flag, the Bulk-Binding-Update flag (B), is defined in the Proxy Binding Update message specified in [RFC5213]. The bit value of Bulk-Binding-Update flag (B) in the flags field of the message will be 0x0040.
[RFC5213]中指定的代理绑定更新消息中定义了一个新标志，即批量绑定更新标志（B）。消息标志字段中大容量绑定更新标志（B）的位值将为0x0040。
If the Bulk-Binding-Update flag (B) is set to a value of (1), it informs the local mobility anchor to enable bulk binding update support for the mobility session associated with this message. If the (B) flag is set to a value of (0), the local mobility anchor MUST exclude the mobility session associated with this message from any bulk-binding-related operations and any binding update, or binding revocation operations with bulk-specific scope will not be relevant to that mobility session.
如果批量绑定更新标志（B）设置为（1）的值，它将通知本地移动锚，以便为与此消息相关联的移动会话启用批量绑定更新支持。如果（B）标志设置为（0）值，则本地移动锚必须将与此消息关联的移动会话从任何批量绑定相关操作和任何绑定更新中排除，否则具有批量特定作用域的绑定撤销操作将与该移动会话无关。
This flag is relevant only for Proxy Mobile IPv6 and therefore MUST be set to the value of (0) when the (P) flag is set to a value of (0).
此标志仅与代理移动IPv6相关，因此当（P）标志设置为值（0）时，必须将其设置为值（0）。
All other fields in the Proxy Binding Update message and the mobility options that can be carried in the message conform to the appropriate specifications.
代理绑定更新消息中的所有其他字段以及消息中可以携带的移动选项都符合相应的规范。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |K|R|P|T|B| Res.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |K|R|P|T|B| Res.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Extensions to Proxy Binding Acknowledgement Message
图3：代理绑定确认消息的扩展
A new flag, the Bulk-Binding-Update flag (B), is defined in the Proxy Binding Acknowledgement message specified in [RFC5213]. The bit value of Bulk-Binding-Update flag (B) in the flags field of the message is 0x08.
[RFC5213]中指定的代理绑定确认消息中定义了一个新标志，即批量绑定更新标志（B）。消息标志字段中大容量绑定更新标志（B）的位值为0x08。
If the Bulk-Binding-Update flag (B) is set to a value of (1), it serves as an indication to the mobile access gateway that the local mobility anchor has enabled bulk binding update support for the mobility session associated with this message. The value of the flag MUST be set to the value of (0) if the value of the (B) flag in the Proxy Binding Update message that it received from the mobile access gateway was set to a value of (0).
如果批量绑定更新标志（B）被设置为值（1），则其用作向移动接入网关指示本地移动锚已经为与该消息相关联的移动会话启用了批量绑定更新支持。如果从移动接入网关接收的代理绑定更新消息中的（B）标志的值设置为（0），则该标志的值必须设置为（0）。
This flag is relevant only for Proxy Mobile IPv6 and therefore MUST be set to a value of (0) when the (P) flag is set to a value of (0).
此标志仅与代理移动IPv6相关，因此当（P）标志设置为值（0）时，必须将其设置为值（0）。
All other fields in the Proxy Binding Acknowledgement message and the mobility options that can be carried in the message conform to the appropriate specifications.
代理绑定确认消息中的所有其他字段以及消息中可携带的移动选项符合适当的规范。
A new option, the Mobile Node Group Identifier option, is defined for use in Proxy Mobile IPv6 signaling messages exchanged between a local mobility anchor and a mobile access gateway. This option is used for carrying the mobile node's group identifier. There can be multiple instances of this option in a given signaling message; however, each of the instances SHOULD have a different sub-type value. This option is a generic option, and this specification uses only the sub-type value of (1).
定义了一个新选项，即移动节点组标识符选项，用于在本地移动锚和移动接入网关之间交换的代理移动IPv6信令消息中。此选项用于携带移动节点的组标识符。在给定的信令消息中可以有多个该选项的实例；但是，每个实例都应具有不同的子类型值。此选项是通用选项，并且此规范仅使用子类型值（1）。
The type value for this option is 50.
此选项的类型值为50。
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 | Sub-type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mobile Node Group 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 | Sub-type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mobile Node Group Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Mobile Node Group Identifier Option
图4：移动节点组标识符选项
Type <50>
类型<50>
Length This is an 8-bit unsigned integer indicating the length in octets of this option, excluding the type and length fields. The value for this field MUST be set to a value of (6).
长度这是一个8位无符号整数，指示此选项的长度（以八位字节为单位），不包括类型和长度字段。此字段的值必须设置为（6）的值。
Sub-type This 8-bit field identifies the specific mobile node's group type. This number space will be managed by the IANA. The sub-type value of (1) is reserved for the Bulk Binding Update Group.
子类型此8位字段标识特定移动节点的组类型。此数字空间将由IANA管理。（1）的子类型值是为批量绑定更新组保留的。
Reserved This 8-bit field is unused for now. The value MUST be initialized to (0) by the sender and MUST be ignored by the receiver.
保留此8位字段目前未使用。发送方必须将该值初始化为（0），接收方必须忽略该值。
Mobile Node Group Identifier This 32-bit field contains the mobile node's group identifier. The value of (0) is reserved and SHOULD NOT be used. The value of (1) ALL-SESSIONS is the default group of all mobility sessions established between a given local mobility anchor and a mobile access gateway.
移动节点组标识符此32位字段包含移动节点的组标识符。（0）的值为保留值，不应使用。（1）ALL-SESSIONS的值是在给定的本地移动锚和移动接入网关之间建立的所有移动会话的默认组。
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节定义的相同数字空间分配的。
INVALID_MOBILE_NODE_GROUP_IDENTIFIER: 175
无效的移动节点组标识符：175
Invalid group identifier value in the request
请求中的组标识符值无效
The following are the considerations relevant to the mobile access gateway when supporting this specification.
以下是支持本规范时与移动接入网关相关的注意事项。
The conceptual Binding Update List entry data structure maintained by the mobile access gateway, described in Section 6.1 of [RFC5213], is extended to include the following REQUIRED additional fields:
[RFC5213]第6.1节中描述的移动接入网关维护的概念绑定更新列表条目数据结构已扩展，以包括以下所需的附加字段：
o MAG-Bulk-Binding-Update-Group-Id This is the bulk binding update group identifier assigned by this mobile access gateway for this mobility session. It is a 32-bit unsigned integer. This identifier is not globally unique within a Proxy Mobile IPv6 domain; the same group identifier value may be used by other nodes.
o MAG批量绑定更新组Id这是此移动访问网关为此移动会话分配的批量绑定更新组标识符。它是一个32位无符号整数。此标识符在代理移动IPv6域中不是全局唯一的；其他节点可以使用相同的组标识符值。
o LMA-Bulk-Binding-Update-Group-Id This is the bulk binding update group identifier assigned by the local mobility anchor for this mobility session. It is a 32-bit unsigned integer. This identifier is received in the Mobile Node Group Identifier option of the Proxy Binding Acknowledgement message. This identifier is not globally unique within a Proxy Mobile IPv6 domain; the same group identifier value may be used by other nodes.
o LMA批量绑定更新组Id这是本地移动锚为此移动会话分配的批量绑定更新组标识符。它是一个32位无符号整数。该标识符在代理绑定确认消息的移动节点组标识符选项中接收。此标识符在代理移动IPv6域中不是全局唯一的；其他节点可以使用相同的组标识符值。
The following are the considerations for the mobile access gateway for requesting bulk binding update support for a mobility session.
以下是移动接入网关为移动会话请求批量绑定更新支持的注意事项。
o When sending a Proxy Binding Update message to the local mobility anchor, the mobile access gateway can choose to request that the local mobility anchor enable bulk binding update support for the mobility session associated with that Proxy Binding Update request. When making such request, the Bulk-Binding-Update flag (B) in the request MUST be set to a value of (1) and the Mobile Node Group Identifier option MUST be present. The decision to request bulk binding update support for a mobile node is a matter of local policy at the mobile access gateway and is controlled by the configuration variable RequestBulkBindingUpdateSupportForMobilitySession.
o 当向本地移动锚发送代理绑定更新消息时，移动接入网关可以选择请求本地移动锚为与该代理绑定更新请求相关联的移动会话启用批量绑定更新支持。在发出此类请求时，请求中的批量绑定更新标志（B）必须设置为值（1），并且必须存在移动节点组标识符选项。请求移动节点的批量绑定更新支持的决定取决于移动访问网关的本地策略，并由配置变量RequestBulkBindingUpdateSupportForMobilitySession控制。
o The mobile access gateway MUST assign a bulk binding update group identifier for the mobility session. Considerations on how the mobile access gateway assigns a group identifier to a mobility session is outside the scope of this document. This group identifier can be unique to the service card on which the mobility session is hosted or based on other grouping considerations. When no such group assignment is done, the mobile access gateway SHOULD assign the default group identifier value of (ALL-SESSIONS). This assigned group identifier value MUST be present in the Mobile Node Group Identifier option, and the sub-type value in the option MUST be set to the value of (1) (Bulk Binding Update Group).
o 移动接入网关必须为移动会话分配批量绑定更新组标识符。关于移动接入网关如何将组标识符分配给移动会话的考虑超出了本文档的范围。该组标识符可以是承载移动会话的服务卡的唯一标识符，也可以是基于其他分组考虑的唯一标识符。当未完成此类组分配时，移动接入网关应分配默认组标识符值（ALL-SESSIONS）。此分配的组标识符值必须出现在移动节点组标识符选项中，并且该选项中的子类型值必须设置为（1）（批量绑定更新组）的值。
o If the received Proxy Binding Acknowledgement message has the status code value set to (0) (Proxy Binding Update accepted) and the Bulk-Binding-Update flag (B) set to a value of (0), in response to a Proxy Binding Update request with the Bulk-Binding-Update flag (B) set to a value of (1), it is an indication that the local mobility anchor has denied the request for enabling bulk binding update support for that mobility session and that the mobility session is not associated with any bulk binding update group. The mobile access gateway SHOULD set the bulk binding update group identifier values LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id to (0) in the Binding Update List entry for that mobility session. Furthermore, the mobility session should be excluded from any bulk binding update operations.
o 如果接收到的代理绑定确认消息的状态代码值设置为（0）（代理绑定更新已接受）且批量绑定更新标志（B）设置为值（0），则响应代理绑定更新请求，批量绑定更新标志（B）设置为值（1），这表示本地移动锚已拒绝为该移动会话启用批量绑定更新支持的请求，并且该移动会话未与任何批量绑定更新组关联。移动接入网关应将该移动会话的绑定更新列表条目中的批量绑定更新组标识符值LMA bulk binding update group Id和MAG bulk binding update group Id设置为（0）。此外，移动会话应该从任何批量绑定更新操作中排除。
o If the received Proxy Binding Acknowledgement message has the status code value set to (0) (Proxy Binding Update accepted) and the Bulk-Binding-Update flag (B) in the reply is set to a value of (1), it is an indication that the local mobility anchor has accepted the request to allow bulk binding update support for that mobility session. Furthermore, the Mobile Node Group Identifier option in the reply, with the sub-type value of (1) (Bulk Binding Update Group), contains the bulk binding update group identifier for that mobility session assigned by the local mobility anchor. The mobile access gateway MUST update the LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id parameters in the Binding Update List entry for that mobility session. However, if the received Proxy Binding Acknowledgement message has the Bulk-Binding-Update flag (B) set to a value of (1), but the Mobile Node Group Identifier option is not present, the message MUST be considered malformed and ignored.
o 如果接收到的代理绑定确认消息的状态代码值设置为（0）（代理绑定更新已接受），并且应答中的批量绑定更新标志（B）设置为值（1），则表示本地移动锚已接受允许该移动会话的批量绑定更新支持的请求。此外，应答中的子类型值为（1）（批量绑定更新组）的移动节点组标识符选项包含由本地移动锚分配的该移动会话的批量绑定更新组标识符。移动接入网关必须更新该移动会话的绑定更新列表条目中的LMA批量绑定更新组Id和MAG批量绑定更新组Id参数。但是，如果接收到的代理绑定确认消息的批量绑定更新标志（B）设置为值（1），但移动节点组标识符选项不存在，则必须将该消息视为格式错误并忽略。
o If, at any point in time, the mobile access gateway chooses to request the local mobility anchor to disable bulk binding update support for a mobility session, it MUST send a Proxy Binding Update message with the (B) flag set to a value of (0), and the
o 如果在任何时间点，移动接入网关选择请求本地移动锚来禁用移动会话的批量绑定更新支持，则它必须发送（B）标志设置为（0）值的代理绑定更新消息，并且
Mobile Node Group Identifier option MUST NOT be present. This message is sent as a normal binding update request for lifetime extension. Requirements from Section 6.9.1 of [RFC5213] apply. Furthermore, the mobile access gateway MUST update the Binding Update List entry by setting the bulk binding update group identifier values LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id to (0), and the mobility session MUST be excluded from any bulk binding update operations.
移动节点组标识符选项不得存在。此消息作为正常绑定更新请求发送，以延长生存期。[RFC5213]第6.9.1节的要求适用。此外，移动接入网关必须通过将批量绑定更新组标识符值LMA批量绑定更新组Id和MAG批量绑定更新组Id设置为（0）来更新绑定更新列表条目，并且必须从任何批量绑定更新操作中排除移动性会话。
The following section identifies the considerations for a mobile access gateway performing binding update and revocation operations with group-specific scope.
下一节确定了移动访问网关在特定于组的范围内执行绑定更新和撤销操作的注意事项。
o For extending the lifetime of all mobility sessions that share the same bulk binding update group identifier, the mobile access gateway can choose to send a bulk binding update request. To make such a request, it can send a Proxy Binding Update message to the local mobility anchor, including the Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group) and with the Bulk-Binding-Update flag (B) set to a value of (0). The identifier value in the option MUST be set to the bulk binding update group identifier of the group for which bulk binding update operation is being requested. The message MUST NOT include any individual session identifiers such as the Mobile Node Identifier option [RFC4283], the Home Network Prefix option [RFC5213], the IPv4 Home Address Request option [RFC5844], or the GRE Key option [RFC5845]. All the considerations from Section 5.3.3 of [RFC5213] MUST be followed when sending the bulk binding update request, with the exception related to the use of Mobile Node Group Identifier option in place of the individual session identifiers (Mobile Node Identifier option, Home Network Prefix option, GRE Key option, and IPv4 Home Address Request option).
o 为了延长共享相同批量绑定更新组标识符的所有移动会话的生存期，移动接入网关可以选择发送批量绑定更新请求。为了发出这样的请求，它可以向本地移动锚发送代理绑定更新消息，包括子类型值为（1）（批量绑定更新组）且批量绑定更新标志（B）设置为值（0）的移动节点组标识符选项。选项中的标识符值必须设置为请求批量绑定更新操作的组的批量绑定更新组标识符。消息不得包括任何单独的会话标识符，如移动节点标识符选项[RFC4283]、家庭网络前缀选项[RFC5213]、IPv4家庭地址请求选项[RFC5844]或GRE密钥选项[RFC5845]。发送批量绑定更新请求时，必须遵循[RFC5213]第5.3.3节中的所有注意事项，使用移动节点组标识符选项代替单个会话标识符的情况除外（移动节点标识符选项、家庭网络前缀选项、GRE密钥选项和IPv4家庭地址请求选项）。
o When requesting binding revocation for all the sessions that share the same bulk binding update group identifier, the mobile access gateway can choose to send a bulk revocation request. To make such a request, it can send a Binding Revocation Indication message [RFC5846] to the local mobility anchor, including the Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group). The identifier value in the option MUST be set to the bulk binding update group identifier of the group for which bulk binding update operation is being requested. The message MUST NOT include any individual session identifiers such as the Mobile Node Identifier option [RFC4283], the Home Network Prefix option [RFC5213], the IPv4 Home Address Request option [RFC5844], or the GRE Key option [RFC5845]. All the
o 当为共享相同批量绑定更新组标识符的所有会话请求绑定撤销时，移动访问网关可以选择发送批量撤销请求。为了发出这样的请求，它可以向本地移动锚发送绑定撤销指示消息[RFC5846]，包括子类型值为（1）（批量绑定更新组）的移动节点组标识符选项。选项中的标识符值必须设置为请求批量绑定更新操作的组的批量绑定更新组标识符。消息不得包括任何单独的会话标识符，如移动节点标识符选项[RFC4283]、家庭网络前缀选项[RFC5213]、IPv4家庭地址请求选项[RFC5844]或GRE密钥选项[RFC5845]。所有的
considerations from Section 9.2 of [RFC5846] MUST be followed when sending the bulk binding update request, with the exception related to the use of Mobile Node Group Identifier option in place of the individual session identifiers (Mobile Node Identifier option, Home Network Prefix option, GRE Key option, IPv4 Home Address Request option).
发送批量绑定更新请求时，必须遵循[RFC5846]第9.2节的注意事项，但使用移动节点组标识符选项代替单个会话标识符（移动节点标识符选项、家庭网络前缀选项、GRE密钥选项、IPv4家庭地址请求选项）的情况除外。
o Any time the mobile access gateway receives a Binding Revocation Indication message [RFC5846], with a Mobile Node Group Identifier option present in the request and with the sub-type value of (1) (Bulk Binding Update Group), this message serves as a bulk revocation request, with the request scope for revoking of all the mobility sessions that are part of that bulk binding update group specific to that local mobility anchor and identified by the group identifier in the Mobile Node Group Identifier option.
o 当移动接入网关接收到绑定撤销指示消息[RFC5846]，且请求中存在移动节点组标识符选项且子类型值为（1）（批量绑定更新组）时，该消息用作批量撤销请求，请求范围为撤销所有移动会话，这些移动会话是特定于该本地移动锚的批量绑定更新组的一部分，并由移动节点组标识符选项中的组标识符标识。
o All the considerations from [RFC5846] apply when processing a binding revocation request, except making the scope of the operation apply to a set of mobility sessions identified by the bulk binding update group identifier present in the request.
o [RFC5846]中的所有注意事项在处理绑定撤销请求时适用，但使操作范围适用于由请求中存在的批量绑定更新组标识符标识的一组移动会话除外。
o If the received Binding Revocation Indication message includes the Mobile Node Identifier option [RFC4283], the Home Network Prefix option [RFC5213], the IPv4 Home Address Request option [RFC5844], or the GRE Key option [RFC5845], the mobile access gateway MUST consider this as an invalid message; it MUST reject the Binding Revocation Indication message and send a Binding Revocation Acknowledgement message with the Status field set to a value of 128 (Binding Does NOT Exist).
o 如果接收到的绑定撤销指示消息包括移动节点标识符选项[RCF483]、家庭网络前缀选项[RCF5213]、IPv4家庭地址请求选项[RCF5844 ]或GRE密钥选项[RCF5845 ]，则移动接入网关必须将其视为无效消息；它必须拒绝绑定撤销指示消息，并发送状态字段设置为128（绑定不存在）的绑定撤销确认消息。
The following are the considerations relevant to a local mobility anchor when supporting this specification.
以下是支持本规范时与本地移动锚相关的注意事项。
The conceptual Binding Cache entry data structure maintained by the local mobility anchor, described in Section 5.1 of [RFC5213], is extended to include the following REQUIRED additional fields.
[RFC5213]第5.1节中描述的由本地移动锚维护的概念绑定缓存条目数据结构被扩展，以包括以下所需的附加字段。
o MAG-Bulk-Binding-Update-Group-Id
o MAG批量绑定更新组Id
This is the bulk binding update group identifier assigned by the mobile access gateway for this mobility session. It is a 32-bit unsigned integer. This identifier is received in the Mobile Node Group Identifier option of the Proxy Binding Update message. This
这是移动接入网关为此移动会话分配的批量绑定更新组标识符。它是一个32位无符号整数。此标识符在代理绑定更新消息的移动节点组标识符选项中接收。这
identifier is not globally unique within a Proxy Mobile IPv6 domain; the same group identifier value may be used by other nodes.
标识符在代理移动IPv6域中不是全局唯一的；其他节点可以使用相同的组标识符值。
o LMA-Bulk-Binding-Update-Group-Id
o LMA批量绑定更新组Id
This is the bulk binding update group identifier assigned by this local mobility anchor for this mobility session. It is a 32-bit unsigned integer. This identifier is not globally unique within a Proxy Mobile IPv6 domain; the same group identifier value may be used by other nodes.
这是此本地移动锚为此移动会话分配的批量绑定更新组标识符。它是一个32位无符号整数。此标识符在代理移动IPv6域中不是全局唯一的；其他节点可以使用相同的组标识符值。
The local mobility anchor will process a received Proxy Binding Update message as specified in [RFC5213]. However, if the (B) flag in the received Proxy Binding Update message is set to a value of (1) and if it includes a Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group), the following processing takes place:
本地移动锚将按照[RFC5213]中的规定处理接收到的代理绑定更新消息。然而，如果所接收的代理绑定更新消息中的（B）标志被设置为值（1），并且如果其包括子类型值为（1）（批量绑定更新组）的移动节点组标识符选项，则发生以下处理：
o If the (B) flag in the received Proxy Binding Update message is set to a value of (1) and if the Mobile Node Group Identifier option is present in the request, the message serves as a request to the local mobility anchor to enable bulk binding update support for that mobility session.
o 如果接收到的代理绑定更新消息中的（B）标志被设置为值（1），并且如果请求中存在移动节点组标识符选项，则该消息用作对本地移动锚的请求，以启用对该移动会话的批量绑定更新支持。
o Upon successful processing and acceptance of the Proxy Binding Update, the local mobility anchor can choose to enable bulk binding update support for this mobility session. The decision whether to enable bulk binding update support for that mobility session is a matter of local policy and is controlled by the configuration variable AcceptBulkBindingUpdateReqForMobilitySession.
o 成功处理并接受代理绑定更新后，本地移动锚可以选择为此移动会话启用批量绑定更新支持。是否为该移动会话启用批量绑定更新支持的决定取决于本地策略，并由配置变量AcceptBulkBindingUpdateReqForMobilitySession控制。
o For enabling the bulk binding update support for the mobility session, the local mobility anchor MUST associate the mobility session to a specific bulk binding update group locally. The specific details on how the local mobility anchor associates the given mobility session to a specific bulk binding update group is outside the scope of this document. The local mobility anchor can choose to assign a default bulk binding update group identifier value of (ALL-SESSIONS), indicating that all the mobility sessions from that mobile access gateway are part of that group. The local mobility anchor SHOULD update the bulk binding update group identifier values in the Binding Cache entry, LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id, to the respective values.
o 为了支持移动会话的批量绑定更新，本地移动锚必须将移动会话与本地特定的批量绑定更新组相关联。本地移动锚如何将给定移动会话关联到特定批量绑定更新组的具体细节不在本文档的范围内。本地移动锚可以选择分配默认批量绑定更新组标识符值（ALL-SESSIONS），指示来自该移动接入网关的所有移动会话都是该组的一部分。本地移动锚应将绑定缓存项中的批量绑定更新组标识符值LMA批量绑定更新组Id和MAG批量绑定更新组Id更新为相应的值。
o If the bulk binding update support is enabled for the mobile node's mobility session, the local mobility anchor MUST send the assigned bulk binding update group identifier as part of the Mobile Node Group Identifier option, with the sub-type value of (1) (Bulk Binding Update Group) in the Proxy Binding Acknowledgement message that it sends to the mobile access gateway. The (B) flag in the Proxy Binding Acknowledgement message MUST be set to value of (1).
o 如果为移动节点的移动会话启用了批量绑定更新支持，则本地移动锚必须发送分配的批量绑定更新组标识符，作为移动节点组标识符选项的一部分，子类型值为（1）（批量绑定更新组）在它发送到移动接入网关的代理绑定确认消息中。代理绑定确认消息中的（B）标志必须设置为值（1）。
o If the bulk binding update support is not enabled for the mobility session, the local mobility anchor MUST NOT include the Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group), in the Proxy Binding Acknowledgement message that it sends to the mobile access gateway. Furthermore, the (B) flag in the Proxy Binding Acknowledgement message MUST be set to value of (0). It is to be noted that the Mobile Node Group Identifier option is a generic option and new sub-types may be defined by future specifications.
o 如果未为移动会话启用批量绑定更新支持，则本地移动锚不得在其发送到移动接入网关的代理绑定确认消息中包括子类型值为（1）（批量绑定更新组）的移动节点组标识符选项。此外，代理绑定确认消息中的（B）标志必须设置为值（0）。应当注意，移动节点组标识符选项是通用选项，并且新的子类型可以由未来的规范定义。
o If the received Proxy Binding Update message is not a bulk binding update request, (i.e., the (B) flag is set to a value of (0) and the Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group) is not present), but is a request for extending the lifetime of an existing mobility session, for which the bulk binding update support is already enabled, then the local mobility anchor MUST process the request as specified in [RFC5213]. However, the value of (0) in the (B) flag in the message serves as a request for the local mobility anchor to disable bulk binding update support for that mobility session. Upon accepting the request, the local mobility anchor SHOULD set the parameters, LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id in the Binding Cache entry to a value of (0) and the mobility session MUST be excluded from any bulk binding update operations.
o 如果接收到的代理绑定更新消息不是批量绑定更新请求，（即，（B）标志被设置为（0）值，并且子类型值为（1）（批量绑定更新组）的移动节点组标识符选项不存在），而是用于延长现有移动性会话的生存期的请求，如果已启用批量绑定更新支持，则本地移动锚必须按照[RFC5213]中的规定处理请求。然而，消息中（B）标志中的（0）值用作本地移动锚的请求，以禁用该移动会话的批量绑定更新支持。在接受请求后，本地移动锚应将绑定缓存项中的参数、LMA批量绑定更新组Id和MAG批量绑定更新组Id设置为（0）值，并且必须从任何批量绑定更新操作中排除移动会话。
o Any time the local mobility anchor detects that the mobile node has roamed and changed its point of attachment to a new mobile access gateway, it SHOULD also update the bulk binding update group identifier of the mobility session. Additionally, it should also update the existing group identifiers associated with that session. As part of sending the Proxy Binding Acknowledgement to the new mobile access gateway, it MUST include the updated group identifier in the Mobile Node Group Identifier option, with a sub-type value of (1). However, if the if the received Proxy Binding Update from the new mobile access gateway did not have the (B) flag set to a value of (1), then it MUST NOT include the mobility
o 当本地移动锚检测到移动节点已经漫游并将其连接点更改为新的移动接入网关时，它还应该更新移动会话的批量绑定更新组标识符。此外，它还应该更新与该会话关联的现有组标识符。作为向新移动接入网关发送代理绑定确认的一部分，它必须在移动节点组标识符选项中包含更新的组标识符，子类型值为（1）。但是，如果从新的移动接入网关接收的代理绑定更新没有将（B）标志设置为值（1），则它不能包括移动性
session in any of bulk binding update group and MUST NOT include the Mobile Node Group Identifier option with the sub-type value of (1).
会话位于任何批量绑定更新组中，并且不得包含子类型值为（1）的移动节点组标识符选项。
o Any time a mobile node's mobility session is de-registered by the mobile access gateway, or the session is revoked for administrative or any other reasons, the mobility session MUST also be removed from the bulk binding update group.
o 任何时候，移动节点的移动会话被移动接入网关注销，或者会话由于管理或任何其他原因被撤销，移动会话也必须从批量绑定更新组中删除。
The following section identifies the considerations for a local mobility anchor for performing bulk binding update and revocation operations with group-specific scope.
以下部分确定了本地移动锚在执行组特定范围的批量绑定更新和撤销操作时的注意事项。
o Any time the local mobility anchor receives a Proxy Binding Update message with the (B) flag in the request set to a value of (0) and a Mobile Node Group Identifier option present in the request with sub-type value of (1) (Bulk Binding Update Group), the local mobility anchor MUST consider the request a bulk binding update request, with the request scope including all the mobility sessions that are part of that bulk binding update group, specific to that mobile access gateway, and identified by the group identifier in Mobile Node Group Identifier option. However, if the received request also includes any individual session identifiers such as the Mobile Node Identifier option [RFC4283], the Home Network Prefix option [RFC5213], the IPv4 Home Address Request option [RFC5844], or the GRE Key option [RFC5845], the local mobility anchor MUST consider this as an invalid message; it MUST reject the Proxy Binding Update message and send a Proxy Binding Acknowledgement message with the Status field set to INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier value in the request).
o 在本地移动性锚点接收到具有请求（b）中的（b）标志的代理绑定更新消息的时间（0）和存在于具有子类型值（1）（批量绑定更新组）的请求中的移动节点组标识符选项时，本地移动性锚点必须考虑请求批量绑定更新请求，请求范围包括作为批量绑定更新组一部分的所有移动会话，特定于该移动接入网关，并由移动节点组标识符选项中的组标识符标识。然而，如果所接收的请求还包括任何单独的会话标识符，例如移动节点标识符选项[RCF483]、家庭网络前缀选项[RCF5213]、IPv4家庭地址请求选项[RCF5844 ]或GRE密钥选项[RCF5845 ]，本地移动性锚必须将其视为无效消息；它必须拒绝代理绑定更新消息，并发送一条代理绑定确认消息，状态字段设置为INVALID_MOBILE_NODE_GROUP_IDENTIFIER（请求中的无效组标识符值）。
o The local mobility anchor MUST consider the message as a request for extending the lifetime of all the mobility sessions that are associated with the group identifier in the Mobile Node Group Identifier option. However, if the Mobile Node Group Identifier option with the sub-type value of (1) (Bulk Binding Update Group) has an unknown group identifier, then the local mobility anchor MUST reject the Proxy Binding Update message and send a Proxy Binding Acknowledgement message with the Status field set to INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier value in the request).
o 本地移动性锚必须将消息视为延长与移动节点组标识符选项中的组标识符相关联的所有移动性会话的生存期的请求。但是，如果子类型值为（1）（批量绑定更新组）的移动节点组标识符选项具有未知的组标识符，则本地移动锚必须拒绝代理绑定更新消息，并发送状态字段设置为无效的\u Mobile\u Node\u Group\u Identifier的代理绑定确认消息（请求中的组标识符值无效）。
o Upon accepting the bulk binding update request, the local mobility anchor SHOULD extend the lifetime for all the mobility sessions that are part of the bulk binding update group identified by the
o 在接受批量绑定更新请求后，本地移动锚应该延长作为由本地移动锚标识的批量绑定更新组的一部分的所有移动会话的生存期
group identifier in the Mobile Node Group Identifier in the message. Considerations from [RFC5213] MUST be applied for extending the lifetime of a mobile node's session. It MUST also send a Proxy Binding Acknowledgement message with the Status field value set to 0 (Proxy Binding Update accepted). The lifetime field in the message MUST be set to the allocated lifetime for all the mobility sessions. The message MUST also include the Mobile Node Group Identifier option, with the sub-type value of (1) (Bulk Binding Update Group) and with the identifier value copied from the Mobile Node Group Identifier option present in the received Proxy Binding Update message.
移动节点中的组标识符消息中的组标识符。必须应用[RFC5213]中的注意事项来延长移动节点会话的生存期。它还必须发送状态字段值设置为0（接受代理绑定更新）的代理绑定确认消息。消息中的生存期字段必须设置为所有移动会话的分配生存期。消息还必须包括移动节点组标识符选项，子类型值为（1）（批量绑定更新组），并且标识符值从移动节点组标识符选项复制到接收到的代理绑定更新消息中。
o If the local mobility anchor rejects the bulk binding update request for any administrative reason, then it MUST NOT update the lifetime in the Binding Cache entries of any of the mobile nodes identified by the group identifier. The local mobility anchor SHOULD send a Proxy Binding Acknowledgement indicating the reason for the rejection in the status code.
o 如果本地移动锚出于任何管理原因拒绝批量绑定更新请求，则它不得更新由组标识符标识的任何移动节点的绑定缓存项中的生存期。本地移动锚应该发送一个代理绑定确认，在状态代码中指明拒绝的原因。
o Any time the local mobility anchor receives a Binding Revocation Indication Message [RFC5846] with a Mobile Node Group Identifier option present in the request and with the sub-type value of (1) (Bulk Binding Update Group), the local mobility anchor MUST consider the request as a bulk revocation request, with the request scope including all the mobility sessions that are part of the bulk binding update group specific to that mobile access gateway and identified by the group identifier in Mobile Node Group Identifier option. However, if the received request also includes the Mobile Node Identifier option [RFC4283], the Home Network Prefix option [RFC5213], the IPv4 Home Address Request option [RFC5844], or the GRE Key option [RFC5845], the local mobility anchor MUST consider this as an invalid message; it MUST reject the Binding Revocation Indication message and send a BRA message with the Status field set to a value of 128 (Binding Does NOT Exist). All the considerations from [RFC5846] apply when processing a binding revocation request, except making the scope of the operation apply to a set of mobility sessions identified by the group identifier present in the request.
o 本地移动性锚在任何时候接收绑定请求撤消指示消息[RCF5846]，其中存在请求中的移动节点组标识符选项，并且具有子类型值（1）（批量绑定更新组），本地移动性锚必须将请求视为批量撤销请求，请求范围包括所有移动会话，这些会话是特定于该移动接入网关的批量绑定更新组的一部分，并由移动节点组标识符选项中的组标识符标识。然而，如果所接收的请求还包括移动节点标识符选项[RCF483]、家庭网络前缀选项[RCF5213]、IPv4家庭地址请求选项[RCF5844 ]或GRE密钥选项[RCF5845 ]，本地移动性锚必须将其视为无效消息；它必须拒绝绑定撤销指示消息，并发送状态字段设置为128（绑定不存在）的BRA消息。[RFC5846]中的所有注意事项在处理绑定撤销请求时适用，但使操作范围适用于由请求中的组标识符标识的一组移动会话除外。
o Upon accepting the Binding Revocation Indication request and completing the operation, the local mobility anchor MUST send a Binding Revocation Acknowledgement message with the Status field set to a value of 0 (success). The message MUST include the Mobile Node Group Identifier option, with the identifier value copied from the Mobile Node Group Identifier option present in the received Binding Revocation Indication message.
o 在接受绑定撤销指示请求并完成操作后，本地移动锚必须发送绑定撤销确认消息，状态字段设置为0（成功）。消息必须包括移动节点组标识符选项，并且标识符值从移动节点组标识符选项复制，出现在接收到的绑定撤销指示消息中。
This specification adds a new configuration variable for the local mobility anchor. The configured value for this variable is expected to survive server reboots and service restarts.
本规范为本地移动锚添加了一个新的配置变量。此变量的配置值预计在服务器重新启动和服务重新启动后仍然有效。
AcceptBulkBindingUpdateReqForMobilitySession
AcceptBulkBindingUpdateReqForMobilitySession
This flag indicates whether or not the local mobility anchor will accept the request from the mobile access gateway to enable bulk binding update support for the mobility session. The default value for this flag is set to (1), indicating that it will accept the request from the mobile access gateway. If the value of the flag is set to (0), the local mobility anchor will deny the request.
此标志指示本地移动锚是否将接受来自移动接入网关的请求，以便为移动会话启用批量绑定更新支持。此标志的默认值设置为（1），表示它将接受来自移动接入网关的请求。如果该标志的值设置为（0），本地移动锚将拒绝该请求。
This specification adds a new configuration variable for the mobile access gateway. The configured value for this variable is expected to survive server reboots and service restarts.
本规范为移动接入网关添加了一个新的配置变量。此变量的配置值预计在服务器重新启动和服务重新启动后仍然有效。
RequestBulkBindingUpdateSupportForMobilitySession
RequestBulkBindingUpdateSupportForMobilitySession
This flag indicates whether or not the mobile access gateway will request the local mobility anchor to enable bulk binding update support for the mobility session. The default value for this flag is set to (1), indicating that the mobile access gateway will set the bulk binding update flag (B) in the Proxy Binding Update request to a value of (1). If the flag is set to a value of (0), the mobile access gateway will set the bulk binding update flag (B) in the Proxy Binding Update to a value of (0).
该标志指示移动接入网关是否将请求本地移动锚来为移动会话启用批量绑定更新支持。此标志的默认值设置为（1），表示移动接入网关将代理绑定更新请求中的批量绑定更新标志（B）设置为（1）值。如果该标志设置为值（0），则移动接入网关将代理绑定更新中的批量绑定更新标志（B）设置为值（0）。
Per this document, IANA has done the following:
根据本文件，IANA已完成以下工作：
o Action-1: This specification defines a new flag (B) to the Proxy Binding Update message, specified in [RFC5213]. This flag is described in Section 4.1. The value of the flag (B) has been allocated from the "Binding Update Flags" registry.
o 措施1：本规范为代理绑定更新消息定义了一个新标志（B），在[RFC5213]中指定。第4.1节描述了该标志。标志（B）的值已从“绑定更新标志”注册表中分配。
o Action-2: This specification defines a new flag (B) to the Proxy Binding Acknowledgement message, specified in [RFC5213]. This flag is described in Section 4.2. The value of the flag (B) has been allocated from the "Binding Acknowledgement Flags" registry.
o 措施2：本规范为代理绑定确认消息定义了一个新标志（B），在[RFC5213]中指定。第4.2节描述了该标志。标志（B）的值已从“绑定确认标志”注册表中分配。
o Action-3: This specification defines a new Mobility Header option, the Mobile Node Group Identifier option. This option is described in Section 4.3. The Type value for this option has been assigned in the same number space as allocated for the other mobility options [RFC6275].
o 措施3：该规范定义了一个新的移动报头选项，即移动节点组标识符选项。第4.3节介绍了该选项。此选项的类型值已分配到与其他移动选项相同的数字空间[RFC6275]。
o Action-4: The Sub-type field of the Mobile Node Group Identifier option introduces a new number space. This number space is now managed by IANA, under the Registry, "Mobile Node Group Identifier Type Registry". This specification reserves the sub-type value of (1) (Bulk Binding Update Group). Approval of new sub-type values are to be made through IANA Expert Review. The value range of this field is 0 through 255, but the values 0 and 255 are marked as reserved. The remaining values 2-254 are available for allocation.
o 操作4：移动节点组标识符选项的子类型字段引入了一个新的数字空间。这个数字空间现在由IANA在注册表“移动节点组标识符类型注册表”下管理。本规范保留子类型值（1）（批量绑定更新组）。应通过IANA专家评审批准新的子类型值。此字段的值范围为0到255，但值0和255标记为保留。剩余值2-254可供分配。
o Action-5: This document also defines a new status value INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier value in the request: 175) for use in the Proxy Binding Acknowledgement message, as described in Section 4.4. This value has been assigned from the same number space as allocated for other status codes [RFC6275].
o 措施5：本文件还定义了一个新的状态值INVALID_MOBILE_NODE_GROUP_标识符（请求中的无效组标识符值：175），用于代理绑定确认消息，如第4.4节所述。该值是从与分配给其他状态代码相同的数字空间分配的[RFC6275]。
The Mobile Node Group Identifier 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, and it does not require any other special security considerations.
本规范中定义的移动节点组标识符选项用于代理绑定更新和代理绑定确认消息。此选项与任何其他移动报头选项一样，不需要任何其他特殊的安全考虑。
The bulk binding update and the bulk revocation operations specified in this document perform operations on a group of mobility sessions. If proper authorization checks are not in place, a malicious node may be able to hijack a mobile node's mobility session or may carry out a denial-of-service attack. To prevent this attack, this specification requires the local mobility anchor to allow only authorized mobile access gateways to perform bulk operations.
本文档中指定的批量绑定更新和批量撤销操作在一组移动会话上执行操作。如果没有适当的授权检查，恶意节点可能会劫持移动节点的移动会话，或者可能实施拒绝服务攻击。为了防止这种攻击，本规范要求本地移动锚只允许授权的移动访问网关执行批量操作。
The authors would like to specially thank Jouni Korhonen, Basavaraj Patil, Carlos Jesus Bernardos Cano, Dirk Von-Hugo, Pete Resnick, and Jari Arkko for reviewing this document and providing input.
作者要特别感谢Jouni Korhonen、Basavaraj Patil、Carlos Jesus Bernardos Cano、Dirk Von Hugo、Pete Resnick和Jari Arkko审阅本文件并提供意见。
[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月。
[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月。
[RFC5846] Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K., and P. Yegani, "Binding Revocation for IPv6 Mobility", RFC 5846, June 2010.
[RFC5846]Muhanna，A.，Khalil，M.，Gundavelli，S.，Chowdhury，K.，和P.Yegani，“IPv6移动的绑定撤销”，RFC 58462010年6月。
[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月。
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", RFC 4283, November 2005.
[RFC4283]Patel，A.，Leung，K.，Khalil，M.，Akhtar，H.，和K.Chowdhury，“移动IPv6的移动节点标识符选项（MIPv6）”，RFC 4283，2005年11月。
[RFC5845] Muhanna, A., Khalil, M., Gundavelli, S., and K. Leung, "Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6", RFC 5845, June 2010.
[RFC5845]Muhanna，A.，Khalil，M.，Gundavelli，S.，和K.Leung，“代理移动IPv6的通用路由封装（GRE）密钥选项”，RFC 58452010年6月。
Authors' Addresses
作者地址
Fuad Abinader (editor) Instituto Nokia de Tecnologia Av. Torquato Tapajos, 7200 - Km. 12 - Col Terra Nova Manaus, AM 69048-660 Brazil
Fuad Abinader（编辑）诺基亚技术研究院Av。塔帕霍斯，7200公里。12-新马瑙斯高地，上午69048-660巴西
EMail: fabinader@gmail.com
EMail: fabinader@gmail.com
Sri Gundavelli (editor) Cisco 170 West Tasman Drive San Jose, CA 95134 USA
Sri Gundavelli（编辑）思科170西塔斯曼大道圣何塞，加利福尼亚州95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Kent Leung Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
EMail: kleung@cisco.com
EMail: kleung@cisco.com
Suresh Krishnan Ericsson 8400 Decarie Blvd. Town of Mount Royal, QC Canada
苏雷什·克里希南·爱立信德卡里大道8400号。加拿大皇家山镇
Phone: +1 514 345 7900 x42871
EMail: suresh.krishnan@ericsson.com
Phone: +1 514 345 7900 x42871
EMail: suresh.krishnan@ericsson.com
Domagoj Premec Unaffiliated
无附属公司的多马戈普莱梅
EMail: domagoj.premec@gmail.com
EMail: domagoj.premec@gmail.com