Internet Engineering Task Force (IETF) A. Muhanna
Request for Comments: 5846 M. Khalil
Category: Standards Track Ericsson
ISSN: 2070-1721 S. Gundavelli
K. Chowdhury
Cisco
P. Yegani
Juniper Networks
June 2010
Internet Engineering Task Force (IETF) A. Muhanna
Request for Comments: 5846 M. Khalil
Category: Standards Track Ericsson
ISSN: 2070-1721 S. Gundavelli
K. Chowdhury
Cisco
P. Yegani
Juniper Networks
June 2010
Binding Revocation for IPv6 Mobility
IPv6移动性的绑定撤销
Abstract
摘要
This document defines a binding revocation mechanism to terminate a mobile node's mobility session and the associated resources. This mechanism can be used both with base Mobile IPv6 and its extensions, such as Proxy Mobile IPv6. The mechanism allows the mobility entity which initiates the revocation procedure to request its peer to terminate either one, multiple or all specified Binding Cache entries.
本文档定义了一种绑定撤销机制，用于终止移动节点的移动会话和相关资源。此机制可用于基本移动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/rfc5846.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5846.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 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许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4
2.1. Conventions Used in This Document . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. Binding Revocation Protocol and Use Cases Overview . . . . . . 5
3.1. Binding Revocation Protocol . . . . . . . . . . . . . . . 5
3.2. MIPv6 and DSMIP6 Use Case . . . . . . . . . . . . . . . . 6
3.3. Multiple Care-of Addresses (MCoA) Use Case . . . . . . . . 7
3.4. Proxy MIPv6 Use Case . . . . . . . . . . . . . . . . . . . 8
3.4.1. Local Mobility Anchor Initiates PMIPv6 Revocation . . 9
3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings . . 10
4. Binding Revocation Messages over IPv4 Transport Network . . . 10
5. Binding Revocation Message . . . . . . . . . . . . . . . . . . 11
5.1. Binding Revocation Indication Message . . . . . . . . . . 13
5.2. Binding Revocation Acknowledgement Message . . . . . . . . 16
6. Binding Revocation Process Operation . . . . . . . . . . . . . 18
6.1. Sending Binding Revocation Message . . . . . . . . . . . . 18
6.1.1. Sending Binding Revocation Indication . . . . . . . . 18
6.1.2. Sending Binding Revocation Acknowledgement . . . . . . 19
6.2. Receiving Binding Revocation Message . . . . . . . . . . . 20
6.2.1. Receiving Binding Revocation Indication . . . . . . . 20
6.2.2. Receiving Binding Revocation Acknowledgement . . . . . 21
6.3. Retransmission of Binding Revocation Indication . . . . . 22
7. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 22
8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 23
8.1. Sending Binding Revocation Indication . . . . . . . . . . 23
8.2. Receiving Binding Revocation Indication . . . . . . . . . 27
9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 29
9.1. Receiving Binding Revocation Indication . . . . . . . . . 29
9.2. Sending Binding Revocation Indication . . . . . . . . . . 31
10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 32
11. Protocol Configuration Variables . . . . . . . . . . . . . . . 34
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
13. Security Considerations . . . . . . . . . . . . . . . . . . . 36
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
15.1. Normative References . . . . . . . . . . . . . . . . . . . 37
15.2. Informative References . . . . . . . . . . . . . . . . . . 38
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4
2.1. Conventions Used in This Document . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. Binding Revocation Protocol and Use Cases Overview . . . . . . 5
3.1. Binding Revocation Protocol . . . . . . . . . . . . . . . 5
3.2. MIPv6 and DSMIP6 Use Case . . . . . . . . . . . . . . . . 6
3.3. Multiple Care-of Addresses (MCoA) Use Case . . . . . . . . 7
3.4. Proxy MIPv6 Use Case . . . . . . . . . . . . . . . . . . . 8
3.4.1. Local Mobility Anchor Initiates PMIPv6 Revocation . . 9
3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings . . 10
4. Binding Revocation Messages over IPv4 Transport Network . . . 10
5. Binding Revocation Message . . . . . . . . . . . . . . . . . . 11
5.1. Binding Revocation Indication Message . . . . . . . . . . 13
5.2. Binding Revocation Acknowledgement Message . . . . . . . . 16
6. Binding Revocation Process Operation . . . . . . . . . . . . . 18
6.1. Sending Binding Revocation Message . . . . . . . . . . . . 18
6.1.1. Sending Binding Revocation Indication . . . . . . . . 18
6.1.2. Sending Binding Revocation Acknowledgement . . . . . . 19
6.2. Receiving Binding Revocation Message . . . . . . . . . . . 20
6.2.1. Receiving Binding Revocation Indication . . . . . . . 20
6.2.2. Receiving Binding Revocation Acknowledgement . . . . . 21
6.3. Retransmission of Binding Revocation Indication . . . . . 22
7. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 22
8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 23
8.1. Sending Binding Revocation Indication . . . . . . . . . . 23
8.2. Receiving Binding Revocation Indication . . . . . . . . . 27
9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 29
9.1. Receiving Binding Revocation Indication . . . . . . . . . 29
9.2. Sending Binding Revocation Indication . . . . . . . . . . 31
10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 32
11. Protocol Configuration Variables . . . . . . . . . . . . . . . 34
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
13. Security Considerations . . . . . . . . . . . . . . . . . . . 36
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
15.1. Normative References . . . . . . . . . . . . . . . . . . . 37
15.2. Informative References . . . . . . . . . . . . . . . . . . 38
In the case of Mobile IPv6 and for administrative reasons, sometimes it becomes necessary to inform the mobile node that its registration has been revoked and the mobile node is no longer able to receive IP mobility service for its Home Address. A similar Mobile IPv4 registration revocation mechanism [RFC3543] has been specified by the IETF for providing a revocation mechanism for sessions that were established using Mobile IPv4 registration [RFC3344].
在移动IPv6的情况下，出于管理原因，有时需要通知移动节点其注册已被撤销，并且移动节点不再能够接收其家庭地址的IP移动服务。IETF指定了类似的移动IPv4注册撤销机制[RFC3543]，用于为使用移动IPv4注册[RFC3344]建立的会话提供撤销机制。
This document specifies a binding revocation mechanism that can be used to revoke a mobile node's mobility session(s). The same mechanism can be used to revoke bindings created using Mobile IPv6 [RFC3775] or any of its extensions, e.g., Proxy Mobile IPv6 [RFC5213]. The proposed revocation mechanism uses a new Mobility Header (MH) type 16 for revocation signaling that is applicable to Mobile IPv6 [RFC3775] and Proxy Mobile IPv6 [RFC5213] and can be used by any two IP mobility entities. As an example, this mechanism allows a local mobility anchor (LMA), involved in providing IP mobility services to a mobile node, to notify the mobile access gateway (MAG) of the termination of that mobile node binding registration. In another example, a mobile access gateway can use this mechanism to notify its local mobility anchor peer with a bulk termination of all or a subset of proxy mobile IPv6 (PMIPv6) bindings that are registered with the local mobility anchor and currently being served by the mobile access gateway. Any mobility entity is allowed to revoke only the registration of those mobile node(s) mobility sessions that are currently registered with it.
本文档指定了一种绑定撤销机制，可用于撤销移动节点的移动会话。同样的机制可用于撤销使用移动IPv6[RFC3775]或其任何扩展（例如，代理移动IPv6[RFC5213]）创建的绑定。建议的撤销机制使用新的移动报头（MH）类型16进行撤销信令，该撤销信令适用于移动IPv6[RFC3775]和代理移动IPv6[RFC5213]，并且可由任意两个IP移动实体使用。作为示例，该机制允许参与向移动节点提供IP移动服务的本地移动锚（LMA）通知移动接入网关（MAG）该移动节点绑定注册的终止。在另一个示例中，移动接入网关可以使用该机制通知其本地移动锚对等方，以批量终止向本地移动锚注册并当前由移动接入网关服务的所有或一个子集的代理移动IPv6（PMIPv6）绑定。任何移动实体都只允许撤销当前已向其注册的移动节点移动会话的注册。
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 general mobility related terminology and abbreviations are to be interpreted as defined in the Mobile IPv6 [RFC3775], Proxy Mobile IPv6 [RFC5213] and IPv4 Support for Proxy Mobile IPv6 [RFC5844] specifications. The following terms are used in this specification.
所有通用移动相关术语和缩写应按照移动IPv6[RFC3775]、代理移动IPv6[RFC5213]和代理移动IPv6的IPv4支持[RFC5844]规范中的定义进行解释。本规范中使用以下术语。
Initiator
发起者
The mobility node that initiates the binding revocation procedure by sending a Binding Revocation Indication message to its peer, e.g., home agent, local mobility anchor, or mobile access gateway.
移动节点，其通过向其对等方（例如，归属代理、本地移动锚或移动接入网关）发送绑定撤销指示消息来发起绑定撤销过程。
Responder
应答器
The mobility node that receives the Binding Revocation Indication message and responds with a Binding Revocation Acknowledgement message, e.g., mobile node, mobile access gateway, or local mobility anchor.
接收绑定撤销指示消息并用绑定撤销确认消息响应的移动节点，例如，移动节点、移动接入网关或本地移动锚。
This specification specifies a generic binding revocation mechanism where a mobility node can communicate to the mobile node or another mobility node the identity of the mobile node registration binding that is being terminated. In the case when this mechanism is used for bulk termination or multiple bindings, the identities of these bindings are communicated to the mobile node or mobility node using the same generic mechanism. The following subsections present the protocol overview and applicable use cases.
该规范规定了通用绑定撤销机制，其中移动节点可以向移动节点或另一个移动节点传递正在终止的移动节点注册绑定的标识。在该机制用于批量终止或多个绑定的情况下，使用相同的通用机制将这些绑定的标识传递给移动节点或移动节点。以下小节介绍了协议概述和适用的用例。
In the case of Mobile IPv6, if the home network decides to terminate the service of the mobile node, the home agent sends a Binding Revocation Indication (BRI) message to the mobile node. The home agent includes the home address (HoA) of the mobile node in the Type 2 routing header as specified in [RFC3775] to indicate the impacted mobile node binding. In the case of Dual Stack Mobile IPv6 (DSMIPv6) [RFC5555], the home agent may include the IPv4 Home Address option with the home IPv4 address assigned by the mobile node. Additionally, if the mobile node registered multiple care-of addresses [RFC5648], the home agent includes the Binding Identifier (BID) option(s) in the Binding Revocation Indication message to identify which binding is being revoked. When the mobile node receives a Binding Revocation Indication message with its HoA included in the Type 2 routing header, the mobile node responds by sending a Binding Revocation Acknowledgement (BRA) message.
在移动IPv6的情况下，如果归属网络决定终止移动节点的服务，则归属代理向移动节点发送绑定撤销指示（BRI）消息。归属代理在[RFC3775]中指定的类型2路由报头中包括移动节点的归属地址（HoA），以指示受影响的移动节点绑定。在双栈移动IPv6（dsmpv6）[rfc555]的情况下，归属代理可以包括具有由移动节点分配的归属IPv4地址的IPv4归属地址选项。此外，如果移动节点注册了多个转交地址[RFC5648]，则归属代理在绑定撤销指示消息中包括绑定标识符（BID）选项，以识别正在撤销的绑定。当移动节点接收到绑定撤销指示消息且其HoA包括在类型2路由报头中时，移动节点通过发送绑定撤销确认（BRA）消息来响应。
Similarly, in the case of Proxy Mobile IPv6 [RFC5213], the revocation procedure can be initiated by the local mobility anchor by sending a Binding Revocation Indication message to communicate the termination of a mobile node registration binding to the mobile access gateway. In this case, the local mobility anchor includes the mobile node Home Network Prefix (MN-HNP) option [RFC5213] and the MN-ID option
类似地，在代理移动IPv6[RFC5213]的情况下，本地移动锚可通过发送绑定撤销指示消息来发起撤销过程，以将移动节点注册绑定的终止通知给移动接入网关。在这种情况下，本地移动性锚包括移动节点归属网络前缀（MN-HNP）选项[RFC5213]和MN-ID选项
[RFC4283] to indicate to the mobility access gateway the identity of the PMIPv6 binding that needs to be terminated. When the mobile access gateway receives the Binding Revocation Indication message, the mobile access gateway responds to the local mobility anchor by sending a Binding Revocation Acknowledgement message.
[RFC4283]向移动接入网关指示需要终止的PMIPv6绑定的标识。当移动接入网关接收到绑定撤销指示消息时，移动接入网关通过发送绑定撤销确认消息来响应本地移动锚。
On the other hand, the mobile access gateway usually sends a de-registration message by sending a Proxy Binding Update with a lifetime of zero to indicate to the local mobility anchor of the termination of the PMIPv6 mobile node binding registration. In this case, the mobile access gateway includes the MN-HNP option, the MN-ID option, and all other required mobility options as per [RFC5213] in order for the local mobility anchor to identify the mobile node PMIPv6 binding. Additionally, in the case when the mobile access gateway communicates a bulk termination of PMIPv6 mobility sessions, the mobile access gateway sends a Binding Revocation Indication message with the Global (G) bit set and includes the mobile access gateway identity in the MN-ID option, see Section 9.2 and Section 8.2. When the local mobility anchor receives such a Binding Revocation Indication message, it ensures that the mobile access gateway is authorized to send such a bulk termination message, see Section 13, and then processes the Binding Revocation Indication message accordingly. If the local mobility anchor processes the Binding Revocation Indication message successfully, the local mobility anchor responds to the mobile access gateway by sending Binding Revocation Acknowledgement message.
另一方面，移动接入网关通常通过发送生存期为零的代理绑定更新来发送取消注册消息，以向本地移动锚指示PMIPv6移动节点绑定注册的终止。在这种情况下，移动接入网关包括MN-HNP选项、MN-ID选项以及根据[RFC5213]的所有其他所需的移动选项，以便本地移动锚识别移动节点PMIPv6绑定。此外，在移动接入网关通信PMIPv6移动会话的批量终止的情况下，移动接入网关发送具有全局（G）比特集的绑定撤销指示消息，并在MN-ID选项中包括移动接入网关标识，参见第9.2节和第8.2节。当本地移动锚接收到这样的绑定撤销指示消息时，它确保移动接入网关被授权发送这样的批量终止消息，参见第13节，然后相应地处理绑定撤销指示消息。如果本地移动锚成功处理绑定撤销指示消息，则本地移动锚通过发送绑定撤销确认消息来响应移动接入网关。
In any of the above cases, the initiator of the binding revocation procedure, e.g., home agent, local mobility anchor, or mobile access gateway, uses the Revocation Trigger field in the Binding Revocation Indication message to indicate to the receiving node the reason for initiating the revocation procedure.
在上述任一情况下，绑定撤销过程的发起方，例如归属代理、本地移动锚或移动接入网关，使用绑定撤销指示消息中的撤销触发字段向接收节点指示发起撤销过程的原因。
The binding revocation mechanism is applicable to Mobile IPv6 and DSMIPv6 session(s) when the home agent needs to inform the mobile node that its binding registration has been revoked, e.g., for an administrative reason. This mechanism enables the user or the mobile node to react to the revocation, e.g., reinstate its interrupted Mobile IPv6 services.
当归属代理需要通知移动节点其绑定注册已被撤销（例如，出于管理原因）时，绑定撤销机制适用于移动IPv6和dsmpv6会话。该机制使得用户或移动节点能够对撤销作出反应，例如，恢复其中断的移动IPv6服务。
In this case, the home agent sends a Binding Revocation Indication message to indicate to the mobile node that its current mobile IPv6 (MIPv6) binding has been revoked and it is no longer able to receive IP mobility service. The home agent includes the HoA in a Type 2 routing header as used in [RFC3775] and sets the Revocation Trigger field to a proper value, e.g., Administrative Reason. In the case of
在这种情况下，归属代理发送绑定撤销指示消息，以指示移动节点其当前移动IPv6（MIPv6）绑定已被撤销，并且不再能够接收IP移动服务。归属代理在[RFC3775]中使用的类型2路由报头中包括HoA，并将撤销触发字段设置为适当的值，例如，管理原因。就
a DSMIPv6 session, the home agent may additionally include the mobile-node-assigned IPv4 Home Address in the IPv4 Home Address option. When the mobile node receives the Binding Revocation Indication message, it sends a Binding Revocation Acknowledgement message to the home agent. Figure 1 illustrates the message sequencing when a home agent revokes a mobile node binding registration.
在ipv6会话中，归属代理还可以在IPv4归属地址选项中包括移动节点分配的IPv4归属地址。当移动节点接收到绑定撤销指示消息时，它向归属代理发送绑定撤销确认消息。图1说明了归属代理撤销移动节点绑定注册时的消息顺序。
MN HA
| |
| HoA in Type 2 Routing Hdr |
|<<<------------... + ...-----------------|
| BRI [seq.#, Revocation Trigger] |
| |
| |
| BRA (HoA in Dest. Option)[seq.#, Status] |
|---------------------------------------->>>|
| |
| |
MN HA
| |
| HoA in Type 2 Routing Hdr |
|<<<------------... + ...-----------------|
| BRI [seq.#, Revocation Trigger] |
| |
| |
| BRA (HoA in Dest. Option)[seq.#, Status] |
|---------------------------------------->>>|
| |
| |
Figure 1: Home Agent Revokes a Mobile Node Binding Registration
图1：归属代理撤销移动节点绑定注册
In the case of multiple care-of address registrations [RFC5648], the home agent maintains a different binding for each care-of address and home address pair. These bindings are also indexed and identified during the mobile node registration using a BID mobility option. The HA may revoke one or multiple bindings for the same mobile node home address.
在多个转交地址注册[RFC5648]的情况下，归属代理为每个转交地址和归属地址对维护不同的绑定。在移动节点注册期间，还使用BID移动选项对这些绑定进行索引和标识。HA可以撤销同一移动节点主地址的一个或多个绑定。
If the home agent revokes a single binding for a mobile node with multiple care-of address registrations, the home agent sends a Binding Revocation Indication message to the mobile node with the corresponding BID option included. If more than one of the mobile node registered care-of addresses needs to be revoked, the home agent includes all the corresponding BID options in the same Binding Revocation Indication message. Figure 2 illustrates the message flow when the home agent revokes two registered care-of addresses for the same mobile node in a single Binding Revocation Indication message.
如果归属代理撤销具有多个转交地址注册的移动节点的单个绑定，则归属代理向移动节点发送绑定撤销指示消息，其中包括相应的出价选项。如果需要撤销移动节点注册的转交地址中的多个，则归属代理在同一绑定撤销指示消息中包括所有对应的出价选项。图2说明了当归属代理在单个绑定撤销指示消息中撤销同一移动节点的两个注册转交地址时的消息流。
HA Binding Cache
================
MN-BID1 [CoA1+HoA]
MN HA MN-BID2 [CoA2+HoA]
| | MN-BID3 [CoA3+HoA]
| | MN-BID4 [CoA4+HoA]
| HoA in Type 2 Routing Hdr |
|<<<<-------------- + ---------------------|
| BRI [seq.#, R. Trigger, BID1, BID4] |
| |
| |
| BRA (HoA in Dest. Option) [seq.#, Status] |
|---------------------------------------->>>>|
| |
| |
HA Binding Cache
================
MN-BID1 [CoA1+HoA]
MN HA MN-BID2 [CoA2+HoA]
| | MN-BID3 [CoA3+HoA]
| | MN-BID4 [CoA4+HoA]
| HoA in Type 2 Routing Hdr |
|<<<<-------------- + ---------------------|
| BRI [seq.#, R. Trigger, BID1, BID4] |
| |
| |
| BRA (HoA in Dest. Option) [seq.#, Status] |
|---------------------------------------->>>>|
| |
| |
Figure 2: Home Agent Revokes MN's Specific Care-of Address Bindings
图2：归属代理撤销MN的特定转交地址绑定
Additionally, the home agent may revoke all of the mobile node registered bindings by sending a BRI message without including any BID options while the HoA is included in the Type 2 routing header. Figure 1 illustrates the message flow when the home agent revokes all registered care-of address bindings for a mobile node in a single Binding Revocation Indication message.
此外，当HoA包括在类型2路由报头中时，归属代理可以通过发送BRI消息而不包括任何出价选项来撤销所有移动节点注册的绑定。图1说明了归属代理在单个绑定撤销指示消息中撤销移动节点的所有已注册转交地址绑定时的消息流。
Since the mobile node does not participate in the mobility mechanism in the case of PMIPv6, there are many scenarios where the Binding Revocation mechanism is needed to clean resources and make sure that the mobility entities, i.e., mobile access gateway and local mobility anchor, are always synchronized with respect to the status of the existing PMIPv6 bindings. The binding revocation mechanism is generic enough that it can be used for all Proxy Mobile IPv6 scenarios that follow the [RFC5213] and [RFC5844] specifications.
由于在PMIPv6的情况下移动节点不参与移动机制，因此存在许多场景，其中需要绑定撤销机制来清理资源并确保移动实体，即移动接入网关和本地移动锚，始终与现有PMIPv6绑定的状态同步。绑定撤销机制非常通用，可以用于遵循[RFC5213]和[RFC5844]规范的所有代理移动IPv6场景。
When the mobile access gateway receives a Binding Revocation Indication message as in Section 9.1, the mobile access gateway sends a Binding Revocation Acknowledgement message to the local mobility anchor following the rules described in Section 6.1.2. Similarly, if the local mobility anchor receives a Binding Revocation Indication message, the local mobility anchor responds to the mobile access gateway by sending a Binding Revocation Acknowledgement message.
当移动接入网关收到如第9.1节所述的绑定撤销指示消息时，移动接入网关按照第6.1.2节所述的规则向本地移动锚发送绑定撤销确认消息。类似地，如果本地移动锚接收到绑定撤销指示消息，则本地移动锚通过发送绑定撤销确认消息来响应移动接入网关。
The local mobility anchor may send a Binding Revocation Indication message with the appropriate revocation trigger value to the mobile access gateway that hosts a specific PMIPv6 binding to indicate that the mobile node binding has been terminated and the mobile access gateway can clean up the applicable resources. When the mobile access gateway receives a Binding Revocation Indication message, the mobile access gateway identifies the respective binding and it sends a Binding Revocation Acknowledgement message to the local mobility anchor. In this case, the mobile access gateway could terminate the IPv6 or IPv4 mobility session on the access link and notify the mobile node as in Section 9.1.
本地移动锚可以向承载特定PMIPv6绑定的移动接入网关发送具有适当撤销触发值的绑定撤销指示消息，以指示移动节点绑定已经终止，并且移动接入网关可以清理适用的资源。当移动接入网关接收到绑定撤销指示消息时，移动接入网关识别相应的绑定，并向本地移动锚发送绑定撤销确认消息。在这种情况下，移动接入网关可以终止接入链路上的IPv6或IPv4移动会话，并如第9.1节所述通知移动节点。
As an example, Figure 3, illustrates the message sequence for revoking a mobile node binding at the source mobile access gateway during the mobile node inter-MAG handover. During the inter-MAG handover, the mobile node moves from the source MAG to the target MAG. The target MAG sends a Proxy Binding Update with the new care-of address to the local mobility anchor to update the mobile node's point of attachment. Since the mobile node binding at the local mobility anchor points to the source MAG and upon receiving the Proxy Binding Update from the target MAG, the local mobility anchor updates the MN Binding Cache entry (BCE) and sends a Proxy Binding Acknowledgement to the target MAG. The local mobility anchor can send a Binding Revocation Indication message with the appropriate revocation trigger value, e.g., inter-MAG handover - different Access Types, to the source MAG in order to clean up the applicable resources reserved for the specified mobile node binding. The source mobile access gateway acknowledges the Binding Revocation Indication message by sending a Binding Revocation Acknowledgement message to indicate the success or failure of the termination of the mobile node's binding.
作为示例，图3说明了在移动节点间MAG切换期间在源移动接入网关处撤销移动节点绑定的消息序列。在MAG间切换期间，移动节点从源MAG移动到目标MAG。目标MAG向本地移动锚发送具有新转交地址的代理绑定更新，以更新移动节点的连接点。由于本地移动锚处的移动节点绑定指向源MAG，并且在从目标MAG接收到代理绑定更新时，本地移动锚更新MN绑定缓存条目（BCE）并向目标MAG发送代理绑定确认。本地移动锚可向源MAG发送具有适当撤销触发值（例如，MAG间切换-不同接入类型）的绑定撤销指示消息，以便清理为指定移动节点绑定保留的适用资源。源移动接入网关通过发送绑定撤销确认消息来确认绑定撤销指示消息，以指示移动节点的绑定终止的成功或失败。
The process identified above can also be used by the local mobility anchor in scenarios other than the inter-MAG handover with the proper revocation trigger value to indicate to the peer mobile access gateway that a specific PMIPv6 binding or bindings have been revoked.
上述识别的过程也可由本地移动锚在除MAG间切换之外的场景中使用，具有适当的撤销触发值以向对等移动接入网关指示特定PMIPv6绑定已被撤销。
oldMAG newMAG LMA
| | |
| | PBU |
| |--------------------------->|
| | PBU triggers
| | BRI Msg to oldMAG
| | |
| | PBA |
| |<---------------------------|
| | |
| | |
| BRI [seq.#, R. Trigger, P bit, NAI] |
|<-----------------------------------------|
| | |
| | |
| | |
| | |
| BRA [seq.#, Status, P bit] |
|----------------------------------------->|
| | |
| | |
oldMAG newMAG LMA
| | |
| | PBU |
| |--------------------------->|
| | PBU triggers
| | BRI Msg to oldMAG
| | |
| | PBA |
| |<---------------------------|
| | |
| | |
| BRI [seq.#, R. Trigger, P bit, NAI] |
|<-----------------------------------------|
| | |
| | |
| | |
| | |
| BRA [seq.#, Status, P bit] |
|----------------------------------------->|
| | |
| | |
Figure 3: LMA Revokes an MN Registration During Inter-MAG Handover
图3:LMA在MAG间切换期间撤销MN注册
In addition, the local mobility anchor can send a Binding Revocation Indication message to indicate that all bindings that are hosted by the peer mobile access gateway and registered with the local mobility anchor are being revoked by setting the Global (G) bit as described in Section 8.1.
此外，本地移动锚可发送绑定撤销指示消息，以指示通过设置第8.1节中所述的全局（G）位来撤销由对等移动接入网关承载并向本地移动锚注册的所有绑定。
The mobile access gateway sends a BRI message with the Global (G) bit set and the Revocation Trigger field set to "Per-Peer Policy" to indicate that all mobility bindings that are registered at the local mobility anchor and attached to the mobile access gateway are being revoked as in Section 9.2. When the local mobility anchor receives this Binding Revocation Indication message from the specified mobile access gateway, the local mobility anchor first checks if the mobile access gateway is authorized to use global revocations, then it responds with the appropriate status code by sending a Binding Revocation Acknowledgement message as in Section 6.1.2.
移动接入网关发送BRI消息，其中全局（G）位设置和撤销触发字段设置为“每对等策略”，以指示在本地移动锚注册并连接到移动接入网关的所有移动绑定正在撤销，如第9.2节所述。当本地移动锚从指定的移动接入网关接收到此绑定撤销指示消息时，本地移动锚首先检查移动接入网关是否被授权使用全局撤销，然后，它通过发送绑定撤销确认消息（如第6.1.2节所述）以适当的状态代码进行响应。
In some deployments, the network between the mobile access gateway and the local mobility anchor may only support IPv4 transport. Another case is when a mobile node that supports client mobile IPv6
在某些部署中，移动接入网关和本地移动锚之间的网络可能仅支持IPv4传输。另一种情况是，支持客户端移动IPv6的移动节点
roams to an access network where only IPv4 addressing and transport is supported. In this case, the mobile node is required to register an IPv4 home address with its home agent using a mobile IPv6 Binding Update message.
漫游到仅支持IPv4寻址和传输的访问网络。在这种情况下，移动节点需要使用移动IPv6绑定更新消息向其归属代理注册IPv4归属地址。
If the Proxy Binding Update and Proxy Binding Acknowledgement messages or the Binding Update and Binding Acknowledgement messages are sent using UDP encapsulation [RFC5844] [RFC5555], then the Binding Revocation Messages are sent using the same UDP encapsulation. The same UDP source and destination port numbers and IPv4 addresses used for exchanging the Proxy Binding Update and Proxy Binding Acknowledgement or the Binding Update and Binding Acknowledgement messages MUST be used when transporting Binding Revocation Messages over IPv4 using UDP encapsulation. For example, the source UDP port number, the destination UDP port number, the source IPv4 address, and the destination IPv4 address of the Binding Revocation Indication message are set to the destination UDP port number, the source UDP port number, destination IPv4 address, and source IPv4 address of the latest received and successfully processed Proxy Binding Update or Binding Update message, respectively. For more details on tunneling Proxy Mobile IPv6 and Mobile IPv6 signaling messages over IPv4, see [RFC5844] and [RFC5555], respectively.
如果使用UDP封装[RFC5844][RFC5555]发送代理绑定更新和代理绑定确认消息或绑定更新和绑定确认消息，则使用相同的UDP封装发送绑定撤销消息。在使用UDP封装通过IPv4传输绑定撤销消息时，必须使用用于交换代理绑定更新和代理绑定确认或绑定更新和绑定确认消息的相同UDP源和目标端口号以及IPv4地址。例如，绑定撤销指示消息的源UDP端口号、目标UDP端口号、源IPv4地址和目标IPv4地址设置为目标UDP端口号、源UDP端口号、目标IPv4地址，和最新接收并成功处理的代理绑定更新或绑定更新消息的源IPv4地址。有关IPv4上隧道代理移动IPv6和移动IPv6信令消息的更多详细信息，请分别参阅[RFC5844]和[RFC5555]。
This section defines the Binding Revocation Message format using an MH Type 16 as illustrated in Figure 4. The value in the Binding Revocation Type field defines whether the Binding Revocation Message is a Binding Revocation Indication or Binding Revocation Acknowledgement. If the Binding Revocation Type field is set to 1, the Binding Revocation Message is a Binding Revocation Indication as in Section 5.1. However, if the value is 2, it is a Binding Revocation Acknowledgement message as in Section 5.2.
本节使用MH类型16定义绑定撤销消息格式，如图4所示。绑定撤销类型字段中的值定义绑定撤销消息是绑定撤销指示还是绑定撤销确认。如果绑定撤销类型字段设置为1，则绑定撤销消息是绑定撤销指示，如第5.1节所示。但是，如果该值为2，则它是一条具有约束力的撤销确认消息，如第5.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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Proto | Header Len | MH Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | B.R. Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
. Binding Revocation Message Data .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Proto | Header Len | MH Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | B.R. Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
. Binding Revocation Message Data .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Binding Revocation Message
图4：绑定撤销消息
Payload Proto
荷协议
8-bit selector. See [RFC3775] for more details.
8位选择器。有关更多详细信息，请参阅[RFC3775]。
Header Len
割台透镜
8-bit unsigned integer. Representing the length of the Mobility Header in units of 8 octets, excluding the first 8 octets. See [RFC3775] for more details.
8位无符号整数。以8个八位字节为单位表示移动报头的长度，不包括前8个八位字节。有关更多详细信息，请参阅[RFC3775]。
MH Type
MH型
16, which identifies the mobility message as a Binding Revocation Message.
16，它将移动消息标识为绑定撤销消息。
Reserved
含蓄的
8-bit field reserved for future use. The value MUST be initialized to zero by the sender and MUST be ignored by the receiver.
保留8位字段供将来使用。发送方必须将该值初始化为零，接收方必须忽略该值。
Checksum
校验和
16-bit unsigned integer. This field contains the checksum of the Mobility Header. The checksum is calculated as described in [RFC3775].
16位无符号整数。此字段包含移动标头的校验和。按照[RFC3775]中的说明计算校验和。
Binding Revocation Type
绑定撤销类型
8-bit unsigned integer. It defines the type of the Binding Revocation Message. It can be assigned one of the following values:
8位无符号整数。它定义绑定撤销消息的类型。可以为其指定以下值之一：
0 Reserved
0保留
1 Binding Revocation Indication
1有约束力的撤销指示
2 Binding Revocation Acknowledgement
2具有约束力的撤销确认
All other values are unassigned
所有其他值均未赋值
Binding Revocation Message Data
绑定撤销消息数据
The Binding Revocation Message Data follows the Binding Revocation Message format that is defined in this document for the specified value in the Binding Revocation Type field. In this document, it is either a Binding Revocation Indication as in Section 5.1 or Binding Revocation Acknowledgement as in Section 5.2.
绑定撤销消息数据遵循本文档中为绑定撤销类型字段中的指定值定义的绑定撤销消息格式。在本文件中，它要么是第5.1节中的具有约束力的撤销指示，要么是第5.2节中的具有约束力的撤销确认。
The Binding Revocation Indication (BRI) message is a Binding Revocation Message that has an MH type 16 and a Binding Revocation Type value of 1. It is used by the initiator to inform the responder of the identity of a specific binding or bindings for which IP mobility service are being revoked. Binding Revocation Indication message is sent as described in Sections 7, 8.1, and 9.2.
绑定撤销指示（BRI）消息是具有MH类型16和绑定撤销类型值1的绑定撤销消息。发起方使用它通知响应方正在撤销IP移动服务的一个或多个特定绑定的标识。按照第7节、第8.1节和第9.2节的说明发送绑定撤销指示消息。
When the value 1 is indicated in the Binding Revocation Type field of the Binding Revocation Message, the format of the Binding Revocation Message Data follows the Binding Revocation Indication message as in Figure 5
当值1在绑定撤销消息的绑定撤销类型字段中指示时，绑定撤销消息数据的格式遵循绑定撤销指示消息，如图5所示
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B.R. Type = 1 | R. Trigger |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B.R. Type = 1 | R. Trigger |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Binding Revocation Indication Message
图5：绑定撤销指示消息
Revocation Trigger
撤销触发器
8-bit unsigned integer indicating the event that triggered the initiator to send the BRI message. The Per-MN Revocation Trigger values are less than 128. The Per-MN Revocation Trigger is used when the BRI message intends to revoke one or more bindings for the same mobile node. The Global Revocation Trigger values are greater than 128 and less than 250 and used in the BRI message when the Global (G) bit is set for global revocation. The values 250-255 are reserved for testing purposes only. The following Revocation Trigger values are currently defined:
8位无符号整数，指示触发启动器发送BRI消息的事件。每MN吊销触发值小于128。当BRI消息打算撤销同一移动节点的一个或多个绑定时，使用Per MN REVOCIATION触发器。全局撤销触发值大于128小于250，并在全局（G）位设置为全局撤销时用于BRI消息。250-255值仅保留用于测试目的。当前定义了以下吊销触发器值：
Per-MN Revocation Trigger Values: 0 Unspecified 1 Administrative Reason 2 Inter-MAG Handover - same Access Type 3 Inter-MAG Handover - different Access Type 4 Inter-MAG Handover - Unknown 5 User-Initiated Session(s) Termination
每MN撤销触发值：0未指定1管理原因2 MAG间切换-相同访问类型3 MAG间切换-不同访问类型4 MAG间切换-未知5用户启动的会话终止
6 Access Network Session(s) Termination 7 Possible Out-of-Sync BCE State
6接入网络会话终止7可能的不同步BCE状态
Global Revocation Trigger Values: 128 Per-Peer Policy 129 Revoking Mobility Node Local Policy
全局吊销触发值：每个对等策略128 129吊销移动节点本地策略
Reserved Revocation Trigger Values: 250-255 Reserved For Testing Purposes only All other values are Reserved
保留撤销触发器值：250-255保留用于测试目的只有所有其他值保留
Sequence Number
序列号
A 16-bit unsigned integer used by the initiator to match a returned Binding Revocation Acknowledgement with this Binding Revocation Indication. This sequence number could be a random number. At any time, implementations MUST ensure there is no collision between the sequence numbers of all outstanding Binding Revocation Indication Messages.
启动器使用的16位无符号整数，用于将返回的绑定撤销确认与此绑定撤销指示相匹配。该序列号可以是随机数。在任何时候，实现都必须确保所有未完成的绑定撤销指示消息的序列号之间没有冲突。
Proxy Binding (P)
代理绑定（P）
The Proxy Binding (P) bit is set by the initiator to indicate that the revoked binding(s) is a PMIPv6 binding.
发起方设置代理绑定（P）位，以指示已撤销的绑定是PMIPv6绑定。
IPv4 HoA Binding Only (V)
仅IPv4 HoA绑定（V）
The IPv4 HoA Binding Only (V) bit is set by the initiator, home agent, or local mobility anchor to indicate to the receiving mobility entity the termination of the IPv4 Home Address binding only as in Sections 7 and 8.1.
仅IPv4 HoA绑定（V）位由启动器、归属代理或本地移动锚设置，以向接收移动实体指示IPv4归属地址绑定的终止，如第7节和第8.1节所述。
Global (G)
全球（G）
The Global (G) bit is set by the initiator, LMA or MAG, to indicate the termination of all Per-Peer mobility Bindings or Multiple Bindings that share a common identifier(s) and are served by the initiator and responder as in Sections 8.1 and 9.2.
全局（G）位由发起方（LMA或MAG）设置，以指示所有对等移动绑定或共享公共标识符并由发起方和响应方提供服务的多个绑定的终止，如第8.1节和第9.2节所述。
Reserved
含蓄的
These fields are unused. They MUST be initialized to zero by the sender and MUST be ignored by the receiver.
这些字段未使用。发送方必须将它们初始化为零，接收方必须忽略它们。
Mobility Options
移动选项
A variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. This field
一种可变长度字段，其长度使得完整移动报头是8个八位字节长的整数倍。这个领域
contains zero or more TLV-encoded mobility options. This document does not define any new mobility option. The receiver MUST ignore and skip any options that it does not understand. These mobility options are used by the responder to identify the specific binding or bindings that the initiator is requesting be revoked.
包含零个或多个TLV编码的移动性选项。本文件未定义任何新的移动选项。接收方必须忽略并跳过其不理解的任何选项。响应程序使用这些移动选项来标识发起程序请求撤销的一个或多个特定绑定。
The following options are valid in a Binding Revocation Indication:
以下选项在绑定撤销指示中有效：
o Home Network Prefix option [RFC5213]. This option MAY be used only when the (P) bit is set. This option MUST be present when the BRI is used to revoke a single Proxy MIPv6 Binding Cache entry.
o 家庭网络前缀选项[RFC5213]。此选项仅在设置（P）位时使用。当BRI用于撤销单个代理MIPv6绑定缓存项时，此选项必须存在。
o Mobile Node Identifier option [RFC4283]. This option MUST be present when the (P) bit is set. Additionally, if the Global (G) bit is set by the mobile access gateway, this option MUST carry the MAG identity. In this specification, only the Mobile Node Identifier option with subtype 1 is required and other subtypes are currently not supported.
o 移动节点标识符选项[RFC4283]。设置（P）位时，此选项必须存在。此外，如果移动接入网关设置了全局（G）位，则此选项必须带有MAG标识。在本规范中，仅需要子类型为1的移动节点标识符选项，当前不支持其他子类型。
o Binding Identifier mobility option [RFC5648]. This option MUST be present if the initiator requests to terminate one binding of a multiple care-of address bindings for the same mobile node. The initiator may include more than one of the BID mobility options.
o 绑定标识符移动选项[RFC5648]。如果启动器请求终止同一移动节点的多个转交地址绑定的一个绑定，则必须存在此选项。发起人可以包括不止一个投标移动性选项。
o IPv4 Home Address option, which contains the mobile node home IPv4 address [RFC5555]. This option MUST only be included when the IPv4 HoA Binding only (V) bit is set and the (P) bit is cleared.
o IPv4主地址选项，其中包含移动节点主IPv4地址[RFC5555]。仅当设置了IPv4 HoA仅绑定（V）位且清除了（P）位时，才必须包括此选项。
o IPv4 Home Address Request option, which contains the mobile node proxy home IPv4 address [RFC5844]. This option MUST only be included when the IPv4 HoA Binding only (V) and the (P) bits are set.
o IPv4家庭地址请求选项，其中包含移动节点代理家庭IPv4地址[RFC5844]。仅当设置了IPv4 HoA仅绑定（V）和（P）位时，才必须包括此选项。
o Alternate Care-of Address mobility option [RFC3775]. According to [RFC5213], the mobile access gateway is allowed to include this option in the Proxy Binding Update to indicate the proxy care-of address of the mobile node mobility session. This option MAY be included to indicate the proxy care-of address of the mobile node's binding that is being revoked. In the case when the Global (G) bit is set, this option identifies all mobility bindings that share the same proxy care-of address.
o 替代转交地址移动选项[RFC3775]。根据[RFC5213]，允许移动接入网关在代理绑定更新中包括该选项，以指示移动节点移动会话的代理转交地址。可以包括该选项以指示正在被撤销的移动节点的绑定的代理转交地址。在设置全局（G）位的情况下，此选项标识共享同一代理转交地址的所有移动绑定。
If no mobility options are present in this message, 4 octets of padding are necessary and the Header Len field of the Binding Revocation Message will be set to 1.
如果此消息中没有移动选项，则需要4个八位字节的填充，并且绑定撤销消息的Header Len字段将设置为1。
The Binding Revocation Acknowledgement (BRA) message is a Binding Revocation Message that has an MH type 16 and a Binding Revocation Type value of 2. It is used to acknowledge the receipt of a Binding Revocation Indication message described in Section 5.1. This packet is sent as described in Section 6.1.2.
绑定撤销确认（BRA）消息是具有MH类型16和绑定撤销类型值2的绑定撤销消息。它用于确认收到第5.1节所述的绑定撤销指示消息。按照第6.1.2节所述发送该数据包。
When the value 2 is indicated in the Binding Revocation Type field of the Binding Revocation Message, the format of the Binding Revocation Message Data follows the Binding Revocation Acknowledgement message as in Figure 6.
当值2在绑定撤销消息的绑定撤销类型字段中指示时，绑定撤销消息数据的格式遵循绑定撤销确认消息，如图6所示。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B.R. Type = 2 | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B.R. Type = 2 | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Binding Revocation Acknowledgement Message
图6：绑定撤销确认消息
Status 8-bit unsigned integer indicating the result of processing the Binding Revocation Indication message by the responder. Values of the Status field less than 128 indicate that the Binding Revocation Indication was processed successfully by the responder. Values greater than or equal to 128 indicate that the Binding Revocation Indication was rejected by the responder. The following Status values are currently defined:
状态8位无符号整数，指示响应程序处理绑定撤销指示消息的结果。状态字段的值小于128表示绑定撤销指示已由响应程序成功处理。大于或等于128的值表示绑定撤销指示已被响应程序拒绝。当前定义了以下状态值：
0 success 1 partial success 128 Binding Does NOT Exist 129 IPv4 Home Address Option Required 130 Global Revocation NOT Authorized 131 Revoked Mobile Nodes Identity Required 132 Revocation Failed - MN is Attached 133 Revocation Trigger NOT Supported 134 Revocation Function NOT Supported 135 Proxy Binding Revocation NOT Supported
0成功1部分成功128绑定不存在129 IPv4 Home Address选项需要130全局吊销未授权131吊销的移动节点身份需要132吊销失败-MN已连接133吊销触发器不支持134吊销功能不支持135代理绑定吊销不支持
Sequence Number
序列号
The sequence number in the Binding Revocation Acknowledgement is copied from the Sequence Number field in the Binding Revocation Indication. It is used by the initiator, e.g., HA, LMA, MAG, in matching this Binding Revocation Acknowledgement with the outstanding Binding Revocation Indication.
绑定撤销确认中的序列号从绑定撤销指示中的序列号字段复制。它由发起方（例如HA、LMA、MAG）用于将该绑定撤销确认与未完成的绑定撤销指示相匹配。
Proxy Binding (P)
代理绑定（P）
The Proxy Binding (P) bit is set if the (P) bit is set in the corresponding Binding Revocation Indication message.
如果在相应的绑定撤销指示消息中设置了（P）位，则设置代理绑定（P）位。
IPv4 HoA Binding Only (V)
仅IPv4 HoA绑定（V）
The IPv4 HoA Binding Only (V) bit is set if the (V) bit is set in the corresponding Binding Revocation Indication message.
如果在相应的绑定撤销指示消息中设置了（V）位，则只设置IPv4 HoA绑定（V）位。
Global (G)
全球（G）
The Global (G) bit is set if the (G) bit is set in the corresponding Binding Revocation Indication message.
如果在相应的绑定撤销指示消息中设置了（G）位，则设置全局（G）位。
Reserved
含蓄的
These fields are unused. They MUST be initialized to zero by the sender and MUST be ignored by the receiver.
这些字段未使用。发送方必须将它们初始化为零，接收方必须忽略它们。
Mobility Options
移动选项
A variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. This field contains zero or more TLV-encoded mobility options. In the case when the Status field is set to success, no mobility option is required. The mobility option(s) is usually used to communicate information of the bindings that failed the revocation procedure.
一种可变长度字段，其长度使得完整移动报头是8个八位字节长的整数倍。此字段包含零个或多个TLV编码的移动性选项。在状态字段设置为成功的情况下，不需要移动选项。移动选项通常用于传递撤销过程失败的绑定的信息。
The following mobility options are valid in a Binding Revocation Acknowledgement:
以下移动选项在绑定撤销确认中有效：
o Home Network Prefix option [RFC5213]. This option MAY be included only when the (P) bit is set.
o 家庭网络前缀选项[RFC5213]。仅当设置了（P）位时，才可包括此选项。
o Mobile Node Identifier Option [RFC4283]. This option MAY be included when the (P) bit is set. This option SHOULD be included if the Home Network Prefix option is included.
o 移动节点标识符选项[RFC4283]。设置（P）位时，可包括此选项。如果包括家庭网络前缀选项，则应包括此选项。
o Binding Identifier mobility option [RFC5648]. The responder MAY include this option to indicate the specific BID that failed the revocation procedure.
o 绑定标识符移动选项[RFC5648]。响应者可包括此选项，以指示未通过撤销程序的特定投标。
If no options are present in this message, 4 octets of padding are necessary and the Header Len field of the Binding Revocation Message will be set to 1.
如果此消息中不存在任何选项，则需要4个八位字节的填充，并且绑定撤销消息的Header Len字段将设置为1。
The following subsections describe the details of the generic binding revocation process as used by the different mobility entities.
以下小节描述了不同移动实体使用的通用绑定撤销过程的详细信息。
When sending a Binding Revocation message, the initiator constructs the packet as it would do with any other Mobility Header with the exception of setting the MH Type field to 16.
当发送绑定撤销消息时，发起方构造数据包，就像它对任何其他移动报头所做的一样，但将MH Type字段设置为16除外。
The Binding Revocation Message MUST be protected using the same underlying security association, e.g., IPsec, that is being used between the two peers to protect the mobile node's Mobile IPv6 and its extensions binding registration signaling. If IPsec is not used as the underlying security mechanism to protect the binding registration signaling, the used underlying security mechanism MUST provide protection against all identified security threats as described under "Security Considerations" in [RFC3775] and [RFC5213].
必须使用相同的基础安全关联（例如，IPsec）来保护绑定撤销消息，该关联在两个对等方之间用于保护移动节点的移动IPv6及其扩展绑定注册信令。如果IPsec未用作保护绑定注册信令的基础安全机制，则所用的基础安全机制必须针对所有已识别的安全威胁提供保护，如[RFC3775]和[RFC5213]中“安全注意事项”所述。
The initiator MUST construct the Binding Revocation Message Data following the format of the Binding Revocation Indication message as described in Section 5.1 and the following:
发起人必须按照第5.1节所述的绑定撤销指示消息格式和以下内容构建绑定撤销消息数据：
o The initiator MUST set the Sequence Number field to a valid sequence number for Binding Revocation. Since sending a Binding Revocation Indication message is not done on a regular basis, a 16-bit Sequence Number field is large enough to allow the initiator to match the Binding Revocation Acknowledgement to the associated Binding Revocation Indication using the Sequence Number field only.
o 发起人必须将序列号字段设置为有效的序列号，以便进行绑定吊销。由于没有定期发送绑定撤销指示消息，因此16位序列号字段足够大，允许启动器仅使用序列号字段将绑定撤销确认与关联的绑定撤销指示相匹配。
o If the initiator is revoking a binding that was created using proxy MIPv6 registration, the initiator MUST set the Proxy Binding (P) bit.
o 如果启动器正在撤消使用代理MIPv6注册创建的绑定，则启动器必须设置代理绑定（P）位。
o If the initiator is sending the Binding Revocation Indication message to revoke multiple mobility sessions, the initiator MUST set the Global (G) bit. In this case, the initiator MUST set the Revocation Trigger field to a valid value from the list of Global Revocation Triggers.
o 如果发起方发送绑定撤销指示消息以撤销多个移动会话，则发起方必须设置全局（G）位。在这种情况下，启动器必须将吊销触发器字段设置为全局吊销触发器列表中的有效值。
o If the initiator is sending the Binding Revocation Indication message with the Global (G) bit cleared, the initiator MUST set the Revocation Trigger field to a valid value from the list of Per-MN Revocation Triggers.
o 如果启动器发送绑定撤销指示消息时清除了全局（G）位，则启动器必须将撤销触发器字段设置为每MN撤销触发器列表中的有效值。
o If the initiator is sending the Binding Revocation Indication message to indicate the revocation of the mobile node IPv4 HoA Binding Only, the initiator MUST set the (V) bit. In this case, the initiator MUST include either the IPv4 Home Address option or the IPv4 Home Address Request option in the BRI to identify the IPv4 HoA that is being revoked.
o 如果发起方正在发送绑定撤销指示消息以指示仅撤销移动节点IPv4 HoA绑定，则发起方必须设置（V）位。在这种情况下，启动器必须在BRI中包含IPv4家庭地址选项或IPv4家庭地址请求选项，以标识正在撤销的IPv4 HoA。
The responder MUST send a Binding Revocation Acknowledgement message to indicate the receipt and the status of processing of the corresponding Binding Revocation Indication message as follows:
响应者必须发送绑定撤销确认消息，以指示相应绑定撤销指示消息的接收和处理状态，如下所示：
o Whenever the Binding Revocation Indication is discarded, e.g., as described in Section 6.2, a Binding Revocation Acknowledgement MUST NOT be sent. Otherwise, the treatment depends on the following rules.
o 每当丢弃绑定撤销指示时，如第6.2节所述，不得发送绑定撤销确认。否则，处理取决于以下规则。
o If the responder accepts the Binding Revocation Indication message, the responder MUST send a successful Binding Revocation Acknowledgement with an appropriate status code.
o 如果响应者接受绑定撤销指示消息，则响应者必须发送带有适当状态代码的成功绑定撤销确认。
o If the responder rejects the Binding Revocation Indication message, the responder MUST send a Binding Revocation Acknowledgement with an appropriate failure status code.
o 如果响应者拒绝绑定撤销指示消息，则响应者必须发送带有适当故障状态代码的绑定撤销确认。
If the Source Address field of the IPv6 header that carried the Binding Revocation Indication message does not contain a unicast address, the Binding Revocation Indication packet MUST be silently discarded.
如果承载绑定撤销指示消息的IPv6标头的源地址字段不包含单播地址，则必须以静默方式丢弃绑定撤销指示数据包。
When the responder acknowledges the received Binding Revocation Indication message, the responder MUST construct the Binding Revocation Message Data following the format of the Binding Revocation Acknowledgement message as described in Section 5.2 and the following:
当响应者确认收到的绑定撤销指示消息时，响应者必须按照第5.2节所述的绑定撤销确认消息格式和以下内容构造绑定撤销消息数据：
o The responder MUST set the Sequence Number field by copying the value from the Sequence Number field of the received Binding Revocation Indication.
o 响应程序必须通过复制接收到的绑定撤销指示的序列号字段中的值来设置序列号字段。
o The responder MUST set the Status field to a valid value that reflects the status of the processing of the received Binding Revocation Indication message.
o 响应者必须将Status字段设置为有效值，该值反映接收到的绑定撤销指示消息的处理状态。
o If the (P) bit is set in the received Binding Revocation Indication, the responder MUST set the (P) bit in the Binding Revocation Acknowledgement.
o 如果在收到的绑定撤销指示中设置了（P）位，则响应者必须在绑定撤销确认中设置（P）位。
o If the Global (G) bit is set in the received Binding Revocation Indication, the responder MUST set the Global (G) bit in the Binding Revocation Acknowledgement.
o 如果在收到的绑定撤销指示中设置了全局（G）位，则响应者必须在绑定撤销确认中设置全局（G）位。
o If the IPv4 HoA Binding Only (V) bit is set in the received Binding Revocation Indication, the responder MUST set the (V) bit in the Binding Revocation Acknowledgement.
o 如果在收到的绑定撤销指示中设置了IPv4 HoA仅绑定（V）位，则响应者必须在绑定撤销确认中设置（V）位。
o The destination IP address of the IPv6 packet of the Binding Revocation Acknowledgement is set to the source IP address of the received Binding Revocation Indication.
o 绑定撤销确认的IPv6数据包的目标IP地址设置为接收到的绑定撤销指示的源IP地址。
When receiving a Binding Revocation Message, the responder MUST verify the Mobility Header as described in Section 9.2. of [RFC3775]. If the packet is dropped due to failing any of the Mobility Header test checks, the responder MUST follow the processing rules as in Section 9.2 of [RFC3775]. If the responder does not support the Binding Revocation Indication message and does not recognize the MH type 16, it sends a Binding Error message with the Status field set to 2 as described in [RFC3775].
当收到绑定撤销消息时，响应者必须按照第9.2节所述验证移动报头。属于[RFC3775]。如果由于未通过任何移动性报头测试检查而丢弃数据包，则响应者必须遵循[RFC3775]第9.2节中的处理规则。如果响应者不支持绑定撤销指示消息，并且不识别MH类型16，则会发送一条绑定错误消息，状态字段设置为2，如[RFC3775]中所述。
Upon receiving a packet carrying a Binding Revocation Message, BRI or BRA, the receiving mobility entity MUST verify that the packet was received protected by the security association that is being used to protect the binding registration and Binding Revocation signaling between the two peers, e.g., an IPsec Security Association (SA).
在接收到携带绑定撤销消息、BRI或BRA的分组时，接收移动实体必须验证该分组是由用于保护两个对等方之间的绑定注册和绑定撤销信令的安全关联（例如，IPsec安全关联（SA））保护的。
When the responder receives a packet carrying a Binding Revocation Indication message that was successfully processed as in Section 6.2, the responder, in addition, processes the message as follows:
当响应者接收到一个数据包，该数据包携带一条绑定撤销指示消息，该消息已按照第6.2节的规定成功处理，响应者还将按照以下方式处理该消息：
o The responder MUST validate that the Binding Revocation Indication is formatted as in Section 5.1.
o 响应者必须验证绑定撤销指示的格式是否如第5.1节所述。
o If the Revocation Trigger field is set to a value that the responder does not support, the responder SHOULD reject the Binding Revocation Indication message using status code "Revocation Trigger NOT Supported".
o 如果撤销触发器字段设置为响应程序不支持的值，则响应程序应使用状态代码“撤销触发器不支持”拒绝绑定撤销指示消息。
o If the Revocation Trigger value is NOT allowed with the Binding Revocation Indication message intent, e.g., the Global (G) bit is set and the Revocation Trigger field value is Per-MN-specific, the responder SHOULD reject the Binding Revocation Indication message using status code "Revocation Function NOT Supported".
o 如果绑定撤销指示消息意图不允许撤销触发值，例如，设置了全局（g）位，且撤销触发字段值为每MN特定值，则响应者应使用状态代码“撤销功能不受支持”拒绝绑定撤销指示消息。
o If the responder failed to identify the mobile node(s) bindings as identified in the Binding Revocation Indication message, the responder MUST reject the BRI using status code "Binding Does NOT Exist".
o 如果响应者未能识别绑定撤销指示消息中标识的移动节点绑定，则响应者必须使用状态代码“绑定不存在”拒绝BRI。
When the initiator receives a packet carrying a Binding Revocation Acknowledgement message that was successfully processed as in Section 6.2, the initiator, in addition, processes the message and examines the Status field as follows:
当启动器收到一个数据包，该数据包中包含一条绑定撤销确认消息，该消息已按照第6.2节的要求成功处理，此外，启动器还处理该消息并检查状态字段，如下所示：
o The initiator MUST validate that the sequence number in the Sequence Number field matches the sequence number of an outstanding Binding Revocation Indication that was sent by the initiator. If the sequence number does not match a sequence number of any of the outstanding Binding Revocation Indication messages, the initiator MUST silently discard the message but MAY log the event.
o 启动器必须验证序列号字段中的序列号是否与启动器发送的未完成绑定撤销指示的序列号匹配。如果序列号与任何未完成的绑定撤销指示消息的序列号不匹配，则发起方必须以静默方式放弃该消息，但可以记录该事件。
o If the Status field indicates that the Binding Revocation Indication was processed successfully, the initiator MUST delete the current timer and the mobile node(s) binding(s) and all associated resources.
o 如果状态字段指示绑定撤销指示已成功处理，则启动器必须删除当前计时器和移动节点绑定以及所有相关资源。
o If the Status field indicates any value other than success, the initiator SHOULD examine any mobility options included in the Binding Revocation Acknowledgement. In this case, it is based on the initiator local policy how to handle the mobile node binding. The initiator MAY log the appropriate event to reflect the received status.
o 如果Status字段指示除success以外的任何值，则发起方应检查绑定撤销确认中包含的任何移动选项。在这种情况下，如何处理移动节点绑定取决于启动器本地策略。启动器可以记录适当的事件以反映接收到的状态。
If the initiator does not receive a Binding Revocation Acknowledgement in response to the outstanding Binding Revocation Indication before the InitMINDelayBRIs timer expires, the initiator, e.g., LMA, SHOULD retransmit the same BRI message up to the BRIMaxRetriesNumber as defined in Section 11.
如果启动器在InitMINDelayBRIs计时器到期之前没有收到响应未完成的绑定撤销指示的绑定撤销确认，则启动器（例如LMA）应将相同的BRI消息重新传输至第11节中定义的BRIMaxRetriesNumber。
The retransmissions by the initiator MUST use an exponential back-off process in which the timeout period is doubled upon each retransmission, until either the initiator receives a response or the timeout period reaches the value MAX_BRACK_TIMEOUT. The initiator MAY continue to send these messages at this slower rate up to the BRIMaxRetriesNumber.
发起者的重新传输必须使用指数退避过程，在该过程中，每次重新传输时超时时间加倍，直到发起者接收到响应或超时时间达到值MAX_BRACK_timeout。发起者可以继续以这种较慢的速率发送这些消息，直到BRIMaxRetriesNumber。
If the initiator does not receive a Binding Revocation Acknowledgement message after the BRIMaxRetriesNumber of retransmits have been sent, the initiator SHOULD clean up all resources associated with this mobile node binding. The initiator may log the event.
如果启动器在发送重新传输次数后未收到绑定撤销确认消息，则启动器应清理与此移动节点绑定相关的所有资源。发起者可以记录事件。
To terminate a mobile node registration and its current binding with the home agent, the home agent sends a packet to the mobile node containing a Binding Revocation Indication, with the packet constructed as follows:
为了终止移动节点注册及其与归属代理的当前绑定，归属代理向移动节点发送包含绑定撤销指示的分组，分组构造如下：
o The Revocation Trigger field MUST be set to indicate to the mobile node the reason for revoking its IP mobility binding with the home agent. The Revocation Trigger may be used by the mobile node to take further steps if necessary.
o 必须设置吊销触发器字段，以向移动节点指示吊销其与归属代理的IP移动绑定的原因。如有必要，移动节点可以使用撤销触发器来采取进一步的步骤。
o The Binding Revocation Indication MUST be sent using a Type 2 routing header that contains the mobile node's registered IPv6 home address for the binding being revoked.
o 必须使用类型2路由报头发送绑定撤销指示，该报头包含要撤销的绑定的移动节点的注册IPv6主地址。
o The care-of address for the binding MUST be used as the destination address in the packet's IPv6 header.
o 绑定的转交地址必须用作数据包的IPv6标头中的目标地址。
o If the home agent needs to only revoke the mobile node's IPv4 home address binding, the home agent MUST set the IPv4 HoA Binding Only (V) bit and MUST include the mobile node's registered IPv4 home address that is being revoked in the IPv4 Home Address option.
o 如果归属代理只需要撤销移动节点的IPv4 home address绑定，则归属代理必须设置IPv4 HoA binding only（V）位，并且必须在IPv4 home address选项中包含正在撤销的移动节点的注册IPv4 home address。
When the home agent sends a Binding Revocation Indication to the mobile node, the home agent sets a flag in the mobile node BCE to indicate that revocation is in progress and starts the
当归属代理向移动节点发送绑定撤销指示时，归属代理在移动节点BCE中设置标志以指示撤销正在进行，并启动绑定
InitMINDelayBRIs timer. The home agent maintains the mobile node BCE in this state until it receives a Binding Revocation Acknowledgement or retransmits the Binding Revocation Indication message as described in Section 6.3.
InitMINDelayBRIs计时器。归属代理将移动节点BCE保持在此状态，直到其接收到绑定撤销确认或重新传输绑定撤销指示消息，如第6.3节所述。
In a race condition case, the home agent may receive a Binding Update from the mobile node while the mobile node's BCE has the revocation in progress flag set, the home agent SHOULD handle this case based on the reason for sending the Binding Revocation Indication message and its local policy. In this case, if the home agent accepts the Binding Update, it needs to update the mobile node BCE accordingly, e.g., removing the revocation in progress flag.
在竞争条件情况下，当移动节点的BCE设置了撤销进行中标志时，归属代理可以从移动节点接收绑定更新，归属代理应该基于发送绑定撤销指示消息的原因及其本地策略来处理这种情况。在这种情况下，如果归属代理接受绑定更新，则它需要相应地更新移动节点BCE，例如，移除撤销进行中标志。
When the home agent needs to revoke one or more of a mobile node bindings that were created using multiple care-of address registrations as in [RFC5648], the home agent MUST include all the related BID mobility options that identify these bindings in the Binding Revocation Indication message. In the case when the home agent needs to revoke all of the mobile node bindings, the home agent SHOULD NOT include any of the BID mobility options.
当归属代理需要撤销使用[RFC5648]中的多个转交地址注册创建的一个或多个移动节点绑定时，归属代理必须在绑定撤销指示消息中包含识别这些绑定的所有相关出价移动选项。在归属代理需要撤销所有移动节点绑定的情况下，归属代理不应包括任何出价移动选项。
When the home agent receives a packet carrying a valid Binding Revocation Acknowledgement message, the home agent follows Section 6.2 in processing this message.
当归属代理接收到携带有效绑定撤销确认消息的数据包时，归属代理遵循第6.2节处理该消息。
To terminate a mobile node PMIPv6 registration and its current binding with the local mobility anchor, the local mobility anchor sends a packet to the mobile access gateway containing a Binding Revocation Indication message following the procedure in Section 6.1 and the following rules:
为了终止移动节点PMIPv6注册及其与本地移动锚的当前绑定，本地移动锚按照第6.1节中的过程和以下规则向移动接入网关发送包含绑定撤销指示消息的分组：
o The Proxy Binding (P) bit MUST be set to indicate that the binding being revoked is a PMIPv6 binding.
o 必须设置代理绑定（P）位以指示要撤销的绑定是PMIPv6绑定。
o The Revocation Trigger field MUST be set to indicate to the mobile access gateway the reason for removing the specified mobile node PMIPv6 binding at the local mobility anchor. The Revocation Trigger may be used by the mobile access gateway to learn the mobile node's latest movement.
o 必须设置吊销触发字段，以向移动接入网关指示在本地移动锚处移除指定移动节点PMIPv6绑定的原因。撤销触发器可由移动接入网关用于学习移动节点的最新移动。
o The packet MUST contain the Mobile Node Identifier (MN-ID) option, which contains the mobile node's Network Access Identifier (NAI) that was used in the Proxy Binding Update during the mobile node registration.
o 数据包必须包含移动节点标识符（MN-ID）选项，该选项包含移动节点注册期间在代理绑定更新中使用的移动节点的网络访问标识符（NAI）。
o If the Mobile Node Identifier (MN-ID) is registered in more than one of the mobile node's BCEs and the local mobility anchor does NOT need to revoke all of the mobile node's bindings, the Binding Revocation Indication message MUST contain another identifier to uniquely identify the mobile node binding(s) that is being revoked, e.g., at least one Home Network Prefix option that contains the mobile node's registered Home Network Prefix (HNP) for the binding being revoked.
o 如果移动节点标识符（MN-ID）在移动节点的多个bce中注册，并且本地移动锚不需要撤销移动节点的所有绑定，则绑定撤销指示消息必须包含另一个标识符以唯一地标识正在撤销的移动节点绑定，例如。，至少一个家庭网络前缀选项，其中包含正在撤销的绑定的移动节点的注册家庭网络前缀（HNP）。
o In the case of revoking all Per-Peer bindings, the local mobility anchor MUST set the Global (G) bit and the Revocation Trigger MUST contain the value "Per-Peer Policy" to request the mobile access gateway to remove all Per-Peer bindings that are registered with the local mobility anchor and this mobile access gateway.
o 在撤销所有每对等绑定的情况下，本地移动锚必须设置全局（G）位，并且撤销触发器必须包含值“每对等策略”，以请求移动接入网关删除在本地移动锚和该移动接入网关注册的所有每对等绑定。
o The proxy care-of address for the binding MUST be used as the destination address in the packet's IPv6 header. However, in the case when IPsec is used to protect the Proxy MIPv6 signaling as specified in [RFC5213], the destination address MUST be set to the mag_address that is being used for keying the IPsec SA. If the mag_address is different than the mobile node proxy care-of address, the Alternate Care-of Address option MUST be included and MUST contain the mobile node proxy care-of address.
o 绑定的代理转交地址必须用作数据包的IPv6标头中的目标地址。但是，如果使用IPsec保护[RFC5213]中指定的代理MIPv6信令，则必须将目标地址设置为用于为IPsec SA设置密钥的mag_地址。如果mag_地址不同于移动节点代理转交地址，则必须包括备用转交地址选项，并且必须包含移动节点代理转交地址。
The local mobility anchor MAY delete the mobile node(s) IP tunnel immediately after sending the initial Binding Revocation Indication and before receiving the Binding Revocation Acknowledgement message.
本地移动锚可以在发送初始绑定撤销指示之后和在接收绑定撤销确认消息之前立即删除移动节点IP隧道。
When the local mobility anchor sends a Binding Revocation Indication to the mobile access gateway to remove a specific binding, the local mobility anchor sets a flag in the mobile node proxy BCE to indicate that revocation is in progress and starts the InitMINDelayBRIs timer. The local mobility anchor SHOULD maintain the mobile node proxy BCE in this state until it receives a Binding Revocation Acknowledgement or the BRIMaxRetransmitNumber is reached. In the case when the local mobility anchor sets the Revocation Trigger field to a value that indicates inter-MAG handover, the local mobility anchor MAY switch the mobile node IP tunnel to the target mobile access gateway before sending the Binding Revocation Indication to the source mobile access gateway.
当本地移动锚向移动接入网关发送绑定撤销指示以移除特定绑定时，本地移动锚在移动节点代理BCE中设置标志以指示撤销正在进行，并启动InitMINDelayBRIs计时器。本地移动锚应将移动节点代理BCE保持在此状态，直到它收到绑定撤销确认或达到重新传输编号。在本地移动锚将撤销触发字段设置为指示MAG间切换的值的情况下，本地移动锚可以在将绑定撤销指示发送到源移动接入网关之前将移动节点IP隧道切换到目标移动接入网关。
In a race condition case, the local mobility anchor may receive a Proxy Binding Update from the mobile access gateway while the mobile node's proxy BCE has the revocation in progress flag set. The local mobility anchor should handle this case based on the reason for sending the Binding Revocation Indication message and its local
在竞争条件情况下，当移动节点的代理BCE设置了撤销进行中标志时，本地移动锚可以从移动接入网关接收代理绑定更新。本地移动性锚应根据发送绑定撤销指示消息的原因及其本地特性来处理这种情况
policy. In this case, if the local mobility anchor accepts the Proxy Binding Update, it needs to update the mobile node proxy BCE accordingly, e.g., removing the revocation in progress flag.
政策在这种情况下，如果本地移动锚接受代理绑定更新，则它需要相应地更新移动节点代理BCE，例如，移除撤销进行中标志。
When the local mobility anchor needs to revoke all the mobile node proxy BCEs that are registered with the local mobility anchor and the mobile access gateway peer, it MUST set the Global (G) bit and set the value of the Revocation Trigger field to "Per-Peer Policy". In this case, the local mobility anchor MUST NOT include any mobility options in this Binding Revocation Indication message.
当本地移动锚需要撤销在本地移动锚和移动接入网关对等方注册的所有移动节点代理bce时，它必须设置全局（G）位，并将撤销触发字段的值设置为“每个对等方策略”。在这种情况下，本地移动性锚点不得在此绑定撤销指示消息中包括任何移动性选项。
When the local mobility anchor needs to revoke all mobile nodes proxy BCEs that belong to a specific realm and are registered with the local mobility anchor and the mobile access gateway peer, the local mobility anchor MUST set the Global (G) bit and set the value of the Revocation Trigger field to "Revoking Mobility Node Local Policy". In this case, the local mobility anchor MUST include a mobility option in the Binding Revocation Indication that is shared among all the impacted mobile nodes BCEs, e.g., the mobile node identifier option, MN-ID option, with a subtype value of 1. In this case, the NAI value in the MN-ID MUST follow the format where the content after the "@" character defines the realm that is shared amongst all of the impacted mobile nodes proxy BCEs. As an example: @example.com identifies all mobile nodes whose MN-ID value contains "example.com" as the realm, e.g., "1234abdelta@example.com", "axxxyzd@example.com", and "abcdefg.xyz123@example.com", but not "1234abdelta@foo.example.com".
当本地移动性锚点需要撤销属于特定领域并在本地移动性锚点和移动接入网关对等点注册的所有移动节点代理BCE时，本地移动性锚点必须设置全局（G）位，并将撤销触发字段的值设置为“撤销移动性节点本地策略”。在这种情况下，本地移动锚必须在绑定撤销指示中包括在所有受影响的移动节点bce之间共享的移动选项，例如，子类型值为1的移动节点标识符选项MN-ID选项。在这种情况下，MN-ID中的NAI值必须遵循“@”字符后的内容定义在所有受影响的移动节点代理BCE之间共享的领域的格式。例如：@example.com将其MN-ID值包含“example.com”的所有移动节点标识为域，例如“1234abdelta@example.com", "axxxyzd@example.com以及"abcdefg。xyz123@example.com“，但不是”1234abdelta@foo.example.com".
When the local mobility anchor needs to revoke a subgroup of the mobile nodes proxy BCEs that belong to a specific realm and are registered with the local mobility anchor and the mobile access gateway, the local mobility anchor MUST set the Global (G) bit and set the value of the Revocation Trigger field to "Revoking Mobility Node Local Policy". In this case, the local mobility anchor MUST include an additional mobility option to the mobile node identifier option (MN-ID) option, with a subtype value of 1. In other words, the impacted mobile node BCEs are those that have an MN-ID with a realm as specified above and, e.g., are assigned the same proxy care-of address as the one included in the Alternate Care-of Address mobility option.
当本地移动性锚需要撤销属于特定领域并在本地移动性锚和移动接入网关注册的移动节点代理bce的子组时，本地移动性锚必须设置全局（G）位并将撤销触发字段的值设置为“撤销移动性节点本地策略”。在这种情况下，本地移动性锚必须包括移动节点标识符选项（MN-ID）选项之外的附加移动性选项，子类型值为1。换句话说，受影响的移动节点bce是那些具有具有如上所述的域的MN-ID的移动节点bce，并且例如，被分配了与包括在备用转交地址移动选项中的代理转交地址相同的代理转交地址。
When the mobile node is registered with multiple Home Network Prefixes for the same proxy care-of address, the local mobility anchor SHOULD include an HNP option for each registered HNP in the Binding Revocation Indication. Alternatively, it MAY include only the mobile node identifier (MN-ID) option with the mobile node NAI included to indicate to the mobile access gateway to remove all bindings of the specified mobile node NAI in the MN-ID option.
当移动节点为同一代理转交地址使用多个家庭网络前缀注册时，本地移动锚应在绑定撤销指示中为每个注册的HNP包括HNP选项。或者，它可以仅包括移动节点标识符（MN-ID）选项，其中包括移动节点NAI，以指示移动接入网关移除MN-ID选项中指定的移动节点NAI的所有绑定。
According to the Proxy Mobile IPv6 specification [RFC5213], if the local mobility anchor receives a Proxy Binding Update message from a new mobile access gateway for extending the binding lifetime of the only BCE of this mobile node with the Handoff Indicator value set to "Handoff state unknown (4)", the local mobility anchor waits a period of MaxDelayBeforeNewBCEAssign to receive a de-registration message from the previous mobile access gateway before updating the mobile node's BCE with the new point of attachment. If a de-registration message is not received, the local mobility anchor considers the received Proxy Binding Update message as a request for a new BCE and if processed successfully, the local mobility anchor assigns a different HNP for the new BCE.
根据代理移动IPv6规范[RFC5213]，如果本地移动锚从新的移动接入网关接收到代理绑定更新消息，用于延长该移动节点的唯一BCE的绑定生存期，切换指示符值设置为“切换状态未知（4）”，本地移动锚在使用新的连接点更新移动节点的BCE之前，等待maxdelaybeforewbeasign一段时间，以从先前的移动接入网关接收取消注册消息。如果未接收到注销消息，则本地移动锚将接收到的代理绑定更新消息视为对新BCE的请求，并且如果处理成功，则本地移动锚将为新BCE分配不同的HNP。
This document updates the local mobility anchor's behavior in this case. If the local mobility anchor supports the binding revocation mechanism as described in this document, it SHOULD proactively send a Binding Revocation Indication message to the previous mobile access gateway instead of waiting for a de-registration from the previous mobile access gateway. In the Binding Revocation Indication message, the Revocation Trigger MUST be set to "Inter-MAG Handover - Unknown".
本文档更新了本地移动锚在这种情况下的行为。如果本地移动锚支持本文档中所述的绑定撤销机制，则其应主动向前一个移动接入网关发送绑定撤销指示消息，而不是等待从前一个移动接入网关取消注册。在绑定撤销指示消息中，撤销触发器必须设置为“MAG间切换-未知”。
If the local mobility anchor sent a Binding Revocation Indication message with the Revocation Trigger field set to "Inter-MAG Handover - Unknown" and while waiting for a response, Binding Revocation Acknowledgement, the following are possible conditions that the local mobility anchor MUST handle as specified below:
如果本地移动锚发送了绑定撤销指示消息，撤销触发字段设置为“MAG间切换-未知”，并且在等待响应、绑定撤销确认时，本地移动锚必须按照以下规定处理以下可能情况：
o If the local mobility anchor receives a successful Binding Revocation Acknowledgement message or a de-registration message from the previous mobile access gateway, the local mobility anchor MUST update the mobile node BCE as if it received a de-registration message as described in [RFC5213].
o 如果本地移动性锚从先前的移动接入网关接收到成功的绑定撤销确认消息或注销消息，则本地移动性锚必须更新移动节点BCE，如同其接收到[RFC5213]中所述的注销消息一样。
o If the local mobility anchor receives a Binding Revocation Acknowledgement message with the Status field set to "Revocation Failed - MN is Attached", the local mobility anchor SHOULD update the mobile node BCE as if it did NOT receive a de-registration before the MaxDelayBeforeNewBCEAssign timer expired by creating a new BCE as described in [RFC5213].
o 如果本地移动性锚接收到状态字段设置为“吊销失败-MN已连接”的绑定吊销确认消息，则本地移动性锚应更新移动节点BCE，如同在MaxDelayBeforeNewbeasSign计时器过期之前未接收到注销一样，方法是创建新的BCE，如中所述[RFC5213]。
o If the local mobility anchor did not receive a Binding Revocation Acknowledgement message or a de-registration Proxy Binding Update from the previous mobile access gateway after it exhausted all of the Binding Revocation Indication message retransmissions as described in Section 6.3, the local mobility anchor SHOULD update the mobile node's BCE as if it did NOT receive a de-registration before the MaxDelayBeforeNewBCEAssign timer expired by creating a new BCE as described in [RFC5213]. Note that the local mobility
o 如第6.3节所述，如果本地移动锚在耗尽所有绑定撤销指示消息重传后未从先前移动接入网关接收到绑定撤销确认消息或注销代理绑定更新，如[RFC5213]所述，本地移动锚应通过创建新的BCE更新移动节点的BCE，就像在MaxDelayBeforeNewbeasSign计时器过期之前没有收到取消注册一样。请注意，本地移动性
anchor SHOULD use the recommended number of retransmissions for the Binding Revocation Indication message as described in Section 11 to avoid delaying the creation of a new Binding Cache entry for too long, if the mobile node is actually attaching to the new MAG with a different interface.
如果移动节点实际连接到具有不同接口的新MAG，则锚点应使用第11节中描述的绑定撤销指示消息的建议重传次数，以避免延迟创建新绑定缓存项太长时间。
When the mobile node is registered with an IPv4 proxy home address in addition to the Home Network Prefix where both of the IPv4 proxy HoA (pHoA) and HNP are bound to the same proxy CoA (pCoA), the local mobility anchor MAY revoke the mobile node IPv4 proxy HoA binding to the current mobile node proxy CoA while maintaining the mobile node binding of the HNP to its current pCoA as part of the mobile node BCE. In this case, if the local mobility anchor decides to revoke the mobile node IPv4 proxy HoA only, it MUST send a Binding Revocation Indication message following the procedure in Section 6.1 and the following rules:
当移动节点在归属网络前缀之外注册IPv4代理归属地址时，其中IPv4代理HoA（pHoA）和HNP都绑定到同一代理CoA（pCoA），本地移动锚可以撤销移动节点IPv4代理HoA与当前移动节点代理CoA的绑定，同时保持HNP与其当前pCoA的移动节点绑定，作为移动节点BCE的一部分。在这种情况下，如果本地移动锚决定仅撤销移动节点IPv4代理HoA，则必须按照第6.1节中的过程和以下规则发送绑定撤销指示消息：
o The IPv4 HoA Binding Only (V) bit MUST be set in the BRI to indicate that only the IPv4 home address binding is being revoked.
o 必须在BRI中设置仅IPv4 HoA绑定（V）位，以指示仅撤销IPv4家庭地址绑定。
o The IPv4 Home Address Request option MUST be included with the mobile node's registered proxy home IPv4 address that is being released in addition to the MN-ID option.
o 除了MN-ID选项外，移动节点的注册代理主IPv4地址还必须包括IPv4主地址请求选项。
o The mobile node Home Network Prefix option MUST NOT be included.
o 不得包括移动节点家庭网络前缀选项。
o The Revocation Trigger field MUST be set to an appropriate value, e.g., "User Initiated Session(s) Termination".
o 撤销触发字段必须设置为适当的值，例如“用户发起的会话终止”。
When the local mobility anchor receives a packet carrying a Binding Revocation Indication that was successfully processed as in Section 6.2, the local mobility anchor processes the message as follows:
当本地移动性锚接收到携带绑定撤销指示的数据包，该数据包已按照第6.2节的要求成功处理时，本地移动性锚按如下方式处理该消息：
o If the (P) bit is set, the local mobility anchor MUST validate that all impacted bindings have the proxy binding flag set.
o 如果设置了（P）位，则本地移动锚必须验证所有受影响的绑定是否设置了代理绑定标志。
o If the Global (G) bit is set and the Revocation Trigger field value is "Per-Peer Policy", the LMA MUST validate that the Proxy (P) bit is set and the MN-ID option is present with the mobile access gateway identity included. In addition, the local mobility anchor MUST verify that the identified mobile access gateway as per the value in the MN-ID option is authorized to use the global revocation with revocation trigger value "Per-Peer Policy", see Section 13. If the local mobility anchor processes the Global
o 如果设置了全局（G）位，且撤销触发字段值为“每个对等策略”，则LMA必须验证是否设置了代理（P）位，以及是否存在MN-ID选项以及是否包含移动接入网关标识。此外，本地移动锚必须验证根据MN-ID选项中的值识别的移动接入网关是否被授权使用具有撤销触发值的全局撤销“每对等策略”，参见第13节。如果本地移动性锚处理全局
Binding Revocation Indication message successfully, it MUST accept the Binding Revocation Indication message using the status code "success".
绑定撤销指示消息成功，它必须使用状态代码“成功”接受绑定撤销指示消息。
o If the mobile access gateway is not authorized to use the Per-Peer Global revocation feature or the received Binding Revocation Indication message has the Global (G) bit set and the Revocation Trigger field is set to "Per-Peer Policy", but the MN-ID option is not included, the local mobility anchor MUST reject the Binding Revocation Indication message using status code "Global Revocation NOT Authorized".
o 如果移动接入网关未被授权使用每对等全局撤销功能，或者接收到的绑定撤销指示消息设置了全局（G）位，并且撤销触发字段设置为“每对等策略”，但不包括MN-ID选项，本地移动锚必须使用状态代码“Global Revocation NOT Authorized”拒绝绑定撤销指示消息。
o If the Global (G) bit is set and the Revocation Trigger value is "Per-Peer Policy", and only the mobile node identifier (MN-ID) option is included, the local mobility anchor MUST revoke all mobile node bindings for which the proxy CoA is the one used as the source of the IPv6 packet that carried the Binding Revocation Indication. However, if the Alternate Care-of Address option is included in addition to the mobile node identifier option, the local mobility anchor MUST revoke all mobile node bindings whose proxy care-of address matches the care-of address in the Alternate Care-of Address option. After the local mobility anchor successfully processes the Binding Revocation Indication message and identifies all impacted mobile nodes bindings, it MUST accept the Binding Revocation Indication message using the status code "success".
o 如果设置了全局（G）位且撤销触发值为“每个对等策略”，并且仅包括移动节点标识符（MN-ID）选项，则本地移动锚必须撤销所有移动节点绑定，其中代理CoA是作为携带绑定撤销指示的IPv6包的源的移动节点绑定。但是，如果除了移动节点标识符选项之外还包括备用转交地址选项，则本地移动锚必须撤销其代理转交地址与备用转交地址选项中的转交地址匹配的所有移动节点绑定。本地移动锚成功处理绑定撤销指示消息并识别所有受影响的移动节点绑定后，它必须使用状态代码“success”接受绑定撤销指示消息。
o If the local mobility anchor accepted the Binding Revocation Indication message but one or more of the bindings identified in the received Binding Revocation Indication message has already been released, the local mobility anchor MUST accept the message and it MAY set the Status field to "partial success" and include the mobile node identifier (MN-ID) or the Home Network Prefix option to identify the binding(s) that failed the revocation procedure.
o 如果本地移动锚接受绑定撤销指示消息，但是在接收到的绑定撤销指示消息中标识的一个或多个绑定已经被释放，则本地移动锚必须接受该消息，并且它可以将状态字段设置为“部分成功”，并包括移动节点标识符（MN-ID）或家庭网络前缀选项，以标识撤销过程失败的绑定。
o If the Global (G) bit is not set, the local mobility anchor uses the included mobility options to identify the impacted mobile node binding as follows:
o 如果未设置全局（G）位，则本地移动锚使用包括的移动选项来识别受影响的移动节点绑定，如下所示：
1. If only the mobile node identifier (MN-ID) option is included, the local mobility anchor MUST accept the message and revoke all bindings for this mobile node that use the specified mobile node NAI including the IPv4 Home Address binding(s) if present.
1. 如果仅包括移动节点标识符（MN-ID）选项，则本地移动锚必须接受该消息并撤销该移动节点使用指定移动节点NAI的所有绑定，包括IPv4家庭地址绑定（如果存在）。
2. If the mobile node identifier (MN-ID) and one Home Network Prefix option are included, the local mobility anchor MUST accept the message and only remove the specified mobile node proxy binding.
2. 如果包括移动节点标识符（MN-ID）和一个家庭网络前缀选项，则本地移动锚必须接受消息并仅移除指定的移动节点代理绑定。
3. If the mobile node identifier (MN-ID) option and more than one Home Network Prefix options are included, the local mobility anchor MUST accept the message and remove all bindings that are referenced by these Home Network Prefixes for the specified mobile node NAI.
3. 如果包括移动节点标识符（MN-ID）选项和多个家庭网络前缀选项，则本地移动锚必须接受消息并删除指定移动节点NAI的这些家庭网络前缀引用的所有绑定。
4. If the IPv4 HoA binding Only (V) bit is set and the mobile node identifier (MN-ID) option and the IPv4 Home Address Request option are included, the local mobility anchor MUST accept the message and remove only the IPv4 HoA address binding to the mobile node current proxy care-of address.
4. 如果设置了仅IPv4 HoA绑定（V）位，并且包括移动节点标识符（MN-ID）选项和IPv4家庭地址请求选项，则本地移动锚必须接受消息并仅删除与移动节点当前代理转交地址的IPv4 HoA地址绑定。
The Revocation Trigger field value in the received Binding Revocation Indication could be used by the local mobility anchor to log an event or update some local parameters that track the state of the peer mobile access gateway.
本地移动锚可使用接收到的绑定撤销指示中的撤销触发字段值来记录事件或更新跟踪对等移动接入网关状态的一些本地参数。
After the local mobility anchor accepts or rejects a Binding Revocation Indication message, the local mobility anchor MUST follow Sections 6.1 and 6.1.2 to send a Binding Revocation Acknowledgement message to the mobile access gateway.
在本地移动锚接受或拒绝绑定撤销指示消息后，本地移动锚必须遵循第6.1节和第6.1.2节，向移动接入网关发送绑定撤销确认消息。
When the mobile access gateway receives a packet carrying a Binding Revocation Indication that was successfully processed as in Section 6.2, the mobile access gateway processes the message as follows:
当移动接入网关接收到一个携带绑定撤销指示的数据包，该数据包已按照第6.2节的要求成功处理，移动接入网关将按如下方式处理该消息：
o If the Global (G) bit is set and the Revocation Trigger field value is "Per-Peer Policy", the mobile access gateway MUST validate that the Proxy (P) bit is set and no mobility options are included in the message. If the mobile access gateway processes the Global Binding Revocation Indication message successfully, it MUST accept the Binding Revocation Indication message using the status code "success".
o 如果设置了全局（G）位，并且吊销触发字段值为“每对等策略”，则移动接入网关必须验证是否设置了代理（P）位，并且消息中不包括移动选项。如果移动接入网关成功处理全局绑定撤销指示消息，则必须使用状态代码“成功”接受绑定撤销指示消息。
o If the Global (G) bit is set and the Revocation Trigger field value is "Revoking Mobility Node Local Policy", the mobile access gateway MUST validate that the Proxy (P) bit is set and at least the MN-ID option with the subtype value of 1 is included in the
o 如果设置了全局（G）位，且撤销触发字段值为“撤销移动节点本地策略”，则移动接入网关必须验证是否设置了代理（P）位，并且至少子类型值为1的MN-ID选项包含在该字段中
Binding Revocation Indication and it is formatted as described is Section 8.1. If the mobile access gateway processes this Global Binding Revocation Indication message successfully, it MUST accept the message using the status code "success".
绑定撤销指示，其格式如第8.1节所述。如果移动接入网关成功处理此全局绑定撤销指示消息，则它必须使用状态代码“success”接受该消息。
o If the Global (G) bit is set and the Revocation Trigger field value is "Revoking Mobility Node Local Policy", and no mobility options are included in the Binding Revocation Indication message or the mobile access gateway is not able to identify the impacted mobile nodes bindings based on the included mobility options, the mobile access gateway MUST treat this as an error scenario. In this case, the mobile access gateway MUST reject the Binding Revocation Indication message using status code "Revoked Mobile Nodes Identity Required".
o 如果设置了全局（G）位且撤销触发字段值为“撤销移动节点本地策略”，并且绑定撤销指示消息中不包括移动选项，或者移动接入网关无法基于包括的移动选项识别受影响的移动节点绑定，移动接入网关必须将此视为错误场景。在这种情况下，移动接入网关必须使用状态代码“需要撤销的移动节点标识”拒绝绑定撤销指示消息。
o If the Revocation Trigger field value in the received Binding Revocation Indication message indicates inter-MAG handover, e.g., Inter-MAG Handover - Unknown, the mobile access gateway uses the mobility option(s) included in the Binding Revocation Indication message to identify the mobile node binding. The mobile access gateway SHOULD ensure that the mobile node is no longer attached to the mobile access gateway before accepting the BRI message using status code "success". However, if the mobile access gateway verified that the mobile node is still directly attached, the mobile access gateway MUST reject the BRI using status code "Revocation failed - MN is Attached".
o 如果接收到的绑定撤销指示消息中的撤销触发字段值指示MAG间切换，例如，MAG间切换-未知，则移动接入网关使用包括在绑定撤销指示消息中的移动选项来识别移动节点绑定。在使用状态代码“成功”接受BRI消息之前，移动接入网关应确保移动节点不再连接到移动接入网关。但是，如果移动接入网关验证移动节点仍然直接连接，则移动接入网关必须使用状态代码“吊销失败-MN已连接”拒绝BRI。
o If the IPv4 HoA Binding Only (V) bit is set, the mobile access gateway uses the MN-ID option to identify the mobile node binding entry in the Binding Update List (BUL). The mobile access gateway MUST verify that the IPv4 address included in the IPv4 Home Address Request option in the received Binding Revocation Indication is the same as the IPv4 proxy HoA that is assigned to the mobile node. After the mobile access gateway successfully validates the received IPv4 home address as the mobile node IPv4 HoA, it MUST consider this as an indication to ONLY release the mobile node IPv4 proxy HoA binding to the mobile node current proxy CoA. Consequently, it MUST continue to maintain the mobile node IPv6 proxy HoA or HNP binding to the current mobile node proxy CoA as part of the mobile node binding in the BUL entry and release all resources associated with the MN IPv4 proxy HoA binding to the MN pCoA. If the mobile access gateway processed the BRI successfully, the mobile access gateway MUST accept the BRI using status code "success". On the other hand, if the mobile access gateway is able to identify the mobile node binding using the MN-ID but failed to identify the received IPv4 proxy HoA, the mobile access gateway MUST reject the BRI using status code "Binding Does NOT Exist".
o 如果设置了IPv4 HoA仅绑定（V）位，则移动访问网关将使用MN-ID选项来标识绑定更新列表（BUL）中的移动节点绑定条目。移动接入网关必须验证接收到的绑定撤销指示中的IPv4家庭地址请求选项中包含的IPv4地址是否与分配给移动节点的IPv4代理HoA相同。在移动接入网关成功验证所接收的IPv4家庭地址作为移动节点IPv4 HoA之后，它必须考虑这是仅释放绑定到移动节点当前代理COA的移动节点IPv4代理HoA的指示。因此，它必须继续维护移动节点IPv6代理HoA或HNP绑定到当前移动节点代理CoA，作为BUL条目中移动节点绑定的一部分，并释放与MN IPv4代理HoA绑定到MN pCoA相关的所有资源。如果移动接入网关成功处理BRI，则移动接入网关必须使用状态代码“成功”接受BRI。另一方面，如果移动接入网关能够使用MN-ID识别移动节点绑定，但未能识别接收到的IPv4代理HoA，则移动接入网关必须使用状态代码“绑定不存在”拒绝BRI。
o If the mobile access gateway accepts the Binding Revocation Indication message but one or more of the bindings identified in the received Binding Revocation Indication message has already been released before processing the Binding Revocation Indication, the mobile access gateway MUST accept the Binding Revocation Indication message. In this case, the mobile access gateway MAY set the Status field to "partial success" and include the mobile node identifier (MN-ID) or the Home Network Prefix option to identify the binding(s) that failed to be removed as part of the revocation procedure.
o 如果移动接入网关接受绑定撤销指示消息，但在处理绑定撤销指示之前已释放接收到的绑定撤销指示消息中标识的一个或多个绑定，则移动接入网关必须接受绑定撤销指示消息。在这种情况下，移动接入网关可将状态字段设置为“部分成功”，并包括移动节点标识符（MN-ID）或家庭网络前缀选项，以识别作为撤销过程的一部分而未能移除的绑定。
The Revocation Trigger field value in the received Binding Revocation Indication could be used by the mobile access gateway to define what actions the mobile access gateway could do to inform the mobile node that its IP connectivity to the current HNP has been terminated, e.g., if the Revocation Trigger field is set to "Administrative Reason", the mobile access gateway may terminate the IPv6 or IPv4 mobility session on the access link and notify the mobile node. The specific details and considerations on how the mobile access gateway terminates IPv6 or IPv4 mobility session on the access link and notifies the mobile node can be found in [RFC5213] and [RFC5844].
移动接入网关可以使用接收到的绑定撤销指示中的撤销触发字段值来定义移动接入网关可以执行哪些操作来通知移动节点其与当前HNP的IP连接已终止，例如，如果撤销触发字段设置为“管理原因”，移动接入网关可终止接入链路上的IPv6或IPv4移动会话并通知移动节点。有关移动接入网关如何在接入链路上终止IPv6或IPv4移动会话并通知移动节点的具体细节和注意事项，请参见[RFC5213]和[RFC5844]。
After the mobile access gateway accepts or rejects a Binding Revocation Indication message, the mobile access gateway MUST follow Sections 6.1 and 6.1.2 to send a Binding Revocation Acknowledgement message to the local mobility anchor.
在移动接入网关接受或拒绝绑定撤销指示消息后，移动接入网关必须遵循第6.1节和第6.1.2节，向本地移动锚发送绑定撤销确认消息。
The mobile access gateway could send a Binding Revocation Indication message to indicate the termination of multiple mobile node bindings, e.g., when using the global revocation with the Global (G) bit set. In this case, when an event occurs that requires the mobile access gateway to inform the local mobility anchor peer to terminate all mobile node bindings that are registered at the local mobility anchor and the mobile access gateway, the mobile access gateway sends a Binding Revocation Indication message following the procedure in Section 6.1 and the following:
移动接入网关可发送绑定撤销指示消息以指示多个移动节点绑定的终止，例如，当使用具有全局（g）比特集的全局撤销时。在这种情况下，当发生要求移动接入网关通知本地移动锚对等方终止在本地移动锚和移动接入网关处注册的所有移动节点绑定的事件时，移动接入网关按照第6.1节中的步骤和以下步骤发送绑定撤销指示消息：
o The Proxy Binding (P) bit MUST be set to indicate that the binding(s) being revoked is a PMIPv6 binding.
o 必须设置代理绑定（P）位，以指示要撤销的绑定是PMIPv6绑定。
o The Global (G) bit MUST be set and the Revocation Trigger MUST contain a value of "Per-Peer Policy" in the Binding Revocation Indication to request the local mobility anchor to remove all Per-Peer bindings that are registered with the local mobility anchor and the mobile access gateway. In this case, the MN-ID option MUST be included in the Binding Revocation Indication and contain
o 必须设置全局（G）位，并且撤销触发器必须在绑定撤销指示中包含“每对等策略”值，以请求本地移动锚删除在本地移动锚和移动接入网关中注册的所有每对等绑定。在这种情况下，MN-ID选项必须包含在绑定撤销指示中并包含
the mobile access gateway identity. In addition, the mobile access gateway MAY include the Alternate Care-of Address option. If included, the Alternate Care-of Address option MUST contain the proxy care-of address the bindings that are being impacted by this Binding Revocation Indication message.
移动接入网关标识。此外，移动接入网关可包括备用转交地址选项。如果包括，备用转交地址选项必须包含受此绑定撤销指示消息影响的绑定的代理转交地址。
o The mobile access gateway address MAY be used as the source address in the packet's IPv6 header.
o 移动接入网关地址可用作分组的IPv6报头中的源地址。
As described in Section 6.3, the mobile access gateway SHOULD retransmit the Binding Revocation Indication to the local mobility anchor until it receives a matching Binding Revocation Acknowledgement or the BRIMaxRetransmitNumber is reached. The mobile access gateway MAY delete the mobile node IP tunnels immediately after sending the Binding Revocation Indication and before receiving a Binding Revocation Acknowledgement message from the LMA.
如第6.3节所述，移动接入网关应将绑定撤销指示重新传输到本地移动锚，直到收到匹配的绑定撤销确认或达到重新传输号码。移动接入网关可以在发送绑定撤销指示之后和从LMA接收绑定撤销确认消息之前立即删除移动节点IP隧道。
In response to a Binding Revocation Indication message, if the mobile access gateway receives a packet carrying a Binding Revocation Acknowledgement that was successfully processed as in Section 6.2 and the Status field indicates "Global Revocation NOT Authorized", the mobile access gateway is not authorized to participate in a Per-Peer Global Revocation. The mobile access gateway SHOULD NOT retry sending a Binding Revocation Indication with the Global (G) bit set and the Revocation Trigger field value set to "Per-Peer Policy" to the same local mobility agent. The mobile access gateway should raise an alarm or log an event to indicate this rejection.
作为对绑定撤销指示消息的响应，如果移动接入网关接收到携带绑定撤销确认的数据包，该确认已按照第6.2节的要求成功处理，并且状态字段指示“未授权全局撤销”，移动访问网关未被授权参与对等全局吊销。移动接入网关不应尝试向同一本地移动代理发送绑定撤销指示，其中全局（G）位设置和撤销触发字段值设置为“每对等策略”。移动接入网关应发出警报或记录事件以指示此拒绝。
Upon receiving a packet carrying a Binding Revocation Indication, the mobile node MUST validate the packet according to Section 6.2 and the following tests:
在接收到携带绑定撤销指示的分组后，移动节点必须根据第6.2节和以下测试验证该分组：
o The mobile node MUST verify that the IP address in the Type 2 routing header is its Home Address and that its Binding Update List contains an entry for that Home Address. If one of the tests fails, the mobile node SHOULD silently discard the received Binding Revocation Indication message.
o 移动节点必须验证类型2路由报头中的IP地址是否为其家庭地址，以及其绑定更新列表是否包含该家庭地址的条目。如果其中一个测试失败，移动节点应该默默地丢弃接收到的绑定撤销指示消息。
o If mobile node Binding Update List contains an entry for the IP address in the Type 2 routing header of the received Binding Revocation Indication packet, the mobile node MUST accept the BRI message using status code "success".
o 如果移动节点绑定更新列表包含接收到的绑定撤销指示数据包的类型2路由报头中的IP地址条目，则移动节点必须使用状态代码“success”接受BRI消息。
o If the IPv4 HoA Binding Only (V) bit is set in the received BRI message, the mobile node MUST verify that there is an IPv4 Home Address option in the received Binding Revocation Indication and
o 如果在接收到的BRI消息中设置了IPv4 HoA仅绑定（V）位，则移动节点必须验证接收到的绑定撤销指示中是否存在IPv4 Home Address选项，并且
the IPv4 address included in the IPv4 Home Address option is the same as its IPv4 HoA that is assigned to the mobile node. If this verification is successful, the mobile node MUST consider this Binding Revocation Indication as an indication to ONLY release the mobile node IPv4 HoA binding to its current care-of address. Consequently, the mobile node MUST continue to maintain its IPv6 HoA binding to the current CoA as part of the mobile node binding in the BUL entry and release all resources associated with the MN IPv4 HoA binding. In this case, the mobile node MUST accept the Binding Revocation Indication message using status code "success". On the other hand, if the IPv4 Home Address Option was NOT included in the received BRI with the (V) bit is set, the MN MUST reject the BRI message with status code "IPv4 Home Address Option Required". Additionally, if the IPv4 HoA received in the IPv4 Home Address Option is NOT the one assigned to the mobile node, the mobile node SHOULD reject the Binding Revocation Indication with status code "Binding Does NOT Exist".
IPv4 Home address选项中包含的IPv4地址与其分配给移动节点的IPv4 HoA相同。如果该验证是成功的，则移动节点必须考虑此绑定撤销指示作为仅释放绑定到其当前的护理地址的移动节点IPv4 HoA的指示。因此，移动节点必须继续保持其与当前CoA的IPv6 HoA绑定，作为BUL条目中移动节点绑定的一部分，并释放与MN IPv4 HoA绑定相关联的所有资源。在这种情况下，移动节点必须使用状态代码“success”接受绑定撤销指示消息。另一方面，如果在设置了（V）位的情况下，接收到的BRI中未包括IPv4家庭地址选项，则MN必须拒绝状态代码为“需要IPv4家庭地址选项”的BRI消息。此外，如果在IPv4 Home Address选项中接收的IPv4 HoA不是分配给移动节点的，则移动节点应拒绝状态代码为“Binding NOT Existence”（绑定不存在）的绑定撤销指示。
o The mobile node MUST verify that the (P) bit in the Binding Revocation Indication is NOT set. If the (P) bit is set, the mobile node MUST reject the Binding Revocation Indication using status code "Proxy Binding Revocation NOT Supported".
o 移动节点必须验证绑定撤销指示中的（P）位未设置。如果设置了（P）位，则移动节点必须使用状态代码“不支持代理绑定撤销”，拒绝绑定撤销指示。
o If the mobile node has registered multiple care-of addresses with its home agent, the mobile node MUST verify which binding is being revoked by examining the content of the Binding Revocation Indication message. If the mobile node received a Binding Revocation Indication with one or more BID options and its home address is included in the Type 2 routing header, the mobile node MUST consider all of the care-of addresses bindings, identified in the BID options, with this home address as being revoked. In this case, if the BRI validation is successful, the mobile node MUST accept the Binding Revocation Indication message with status code "success".
o 如果移动节点已向其归属代理注册了多个转交地址，则移动节点必须通过检查绑定撤销指示消息的内容来验证正在撤销哪个绑定。如果移动节点接收到具有一个或多个出价选项的绑定撤销指示并将其归属地址包含在类型2路由报头中，则移动节点必须考虑所有在投标选项中标识的地址绑定，并将该归属地址作为撤销。在这种情况下，如果BRI验证成功，移动节点必须接受状态代码为“成功”的绑定撤销指示消息。
o If the mobile node has multiple care-of address bindings with its home agent and received a Binding Revocation Indication, without any BID option included and its home address was included in the Type 2 routing header, the mobile node MUST consider all of its registered care-of address bindings with this home address as being revoked. If the mobile node validates the BRI successfully, the mobile node MUST accept the Binding Revocation Indication message with status code "success".
o 如果移动节点与它的归属代理具有多个照护地址绑定，并且接收绑定撤销指示，而没有包含任何竞标选项，并且它的归属地址被包含在类型2路由报头中，则移动节点必须考虑其所有注册地址的归属地址与被撤销的地址绑定。如果移动节点成功验证BRI，则移动节点必须接受状态代码为“成功”的绑定撤销指示消息。
If the mobile node accepts or rejects the Binding Revocation Indication message, the mobile node MUST follow Sections 6.1 and 6.1.2 to send a Binding Revocation Acknowledgement message to the home agent. Note that anytime the MN does not send a Binding
如果移动节点接受或拒绝绑定撤销指示消息，则移动节点必须遵循第6.1节和第6.1.2节向归属代理发送绑定撤销确认消息。请注意，只要MN不发送绑定
Revocation Acknowledgement to a BRI, the initiator is likely to retransmit the BRI at least one time. This causes additional load on the initiator who sends the retransmissions, as well as on the MN that will receive and process them.
撤销对BRI的确认，发起方可能至少重新传输一次BRI。这会给发送重传的启动器以及接收和处理重传的MN带来额外的负载。
The Revocation Trigger field value in the received Binding Revocation Indication could be used by the mobile node to define what action the mobile node could do to be able to register again and receive its IP mobility service, e.g., contacting its home operator.
移动节点可以使用接收到的绑定撤销指示中的撤销触发字段值来定义移动节点可以执行哪些操作以能够再次注册并接收其IP移动服务，例如，联系其家庭运营商。
Any mobility entity that is allowed to invoke the binding revocation procedure by sending a Binding Revocation Indication message SHOULD allow the following variables to be configured.
允许通过发送绑定撤销指示消息来调用绑定撤销过程的任何移动实体都应允许配置以下变量。
BRI Maximum Number of Retries (BRIMaxRetriesNumber)
BRI最大重试次数（BRIMaxRetriesNumber）
This variable specifies the maximum Number of times a mobility entity can retransmit a Binding Revocation Indication message before receiving a Binding Revocation Acknowledgement message. The default value for this parameter is 1.
此变量指定移动实体在接收绑定撤销确认消息之前可以重新传输绑定撤销指示消息的最大次数。此参数的默认值为1。
Initial Minimum Delay Between BRI messages (InitMINDelayBRIs)
BRI消息之间的初始最小延迟（InitMINDelayBRIs）
This variable specifies the initial delay timeout in seconds before the revoking mobility entity retransmits a BRI message. The default is 1 second but is not to be configured to less than 0.5 seconds.
此变量指定撤销移动实体重新传输BRI消息之前的初始延迟超时（秒）。默认值为1秒，但不能配置为小于0.5秒。
Maximum BRA TIMEOUT (MAX_BRACK_TIMEOUT)
最大BRA超时（最大BRAK超时）
This variable specifies the maximum delay timeout in seconds before the revoking mobility entity retransmits a BRI message. The default is 2 seconds.
此变量指定撤销移动实体重新传输BRI消息之前的最大延迟超时（秒）。默认值为2秒。
This specification defines a new Binding Revocation Message using a new Mobility Header Type 16, as described in Section 5. The new Mobility Header type value needs to be assigned from the same numbering space as allocated for the other Mobility Header types registry.
如第5节所述，本规范使用新的移动报头类型16定义新的绑定撤销消息。新的移动头类型值需要从为其他移动头类型注册表分配的相同编号空间分配。
This document also creates a new registry "Binding Revocation Type" that indicates the type of the binding revocation message. The current binding revocation message types are described in Sections 5.1 and 5.2, and are the following:
本文档还创建了一个新的注册表“Binding Revocation Type”，该注册表指示Binding Revocation消息的类型。第5.1节和第5.2节描述了当前绑定撤销消息类型，如下所示：
0 Reserved 1 Binding Revocation Indication 2 Binding Revocation Acknowledgement All other values are unassigned
0保留1绑定撤销指示2绑定撤销确认所有其他值均未分配
Future values of the Binding Revocation Type can be allocated using Standards Action or IESG Approval [RFC5226].
绑定撤销类型的未来值可以使用标准操作或IESG批准[RFC5226]进行分配。
In addition, this document also creates a second new registry for the Revocation Trigger that indicates the reason behind sending the Binding Revocation Indication message. The current Revocation Trigger values are described in Section 5.1, and are the following:
此外，本文档还为吊销触发器创建了第二个新注册表，该注册表指示发送绑定吊销指示消息的原因。第5.1节描述了当前撤销触发值，如下所示：
Per-MN Revocation Trigger Values: 0 Unspecified 1 Administrative Reason 2 Inter-MAG Handover - same Access Type 3 Inter-MAG Handover - different Access Type 4 Inter-MAG Handover - Unknown 5 User-Initiated Session(s) Termination 6 Access Network Session(s) Termination 7 Possible Out-of-Sync BCE State
每MN撤销触发值：0未指定1管理原因2 MAG间切换-相同访问类型3 MAG间切换-不同访问类型4 MAG间切换-未知5用户启动会话终止6访问网络会话终止7可能不同步BCE状态
Global Revocation Trigger Values: 128 Per-Peer Policy 129 Revoking Mobility Node Local Policy
全局吊销触发值：每个对等策略128 129吊销移动节点本地策略
Reserved Revocation Trigger Values: 250-255 Reserved For Testing Purposes only All other values are Unassigned
保留吊销触发器值：250-255保留用于测试目的只有所有其他值未分配
Future values of the Revocation Trigger can be allocated using Standards Action or IESG Approval [RFC5226].
撤销触发器的未来值可以使用标准操作或IESG批准[RFC5226]进行分配。
Furthermore, this document creates a third new registry "Binding Revocation Acknowledgement Status Codes". The current values are described in Section 5.2, and are the following:
此外，本文档还创建了第三个新注册表“绑定撤销确认状态代码”。第5.2节描述了电流值，如下所示：
0 success 1 partial success 128 Binding Does NOT Exist 129 IPv4 Home Address Option Required 130 Global Revocation NOT Authorized 131 Revoked Mobile Nodes Identity Required 132 Revocation Failed - MN is Attached 133 Revocation Trigger NOT Supported 134 Revocation Function NOT Supported 135 Proxy Binding Revocation NOT Supported
0成功1部分成功128绑定不存在129 IPv4 Home Address选项需要130全局吊销未授权131吊销的移动节点身份需要132吊销失败-MN已连接133吊销触发器不支持134吊销功能不支持135代理绑定吊销不支持
Future values of the Status field can be allocated using Standards Action or IESG Approval [RFC5226].
状态字段的未来值可以使用标准操作或IESG批准[RFC5226]进行分配。
All fields labeled "Reserved" are only to be assigned through Standards Action or IESG Approval.
所有标记为“保留”的字段只能通过标准行动或IESG批准进行分配。
This specification allows the mobility node that initiates the binding revocation procedure to revoke a mobility session(s) that is currently registered with it. It is NOT allowed for any mobility node to revoke a mobile node mobility session that is not registered with this mobility node.
该规范允许发起绑定撤销过程的移动节点撤销当前向其注册的移动会话。不允许任何移动节点撤销未向该移动节点注册的移动节点移动会话。
The binding revocation protocol described in this specification uses the same security association between the mobile node and the home agent or the mobile access gateway and the local mobility anchor that is being used to exchange the MIPv6 or PMIPv6 Binding Update and Binding Acknowledgement signaling. If IPsec is used, the traffic selectors associated with the Security Policy Database (SPD) entry protecting the Binding Update and Binding Acknowledgement MUST be extended to include Binding Revocation Message MH type 16. Extending the traffic selectors of the SPD entry in order to reuse the SA protecting the Binding Update and Binding Acknowledgement (instead of creating new ones) ensures that those SAs will be up and running when the revoking entity needs to send a binding revocation signaling message.
本规范中描述的绑定撤销协议使用移动节点与归属代理或移动接入网关与本地移动锚之间的相同安全关联，该本地移动锚用于交换MIPv6或PMIPv6绑定更新和绑定确认信令。如果使用IPsec，则必须扩展与保护绑定更新和绑定确认的安全策略数据库（SPD）条目相关联的流量选择器，以包括绑定撤销消息MH类型16。扩展SPD条目的流量选择器，以重用SA，保护绑定更新和绑定确认（而不是创建新的），确保当撤销实体需要发送绑定撤销信令消息时，这些SA将启动并运行。
On the other hand, if IPsec is not used as the underlying security mechanism to protect the Mobile IPv6 and its extensions binding registration signaling, the used underlying security mechanism MUST provide protection against all identified security threats as described under "Security Considerations" in [RFC3775] and [RFC5213].
另一方面，如果IPsec未用作基础安全机制来保护移动IPv6及其绑定注册信令的扩展，则所使用的基础安全机制必须针对所有已识别的安全威胁提供保护，如[RFC3775]和[RFC5213]中“安全注意事项”所述。
Since some mobility entities, e.g., local mobility anchor and mobile access gateway, are allowed to send and receive Binding Revocation Indications and Binding Revocation Acknowledgements for different cases, when IPsec is used to secure signaling between the local mobility anchor and mobile access gateway, it prevents any of them from processing a Binding Revocation Message that was not constructed by an authorized party.
由于一些移动实体（例如，本地移动锚和移动接入网关）被允许针对不同的情况发送和接收绑定撤销指示和绑定撤销确认，当IPsec被用于保护本地移动锚和移动接入网关之间的信令时，它阻止它们中的任何一个处理不是由授权方构造的绑定撤销消息。
The Proxy Mobile IPv6 [RFC5213] requires the local mobility anchor to restrict the creation and manipulation of proxy bindings to specifically authorized mobile access gateways. Therefore, the mobile access gateway that is authorized to create or manipulate the mobile node proxy BCE is also authorized to revoke such mobile node registration by sending a de-registration with lifetime of zero.
代理移动IPv6[RFC5213]需要本地移动锚来限制对特定授权移动访问网关的代理绑定的创建和操作。因此，被授权创建或操作移动节点代理BCE的移动接入网关也被授权通过发送生存期为零的取消注册来撤销这种移动节点注册。
However, since bulk termination using Binding Revocation Indication with the Global (G) bit set and the Revocation Trigger field set to "Per-Peer Policy" impacts all mobility sessions that are registered with the mobile access gateway and its local mobility anchor peer, the local mobility anchor MUST be locally configurable to authorize such specific functionality. Additional mechanisms, such as a policy store or Authentication, Authorization, and Accounting (AAA) may be employed, but these are outside the scope of this specification.
然而，由于使用绑定撤销指示的批量终止（全局（G）位设置和撤销触发字段设置为“每对等策略”）会影响在移动接入网关及其本地移动锚对等机上注册的所有移动会话，本地移动锚必须是本地可配置的，以授权此类特定功能。可以使用其他机制，例如策略存储或身份验证、授权和记帐（AAA），但这些不在本规范的范围内。
The authors would like to thank Ryuji Wakikawa, Bruno Mongazon-Cazavet, Domagoj Premec, Arnaud Ebalard, Patrick Stupar, Vijay Devarapalli, and Joel Hortelius for their review and comments of this document and all colleagues who have supported the advancement of this effort.
作者要感谢Wakikawa Ryuji、Bruno Mongazon Cazavet、Domagoj Premec、Arnaud Ebalard、Patrick Stupar、Vijay Devarapalli和Joel Hortelius对本文件的审查和评论，以及所有支持这项工作的同事。
Also, we would like to thank Jari Arkko, Ben Campbell, Pasi Eronen, Ralph Droms, Alexey Melnikov, Tim Polk, Adrian Farrel, and Robert Sparks for their reviews of this document as part of the IESG review process.
此外，我们还要感谢Jari Arkko、Ben Campbell、Pasi Eronen、Ralph Droms、Alexey Melnikov、Tim Polk、Adrian Farrel和Robert Sparks在IESG审查过程中对本文件的审查。
[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月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004.
[RFC3775]Johnson，D.，Perkins，C.，和J.Arkko，“IPv6中的移动支持”，RFC 37752004年6月。
[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月。
[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月。
[RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T., and K. Nagami, "Multiple Care-of Addresses Registration", RFC 5648, October 2009.
[RFC5648]Wakikawa，R.，Devarapalli，V.，Tsirtsis，G.，Ernst，T.，和K.Nagami，“多重托管地址注册”，RFC 5648，2009年10月。
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers", RFC 5555, June 2009.
[RFC5555]Soliman，H.，“双栈主机和路由器的移动IPv6支持”，RFC 55552009年6月。
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002.
[RFC3344]Perkins，C.，“IPv4的IP移动支持”，RFC 3344，2002年8月。
[RFC3543] Glass, S. and M. Chandra, "Registration Revocation in Mobile IPv4", RFC 3543, August 2003.
[RFC3543]Glass，S.和M.Chandra，“移动IPv4中的注册撤销”，RFC 3543，2003年8月。
Authors' Addresses
作者地址
Ahmad Muhanna Ericsson, Inc. 2201 Lakeside Blvd. Richardson, TX 75082 USA
艾哈迈德·穆哈纳·爱立信公司，湖畔大道2201号。美国德克萨斯州理查森75082
EMail: ahmad.muhanna@ericsson.com
EMail: ahmad.muhanna@ericsson.com
Mohamed Khalil Ericsson, Inc. 6300 Legacy Dr. Plano, TX 75024 USA
Mohamed Khalil Ericsson，Inc.6300 Legacy Dr.Plano，德克萨斯州75024美国
EMail: mohamed.khalil@ericsson.com
EMail: mohamed.khalil@ericsson.com
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Kuntal Chowdhury Cisco 30 International Place Tewksbury, MA 01876 USA
Kuntal Chowdhury Cisco美国马萨诸塞州特克斯伯里国际广场30号01876
EMail: kchowdhu@cisco.com
EMail: kchowdhu@cisco.com
Parviz Yegani Juniper Networks 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA
美国加利福尼亚州桑尼维尔北马蒂尔达大道1194号帕维兹·耶加尼·杜松网络公司，邮编94089
EMail: pyegani@juniper.net
EMail: pyegani@juniper.net