draft-ietf-mext-binding-revocation-12.txt   draft-ietf-mext-binding-revocation-13.txt 
Network Working Group A. Muhanna Network Working Group A. Muhanna
Internet-Draft M. Khalil Internet-Draft M. Khalil
Intended status: Standards Track Nortel Intended status: Standards Track Nortel
Expires: March 14, 2010 S. Gundavelli Expires: April 3, 2010 S. Gundavelli
Cisco Systems Cisco Systems
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
P. Yegani P. Yegani
Juniper Networks Juniper Networks
September 10, 2009 September 30, 2009
Binding Revocation for IPv6 Mobility Binding Revocation for IPv6 Mobility
draft-ietf-mext-binding-revocation-12.txt draft-ietf-mext-binding-revocation-13.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 48 skipping to change at page 1, line 48
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 14, 2010. This Internet-Draft will expire on April 3, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 7 skipping to change at page 3, line 7
This document defines a binding revocation mechanism to terminate a This document defines a binding revocation mechanism to terminate a
mobile node's mobility session and the associated resources. These mobile node's mobility session and the associated resources. These
semantics are generic enough and can be used by mobility entities in semantics are generic enough and can be used by mobility entities in
the case of Mobile IPv6 and its extensions. This mechanism allows the case of Mobile IPv6 and its extensions. This mechanism allows
the mobility entity which initiates the revocation procedure to the mobility entity which initiates the revocation procedure to
request its peer to terminate either one, multiple or all specified request its peer to terminate either one, multiple or all specified
binding(s). binding(s).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 5 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 4
2.1. Conventions used in this document . . . . . . . . . . . . 5 2.1. Conventions used in this document . . . . . . . . . . . . 4
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. Binding Revocation Protocol and Use Cases Overview . . . . . . 5 3. Binding Revocation Protocol and Use Cases Overview . . . . . . 5
3.1. Binding Revocation Protocol . . . . . . . . . . . . . . . 6 3.1. Binding Revocation Protocol . . . . . . . . . . . . . . . 5
3.2. MIPv6 and DSMIP6 Use Case . . . . . . . . . . . . . . . . 7 3.2. MIPv6 and DSMIP6 Use Case . . . . . . . . . . . . . . . . 6
3.3. Multiple Care-of Addresses (Monami6) Use Case . . . . . . 8 3.3. Multiple Care-of Addresses (Monami6) Use Case . . . . . . 7
3.4. Proxy MIPv6 Use Case . . . . . . . . . . . . . . . . . . . 9 3.4. Proxy MIPv6 Use Case . . . . . . . . . . . . . . . . . . . 8
3.4.1. Local Mobility Anchor Initiates PMIPv6 Binding 3.4.1. Local Mobility Anchor Initiates PMIPv6 Revocation . . 9
Revocation . . . . . . . . . . . . . . . . . . . . . . 10 3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings . . 10
3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings . . 11 4. Binding Revocation Messages over IPv4 Transport Network . . . 11
4. Binding Revocation Messages over IPv4 Transport Network . . . 12 5. Binding Revocation Message . . . . . . . . . . . . . . . . . . 11
5. Binding Revocation Message . . . . . . . . . . . . . . . . . . 12 5.1. Binding Revocation Indication Message . . . . . . . . . . 13
5.1. Binding Revocation Indication Message . . . . . . . . . . 14 5.2. Binding Revocation Acknowledgement Message . . . . . . . . 16
5.2. Binding Revocation Acknowledgement Message . . . . . . . . 17 6. Binding Revocation Process Operation . . . . . . . . . . . . . 18
6. Binding Revocation Process Operation . . . . . . . . . . . . . 20 6.1. Sending Binding Revocation Message . . . . . . . . . . . . 18
6.1. Sending Binding Revocation Messages . . . . . . . . . . . 20 6.1.1. Sending Binding Revocation Indication . . . . . . . . 19
6.2. Receiving Binding Revocation Messages . . . . . . . . . . 20 6.1.2. Sending Binding Revocation Acknowledgement . . . . . . 19
6.2. Receiving Binding Revocation Message . . . . . . . . . . . 21
6.2.1. Receiving Binding Revocation Indication . . . . . . . 21
6.2.2. Receiving Binding Revocation Acknowledgement . . . . . 21
6.3. Retransmission of Binding Revocation Indication . . . . . 22 6.3. Retransmission of Binding Revocation Indication . . . . . 22
7. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 22 7. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 22
7.1. Sending Binding Revocation Indication . . . . . . . . . . 22
7.2. Receiving Binding Revocation Acknowledgement . . . . . . . 24
8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 24 8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 24
8.1. Binding Revocation Initiator . . . . . . . . . . . . . . . 24 8.1. Sending Binding Revocation Indication . . . . . . . . . . 24
8.1.1. Sending Binding Revocation Indication . . . . . . . . 24 8.2. Receiving Binding Revocation Indication . . . . . . . . . 28
8.1.2. Receiving Binding Revocation Acknowledgement . . . . . 29 9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 30
8.2. Binding Revocation Responder . . . . . . . . . . . . . . . 29 9.1. Receiving Binding Revocation Indication . . . . . . . . . 30
8.2.1. Receiving Binding Revocation Indication . . . . . . . 29 9.2. Sending Binding Revocation Indication . . . . . . . . . . 32
8.2.2. Sending Binding Revocation Acknowledgement . . . . . . 31 10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 33
9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 32 11. Protocol Configuration Variables . . . . . . . . . . . . . . . 34
9.1. Binding Revocation Responder . . . . . . . . . . . . . . . 32 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
9.1.1. Receiving Binding Revocation Indication . . . . . . . 32 13. Security Considerations . . . . . . . . . . . . . . . . . . . 36
9.1.2. Sending Binding Revocation Acknowledgement . . . . . . 34 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 38
9.2. Binding Revocation Initiator . . . . . . . . . . . . . . . 35 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.2.1. Sending Binding Revocation Indication . . . . . . . . 35 15.1. Normative References . . . . . . . . . . . . . . . . . . . 38
9.2.2. Receiving Binding Revocation Acknowledgement . . . . . 36 15.2. Informative References . . . . . . . . . . . . . . . . . . 39
10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
10.1. Receiving Binding Revocation Indication . . . . . . . . . 36
10.2. Sending Binding Revocation Acknowledgement . . . . . . . . 38
11. Protocol Configuration Variables . . . . . . . . . . . . . . . 38
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39
13. Security Considerations . . . . . . . . . . . . . . . . . . . 40
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41
15.1. Normative References . . . . . . . . . . . . . . . . . . . 41
15.2. Informative References . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
In the case of Mobile IPv6 and for administrative reason, sometimes In the case of Mobile IPv6 and for administrative reason, sometimes
it becomes necessary to inform the mobile node that its registration 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 has been revoked and the mobile node is no longer able to receive IP
mobility service using its Home Address. A similar Mobile IPv4 mobility service using its Home Address. A similar Mobile IPv4
registration revocation mechanism [RFC3543] has been specified by registration revocation mechanism [RFC3543] has been specified by
IETF for providing a revocation mechanism for sessions that were IETF for providing a revocation mechanism for sessions that were
established using Mobile IPv4 registration [RFC3344]. established using Mobile IPv4 registration [RFC3344].
skipping to change at page 5, line 46 skipping to change at page 4, line 46
2.1. Conventions used in this document 2.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.2. Terminology 2.2. Terminology
All the general mobility related terminology and abbreviations are to All the general mobility related terminology and abbreviations are to
be interpreted as defined in Mobile IPv6 [RFC3775] and Proxy Mobile be interpreted as defined in Mobile IPv6 [RFC3775] and Proxy Mobile
IPv6 [RFC5213] specifications. IPv6 [RFC5213] specifications. The following terms are used in this
specification.
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.
3. Binding Revocation Protocol and Use Cases Overview 3. Binding Revocation Protocol and Use Cases Overview
This specification specifies a generic binding revocation mechanism This specification specifies a generic binding revocation mechanism
where a mobility node can communicate to the mobile node or another where a mobility node can communicate to the mobile node or another
mobility node the identity of the the mobile node registration mobility node the identity of the the mobile node registration
binding that is being terminated. In the case when this mechanism is binding that is being terminated. In the case when this mechanism is
used for bulk termination or multiple bindings, the identities of used for bulk termination or multiple bindings, the identities of
these bindings are communicated to the mobile node or mobility node these bindings are communicated to the mobile node or mobility node
using the same generic mechanism. The following subsections present using the same generic mechanism. The following subsections present
skipping to change at page 6, line 26 skipping to change at page 5, line 43
Revocation Indication (BRI) message to the mobile node. The home Revocation Indication (BRI) message to the mobile node. The home
agent includes the home address (HoA) of the mobile node in the Type agent includes the home address (HoA) of the mobile node in the Type
2 routing header as specified in [RFC3775] to indicate the impacted 2 routing header as specified in [RFC3775] to indicate the impacted
mobile node binding. In the case of Dual Stack Mobile IPv6 (DSMIPv6) mobile node binding. In the case of Dual Stack Mobile IPv6 (DSMIPv6)
[RFC5555], the home agent may include the IPv4 Home Address option [RFC5555], the home agent may include the IPv4 Home Address option
with the mobile node assigned home IPv4 address. Additionally, if with the mobile node assigned home IPv4 address. Additionally, if
the mobile node registered multiple care-of addresses [ID-MCoA], the the mobile node registered multiple care-of addresses [ID-MCoA], the
home agent includes the Binding Identifier (BID) option(s) in the home agent includes the Binding Identifier (BID) option(s) in the
Binding Revocation Indication message to identify which binding is Binding Revocation Indication message to identify which binding is
being revoked. When the mobile node receives a Binding Revocation being revoked. When the mobile node receives a Binding Revocation
Indication message with its HoA included in the Type 2 routing header Indication message with its HoA included in the Type 2 routing
and the Acknowledge (A) bit is set, the mobile node responds by header, the mobile node responds by sending a Binding Revocation
sending a Binding Revocation Acknowledgement (BRA) message. Acknowledgement (BRA) message.
Similarly, in the case of Proxy Mobile IPv6 [RFC5213], the revocation Similarly, in the case of Proxy Mobile IPv6 [RFC5213], the revocation
procedure can be initiated by the local mobility anchor by sending a procedure can be initiated by the local mobility anchor by sending a
Binding Revocation Indication message to communicate the termination Binding Revocation Indication message to communicate the termination
of a mobile node registration binding to the mobile access gateway. of a mobile node registration binding to the mobile access gateway.
In this case, the local mobility anchor includes the mobile node Home In this case, the local mobility anchor includes the mobile node Home
Network Prefix (MN-HNP) option [RFC5213] and the MN-ID option Network Prefix (MN-HNP) option [RFC5213] and the MN-ID option
[RFC4283] to indicate to the mobility access gateway the identity of [RFC4283] to indicate to the mobility access gateway the identity of
the PMIPv6 binding that needs to be terminated. When the mobile the PMIPv6 binding that needs to be terminated. When the mobile
access gateway receives the Binding Revocation Indication message access gateway receives the Binding Revocation Indication message,
with the Acknowledge (A) bit set, the mobile access gateway responds the mobile access gateway responds to the local mobility anchor by
to the local mobility anchor by sending a Binding Revocation sending a Binding Revocation Acknowledgement message.
Acknowledgement message.
On the other hand, the mobile access gateway usually sends a de- On the other hand, the mobile access gateway usually sends a de-
registration message by sending a Proxy Binding Update with a registration message by sending a Proxy Binding Update with a
lifetime of zero to indicate to the local mobility anchor of the lifetime of zero to indicate to the local mobility anchor of the
termination of the PMIPv6 mobile node binding registration. In this termination of the PMIPv6 mobile node binding registration. In this
case, the mobile access gateway includes the MN-HNP option, the MN-ID case, the mobile access gateway includes the MN-HNP option, the MN-ID
option and all other required mobility options as per [RFC5213] in option and all other required mobility options as per [RFC5213] in
order for the local mobility anchor to identify the mobile node order for the local mobility anchor to identify the mobile node
PMIPv6 binding. Additionally, in the case when the mobile access PMIPv6 binding. Additionally, in the case when the mobile access
gateway communicates a bulk termination of PMIPv6 mobility sessions, gateway communicates a bulk termination of PMIPv6 mobility sessions,
the mobile access gateway sends a Binding Revocation Indication the mobile access gateway sends a Binding Revocation Indication
message with the Global (G) and Acknowledge (A) bits set and includes message with the Global (G) bit is set and includes the mobile access
the mobile access gateway identity in the MN-ID option, see gateway identity in the MN-ID option, see Section 9.2 and
Section 8.1.1 and Section 9.1.1. When the local mobility anchor Section 8.2. When the local mobility anchor receives such Binding
receives such Binding Revocation Indication message, it ensures that Revocation Indication message, it ensures that the mobile access
the mobile access gateway is authorized to send such bulk termination gateway is authorized to send such bulk termination message, see
message and then processes the Binding Revocation Indication message Section 13, and then processes the Binding Revocation Indication
accordingly. If the local mobility anchor processes the Binding message accordingly. If the local mobility anchor processes the
Revocation Indication message successfully and the Acknowledge (A) Binding Revocation Indication message successfully, the local
bit is set, the local mobility anchor responds to the mobile access mobility anchor responds to the mobile access gateway by sending
gateway by sending Binding Revocation Acknowledgement message. Binding Revocation Acknowledgement message.
In any of the above cases, the initiator of the binding revocation In any of the above cases, the initiator of the binding revocation
procedure, e.g., home agent, local mobility anchor, or mobile access procedure, e.g., home agent, local mobility anchor, or mobile access
gateway, uses the Revocation Trigger field in the Binding Revocation gateway, uses the Revocation Trigger field in the Binding Revocation
Indication message to indicate to the receiving node the reason for Indication message to indicate to the receiving node the reason for
initiating the revocation procedure. initiating the revocation procedure.
3.2. MIPv6 and DSMIP6 Use Case 3.2. MIPv6 and DSMIP6 Use Case
The binding revocation mechanism is applicable to Mobile IPv6 and The binding revocation mechanism is applicable to Mobile IPv6 and
skipping to change at page 7, line 40 skipping to change at page 7, line 8
In this case, the home agent sends a Binding Revocation Indication In this case, the home agent sends a Binding Revocation Indication
message to indicate to the mobile node that its current mobile IPv6 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 (MIPv6) binding has been revoked and it is no longer able to receive
IP mobility service. The home agent includes the HoA in Type 2 IP mobility service. The home agent includes the HoA in Type 2
routing header as used in [RFC3775] and sets the Revocation Trigger routing header as used in [RFC3775] and sets the Revocation Trigger
field to a proper value, e.g., Administrative Reason. In the case of field to a proper value, e.g., Administrative Reason. In the case of
DSMIPv6 session, the home agent may additionally include the mobile DSMIPv6 session, the home agent may additionally include the mobile
node assigned IPv4 Home Address in the IPv4 Home Address option. node assigned IPv4 Home Address in the IPv4 Home Address option.
When the mobile node receives the Binding Revocation Indication When the mobile node receives the Binding Revocation Indication
message, it sends a Binding Revocation Acknowledgement message as message, it sends a Binding Revocation Acknowledgement message to the
described in Section 10.2 to the home agent. Figure 1 illustrates home agent. Figure 1 illustrates the message sequencing when home
the message sequencing when home agent revokes a mobile node binding agent revokes a mobile node binding registration.
registration.
MN HA MN HA
| | | |
| HoA in Type 2 Hdr | | HoA in Type 2 Hdr |
|<<<------------... + ...-----------------| |<<<------------... + ...-----------------|
| BRI [seq.#, A bit, Revocation Trigger] | | BRI [seq.#, Revocation Trigger] |
| | | |
| | | |
| BRA (HoA in Dest. Option)[seq.#, Status] | | BRA (HoA in Dest. Option)[seq.#, Status] |
|---------------------------------------->>>| |---------------------------------------->>>|
| | | |
| | | |
Figure 1: Home Agent Revokes a Mobile Node Binding Registration Figure 1: Home Agent Revokes a Mobile Node Binding Registration
3.3. Multiple Care-of Addresses (Monami6) Use Case 3.3. Multiple Care-of Addresses (Monami6) Use Case
skipping to change at page 9, line 13 skipping to change at page 8, line 13
same mobile node in a single Binding Revocation Indication message. same mobile node in a single Binding Revocation Indication message.
HA Binding Cache HA Binding Cache
================ ================
MN-BID1 [CoA1+HoA] MN-BID1 [CoA1+HoA]
MN HA MN-BID2 [CoA2+HoA] MN HA MN-BID2 [CoA2+HoA]
| | MN-BID3 [CoA3+HoA] | | MN-BID3 [CoA3+HoA]
| | MN-BID4 [CoA4+HoA] | | MN-BID4 [CoA4+HoA]
| HoA in Type 2 Hdr | | HoA in Type 2 Hdr |
|<<<<-------------- + ---------------------| |<<<<-------------- + ---------------------|
| BRI [seq.#, A bit, R. Trigger, BID1, BID4] | | BRI [seq.#, R. Trigger, BID1, BID4] |
| | | |
| | | |
| BRA (HoA in Dest. Option) [seq.#, Status] | | BRA (HoA in Dest. Option) [seq.#, Status] |
|---------------------------------------->>>>| |---------------------------------------->>>>|
| | | |
| | | |
Figure 2: Home Agent Revokes MN's Specific Care-of Addresses Bindings Figure 2: Home Agent Revokes MN's Specific Care-of Addresses Bindings
Additionally, the home agent may revoke all of the mobile node Additionally, the home agent may revoke all of the mobile node
skipping to change at page 9, line 42 skipping to change at page 8, line 42
Since the mobile node does not participate in the mobility mechanism Since the mobile node does not participate in the mobility mechanism
in the case of PMIPv6, there are many scenarios where the Binding in the case of PMIPv6, there are many scenarios where the Binding
Revocation mechanism is needed to clean resources and make sure that Revocation mechanism is needed to clean resources and make sure that
the mobility entities, i.e., mobile access gateway and local mobility the mobility entities, i.e., mobile access gateway and local mobility
anchor, are always synchronized with respect to the status of the anchor, are always synchronized with respect to the status of the
existing PMIPv6 bindings. The binding revocation mechanism is existing PMIPv6 bindings. The binding revocation mechanism is
generic enough that can be used for all Proxy Mobile IPv6 scenarios generic enough that can be used for all Proxy Mobile IPv6 scenarios
that follow [RFC5213] and [ID-PMIP6-IPv4] specifications. that follow [RFC5213] and [ID-PMIP6-IPv4] specifications.
When the mobile access gateway receives a Binding Revocation When the mobile access gateway receives a Binding Revocation
Indication message with the Acknowledge (A) bit set as in Indication message as in Section 9.1, the mobile access gateway sends
Section 9.1.1, the mobile access gateway sends a Binding Revocation a Binding Revocation Acknowledgement message to the local mobility
Acknowledgement message to the local mobility anchor following the anchor following the rules described in Section 6.1.2. Similarly, if
rules described in Section 9.1.2. Similarly, if the local mobility the local mobility anchor receives a Binding Revocation Indication
anchor receives a Binding Revocation Indication message with the message, the local mobility anchor responds to the mobile access
Acknowledge (A) bit is set, the local mobility anchor responds to the gateway by sending a Binding Revocation Acknowledgement message.
mobile access gateway by sending a Binding Revocation Acknowledgement
message.
3.4.1. Local Mobility Anchor Initiates PMIPv6 Binding Revocation 3.4.1. Local Mobility Anchor Initiates PMIPv6 Revocation
The local mobility anchor may send a Binding Revocation Indication The local mobility anchor may send a Binding Revocation Indication
message with the appropriate revocation trigger value to the mobile message with the appropriate revocation trigger value to the mobile
access gateway that hosts a specific PMIPv6 binding to indicate that access gateway that hosts a specific PMIPv6 binding to indicate that
the mobile node binding has been terminated and the mobile access the mobile node binding has been terminated and the mobile access
gateway can clean up the applicable resources. When the mobile gateway can clean up the applicable resources. When the mobile
access gateway receives a Binding Revocation Indication message, the access gateway receives a Binding Revocation Indication message, the
mobile access gateway identifies the respected binding and if the mobile access gateway identifies the respected binding and it sends a
Acknowledge (A) bit is set in the received Binding Revocation Binding Revocation Acknowledgement message to the local mobility
Indication message, it sends a Binding Revocation Acknowledgement anchor. In this case, the mobile access gateway could send a Router
message to the local mobility anchor. In this case, the mobile Advertisement message to the mobile node with the home network prefix
access gateway could send a Router Advertisement message to the valid lifetime set to zero.
mobile node with the home network prefix valid lifetime set to zero.
As an example, Figure 3, illustrates the message sequence for As an example, Figure 3, illustrates the message sequence for
revoking a mobile node binding at the source mobile access gateway revoking a mobile node binding at the source mobile access gateway
during the mobile node inter-MAG handover. During the inter-MAG during the mobile node inter-MAG handover. During the inter-MAG
handover, the mobile node moves from the source MAG to the target 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- 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 of-address to the local mobility anchor to update the mobile node's
point of attachment. Since the mobile node binding at the local point of attachment. Since the mobile node binding at the local
mobility anchor points to the source MAG and upon receiving the Proxy mobility anchor points to the source MAG and upon receiving the Proxy
Binding Update from the target MAG, the local mobility anchor updates Binding Update from the target MAG, the local mobility anchor updates
the MN Binding Cache Entry (BCE) and send a Proxy Binding the MN Binding Cache Entry (BCE) and send a Proxy Binding
Acknowledgement to the target MAG. The local mobility anchor can Acknowledgement to the target MAG. The local mobility anchor can
send a Binding Revocation Indication message with the appropriate send a Binding Revocation Indication message with the appropriate
revocation trigger value, e.g. inter-MAG handover - different Access revocation trigger value, e.g. inter-MAG handover - different Access
Types, to the source MAG in order to clean up the applicable Types, to the source MAG in order to clean up the applicable
resources reserved for the specified mobile node binding. If the resources reserved for the specified mobile node binding. The source
Acknowledge (A) bit is set, the mobile access gateway acknowledges mobile access gateway acknowledges the Binding Revocation Indication
the Binding Revocation Indication message by sending a Binding message by sending a Binding Revocation Acknowledgement message to
Revocation Acknowledgement message to indicate the success or failure indicate the success or failure of the termination of the mobile
of the termination of the mobile node's binding. node's binding.
The process identified above can also be used by the local mobility The process identified above can also be used by the local mobility
anchor in scenarios other than the inter-MAG handover with the proper anchor in scenarios other than the inter-MAG handover with the proper
revocation trigger value to indicate to the peer mobile access revocation trigger value to indicate to the peer mobile access
gateway that a specific PMIPv6 binding or bindings have been revoked. gateway that a specific PMIPv6 binding or bindings have been revoked.
oldMAG newMAG LMA oldMAG newMAG LMA
| | | | | |
| | PBU | | | PBU |
| |--------------------------->| | |--------------------------->|
| | PBU triggers | | PBU triggers
| | BRI Msg to oldMAG | | BRI Msg to oldMAG
| | | | | |
| | PBA | | | PBA |
| |<---------------------------| | |<---------------------------|
| | | | | |
| | | | | |
| BRI [seq.#, R. Trigger, P, A bits, NAI] | | BRI [seq.#, R. Trigger, P bit, NAI] |
|<-----------------------------------------| |<-----------------------------------------|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| BRA [seq.#, Status, P bit] | | BRA [seq.#, Status, P bit] |
|----------------------------------------->| |----------------------------------------->|
| | | | | |
| | | | | |
Figure 3: LMA Revokes a MN Registration During Inter-MAG Handover Figure 3: LMA Revokes a MN Registration During Inter-MAG Handover
In addition, the local mobility anchor can send a Binding Revocation In addition, the local mobility anchor can send a Binding Revocation
Indication message to indicate that all bindings which are hosted by Indication message to indicate that all bindings which are hosted by
the peer mobile access gateway and registered with the local mobility the peer mobile access gateway and registered with the local mobility
anchor are being revoked by setting the Global (G) bit as described anchor are being revoked by setting the Global (G) bit as described
in Section 8.1.1. in Section 8.1.
3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings 3.4.2. Mobile Access Gateway Revokes Bulk PMIPv6 Bindings
The mobile access gateway sends a BRI message with the Global (G) bit 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 set and the Revocation Trigger field set to "Per-Peer Policy" to
indicate that all mobility bindings which are registered at the local indicate that all mobility bindings which are registered at the local
mobility anchor and attached to the mobile access gateway are being mobility anchor and attached to the mobile access gateway are being
revoked as in Section 9.2.1. When the local mobility anchor receives revoked as in Section 9.2. When the local mobility anchor receives
this Binding Revocation Indication message from the specified mobile this Binding Revocation Indication message from the specified mobile
access gateway, the local mobility anchor first checks if the mobile access gateway, the local mobility anchor first checks if the mobile
access gateway is authorized to use global revocations and if the access gateway is authorized to use global revocations, then it
Acknowledge (A) bit is set, then responds with the appropriate status responds with the appropriate status code by sending a Binding
code by sending a Binding Revocation Acknowledgement message as in Revocation Acknowledgement message as in Section 6.1.2.
Section 8.2.2.
4. Binding Revocation Messages over IPv4 Transport Network 4. Binding Revocation Messages over IPv4 Transport Network
In some deployments, the network between the mobile access gateway In some deployments, the network between the mobile access gateway
and the local mobility anchor may only support IPv4 transport. and the local mobility anchor may only support IPv4 transport.
Another case is when a mobile node which supports client mobile IPv6 Another case is when a mobile node which supports client mobile IPv6
roams to an access network where only IPv4 addressing and transport roams to an access network where only IPv4 addressing and transport
is supported. In this case, the mobile node is required to register 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 an IPv4 home address with its home agent using a mobile IPv6 Binding
Update message. Update message.
skipping to change at page 14, line 20 skipping to change at page 13, line 14
0 Reserved 0 Reserved
1 Binding Revocation Indication Message 1 Binding Revocation Indication Message
2 Binding Revocation Acknowledgement Message 2 Binding Revocation Acknowledgement Message
All other values are reserved All other values are reserved
Binding Revocation Message Data Binding Revocation Message Data
The Binding Revocation Message Data follows the Binding Revocation The Binding Revocation Message Data follows the Binding Revocation
Message format that is defined in this document for the specified Message format that is defined in this document for the specified
value in the Binding Revocation Type field. In this value in the Binding Revocation Type field. In this document, it
specification, it is either a Binding Revocation Indication as in is either a Binding Revocation Indication as in Section 5.1 or
Section 5.1 or Binding Revocation Acknowledgement as in Binding Revocation Acknowledgement as in Section 5.2.
Section 5.2.
5.1. Binding Revocation Indication Message 5.1. Binding Revocation Indication Message
The Binding Revocation Indication (BRI) message is a Binding The Binding Revocation Indication (BRI) message is a Binding
Revocation Message which has a MH type <IANA-TBD> and a Binding Revocation Message which has a MH type <IANA-TBD> and a Binding
Revocation Type value of 1. It is used by the revoking mobility node Revocation Type value of 1. It is used by the initiator to inform
to inform the receiving mobility entity of the identity of a specific the responder of the identity of a specific binding or bindings which
binding or bindings which IP mobility service have been revoked. IP mobility service are being revoked. Binding Revocation Indication
Binding Revocation Indication message is sent as described in message is sent as described in Section 7, Section 8.1, and
Section 7.1, Section 8.1.1, and Section 9.2.1. Section 9.2.
When the value 1 is indicated in the B. R. type field of the Binding When the value 1 is indicated in the B. R. type field of the Binding
Revocation Message, the format of the Binding Revocation Message Data Revocation Message, the format of the Binding Revocation Message Data
follows the Binding Revocation Indication message as in Figure 5 follows the Binding Revocation Indication message as in Figure 5
0 1 2 3 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 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 | | B.R. Type = 1 | R. Trigger |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G|A| Reserved | | Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. . . .
. Mobility options . . Mobility options .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Binding Revocation Indication Message Figure 5: Binding Revocation Indication Message
Revocation Trigger Revocation Trigger
8-bit unsigned integer indicating the event which triggered the 8-bit unsigned integer indicating the event which triggered the
revoking node to send the BRI message. The Reserved and Per-MN initiator to send the BRI message. The Per-MN Revocation Trigger
Revocation Trigger values are less than 128 except the reserved values are less than 128. The per-MN revocation trigger is used
values 250-255 as listed below. The per-MN revocation trigger when the BRI message intends to revoke one or more bindings for
value is used when the BRI message intends to revoke one or more the same mobile node. The Global Revocation Trigger values are
bindings for the same mobile node. The Global Revocation Trigger greater than 128 and less than 250 and used in the BRI message
values are greater than 128 and less than 250 and used in the BRI when the Global (G) bit is set for global revocation. The values
message with the Global (G) bit set for global revocation. The 250-255 are reserved for testing purposes only. The following
following Revocation Trigger values are currently defined: Revocation Trigger values are currently defined:
Reserved and Per-MN Revocation Trigger: Per-MN Revocation Trigger Values:
0 Reserved 0 Unspecified
1 Unspecified 1 Administrative Reason
2 Administrative Reason 2 Inter-MAG Handover - same Access Type
3 Inter-MAG Handover - same Access Type 3 Inter-MAG Handover - different Access Type
4 Inter-MAG Handover - different Access Type 4 Inter-MAG Handover - Unknown
5 Inter-MAG Handover - Unknown 5 User Initiated Session(s) Termination
6 User Initiated Session(s) Termination 6 Access Network Session(s) Termination
7 Access Network Session(s) Termination 7 Possible Out-of Sync BCE State
8 Possible Out-of Sync BCE State
250-255 Reserved For Testing Purposes only
All other values are Reserved
Global Revocation Trigger: Global Revocation Trigger Values:
128 Per-Peer Policy 128 Per-Peer Policy
129 Revoking Mobility Node Local Policy 129 Revoking Mobility Node Local Policy
Reserved Revocation Trigger Values:
250-255 Reserved For Testing Purposes only
All other values are Reserved
Sequence # Sequence #
A 16-bit unsigned integer used by the sending mobility node to A 16-bit unsigned integer used by the initiator to match a
match a returned Binding Revocation Acknowledgement with this returned Binding Revocation Acknowledgement with this Binding
Binding Revocation Indication. This sequence number could be a Revocation Indication. This sequence number could be a random
random number. At any time, implementations MUST ensure that number. At any time, implementations MUST ensure there is no
there is no collision between the sequence numbers of all collision between the sequence numbers of all outstanding Binding
outstanding Binding Revocation Indication Messages. Revocation Indication Messages.
Proxy Binding (P) Proxy Binding (P)
The Proxy Binding (P) bit is set by the sending mobility node to The Proxy Binding (P) bit is set by the initiator to indicate that
indicate that the revoked binding(s) is a PMIPv6 binding. the revoked binding(s) is a PMIPv6 binding.
IPv4 HoA Binding Only (V) IPv4 HoA Binding Only (V)
The IPv4 HoA Binding Only (V) bit is set by the sending mobility The IPv4 HoA Binding Only (V) bit is set by the initiator, home
node, home agent or local mobility anchor, to indicate to the agent or local mobility anchor, to indicate to the receiving
receiving mobility entity the termination of the IPv4 Home Address mobility entity the termination of the IPv4 Home Address binding
binding only as in Section 7.1, and Section 8.1.1. only as in Section 7, and Section 8.1.
Global (G) Global (G)
The Global (G) bit is set by the sending mobility node, LMA or The Global (G) bit is set by the initiator, LMA or MAG, to
MAG, to indicate the termination of all Per-Peer mobility Bindings indicate the termination of all Per-Peer mobility Bindings or
or Multiple Bindings which share a common identifier(s) that are Multiple Bindings which share a common identifier(s) and served by
served by the sending and receiving mobility entities as in the initiator and responder as in Section 8.1 and Section 9.2.
Section 8.1.1 and Section 9.2.1.
Acknowledge (A)
The Acknowledge (A) bit is set by the sending mobility node, e.g.
LMA, HA, or MAG, to request a Binding Revocation Acknowledgement
be returned upon receipt of the Binding Revocation Indication as
in Section 7.1, Section 8.1.1, and Section 9.2.1. If Acknowledge
(A) bit is set in the BRI message, the sending mobility node
follows Section 6.3 for retransmitting the BRI message.
Reserved Reserved
These fields are unused. They MUST be initialized to zero by the These fields are unused. They MUST be initialized to zero by the
sender and MUST be ignored by the receiver. sender and MUST be ignored by the receiver.
Mobility Options Mobility Options
Variable-length field of such length that the complete Mobility Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. This document contains zero or more TLV-encoded mobility options. This document
does not define any new mobility option. The receiver MUST ignore does not define any new mobility option. The receiver MUST ignore
and skip any options which it does not understand. These mobility and skip any options which it does not understand. These mobility
option(s) are used by the receiving mobility entity to identify option(s) are used by the responder to identify the specific
the specific binding or bindings that the sending mobility entity binding or bindings that the initiator requesting to be revoked.
requesting to be revoked.
The following options are valid in a Binding Revocation Indication: The following options are valid in a Binding Revocation Indication:
o Home Network Prefix option [RFC5213]. This option MAY be used o Home Network Prefix option [RFC5213]. This option MAY be used
only when the (P) bit is set. This option MUST be present when 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 the BRI is used to revoke a single Proxy MIPv6 binding cache
entry. entry.
o Mobile Node Identifier Option [RFC4283]. This option MUST be o Mobile Node Identifier Option [RFC4283]. This option MUST be
present when the (P) bit is set. Additionally, if the Global (G) present when the (P) bit is set. Additionally, if the Global (G)
bit is set by the mobile access gateway, this option MUST carry bit is set by the mobile access gateway, this option MUST carry
the MAG identity. In this specification, only Mobile Node the MAG identity. In this specification, only Mobile Node
Identifier option with subtype 1 is required and other subtypes Identifier option with subtype 1 is required and other subtypes
are currently not supported. are currently not supported.
o Binding Identifier mobility option [ID-MCoA]. This option MUST be o Binding Identifier mobility option [ID-MCoA]. This option MUST be
present if the sending mobility entity requests to terminate one present if the initiator requests to terminate one binding of a
binding of a multiple care-of addresses bindings for the same multiple care-of addresses bindings for the same mobile node. The
mobile node. The sending mobility entity may include more than initiator may include more than one of the BID mobility options.
one of the BID mobility options.
o IPv4 Home Address option which contains the mobile node home IPv4 o IPv4 Home Address option which contains the mobile node home IPv4
address [RFC5555]. This option MUST only be included when the address [RFC5555]. This option MUST only be included when the
IPv4 HoA Binding only (V) bit is set. IPv4 HoA Binding only (V) bit is set.
o Alternate Care-of Address mobility option [RFC3775]. This option o Alternate Care-of Address mobility option [RFC3775]. This option
MAY be included to indicate the Care-of Address of the mobile MAY be included to indicate the Care-of Address of the mobile
node's binding that is being revoked. In the case when the Global node's binding that is being revoked. In the case when the Global
(G) bit set, this option identifies all the mobility bindings that (G) bit is set, this option identifies all mobility bindings that
share the same care-of address. Additionally, if the Global (G) share the same care-of address. Additionally, if the Global (G)
bit set, more than one Alternate Care-of Address mobility options bit is set, more than one Alternate Care-of Address mobility
MAY be present in the Binding Revocation Indication message. options MAY be present in the Binding Revocation Indication
message.
If no mobility options are present in this message, 4 octets of If no mobility options are present in this message, 4 octets of
padding are necessary and the Header Len field of the Binding padding are necessary and the Header Len field of the Binding
Revocation Message will be set to 1. Revocation Message will be set to 1.
5.2. Binding Revocation Acknowledgement Message 5.2. Binding Revocation Acknowledgement Message
The Binding Revocation Acknowledgement (BRA) message is a Binding The Binding Revocation Acknowledgement (BRA) message is a Binding
Revocation Message which has a MH type <IANA-TBD> and a Binding Revocation Message which has a MH type <IANA-TBD> and a Binding
Revocation Type value of 2. It is used to acknowledge the receipt of Revocation Type value of 2. It is used to acknowledge the receipt of
a Binding Revocation Indication message described in Section 5.1. a Binding Revocation Indication message described in Section 5.1.
This packet is sent as described in Section 8.2.2, Section 9.1.2, and This packet is sent as described in Section 6.1.2.
Section 10.2.
When the value 2 is indicated in the Binding Revocation type field of When the value 2 is indicated in the Binding Revocation type field of
the Binding Revocation Message, the format of the Binding Revocation the Binding Revocation Message, the format of the Binding Revocation
Message Data follows the Binding Revocation Acknowledgement message Message Data follows the Binding Revocation Acknowledgement message
as in Figure 6 as in Figure 6
0 1 2 3 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 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 | | B.R. Type = 2 | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |P|V|G| Reserved | | Sequence # |P|V|G| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. . . .
. Mobility options . . Mobility options .
skipping to change at page 18, line 23 skipping to change at page 17, line 8
. Mobility options . . Mobility options .
. . . .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Binding Revocation Acknowledgement Message Figure 6: Binding Revocation Acknowledgement Message
Status Status
8-bit unsigned integer indicating the result of processing the 8-bit unsigned integer indicating the result of processing the
Binding Revocation Indication message by the receiving mobility Binding Revocation Indication message by the responder. Values of
entity. Values of the Status field less than 128 indicate that the Status field less than 128 indicate that the Binding
the Binding Revocation Indication was processed successfully by Revocation Indication was processed successfully by the responder.
the receiving node. Values greater than or equal to 128 indicate Values greater than or equal to 128 indicate that the Binding
that the Binding Revocation Indication was rejected by the Revocation Indication was rejected by the responder. The
receiving node. The following status values are currently following status values are currently defined:
defined:
0 success 0 success
1 partial success 1 partial success
128 Binding Does NOT Exist 128 Binding Does NOT Exist
129 IPv4 Home Address Option Required 129 IPv4 Home Address Option Required
130 Global Revocation NOT Authorized 130 Global Revocation NOT Authorized
131 Revoked Mobile Nodes Identity Required 131 Revoked Mobile Nodes Identity Required
132 Revocation Failed - MN is Attached 132 Revocation Failed - MN is Attached
133 Revocation Trigger NOT Supported 133 Revocation Trigger NOT Supported
134 Revocation Function NOT Supported 134 Revocation Function NOT Supported
135 Proxy Binding Revocation NOT Supported
Sequence # Sequence #
The sequence number in the Binding Revocation Acknowledgement is The sequence number in the Binding Revocation Acknowledgement is
copied from the Sequence Number field in the Binding Revocation copied from the Sequence Number field in the Binding Revocation
Indication. It is used by the revoking mobility entity, e.g., HA, Indication. It is used by the initiator, e.g., HA, LMA, MAG, in
LMA, MAG, in matching this Binding Revocation Acknowledgement with matching this Binding Revocation Acknowledgement with the
the outstanding Binding Revocation Indication. outstanding Binding Revocation Indication.
Proxy Binding (P) Proxy Binding (P)
The Proxy Binding (P) bit is set if the (P) bit is set in the The Proxy Binding (P) bit is set if the (P) bit is set in the
corresponding Binding Revocation Indication message. corresponding Binding Revocation Indication message.
IPv4 HoA Binding Only (V) IPv4 HoA Binding Only (V)
The IPv4 HoA Binding Only (V) bit is set if the (V) bit is set in The IPv4 HoA Binding Only (V) bit is set if the (V) bit is set in
the corresponding Binding Revocation Indication message. the corresponding Binding Revocation Indication message.
skipping to change at page 19, line 44 skipping to change at page 18, line 29
The following mobility options are valid in a Binding Revocation The following mobility options are valid in a Binding Revocation
Acknowledgement: Acknowledgement:
o Home Network Prefix option [RFC5213]. This option MAY be included o Home Network Prefix option [RFC5213]. This option MAY be included
only when the (P) bit is set. only when the (P) bit is set.
o Mobile Node Identifier Option [RFC4283]. This option MAY be o Mobile Node Identifier Option [RFC4283]. This option MAY be
included when the (P) bit is set. This option SHOULD be included included when the (P) bit is set. This option SHOULD be included
if the Home Network Prefix option is included. if the Home Network Prefix option is included.
o Binding Identifier mobility option [ID-MCoA]. This option MAY be o Binding Identifier mobility option [ID-MCoA]. The responder MAY
included to indicate the specific BID that the receiving node include this option to indicate the specific BID that failed the
failed to revoke. revocation procedure.
If no options are present in this message, 4 octets of padding are If no options are present in this message, 4 octets of padding are
necessary and the Header Len field of the Binding Revocation Message necessary and the Header Len field of the Binding Revocation Message
will be set to 1. will be set to 1.
6. Binding Revocation Process Operation 6. Binding Revocation Process Operation
The following subsections describe the details of the generic binding The following subsections describe the details of the generic binding
revocation process as used by the different mobility entities. revocation process as used by the different mobility entities.
6.1. Sending Binding Revocation Messages 6.1. Sending Binding Revocation Message
When sending a Binding Revocation message, the sending mobility node, When sending a Binding Revocation message, the initiator constructs
initiator, constructs the packet as it would any other Mobility the packet as it would any other Mobility Header with the exception
Header with the exception of setting the MH Type field to <IANA-TBD>. of setting the MH Type field to <IANA-TBD>.
In addition, the initiator, MUST construct the Binding Revocation The Binding Revocation Message MUST be protected using the same
Message Data following the format of the Binding Revocation underlying security association, e.g., IPsec, that is being used
Indication message as described in Section 5.1. In the BRI message, between the two peers to protect the mobile node's Mobile IPv6 and
the initiator MUST set the Sequence Number field to a valid sequence its extensions binding registration signaling. If IPsec is not used
number for Binding Revocation. Since sending Binding Revocation as the underlying security mechanism to protect the binding
Indication message is not done on a regular basis, a 16 bit sequence registration signaling, the used underlying security mechanism MUST
number field is large enough to allow the initiator to match the provide protection against all identified security threats as
Binding Revocation Acknowledgement to the associated Binding described under Security Considerations in [RFC3775] and [RFC5213].
Revocation Indication using the sequence number field only.
However, when the responder acknowledges the Binding Revocation 6.1.1. Sending Binding Revocation Indication
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:
o The initiator MUST set the Sequence Number field to a valid
sequence number for Binding Revocation. Since sending 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 If the initiator is revoking a binding that was created using
proxy MIPv6 registration, the initiator MUST set the Proxy Binding
(P) bit.
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 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 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 the IPv4 Home Address option in the BRI
to identify the IPv4 HoA that is being revoked.
6.1.2. Sending Binding Revocation Acknowledgement
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 If the responder accepts the Binding Revocation Indication
message, the responder MUST send a successful Binding Revocation
Acknowledgement with an appropriate status code.
o If the responder rejects the Binding Revocation Indication
message, the responder MUST send a Binding Revocation
Acknowledgement with an appropriate failure status code.
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.
When the responder acknowledges the received Binding Revocation
Indication message, the responder MUST construct the Binding Indication message, the responder MUST construct the Binding
Revocation message packet as it would any other Mobility Header with Revocation Message Data following the format of the Binding
the exception of setting the MH Type field to <IANA-TBD>. It also Revocation Acknowledgement message as described in Section 5.2 and
MUST construct the Binding Revocation Message Data following the the following:
format of the Binding Revocation Acknowledgement message as described
in Section 5.2. In this case, the responder MUST set the Sequence
Number field by copying the value from the Sequence Number field of
the received Binding Revocation Indication. Additionally, it MUST
set the status field to a valid value that reflects the processing of
the received Binding Revocation Indication message.
The Binding Revocation Indication and Binding Revocation o The responder MUST set the Sequence Number field by copying the
Acknowledgement messages MUST be protected using the same underlying value from the Sequence Number field of the received Binding
security association, e.g., IPsec, that is being used between the two Revocation Indication.
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].
6.2. Receiving Binding Revocation Messages 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.
When receiving a Binding Revocation message, the receiving mobility o If the (P) bit is set in the received Binding Revocation
node MUST verify the Mobility Header as described in section 9.2. of Indication, the responder MUST set the (P) bit in the Binding
[RFC3775]. If the packet is dropped due to failing any of the Revocation Acknowledgement.
Mobility Headers test check, the receiving node MUST follow the
processing rules as in Section 9.2 of [RFC3775]. If the receiving
node does not support the Binding Revocation Indication message and
does not recognize the new MH type, it sends a Binding Error message
with the Status field set to 2 as described in [RFC3775].
Since some mobility entities, e.g., local mobility anchor and mobile o If the Global (G) bit is set in the received Binding Revocation
access gateway, are allowed to send Binding Revocation Indication and Indication, the responder MUST set the Global (G) bit in the
receive Binding Revocation Acknowledgement for different cases, Binding Revocation Acknowledgement.
therefore, if 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.
Upon receiving a packet carrying a Binding Revocation Indication or o If the IPv4 HoA Binding Only (V) bit is set in the received
Binding Revocation Acknowledgement, the receiving mobility entity Binding Revocation Indication, the responder MUST set the (V) bit
MUST verify that the packet was received protected by the security in the Binding Revocation Acknowledgement.
association that is being used to protect the binding registration
and Binding Revocation signaling between the two peers, e.g., an
IPsec SA.
Upon receiving a packet carrying a Binding Revocation o The destination IP address of the IPv6 packet of the Binding
Acknowledgement, the receiving mobility entity, initiator, MUST Revocation Acknowledgement is set to the source IP address of the
validate that sequence number in the Sequence Number field matches received Binding Revocation Indication.
the sequence number of an outstanding Binding Revocation Indication
that was sent by the initiator. If the sequence number does not
match any sequence number of any of the outstanding Binding
Revocation Indication, the receiving node MUST silently discard the
message but MAY log the event.
If a mobility node receives a Binding Revocation Indication message 6.2. Receiving Binding Revocation Message
with the Revocation Trigger field is set to a value that the mobility
node does not support and the Acknowledge (A) bit is set, the
receiving mobility node SHOULD reject the Binding Revocation
Indication message by sending a Binding Revocation Acknowledgement
message with the Status field set to "Revocation Trigger NOT
Supported".
If a mobility node receives a Binding Revocation Indication message When receiving a Binding Revocation message, the responder MUST
with a Revocation Trigger value that is NOT allowed with the Binding verify the Mobility Header as described in section 9.2. of [RFC3775].
Revocation Indication message intent, e.g., the Global (G) bit set If the packet is dropped due to failing any of the Mobility Headers
and the Revocation Trigger field value is a per-MN specific, the test check, the responder MUST follow the processing rules as in
receiving mobility node SHOULD reject the Binding Revocation Section 9.2 of [RFC3775]. If the responder does not support the
Indication message by sending a Binding Revocation Acknowledgement Binding Revocation Indication message and does not recognize the MH
message with the Status field set to "Revocation Function NOT type <IANA-TBD>, it sends a Binding Error message with the Status
Supported". field set to 2 as described in [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 SA.
6.2.1. Receiving Binding Revocation Indication
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:
o The responder MUST validate that the Binding Revocation Indication
is formatted as in Section 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 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 a per-MN specific,
the responder SHOULD reject the Binding Revocation Indication
message using status code "Revocation Function NOT Supported".
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".
6.2.2. Receiving Binding Revocation Acknowledgement
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:
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 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 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.
6.3. Retransmission of Binding Revocation Indication 6.3. Retransmission of Binding Revocation Indication
If the sending mobility entity set the Acknowledge (A) bit in the BRI If the initiator does not receive a Binding Revocation
and does not receive a Binding Revocation Acknowledgement in response Acknowledgement in response to the outstanding Binding Revocation
to the outstanding Binding Revocation Indication before the Indication before the InitMINDelayBRIs timer expires, the initiator,
InitMINDelayBRIs timer expires, the mobility entity, e.g. LMA, e.g. LMA, SHOULD retransmit the same BRI message up to the
SHOULD retransmit the same BRI message up to the BRIMaxRetriesNumber BRIMaxRetriesNumber as defined in Section 11.
as defined in Section 11. However, if the sending mobility entity
does not set the Acknowledge (A) bit in the BRI, the sending mobility
entity SHOULD NOT retransmit the Binding Revocation Indication
message.
The retransmissions by the sending mobility entity MUST use an The retransmissions by the initiator MUST use an exponential back-off
exponential back-off process in which the timeout period is doubled process in which the timeout period is doubled upon each
upon each retransmission, until either the node receives a response retransmission, until either the initiator receives a response or the
or the timeout period reaches the value MAX_BRACK_TIMEOUT. The timeout period reaches the value MAX_BRACK_TIMEOUT. The initiator
sending mobility entity MAY continue to send these messages at this MAY continue to send these messages at this slower rate up to the
slower rate up to the BRIMaxRetriesNumber. BRIMaxRetriesNumber.
If the revoking mobility entity does not receive a Binding Revocation If the initiator does not receive a Binding Revocation
Acknowledgement message after the BRIMaxRetriesNumber of retransmits Acknowledgement message after the BRIMaxRetriesNumber of retransmits
have been sent, the revoking mobility entity can clean the mobile have been sent, the initiator SHOULD clean all resources associated
node binding cache and all resources associated with this binding. with this mobile node binding. The initiator may log the event.
The revoking mobility entity may log the event.
7. Home Agent Operation 7. Home Agent Operation
7.1. Sending Binding Revocation Indication
To terminate a mobile node registration and its current binding with To terminate a mobile node registration and its current binding with
the home agent, the home agent sends a packet to the mobile node the home agent, the home agent sends a packet to the mobile node
containing a Binding Revocation Indication, with the packet containing a Binding Revocation Indication, with the packet
constructed as follows: constructed as follows:
o The Acknowledge (A) bit MAY be set to request the mobile node to
send a Binding Revocation Acknowledgement upon receipt of the
Binding Revocation Indication.
o The Revocation Trigger field MUST be set to indicate to the mobile 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 node the reason for revoking its IP mobility binding with the home
agent. The Revocation Trigger may be used by the mobile node to agent. The Revocation Trigger may be used by the mobile node to
take further steps if necessary. take further steps if necessary.
o The Binding Revocation Indication MUST be sent using a Type 2 o The Binding Revocation Indication MUST be sent using a Type 2
routing header which contains the mobile node's registered IPv6 routing header which contains the mobile node's registered IPv6
home address for the binding being revoked. home address for the binding being revoked.
o The care-of address for the binding MUST be used as the o The care-of address for the binding MUST be used as the
skipping to change at page 23, line 20 skipping to change at page 23, line 29
the destination address in the packet's IPv6 header SHOULD be set the destination address in the packet's IPv6 header SHOULD be set
to the source IP address of the packet that carried the latest to the source IP address of the packet that carried the latest
successful Binding Update with the Alternate Care-of address successful Binding Update with the Alternate Care-of address
included. included.
o If the home agent needs to only revoke the mobile node's IPv4 home 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 address binding, the home agent MUST set the IPv4 HoA Binding Only
(V) bit and MUST include the mobile node's registered IPv4 home (V) bit and MUST include the mobile node's registered IPv4 home
address that is being revoked in the IPv4 Home Address option. address that is being revoked in the IPv4 Home Address option.
The Acknowledge (A) bit in the Binding Revocation Indication requests
the mobile node to return a Binding Revocation Acknowledgement in
response to this Binding Revocation Indication. As described in
Section 6.3, the home agent SHOULD retransmit this Binding Revocation
Indication to the mobile node before terminating its IP connection
until it receives a matching Binding Revocation Acknowledgement or
the BRIMaxRetransmitNumber has been reached.
When the home agent sends a Binding Revocation Indication to the When the home agent sends a Binding Revocation Indication to the
mobile node with the Acknowledge (A) bit set, the home agent sets a mobile node, the home agent sets a flag in the mobile node BCE to
flag in the mobile node BCE to indicate that revocation is in indicate that revocation is in progress and starts the
progress and starts the InitMINDelayBRIs timer. The home agent InitMINDelayBRIs timer. The home agent maintains the mobile node BCE
maintains the mobile node BCE in this state until it receives a in this state until it receives a Binding Revocation Acknowledgement
Binding Revocation Acknowledgement or retransmits the Binding or retransmits the Binding Revocation Indication message as described
Revocation Indication message as described in Section 6.3. in Section 6.3.
In a race condition case, the home agent may receive a Binding Update 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 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 in progress flag set, the home agent SHOULD handle this case based on
the reason for sending the Binding Revocation Indication message and the reason for sending the Binding Revocation Indication message and
its local policy. In this case, if the home agent accepts the its local policy. In this case, if the home agent accepts the
Binding Update, it needs to update the mobile node BCE accordingly, Binding Update, it needs to update the mobile node BCE accordingly,
e.g. removing the revocation in progress flag. e.g. removing the revocation in progress flag.
When the home agent needs to revoke one or more of a mobile node When the home agent needs to revoke one or more of a mobile node
bindings that were created using Multiple Care-of address bindings that were created using Multiple Care-of address
registration as in [ID-MCoA], the home agent MUST include all the registration as in [ID-MCoA], the home agent MUST include all the
related BID mobility options that identify these bindings in the related BID mobility options that identify these bindings in the
Binding Revocation Indication message. In the case when the home Binding Revocation Indication message. In the case when the home
agent needs to revoke all of the mobile node bindings, the home agent agent needs to revoke all of the mobile node bindings, the home agent
SHOULD NOT include any of the BID mobility options. SHOULD NOT include any of the BID mobility options.
7.2. Receiving Binding Revocation Acknowledgement
When the home agent receives a packet carrying a valid Binding When the home agent receives a packet carrying a valid Binding
Revocation Acknowledgement that was successfully processed as in Revocation Acknowledgement message, the home agent follows
Section 6.2, the home agent SHOULD examine the Status field as Section 6.2 in processing this message.
follows:
o If the Status field indicates that the Binding Revocation
Indication was processed successfully, the home agent MUST delete
the current timer and the mobile node bindings and all related
resources.
o If the Status field indicates any value other than success, the
home agent SHOULD examine any mobility options included in the
Binding Revocation Acknowledgement. In this case, it is based on
the home agent local policy how to handle the mobile node BCE.
The home agent MAY log the appropriate event to reflect the
received status.
8. Local Mobility Anchor Operation 8. Local Mobility Anchor Operation
8.1. Binding Revocation Initiator 8.1. Sending Binding Revocation Indication
8.1.1. Sending Binding Revocation Indication
To terminate a mobile node PMIPv6 registration and its current To terminate a mobile node PMIPv6 registration and its current
binding with the local mobility anchor, the local mobility anchor binding with the local mobility anchor, the local mobility anchor
sends a packet to the mobile access gateway containing a Binding sends a packet to the mobile access gateway containing a Binding
Revocation Indication message following the procedure in Section 6.1 Revocation Indication message following the procedure in Section 6.1
and the following rules: and the following rules:
o The Acknowledge (A) bit MAY be set to request the mobile access
gateway to send a Binding Revocation Acknowledgement upon receipt
of the Binding Revocation Indication.
o The Proxy Mobile IP (P) bit MUST be set to indicate that the o The Proxy Mobile IP (P) bit MUST be set to indicate that the
binding being revoked is a PMIPv6 binding. binding being revoked is a PMIPv6 binding.
o The Revocation Trigger field MUST be set to indicate to the mobile o The Revocation Trigger field MUST be set to indicate to the mobile
access gateway the reason for removing the specified mobile node access gateway the reason for removing the specified mobile node
PMIPv6 binding at the local mobility anchor. The Revocation PMIPv6 binding at the local mobility anchor. The Revocation
Trigger may be used by the mobile access gateway to learn the Trigger may be used by the mobile access gateway to learn the
mobile node's latest movement. mobile node's latest movement.
o The packet MUST contain the Mobile Node Identifier, MN-ID, option o The packet MUST contain the Mobile Node Identifier, MN-ID, option
skipping to change at page 25, line 14 skipping to change at page 24, line 41
o If the Mobile Node Identifier, MN-ID, is registered in more than o If the Mobile Node Identifier, MN-ID, is registered in more than
one of the mobile node's BCE and the local mobility anchor does one of the mobile node's BCE and the local mobility anchor does
NOT need to revoke all of the mobile node's bindings, the Binding NOT need to revoke all of the mobile node's bindings, the Binding
Revocation Indication message MUST contain another identifier to Revocation Indication message MUST contain another identifier to
uniquely identify the mobile node binding(s) that is being uniquely identify the mobile node binding(s) that is being
revoked, e.g., at least one Home Network Prefix option which revoked, e.g., at least one Home Network Prefix option which
contains the mobile node's registered Home Network Prefix (HNP) contains the mobile node's registered Home Network Prefix (HNP)
for the binding being revoked. for the binding being revoked.
o In case of revoking all Per-Peer bindings, the Global (G) bit MUST o In case of revoking all Per-Peer bindings, the local mobility
be set and the Revocation Trigger MUST contain the value "Per-Peer anchor MUST set the Global (G) bit and the Revocation Trigger MUST
Policy" to request the mobile access gateway to remove all Per- contain the value "Per-Peer Policy" to request the mobile access
Peer bindings that are registered with the local mobility anchor gateway to remove all Per-Peer bindings that are registered with
and this mobile access gateway. the local mobility anchor and this mobile access gateway.
o Whenever the Global (G) bit is set in the Binding Revocation
Indication, the Acknowledge (A) bit MUST be set to request the
mobile access gateway to send a Binding Revocation
Acknowledgement.
o The care-of address for the binding MUST be used as the o The care-of address for the binding MUST be used as the
destination address in the packet's IPv6 header, unless an destination address in the packet's IPv6 header, unless an
Alternate Care-of Address mobility option is included in the Alternate Care-of Address mobility option is included in the
Binding Revocation Indication message. If an Alternate Care-of Binding Revocation Indication message. If an Alternate Care-of
Address option is included in the Binding Revocation Indication Address option is included in the Binding Revocation Indication
message, the destination address in the packet's IPv6 header message, the destination address in the packet's IPv6 header
SHOULD be set to the source IP address of the packet that carried SHOULD be set to the source IP address of the packet that carried
the latest successful Proxy Binding Update with the Alternate the latest successful Proxy Binding Update with the Alternate
Care-of address included. Care-of address included.
The Acknowledge (A) bit in the Binding Revocation Indication requests The local mobility anchor MAY delete the mobile node(s) IP tunnel
the mobile access gateway to return a Binding Revocation immediately after sending the initial Binding Revocation Indication
Acknowledgement. If the local mobility anchor sets the Acknowledge and before receiving the Binding Revocation Acknowledgement message.
(A) bit in the Binding Revocation Indication message, the local
mobility anchor SHOULD retransmit the Binding Revocation Indication
message by following the procedure described in Section 6.3 until it
receives a matching Binding Revocation Acknowledgement or the
BRIMaxRetransmitNumber is reached before deleting the mobile node IP
tunnel to the mobile access gateway. 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.
When the local mobility anchor sends a Binding Revocation Indication When the local mobility anchor sends a Binding Revocation Indication
to the mobile access gateway to remove a specific binding and the to the mobile access gateway to remove a specific binding, the local
Acknowledge (A) bit is set, the local mobility anchor sets a flag in mobility anchor sets a flag in the mobile node proxy BCE to indicate
the mobile node proxy BCE to indicate that revocation is in progress that revocation is in progress and starts the InitMINDelayBRIs timer.
and starts the InitMINDelayBRIs timer. The local mobility anchor The local mobility anchor SHOULD maintain the mobile node proxy BCE
SHOULD maintain the mobile node proxy BCE in this state until it in this state until it receives a Binding Revocation Acknowledgement
receives a Binding Revocation Acknowledgement or the or the BRIMaxRetransmitNumber is reached. In the case when the local
BRIMaxRetransmitNumber is reached. In the case when the local
mobility anchor sets the Revocation Trigger field to a value which mobility anchor sets the Revocation Trigger field to a value which
indicates inter-MAG handover, the local mobility anchor MAY switch indicates inter-MAG handover, the local mobility anchor MAY switch
the mobile node IP tunnel to the target mobile access gateway before the mobile node IP tunnel to the target mobile access gateway before
sending the Binding Revocation Indication to the source mobile access sending the Binding Revocation Indication to the source mobile access
gateway. gateway.
In a race condition case, the local mobility anchor may receive a In a race condition case, the local mobility anchor may receive a
Proxy Binding Update from the mobile access gateway while the mobile Proxy Binding Update from the mobile access gateway while the mobile
node's proxy BCE has the revocation in progress flag set. The local node's proxy BCE has the revocation in progress flag set. The local
mobility anchor should handle this case based on the reason for mobility anchor should handle this case based on the reason for
sending the Binding Revocation Indication message and its local sending the Binding Revocation Indication message and its local
policy. In this case, if the local mobility anchor accepts the Proxy policy. In this case, if the local mobility anchor accepts the Proxy
Binding Update, it needs to update the mobile node proxy BCE Binding Update, it needs to update the mobile node proxy BCE
accordingly, e.g. removing the revocation in progress flag. accordingly, e.g. removing the revocation in progress flag.
When the local mobility anchor needs to revoke all the mobile nodes When the local mobility anchor needs to revoke all the mobile nodes
proxy BCEs that are registered with the local mobility anchor and the proxy BCEs that are registered with the local mobility anchor and the
mobile access gateway, it MUST set the Global (G) bit and set the mobile access gateway peer, it MUST set the Global (G) bit and set
value of the Revocation Trigger field to "Per-Peer Policy". In this the value of the Revocation Trigger field to "Per-Peer Policy". In
case, the local mobility anchor MUST NOT include any mobility options this case, the local mobility anchor MUST NOT include any mobility
in the this Binding Revocation Indication message. options in this Binding Revocation Indication message.
When the local mobility anchor needs to revoke all mobile nodes proxy When the local mobility anchor needs to revoke all mobile nodes proxy
BCEs that belong to a specific realm and are registered with the BCEs that belong to a specific realm and are registered with the
local mobility anchor and the mobile access gateway, the local 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 mobility anchor MUST set the Global (G) bit and set the value of the
Revocation Trigger field to "Revoking Mobility Node Local Policy". Revocation Trigger field to "Revoking Mobility Node Local Policy".
In this case, the local mobility anchor MUST include a mobility In this case, the local mobility anchor MUST include a mobility
option in the Binding Revocation Indication that is shared among all option in the Binding Revocation Indication that is shared among all
the impacted mobile nodes BCEs, e.g., the mobile node identifier the impacted mobile nodes BCEs, e.g., the mobile node identifier
option, MN-ID option, with subtype value of 1. In this case, the NAI option, MN-ID option, with subtype value of 1. In this case, the NAI
value in the MN-ID MUST follow the format where the content after the value in the MN-ID MUST follow the format where the content after the
"@" character defines the realm which is shared amongst all of the "@" character defines the realm which is shared amongst all of the
impacted mobile nodes proxy BCEs. As an example: @example.com impacted mobile nodes proxy BCEs. As an example: @example.com
identifies all mobile nodes which their MN-ID value contain identifies all mobile nodes which their MN-ID value contain
skipping to change at page 27, line 28 skipping to change at page 26, line 41
bindings of the specified mobile node NAI in the MN-ID option. bindings of the specified mobile node NAI in the MN-ID option.
According to Proxy Mobile IPv6 specification [RFC5213], if the local According to Proxy Mobile IPv6 specification [RFC5213], if the local
mobility anchor receives a Proxy Binding Update message from a new mobility anchor receives a Proxy Binding Update message from a new
mobile access gateway for extending the binding lifetime of the only mobile access gateway for extending the binding lifetime of the only
BCE of this mobile node with the Handoff Indicator value is set to BCE of this mobile node with the Handoff Indicator value is set to
"Inter-MAG Handover - Unknown", the local mobility anchor waits a "Inter-MAG Handover - Unknown", the local mobility anchor waits a
period of MaxDelayBeforeNewBCEAssign to receive a de-registration period of MaxDelayBeforeNewBCEAssign to receive a de-registration
message from the previous mobile access gateway before updating the message from the previous mobile access gateway before updating the
mobile node's BCE with the new point of attachment. If a de- mobile node's BCE with the new point of attachment. If a de-
registration message is not received,, the local mobility anchor registration message is not received, the local mobility anchor
considers the received Proxy Binding Update message as a request for considers the received Proxy Binding Update message as a request for
a new BCE and if processed successfully, the local mobility anchor a new BCE and if processed successfully, the local mobility anchor
assigns a different HNP for the new BCE. assigns a different HNP for the new BCE.
This document updates the local mobility anchor's behavior in this This document updates the local mobility anchor's behavior in this
case. If the local mobility anchor supports the binding revocation case. If the local mobility anchor supports the binding revocation
mechanism as described in this document, it SHOULD proactively send a mechanism as described in this document, it SHOULD proactively send a
Binding Revocation Indication message to the previous mobile access Binding Revocation Indication message to the previous mobile access
gateway instead of waiting for a de-registration from the previous gateway instead of waiting for a de-registration from the previous
mobile access gateway. In the Binding Revocation Indication message, mobile access gateway. In the Binding Revocation Indication message,
the Acknowledge (A) bit MUST be set and the Revocation Trigger MUST the Revocation Trigger MUST be set to "Inter-MAG Handover - Unknown".
be set to "Inter-MAG Handover - Unknown".
If the local mobility anchor sent a Binding Revocation Indication If the local mobility anchor sent a Binding Revocation Indication
message with the Revocation Trigger field set to "Inter-MAG Handover message with the Revocation Trigger field set to "Inter-MAG Handover
- Unknown" and while waiting for a Binding Revocation Acknowledgement - Unknown" and while waiting for a Binding Revocation
response, the following are possible conditions that the local Acknowledgement, the following are possible conditions that the local
mobility anchor MUST handle as specified below: mobility anchor MUST handle as specified below:
o If the local mobility anchor receives a successful Binding o If the local mobility anchor receives a successful Binding
Revocation Acknowledgement message or a de-registration message Revocation Acknowledgement message or a de-registration message
from the previous mobile access gateway, the local mobility anchor from the previous mobile access gateway, the local mobility anchor
MUST update the mobile node BCE in a similar way as if it received MUST update the mobile node BCE in a similar way as if it received
a de-registration message as described in [RFC5213]. a de-registration message as described in [RFC5213].
o If the local mobility anchor receives a Binding Revocation o If the local mobility anchor receives a Binding Revocation
Acknowledgement message with the status field set to "Revocation Acknowledgement message with the status field set to "Revocation
skipping to change at page 28, line 41 skipping to change at page 28, line 8
revoke the mobile node IPv4 proxy HoA binding to the current mobile revoke the mobile node IPv4 proxy HoA binding to the current mobile
node proxy CoA while maintaining the mobile node binding of the HNP 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 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 the local mobility anchor decides to revoke the mobile node IPv4
proxy HoA only, it MUST send a Binding Revocation Indication message proxy HoA only, it MUST send a Binding Revocation Indication message
following the procedure in Section 6.1 and the following rules: following the procedure in Section 6.1 and the following rules:
o The IPv4 HoA Binding Only (V) bit MUST be set in the BRI to 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. indicate that only the IPv4 home address binding is being revoked.
o The Acknowledge (A) bit MUST be set to request the mobile access
gateway to send a Binding Revocation Acknowledgement message.
o The IPv4 Home Address option MUST be included with the mobile o The IPv4 Home Address option MUST be included with the mobile
node's registered IPv4 home address that is being released in node's registered IPv4 home address that is being released in
addition to the MN-ID option. addition to the MN-ID option.
o The mobile node Home Network Prefix option MUST NOT be included. o The mobile node Home Network Prefix option MUST NOT be included.
o The Revocation Trigger field MUST be set to an appropriate value, o The Revocation Trigger field MUST be set to an appropriate value,
e.g. "User Initiated Session(s) Termination". e.g. "User Initiated Session(s) Termination".
8.1.2. Receiving Binding Revocation Acknowledgement 8.2. Receiving Binding Revocation Indication
When the local mobility anchor receives a packet carrying a valid
Binding Revocation Acknowledgement that was successfully processed as
in Section 6.2 and if the mobile node BCE is in the state of
Revocation in progress, the local mobility anchor SHOULD examine the
Status field before clearing the mobile node related resources as
follows:
o If the Status field indicates that the BRI was processed
successfully, the local mobility anchor MUST delete the current
timer and the mobile node proxy bindings and all associated
resources.
o If the Status field indicates partial success value or MN binding
does not exist, the local mobility anchor SHOULD examine the
mobility options that are included in the Binding Revocation
Acknowledgement, if any, before deleting the current timer and the
mobile node associated proxy bindings and other related resources.
It is based on the local mobility anchor local policy how to
handle the mobile node BCE(s) that the mobile access gateway
indicated it failed the revocation procedure, however, the LMA MAY
log the event.
8.2. Binding Revocation Responder
8.2.1. Receiving Binding Revocation Indication
When the local mobility anchor receives a packet carrying a Binding When the local mobility anchor receives a packet carrying a Binding
Revocation Indication that was successfully processed as in Revocation Indication that was successfully processed as in
Section 6.2, the local mobility anchor SHOULD in addition process the Section 6.2, in addition, the local mobility anchor processes the
message as follows: message as follows:
o Validate that Binding Revocation Indication is formatted as in o If the (P) bit is set, the local mobility anchor MUST validate
Section 5.1 and if the (P) bit is set, the local mobility anchor that all impacted binding(s) have the proxy binding flag set.
MUST validate that all impacted binding(s) have the proxy binding
flag set.
o If the Global (G) bit is set and the Revocation Trigger field 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 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 (P) bit is set and the MN-ID option is present with the mobile
access gateway identity included. In addition, the local mobility access gateway identity included. In addition, the local mobility
anchor MUST verify that the identified mobile access gateway as anchor MUST verify that the identified mobile access gateway as
per the value in the MN-ID option is authorized to use the global per the value in the MN-ID option is authorized to use the global
revocation with revocation trigger value "Per-Peer Policy", see revocation with revocation trigger value "Per-Peer Policy", see
Section 13. If the Acknowledge (A) bit is set and the local Section 13. If the local mobility anchor processes the Global
mobility anchor processes the Global Binding Revocation Indication Binding Revocation Indication message successfully, it MUST accept
message successfully, it MUST send a successful Binding Revocation the Binding Revocation Indication message using the Status code
Acknowledgement message. However, if the Acknowledge (A) bit is success.
not set, the local mobility anchor SHOULD silently discard the
Binding Revocation Indication message. 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 If the Global (G) bit is set and the Revocation Trigger value is 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, "Per-Peer Policy", and only the mobile node identifier, MN-ID,
option is included, the local mobility anchor MUST revoke all option is included, the local mobility anchor MUST revoke all
mobile nodes bindings which proxy CoA is the one used as the mobile nodes bindings which proxy CoA is the one used as the
source of the IPv6 packet that carried the Binding Revocation source of the IPv6 packet that carried the Binding Revocation
Indication. However, if one or more Alternate Care-of Address Indication. However, if one or more Alternate Care-of Address
options are included in addition to the mobile node identifier options are included in addition to the mobile node identifier
option, the local mobility anchor MUST revoke all mobile nodes option, the local mobility anchor MUST revoke all mobile nodes
bindings which proxy Care-of Address matches one of the Care-of bindings which proxy Care-of Address matches one of the Care-of
address(es) in the Alternate Care-of Address option(s). address(es) in the Alternate Care-of Address option(s). 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 The local mobility anchor identifies all impacted mobile nodes o If the local mobility anchor accepted the Binding Revocation
bindings and if the Acknowledge (A) bit is set, the local mobility Indication message but one or more of the bindings identified in
anchor MUST send a Binding Revocation Acknowledgement following the received Binding Revocation Indication message has already
Section 8.2.2 using the appropriate status code. 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 If the Global (G) bit is not set, the local mobility anchor SHOULD o If the Global (G) bit is not set, the local mobility anchor uses
use the included mobility options to identify the impacted mobile the included mobility options to identify the impacted mobile node
node binding as follows: binding as follows:
1. If only the mobile node identifier, MN-ID, option is included, 1. If only the mobile node identifier, MN-ID, option is included,
the local mobility anchor MUST revoke all bindings for this the local mobility anchor MUST accept the message and revoke
mobile node which use the specified mobile node NAI including all bindings for this mobile node which use the specified
the IPv4 Home Address binding(s) if present. mobile node NAI including the IPv4 Home Address binding(s) if
present.
2. If the mobile node identifier, MN-ID, and one Home Network 2. If the mobile node identifier, MN-ID, and one Home Network
Prefix option are included, the local mobility anchor MUST Prefix option are included, the local mobility anchor MUST
only remove the specified mobile node proxy binding. accept the message and only remove the specified mobile node
proxy binding.
3. If the mobile node identifier, MN-ID, option and more than one 3. If the mobile node identifier, MN-ID, option and more than one
Home Network Prefix options are included, the local mobility Home Network Prefix options are included, the local mobility
anchor MUST remove all bindings which are referenced by these anchor MUST accept the message and remove all bindings which
Home Network Prefixes for the specified mobile node NAI. are referenced by these Home Network Prefixes for the
specified mobile node NAI.
4. If the IPv4 HoA binding Only (V) bit is set and the mobile 4. If the IPv4 HoA binding Only (V) bit is set and the mobile
node identifier, MN-ID, option and the IPv4 Home Address node identifier, MN-ID, option and the IPv4 Home Address
option are included, the local mobility anchor MUST remove option are included, the local mobility anchor MUST accept the
only the IPv4 HoA address binding to the mobile node current message and remove only the IPv4 HoA address binding to the
proxy Care-of address. mobile node current proxy Care-of address.
The Revocation Trigger field value in the received Binding Revocation The Revocation Trigger field value in the received Binding Revocation
Indication could be used by the local mobility anchor to log an event Indication could be used by the local mobility anchor to log an event
or update some local parameters which tracks the state of the peer or update some local parameters which tracks the state of the peer
mobile access gateway. mobile access gateway.
8.2.2. Sending Binding Revocation Acknowledgement After the local mobility anchor accepts or rejects a Binding
Revocation Indication message, the local mobility anchor MUST follow
When the local mobility anchor receives a valid Binding Revocation Section 6.1 and Section 6.1.2 to send a Binding Revocation
Indication with the Acknowledge (A) bit set and after processing the Acknowledgement message to the mobile access gateway.
Binding Revocation Indication message, the local mobility anchor
sends a packet to the mobile access gateway containing a Binding
Revocation Acknowledgement following the process in Section 6.1 and
the following:
o If the (P) bit was set in the received Binding Revocation
Indication, the local mobility anchor MUST set the (P) bit in the
Binding Revocation Acknowledgement.
o If the Global (G) bit was set in the received Binding Revocation
Indication, the local mobility anchor MUST set the Global (G) bit
in the Binding Revocation Acknowledgement.
o If the IPv4 HoA Binding Only (V) bit was set in the received
Binding Revocation Indication, the local mobility anchor MUST set
the (V) bit in the Binding Revocation Acknowledgement.
o The local mobility anchor MUST set the Status field to a valid
code that reflects the processing of the received Binding
Revocation Indication. 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 set the Status field to (Global Revocation NOT
Authorized).
o In the case that one of the bindings identified in the received
Binding Revocation Indication message has already been released,
the local mobility anchor MAY set the Status field to partial
success and in this case it MAY include the mobile node identifier
or the Home Network Prefix option to identify the binding(s) that
failed the revocation procedure.
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.
9. Mobile Access Gateway Operation 9. Mobile Access Gateway Operation
9.1. Binding Revocation Responder 9.1. Receiving Binding Revocation Indication
9.1.1. Receiving Binding Revocation Indication
Upon receiving a packet carrying a Binding Revocation Indication, the
mobile access gateway MUST validate and process the packet according
to Section 6.2 and the following:
o Binding Revocation Indication MUST be formatted as in Section 5.1
and the (P) bit is set.
o If the Acknowledge (A) bit in the received Binding Revocation When the mobile access gateway receives a packet carrying a Binding
Indication is set, the mobile access gateway MUST send a Binding Revocation Indication that was successfully processed as in
Revocation Acknowledgement following Section 9.1.2 using the Section 6.2, in addition, the mobile access gateway processes the
appropriate status value. message as follows:
o If the Global (G) bit is set and the Revocation Trigger field o If the Global (G) bit is set and the Revocation Trigger field
value is "Per-Peer policy", the mobile access gateway identifies value is "Per-Peer policy", the mobile access gateway MUST
all bindings that are registered at the local mobility anchor and validate that the Proxy (P) bit is set and no mobility options is
the mobile access gateway. If this Binding Revocation Indication included in the message. If the mobile access gateway processes
message does not include any mobility options and the Acknowledge the Global Binding Revocation Indication message successfully, it
(A) bit is set, the mobile access gateway MUST send a successful MUST accept the Binding Revocation Indication message using the
Binding Revocation Acknowledgement with the appropriate status Status code success.
code to the local mobility anchor. Since such Binding Revocation
Indication message impacts all mobility sessions that are
registered with the mobile access gateway and the local mobility
anchor, no mobility option MUST be present in this Binding
Revocation Indication message. However, if this received Binding
Revocation Indication message includes any mobility option and the
Acknowledge (A) bit set, the mobile access gateway MUST send a
Binding Revocation Acknowledgement with status code set to
"Revocation Function NOT Supported".
o If the Global (G) bit is set and the Revocation Trigger field o If the Global (G) bit is set and the Revocation Trigger field
value is "Revoking Mobility Node Local Policy", the mobile access value is "Revoking Mobility Node Local Policy", the mobile access
gateway MUST identify all bindings that are registered at the gateway MUST validate that the Proxy (P) bit is set and at least
local mobility anchor and the mobile access gateway and share the the MN-ID option with the subtype value of 1 is included in the
criteria based on the mobility option(s) included in the Binding Binding Revocation Indication and it is formatted as described is
Revocation Indication. In this case, the mobile access gateway Section 8.1. If the mobile access gateway processes this Global
MUST verify that at least the MN-ID option with the subtype value Binding Revocation Indication message successfully, it MUST accept
of 1 is included in the Binding Revocation Indication and it is the message using the Status code success.
formatted as specified is Section 8.1.1. If the mobile access
gateway successfully process the Binding Revocation Indication and
the Acknowledge (A) bit is set, the mobile access gateway MUST
send a successful Binding Revocation Acknowledgement with the
appropriate status code to the local mobility anchor.
o If the Global (G) bit is set and the Revocation Trigger field o If the Global (G) bit is set and the Revocation Trigger field
value is "Revoking Mobility Node Local Policy", and no mobility value is "Revoking Mobility Node Local Policy", and no mobility
options are included in the Binding Revocation Indication message options are included in the Binding Revocation Indication message
or the mobile access gateway is not able to identify the impacted or the mobile access gateway is not able to identify the impacted
mobile nodes bindings based on the included mobility options, the mobile nodes bindings based on the included mobility options, the
mobile access gateway MUST treat this as an error scenario. In mobile access gateway MUST treat this as an error scenario. In
this case, if the Acknowledge (A) bit is set, the mobile access this case, the mobile access gateway MUST reject the Binding
gateway MUST send a Binding Revocation Acknowledgement message Revocation Indication message using Status code "Revoked Mobile
with status "Revoked Mobile Nodes Identity Required". Nodes Identity Required".
o If the Revocation Trigger field value in the received Binding o If the Revocation Trigger field value in the received Binding
Revocation Indication message indicates inter-MAG handover, e.g., Revocation Indication message indicates inter-MAG handover, e.g.,
Inter-MAG Handover - Unknown, and the Acknowledge (A) bit is set, Inter-MAG Handover - Unknown, the mobile access gateway uses the
the mobile access gateway uses the mobility option(s) included in mobility option(s) included in the Binding Revocation Indication
the Binding Revocation Indication message to identify the mobile message to identify the mobile node binding. The mobile access
node binding. The mobile access gateway SHOULD ensure that the gateway SHOULD ensure that the mobile node is no longer attached
mobile node is no longer attached to the mobile access gateway to the mobile access gateway before accepting the BRI message
before sending a successful Binding Revocation Acknowledgement using Status code success. However, if the mobile access gateway
message to the local mobility anchor. However, if the mobile verified that the mobile node is still directly attached, the
access gateway verified that the mobile node is still directly mobile access gateway MUST reject the BRI using Status code
attached, the mobile access gateway MUST set the status field in "Revocation failed - MN is Attached".
the Binding Revocation Acknowledgement to "Revocation failed - MN
is Attached".
o If the IPv4 HoA Binding Only (V) bit is set, the mobile access 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 gateway uses the MN-ID option to identify the mobile node binding
entry in the Binding Update List (BUL). It MUST verify that the entry in the Binding Update List (BUL). The mobile access gateway
IPv4 address included in the IPv4 Home Address option in the MUST verify that the IPv4 address included in the IPv4 Home
received Binding Revocation Indication is the same as the IPv4 Address option in the received Binding Revocation Indication is
proxy HoA that is assigned to the mobile node. After the mobile the same as the IPv4 proxy HoA that is assigned to the mobile
access gateway successfully validates the received IPv4 home node. After the mobile access gateway successfully validates the
address as the mobile node IPv4 HoA, it MUST consider this as an received IPv4 home address as the mobile node IPv4 HoA, it MUST
indication to ONLY release the mobile node IPv4 proxy HoA binding consider this as an indication to ONLY release the mobile node
to the mobile node current proxy CoA. Consequently, it MUST IPv4 proxy HoA binding to the mobile node current proxy CoA.
continue to maintain the mobile node IPv6 proxy HoA or HNP binding Consequently, it MUST continue to maintain the mobile node IPv6
to the current mobile node proxy CoA as part of the mobile node proxy HoA or HNP binding to the current mobile node proxy CoA as
binding in the BUL entry and release all resources associated with part of the mobile node binding in the BUL entry and release all
the MN IPv4 proxy HoA binding to the MN pCoA. In this case, if resources associated with the MN IPv4 proxy HoA binding to the MN
the Acknowledge (A) bit is set, the mobile access gateway MUST pCoA. If the mobile access gateway processed the BRI
send a Binding Revocation Acknowledgement message with the Status successfully, the mobile access gateway MUST accept the BRI using
field is set to success. On the other hand, if the mobile access Status code success. On the other hand, if the mobile access
gateway is able to identify the mobile node binding using the gateway is able to identify the mobile node binding using the
MN-ID but failed to identify the received IPv4 proxy HoA, it MUST MN-ID but failed to identify the received IPv4 proxy HoA, the
send a Binding Revocation Acknowledgement with Status field is set mobile access gateway MUST reject the BRI using Status code
to "Binding Does NOT Exist". "Binding Does NOT Exist".
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.
The Revocation Trigger field value in the received Binding Revocation The Revocation Trigger field value in the received Binding Revocation
Indication could be used by the mobile access gateway to define what Indication could be used by the mobile access gateway to define what
actions the mobile access gateway could do to inform the mobile node actions the mobile access gateway could do to inform the mobile node
that its IP connectivity to the current HNP has been terminated, that its IP connectivity to the current HNP has been terminated,
e.g., if the Revocation Trigger field is set to "Administrative e.g., if the Revocation Trigger field is set to "Administrative
Reason", the mobile access gateway may send a RA message after Reason", the mobile access gateway may send a RA message after
setting the Home Network Prefix valid lifetime to zero. setting the Home Network Prefix valid lifetime to zero.
9.1.2. Sending Binding Revocation Acknowledgement After the mobile access gateway accepts or rejects a Binding
Revocation Indication message, the mobile access gateway MUST follow
When the mobile access gateway receives a valid Binding Revocation Section 6.1 and Section 6.1.2 to send a Binding Revocation
Indication with the Acknowledge (A) bit set and after processing it, Acknowledgement message to the local mobility anchor.
the mobile access gateway MUST send a packet to the local mobility
anchor containing a Binding Revocation Acknowledgement according to
the procedure in Section 6.1 and the following:
o The mobile access gateway MUST set the (P) bit in the Binding
Revocation Acknowledgement if it is set in the received Binding
Revocation Indication.
o If the Global (G) bit was set in the received Binding Revocation
Indication, the mobile access gateway MUST set the Global (G) bit
in the Binding Revocation Acknowledgement.
o If the IPv4 HoA Binding Only (V) bit was set in the received
Binding Revocation Indication, the mobile access gateway MUST set
the (V) bit in the Binding Revocation Acknowledgement.
o The mobile access gateway MUST set the Status field to a valid
code that reflects the processing of the received Binding
Revocation Indication.
o In the case that one or more of the bindings identified in the
received Binding Revocation Indication message has already been
released before receiving the Binding Revocation Indication, 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 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.
9.2. Binding Revocation Initiator
9.2.1. Sending Binding Revocation Indication 9.2. Sending Binding Revocation Indication
The mobile access gateway could send a Binding Revocation Indication The mobile access gateway could send a Binding Revocation Indication
message to indicate the termination of multiple mobile node bindings, message to indicate the termination of multiple mobile node bindings,
e.g., when using the global revocation with the Global (G) bit set. e.g., when using the global revocation with the Global (G) bit is
In this case when an event occurs which requires the mobile access set. In this case when an event occurs which requires the mobile
gateway to inform the local mobility anchor to terminate all mobile access gateway to inform the local mobility anchor peer to terminate
nodes bindings which are registered at the local mobility anchor and all mobile nodes bindings which are registered at the local mobility
the mobile access gateway, the mobile access gateway sends a Binding anchor and the mobile access gateway, the mobile access gateway sends
Revocation Indication message following Section 6.1 and the a Binding Revocation Indication message following the procedure in
following: Section 6.1 and the followings:
o The Acknowledge (A) bit MUST be set to request the local mobility
anchor to send a Binding Revocation Acknowledgement upon receipt
of the Binding Revocation Indication.
o The Proxy Binding (P) bit MUST be set to indicate that the o The Proxy Binding (P) bit MUST be set to indicate that the
binding(s) being revoked is a PMIPv6 binding. binding(s) being revoked is a PMIPv6 binding.
o The Global (G) bit MUST be set and the Revocation Trigger MUST o The Global (G) bit MUST be set and the Revocation Trigger MUST
contain a value of "Per-Peer Policy" in the Binding Revocation contain a value of "Per-Peer Policy" in the Binding Revocation
Indication to request the local mobility anchor to remove all Per- Indication to request the local mobility anchor to remove all Per-
Peer bindings that are registered with the local mobility anchor Peer bindings that are registered with the local mobility anchor
and this mobile access gateway. In this case, the MN-ID option and the mobile access gateway. In this case, the MN-ID option
MUST be included in the Binding Revocation Indication and contain MUST be included in the Binding Revocation Indication and contain
the mobile access gateway identity. In addition, the mobile the mobile access gateway identity. In addition, the mobile
access gateway MAY include one or more Alternate Care-of Address access gateway MAY include one or more Alternate Care-of Address
option(s). The Alternate Care-of Address option(s) contain the option(s). The Alternate Care-of Address option(s) contain the
proxy Care-of address(es) the bindings of which are being impacted proxy Care-of address(es) the bindings of which are being impacted
by this Binding Revocation Indication message. by this Binding Revocation Indication message.
o The mobile access gateway address MAY be used as the source o The mobile access gateway address MAY be used as the source
address in the packet's IPv6 header. address in the packet's IPv6 header.
The Acknowledge (A) bit in the Binding Revocation Indication requests As described in Section 6.3, the mobile access gateway SHOULD
the local mobility anchor to return a Binding Revocation retransmit the Binding Revocation Indication to the local mobility
Acknowledgement in response to this Binding Revocation Indication. anchor until it receives a matching Binding Revocation
As described in Section 6.3, if the Acknowledge (A) bit is set, the Acknowledgement or the BRIMaxRetransmitNumber is reached. The mobile
mobile access gateway SHOULD retransmit this Binding Revocation access gateway MAY delete the mobile nodes IP tunnels immediately
Indication to the local mobility anchor until it receives a matching after sending the Binding Revocation Indication and before receiving
Binding Revocation Acknowledgement or the BRIMaxRetransmitNumber is a Binding Revocation Acknowledgement message from the LMA.
reached. The mobile access gateway MAY delete the mobile nodes IP
tunnels immediately after sending the Binding Revocation Indication
and before receiving a Binding Revocation Acknowledgement message
from the LMA.
9.2.2. Receiving Binding Revocation Acknowledgement
When the mobile access gateway receives a packet carrying a valid
Binding Revocation Acknowledgement that was successfully processed
according to Section 6.2, the mobile access gateway MUST process the
received Binding Revocation Acknowledgement as per the followings:
o When the mobile access gateway receives a packet carrying a valid
Binding Revocation Acknowledgement and the Global (G) and Proxy
Binding (P) bits are set and the mobile nodes BCEs are in the
state of Revocation in Progress, the mobile access gateway SHOULD
examine the Status field as follows:
* If the Status field indicates that the Binding Revocation
Indication was processed successfully, the mobile access
gateway MUST delete the current timer and the mobile nodes
proxy bindings and all associated resources.
* If the Status field indicates (Global Revocation NOT In a response to a Binding Revocation Indication message, if the
Authorized), the mobile access gateway is not authorized to mobile access gateway receives a packet carrying a Binding Revocation
participate in a Per-Peer Global Revocation. The mobile access Acknowledgement that was successfully processed as in Section 6.2 and
gateway SHOULD NOT retry sending a Binding Revocation the Status field indicates (Global Revocation NOT Authorized), the
Indication with the Global (G) bit set and the Revocation mobile access gateway is not authorized to participate in a Per-Peer
Trigger field value set to "Per-Peer Policy" to the same local Global Revocation. The mobile access gateway SHOULD NOT retry
mobility agent. The mobile access gateway should raise an sending a Binding Revocation Indication with the Global (G) bit is
alarm or log an event to indicate this rejection. set and the Revocation Trigger field value is 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.
10. Mobile Node Operation 10. Mobile Node Operation
10.1. Receiving Binding Revocation Indication
Upon receiving a packet carrying a Binding Revocation Indication, the Upon receiving a packet carrying a Binding Revocation Indication, the
mobile node MUST validate the packet according to Section 6.2 and the mobile node MUST validate the packet according to Section 6.2 and the
following tests: following tests:
o The mobile node MUST verify that the IP address in the Type 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 routing header is its Home Address and that its Binding Update
List contains an entry for that Home Address. If one of the List contains an entry for that Home Address. If one of the tests
tests, fails the mobile node SHOULD silently discard the received fails, the mobile node SHOULD silently discard the received
Binding Revocation Indication message. Binding Revocation Indication message.
o If the Acknowledge (A) bit is set in the Binding Revocation o If mobile node Binding Update List contains an entry for the IP
Indication and its Binding Update List contains an entry for the address in the Type 2 routing header of the received Binding
IP address in the Type 2 routing header, the mobile node MUST send Revocation Indication packet, the mobile node MUST accept the BRI
a Binding Revocation Acknowledgement. However, in all other cases message using Status code success.
when the Acknowledge (A) bit is set in the BRI, the mobile node
SHOULD sends a Binding Revocation Acknowledgement, the mobile node
MUST do so according to Section 10.2.
o If the IPv4 HoA Binding Only (V) bit is set in the received 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 message, the mobile node MUST verify that there is an IPv4 Home
Address option in the received Binding Revocation Indication and Address option in the received Binding Revocation Indication and
the IPv4 address included in the IPv4 Home Address option is the 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 same as its IPv4 HoA that is assigned to the mobile node. If this
verification is successful, the mobile node MUST consider this verification is successful, the mobile node MUST consider this
Binding Revocation Indication as an indication to ONLY release the Binding Revocation Indication as an indication to ONLY release the
mobile node IPv4 HoA binding to its current Care-of Address. mobile node IPv4 HoA binding to its current Care-of Address.
Consequently, the mobile node MUST continue to maintain its IPv6 Consequently, the mobile node MUST continue to maintain its IPv6
HoA binding to the current CoA as part of the mobile node binding 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 in the BUL entry and release all resources associated with the MN
IPv4 HoA binding. In this case, if the Acknowledge (A) bit is IPv4 HoA binding. In this case, the mobile node MUST accept the
set, the mobile node MUST send a Binding Revocation Binding Revocation Indication message using Status code success.
Acknowledgement message with the Status field is set to "success".
On the other hand, if the IPv4 Home Address Option was NOT On the other hand, if the IPv4 Home Address Option was NOT
included in the received BRI with the (V) bit set and the included in the received BRI with the (V) bit is set, the MN MUST
Acknowledge (A) bit is set, the MN SHOULD send a Binding reject the BRI message with Status code "IPv4 Home Address Option
Revocation Acknowledgement message with the Status field set to Required". Additionally, if the IPv4 HoA received in the IPv4
"IPv4 Home Address Option Required". Additionally, if the IPv4 Home Address Option is NOT the one assigned to the mobile node,
HoA received in the IPv4 Home Address Option is NOT the one the mobile node SHOULD reject the Binding Revocation Indication
assigned to the mobile node, the mobile node SHOULD send a Binding with Status code "Binding Does NOT Exist".
Revocation Acknowledgement with the status field set to "Binding
Does NOT Exist".
o The mobile node MUST verify that the (P) bit in the Binding 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 Revocation Indication is NOT set. If the (P) bit is set, the
mobile node MUST silently discard the Binding Revocation mobile node MUST reject the Binding Revocation Indication using
Indication message. Status code "Proxy Binding Revocation NOT Supported".
o If the mobile node has registered multiple care-of addresses with o If the mobile node has registered multiple care-of addresses with
its home agent, the mobile node MUST verify which binding is being its home agent, the mobile node MUST verify which binding is being
revoked by examining the content of the Binding Revocation revoked by examining the content of the Binding Revocation
Indication message. If the mobile node received a Binding Indication message. If the mobile node received a Binding
Revocation Indication with a single or more than one BID options Revocation Indication with a single or more than one BID options
and its home address is included in the Type 2 routing header, the and its home address is included in the Type 2 routing header, the
mobile node MUST consider all of the care-of address(es) mobile node MUST consider all of the care-of address(es)
binding(s), identified in the BID options, with this home address binding(s), identified in the BID options, with this home address
as being revoked. 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 If the mobile node has multiple Care-of Address bindings with its o If the mobile node has multiple Care-of Address bindings with its
home agent and received a Binding Revocation Indication, without home agent and received a Binding Revocation Indication, without
any BID option included and its home address was included in the any BID option included and its home address was included in the
Type 2 routing header, the mobile node MUST consider all of its Type 2 routing header, the mobile node MUST consider all of its
registered care-of addresses bindings with this home address as registered care-of addresses bindings with this home address as
being revoked. being revoked. If the mobile node validates the BRI successfully,
the mobile node MUST accept the Binding Revocation Indication
message with Status code success.
If the mobile node accepts or rejects the Binding Revocation
Indication message, the mobile node MUST follow Section 6.1 and
Section 6.1.2 to send a Binding Revocation Acknowledgement message to
the home agent. Note that anytime the MN does not send a Binding
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.
The Revocation Trigger field value in the received Binding Revocation The Revocation Trigger field value in the received Binding Revocation
Indication could be used by the mobile node to define what action the 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 mobile node could do to be able to register again and receive its IP
mobility service, e.g., contacting its home operator. mobility service, e.g., contacting its home operator.
10.2. Sending Binding Revocation Acknowledgement
When the mobile node receives a Binding Revocation Indication from
its home agent, the mobile node processes the received Binding
Revocation Indication as in Section 10.1. If the mobile node is
required to send a Binding Revocation Acknowledgement message in
response to the received Binding Revocation Indication, the mobile
node sends a packet to its home agent containing a Binding Revocation
Acknowledgement according to the procedure in Section 6.1 and the
following:
o The mobile node MUST set the Status field to an appropriate value.
The mobile node sets the Status field to success to reflect that
it has received the Binding Revocation Indication and acknowledge
that its IP connectivity with its home agent has been revoked.
o The destination IP address of the IPv6 packet of the Binding
Revocation Acknowledgement is set to the source IP address of the
received IPv6 packet of the Binding Revocation Indication. The
Mobile Node MUST include its home address in the Home Address
Destination Option.
11. Protocol Configuration Variables 11. Protocol Configuration Variables
Any mobility entity which is allowed to invoke the binding revocation Any mobility entity which is allowed to invoke the binding revocation
procedure by sending a Binding Revocation Indication message SHOULD procedure by sending a Binding Revocation Indication message SHOULD
allow the following variables to be configured. allow the following variables to be configured.
BRI Maximum Number of Retries (BRIMaxRetriesNumber) BRI Maximum Number of Retries (BRIMaxRetriesNumber)
This variable specifies the maximum Number of times a mobility This variable specifies the maximum Number of times a mobility
entity can retransmit a Binding Revocation Indication message entity can retransmit a Binding Revocation Indication message
skipping to change at page 39, line 37 skipping to change at page 35, line 50
All other values are reserved All other values are reserved
Future values of the Binding Revocation Type can be allocated using Future values of the Binding Revocation Type can be allocated using
Standards Action or IESG Approval [RFC5226]. Standards Action or IESG Approval [RFC5226].
In addition, this document also creates a second new registry for the In addition, this document also creates a second new registry for the
Revocation Trigger which indicates the reason behind sending the Revocation Trigger which indicates the reason behind sending the
Binding Revocation Indication message. The current Revocation Binding Revocation Indication message. The current Revocation
Trigger values are described in Section 5.1, and are the following: Trigger values are described in Section 5.1, and are the following:
Reserved and Per-MN Revocation Trigger Values: Per-MN Revocation Trigger Values:
0 Reserved
1 Unspecified 0 Unspecified
2 Administrative Reason 1 Administrative Reason
3 Inter-MAG Handover - same Access Type 2 Inter-MAG Handover - same Access Type
4 Inter-MAG Handover - different Access Type 3 Inter-MAG Handover - different Access Type
5 Inter-MAG Handover - Unknown 4 Inter-MAG Handover - Unknown
6 User Initiated Session(s) Termination 5 User Initiated Session(s) Termination
7 Access Network Session(s) Termination 6 Access Network Session(s) Termination
8 Possible Out-of Sync BCE State 7 Possible Out-of Sync BCE State
250-255 Reserved For Testing Purposes only
All other values are Reserved
Global Revocation Trigger Values: Global Revocation Trigger Values:
128 Per-Peer Policy 128 Per-Peer Policy
129 Revoking Mobility Node Local Policy 129 Revoking Mobility Node Local Policy
Reserved Revocation Trigger Values:
250-255 Reserved For Testing Purposes only
All other values are Reserved
Future values of the Revocation Trigger can be allocated using Future values of the Revocation Trigger can be allocated using
Standards Action or IESG Approval [RFC5226]. Standards Action or IESG Approval [RFC5226].
Furthermore, this document creates a third new registry "Status Code" Furthermore, this document creates a third new registry "Status Code"
for the Status field in the Binding Revocation Acknowledgement for the Status field in the Binding Revocation Acknowledgement
message. The current values are described in Section 5.2, and are message. The current values are described in Section 5.2, and are
the following: the following:
0 success 0 success
1 partial success 1 partial success
128 Binding Does NOT Exist 128 Binding Does NOT Exist
129 IPv4 Home Address Option Required 129 IPv4 Home Address Option Required
130 Global Revocation NOT Authorized 130 Global Revocation NOT Authorized
131 Revoked Mobile Nodes Identity Required 131 Revoked Mobile Nodes Identity Required
132 Revocation Failed - MN is Attached 132 Revocation Failed - MN is Attached
133 Revocation Trigger NOT Supported 133 Revocation Trigger NOT Supported
134 Revocation Function NOT Supported 134 Revocation Function NOT Supported
135 Proxy Binding Revocation NOT Supported
Future values of the Status field can be allocated using Standards Future values of the Status field can be allocated using Standards
Action or IESG Approval [RFC5226]. Action or IESG Approval [RFC5226].
All fields labeled "Reserved" are only to be assigned through All fields labeled "Reserved" are only to be assigned through
Standards Action or IESG Approval. Standards Action or IESG Approval.
13. Security Considerations 13. Security Considerations
This specification allows the mobility node which initiates the This specification allows the mobility node which initiates the
skipping to change at page 41, line 15 skipping to change at page 37, line 26
Binding Update and Binding Acknowledgement (instead of creating new Binding Update and Binding Acknowledgement (instead of creating new
ones) ensures that those SA will be up and running when the revoking ones) ensures that those SA will be up and running when the revoking
entity needs to send a binding revocation signaling message. entity needs to send a binding revocation signaling message.
On the other hand, if IPsec is not used as the underlying security On the other hand, if IPsec is not used as the underlying security
mechanism to protect the Mobile IPv6 and its extensions binding mechanism to protect the Mobile IPv6 and its extensions binding
registration signaling, the used underlying security mechanism MUST registration signaling, the used underlying security mechanism MUST
provide protection against all identified security threats as provide protection against all identified security threats as
described under Security Considerations in [RFC3775] and [RFC5213]. described under Security Considerations in [RFC3775] and [RFC5213].
Since some mobility entities, e.g., local mobility anchor and mobile
access gateway, are allowed to send and receive Binding Revocation
Indication and Binding Revocation Acknowledgement for different
cases, therefore, 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.
The Proxy Mobile IPv6 [RFC5213] requires the local mobility anchor to The Proxy Mobile IPv6 [RFC5213] requires the local mobility anchor to
restrict the creation and manipulation of proxy bindings to restrict the creation and manipulation of proxy bindings to
specifically authorized mobile access gateways. Therefore, the specifically authorized mobile access gateways. Therefore, the
mobile access gateway which is authorized to create or manipulate the mobile access gateway which is authorized to create or manipulate the
mobile node proxy BCE is also authorized to revoke such mobile node mobile node proxy BCE is also authorized to revoke such mobile node
registration by sending a de-registration with lifetime of zero. registration by sending a de-registration with lifetime of zero.
However, since bulk termination using Binding Revocation Indication However, since bulk termination using Binding Revocation Indication
with the Global (G) bit set and the Revocation Trigger field set to with the Global (G) bit set and the Revocation Trigger field set to
"Per-Peer Policy" impacts all mobility sessions that are registered "Per-Peer Policy" impacts all mobility sessions that are registered
with the mobile access gateway and its local mobility anchor peer, with the mobile access gateway and its local mobility anchor peer,
skipping to change at page 41, line 38 skipping to change at page 38, line 13
employed, but these are outside the scope of this specification. employed, but these are outside the scope of this specification.
14. Acknowledgements 14. Acknowledgements
The authors would like to thank Ryuji Wakikawa, Bruno Mongazon- The authors would like to thank Ryuji Wakikawa, Bruno Mongazon-
Cazavet, Domagoj Premec, Arnaud Ebalard, Patrick Stupar, Vijay Cazavet, Domagoj Premec, Arnaud Ebalard, Patrick Stupar, Vijay
Devarapalli, and Joel Hortelius for their review and comments of this Devarapalli, and Joel Hortelius for their review and comments of this
draft and all colleagues who have supported the advancement of this draft and all colleagues who have supported the advancement of this
draft effort. draft effort.
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.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
skipping to change at page 42, line 15 skipping to change at page 38, line 41
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, November 2005. (MIPv6)", RFC 4283, November 2005.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[ID-PMIP6-IPv4] [ID-PMIP6-IPv4]
Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-15 Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-17
(work in progress), August 2009. (work in progress), September 2009.
[ID-MCoA] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami, [ID-MCoA] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami,
"Multiple Care-of Addresses Registration", "Multiple Care-of Addresses Registration",
draft-ietf-monami6-multiplecoa-14 (work in progress), draft-ietf-monami6-multiplecoa-14 (work in progress),
May 2009. May 2009.
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and [RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", RFC 5555, June 2009. Routers", RFC 5555, June 2009.
15.2. Informative References 15.2. Informative References
 End of changes. 120 change blocks. 
680 lines changed or deleted 573 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/