draft-ietf-mext-binding-revocation-13.txt   draft-ietf-mext-binding-revocation-14.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: April 3, 2010 S. Gundavelli Expires: April 29, 2010 S. Gundavelli
Cisco Systems Cisco Systems
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
P. Yegani P. Yegani
Juniper Networks Juniper Networks
September 30, 2009 October 26, 2009
Binding Revocation for IPv6 Mobility Binding Revocation for IPv6 Mobility
draft-ietf-mext-binding-revocation-13.txt draft-ietf-mext-binding-revocation-14.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 April 3, 2010. This Internet-Draft will expire on April 29, 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 41 skipping to change at page 3, line 41
8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 24 8. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 24
8.1. Sending Binding Revocation Indication . . . . . . . . . . 24 8.1. Sending Binding Revocation Indication . . . . . . . . . . 24
8.2. Receiving Binding Revocation Indication . . . . . . . . . 28 8.2. Receiving Binding Revocation Indication . . . . . . . . . 28
9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 30 9. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 30
9.1. Receiving Binding Revocation Indication . . . . . . . . . 30 9.1. Receiving Binding Revocation Indication . . . . . . . . . 30
9.2. Sending Binding Revocation Indication . . . . . . . . . . 32 9.2. Sending Binding Revocation Indication . . . . . . . . . . 32
10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 33 10. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 33
11. Protocol Configuration Variables . . . . . . . . . . . . . . . 34 11. Protocol Configuration Variables . . . . . . . . . . . . . . . 34
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
13. Security Considerations . . . . . . . . . . . . . . . . . . . 36 13. Security Considerations . . . . . . . . . . . . . . . . . . . 36
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 38 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.1. Normative References . . . . . . . . . . . . . . . . . . . 38 15.1. Normative References . . . . . . . . . . . . . . . . . . . 38
15.2. Informative References . . . . . . . . . . . . . . . . . . 39 15.2. Informative References . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
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
skipping to change at page 5, line 39 skipping to change at page 5, line 39
3.1. Binding Revocation Protocol 3.1. Binding Revocation Protocol
In the case of Mobile IPv6, if the home network decides to terminate In the case of Mobile IPv6, if the home network decides to terminate
the service of the mobile node, the home agent sends a Binding the service of the mobile node, the home agent sends a Binding
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 [RFC5648], 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 Indication message with its HoA included in the Type 2 routing
header, the mobile node responds by sending a Binding Revocation header, the mobile node responds by 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
skipping to change at page 7, line 28 skipping to change at page 7, line 28
| | | |
| 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
In the case of multiple care-of addresses registration [ID-MCoA], the In the case of multiple care-of addresses registration [RFC5648], the
home agent maintains different binding for each pair of care-of home agent maintains different binding for each pair of care-of
address and home address. These bindings are also indexed and address and home address. These bindings are also indexed and
identified during the mobile node registration using a BID mobility identified during the mobile node registration using a BID mobility
option. The HA may revoke one or multiple bindings for the same option. The HA may revoke one or multiple bindings for the same
mobile node home address. mobile node home address.
If the home agent revokes a single binding for a mobile node with If the home agent revokes a single binding for a mobile node with
multiple care-of addresses registration, the home agent sends a multiple care-of addresses registration, the home agent sends a
Binding Revocation Indication message to the mobile node with the Binding Revocation Indication message to the mobile node with the
corresponding BID option included. If more than one of the mobile corresponding BID option included. If more than one of the mobile
skipping to change at page 15, line 48 skipping to change at page 15, line 48
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 [RFC5648]. This option MUST be
present if the initiator requests to terminate one binding of a present if the initiator requests to terminate one binding of a
multiple care-of addresses bindings for the same mobile node. The multiple care-of addresses bindings for the same mobile node. The
initiator may include more than one of the BID mobility options. initiator may include more than 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]. According to
MAY be included to indicate the Care-of Address of the mobile [RFC5213], the mobile access gateway is allowed to include this
option in the Proxy Binding Update to indicate the proxy Care-of
address of the mobile node mobility session. This option MAY be
included to indicate the proxy Care-of address of the mobile
node's binding that is being revoked. In the case when the Global node's binding that is being revoked. In the case when the Global
(G) bit is set, this option identifies all 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 proxy care-of address.
bit is set, more than one Alternate Care-of Address mobility
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
skipping to change at page 18, line 29 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]. The responder MAY o Binding Identifier mobility option [RFC5648]. The responder MAY
include this option to indicate the specific BID that failed the include this option to indicate the specific BID that failed the
revocation procedure. 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
skipping to change at page 23, line 15 skipping to change at page 23, line 15
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
destination address in the packet's IPv6 header, unless an destination address in the packet's IPv6 header.
Alternate Care-of Address mobility option is included in the
Binding Revocation Indication. If an Alternate Care-of Address
option is included in the Binding Revocation Indication message,
the destination address in the packet's IPv6 header SHOULD be set
to the source IP address of the packet that carried the latest
successful Binding Update with the Alternate Care-of address
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.
When the home agent sends a Binding Revocation Indication to the When the home agent sends a Binding Revocation Indication to the
mobile node, the home agent sets a flag in the mobile node BCE to mobile node, the home agent sets a flag in the mobile node BCE to
indicate that revocation is in progress and starts the indicate that revocation is in progress and starts the
InitMINDelayBRIs timer. The home agent maintains the mobile node BCE InitMINDelayBRIs timer. The home agent maintains the mobile node BCE
skipping to change at page 23, line 47 skipping to change at page 23, line 40
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 [RFC5648], 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.
When the home agent receives a packet carrying a valid Binding When the home agent receives a packet carrying a valid Binding
Revocation Acknowledgement message, the home agent follows Revocation Acknowledgement message, the home agent follows
Section 6.2 in processing this message. Section 6.2 in processing this message.
8. Local Mobility Anchor Operation 8. Local Mobility Anchor Operation
skipping to change at page 24, line 47 skipping to change at page 24, line 43
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 local mobility o In case of revoking all Per-Peer bindings, the local mobility
anchor MUST set the Global (G) bit and the Revocation Trigger MUST anchor MUST set the Global (G) bit and the Revocation Trigger MUST
contain the value "Per-Peer Policy" to request the mobile access contain the value "Per-Peer Policy" to request the mobile access
gateway to remove all Per-Peer bindings that are registered with gateway to remove all Per-Peer bindings that are registered with
the local mobility anchor and this mobile access gateway. the local mobility anchor and this mobile access gateway.
o The care-of address for the binding MUST be used as the o The proxy 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. However, in the case
Alternate Care-of Address mobility option is included in the when IPsec is used to protect the Proxy MIPv6 signaling as
Binding Revocation Indication message. If an Alternate Care-of specified in [RFC5213], the destination address MUST be set to the
Address option is included in the Binding Revocation Indication mag_address that is being used for keying the IPsec SA. If the
message, the destination address in the packet's IPv6 header mag_address is different than the mobile node proxy Care-of
SHOULD be set to the source IP address of the packet that carried address, the Alternate Care-of address option MUST be included and
the latest successful Proxy Binding Update with the Alternate MUST contain the mobile node proxy Care-of address.
Care-of address included.
The local mobility anchor MAY delete the mobile node(s) IP tunnel The local mobility anchor MAY delete the mobile node(s) IP tunnel
immediately after sending the initial Binding Revocation Indication immediately after sending the initial Binding Revocation Indication
and before receiving the Binding Revocation Acknowledgement message. 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, the local to the mobile access gateway to remove a specific binding, the local
mobility anchor sets a flag in the mobile node proxy BCE to indicate mobility anchor sets a flag in the mobile node proxy BCE to indicate
that revocation is in progress and starts the InitMINDelayBRIs timer. that revocation is in progress and starts the InitMINDelayBRIs timer.
The local mobility anchor SHOULD maintain the mobile node proxy BCE The local mobility anchor SHOULD maintain the mobile node proxy BCE
skipping to change at page 28, line 52 skipping to change at page 28, line 45
Trigger field is set to "Per-Peer Policy", but the MN-ID option is Trigger field is set to "Per-Peer Policy", but the MN-ID option is
not included, the local mobility anchor MUST reject the Binding not included, the local mobility anchor MUST reject the Binding
Revocation Indication message using Status code (Global Revocation Revocation Indication message using Status code (Global Revocation
NOT Authorized). 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 Alternate Care-of Address option is
options are included in addition to the mobile node identifier included in addition to the mobile node identifier option, the
option, the local mobility anchor MUST revoke all mobile nodes local mobility anchor MUST revoke all mobile nodes bindings which
bindings which proxy Care-of Address matches one of the Care-of proxy Care-of Address matches the Care-of address in the Alternate
address(es) in the Alternate Care-of Address option(s). After the Care-of Address option. After the local mobility anchor
local mobility anchor successfully processes the Binding successfully processes the Binding Revocation Indication message
Revocation Indication message and identifies all impacted mobile and identifies all impacted mobile nodes bindings, it MUST accept
nodes bindings, it MUST accept the Binding Revocation Indication the Binding Revocation Indication message using the Status code
message using the Status code success. success.
o If the local mobility anchor accepted the Binding Revocation o If the local mobility anchor accepted the Binding Revocation
Indication message but one or more of the bindings identified in Indication message but one or more of the bindings identified in
the received Binding Revocation Indication message has already the received Binding Revocation Indication message has already
been released, the local mobility anchor MUST accept the message been released, the local mobility anchor MUST accept the message
and it MAY set the Status field to (partial success) and include and it MAY set the Status field to (partial success) and include
the mobile node identifier, MN-ID, or the Home Network Prefix the mobile node identifier, MN-ID, or the Home Network Prefix
option to identify the binding(s) that failed the revocation option to identify the binding(s) that failed the revocation
procedure. procedure.
skipping to change at page 32, line 33 skipping to change at page 32, line 27
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 the 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 the Alternate Care-of Address option.
option(s). The Alternate Care-of Address option(s) contain the If included, the Alternate Care-of Address option MUST contain the
proxy Care-of address(es) the bindings of which are being impacted proxy Care-of address the bindings of which are being impacted by
by this Binding Revocation Indication message. 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.
As described in Section 6.3, the mobile access gateway SHOULD As described in Section 6.3, the mobile access gateway SHOULD
retransmit the Binding Revocation Indication to the local mobility retransmit the Binding Revocation Indication to the local mobility
anchor until it receives a matching Binding Revocation anchor until it receives a matching Binding Revocation
Acknowledgement or the BRIMaxRetransmitNumber is reached. The mobile Acknowledgement or the BRIMaxRetransmitNumber is reached. The mobile
access gateway MAY delete the mobile nodes IP tunnels immediately access gateway MAY delete the mobile nodes IP tunnels immediately
after sending the Binding Revocation Indication and before receiving after sending the Binding Revocation Indication and before receiving
skipping to change at page 35, line 16 skipping to change at page 35, line 9
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
before receiving a Binding Revocation Acknowledgement message. before receiving a Binding Revocation Acknowledgement message.
The default value for this parameter is 1. The default value for this parameter is 1.
Initial Minimum Delay Between BRI messages (InitMINDelayBRIs) Initial Minimum Delay Between BRI messages (InitMINDelayBRIs)
This variable specifies the initial delay timeout in seconds This variable specifies the initial delay timeout in seconds
before the revoking mobility entity retransmits a BRI message. before the revoking mobility entity retransmits a BRI message.
The default is 1 second but not less than 0.5 seconds. The default is 1 second but not to be configured less than 0.5
seconds.
Maximum BRA TIMEOUT (MAX_BRACK_TIMEOUT) Maximum BRA TIMEOUT (MAX_BRACK_TIMEOUT)
This variable specifies the maximum delay timeout in seconds This variable specifies the maximum delay timeout in seconds
before the revoking mobility entity retransmits a BRI message. before the revoking mobility entity retransmits a BRI message.
The default is 2 seconds. The default is 2 seconds.
12. IANA Considerations 12. IANA Considerations
This specification defines a new Binding Revocation Message using a This specification defines a new Binding Revocation Message using a
skipping to change at page 38, line 44 skipping to change at page 38, line 38
(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-17 Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-17
(work in progress), September 2009. (work in progress), September 2009.
[ID-MCoA] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami, [RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T.,
"Multiple Care-of Addresses Registration", and K. Nagami, "Multiple Care-of Addresses Registration",
draft-ietf-monami6-multiplecoa-14 (work in progress), RFC 5648, October 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
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
[RFC3543] Glass, S. and M. Chandra, "Registration Revocation in [RFC3543] Glass, S. and M. Chandra, "Registration Revocation in
 End of changes. 19 change blocks. 
52 lines changed or deleted 44 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/