draft-ietf-mext-binding-revocation-01.txt   draft-ietf-mext-binding-revocation-02.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 1, 2009 S. Gundavelli Expires: May 29, 2009 S. Gundavelli
Cisco Systems Cisco Systems
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
P. Yegani P. Yegani
Cisco Systems Juniper Networks
August 28, 2008 November 25, 2008
Binding Revocation for IPv6 Mobility Binding Revocation for IPv6 Mobility
draft-ietf-mext-binding-revocation-01.txt draft-ietf-mext-binding-revocation-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 1, 2009. This Internet-Draft will expire on May 29, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines the revocation semantics for terminating a This document defines the revocation semantics for terminating a
mobile node's mobility session and associated resources. These mobile node's mobility session and 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
skipping to change at page 3, line 4 skipping to change at page 3, line 4
9.1.1. Sending Binding Revocation Indication . . . . . . . . 20 9.1.1. Sending Binding Revocation Indication . . . . . . . . 20
9.1.2. Receiving Binding Revocation Acknowledgement . . . . . 23 9.1.2. Receiving Binding Revocation Acknowledgement . . . . . 23
9.2. Binding Revocation Responder . . . . . . . . . . . . . . . 23 9.2. Binding Revocation Responder . . . . . . . . . . . . . . . 23
9.2.1. Receiving Binding Revocation Indication . . . . . . . 23 9.2.1. Receiving Binding Revocation Indication . . . . . . . 23
9.2.2. Sending Binding Revocation Acknowledgement . . . . . . 24 9.2.2. Sending Binding Revocation Acknowledgement . . . . . . 24
10. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 25 10. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 25
10.1. Binding Revocation Responder . . . . . . . . . . . . . . . 25 10.1. Binding Revocation Responder . . . . . . . . . . . . . . . 25
10.1.1. Receiving Binding Revocation Indication . . . . . . . 25 10.1.1. Receiving Binding Revocation Indication . . . . . . . 25
10.1.2. Sending Binding Revocation Acknowledgement . . . . . . 27 10.1.2. Sending Binding Revocation Acknowledgement . . . . . . 27
10.2. Binding Revocation Initiator . . . . . . . . . . . . . . . 27 10.2. Binding Revocation Initiator . . . . . . . . . . . . . . . 27
10.2.1. Sending Binding Revocation Indication . . . . . . . . 27 10.2.1. Sending Binding Revocation Indication . . . . . . . . 28
10.2.2. Receiving Binding Revocation Acknowledgement . . . . . 28 10.2.2. Receiving Binding Revocation Acknowledgement . . . . . 28
11. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 29 11. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 29
11.1. Receiving Binding Revocation Indication . . . . . . . . . 29 11.1. Receiving Binding Revocation Indication . . . . . . . . . 29
11.2. Sending Binding Revocation Acknowledgement . . . . . . . . 30 11.2. Sending Binding Revocation Acknowledgement . . . . . . . . 30
12. Protocol Configuration Variables . . . . . . . . . . . . . . . 30 12. Protocol Configuration Variables . . . . . . . . . . . . . . . 31
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
14. Security Considerations . . . . . . . . . . . . . . . . . . . 31 14. Security Considerations . . . . . . . . . . . . . . . . . . . 31
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
16.1. Normative References . . . . . . . . . . . . . . . . . . . 32 16.1. Normative References . . . . . . . . . . . . . . . . . . . 32
16.2. Informative References . . . . . . . . . . . . . . . . . . 32 16.2. Informative References . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . . . 34 Intellectual Property and Copyright Statements . . . . . . . . . . 34
1. Introduction 1. Introduction
skipping to change at page 6, line 19 skipping to change at page 6, line 19
Binding revocation mechanism is applicable to Client Mobile IPv6 and Binding revocation mechanism is applicable to Client Mobile IPv6 and
DSMIPv6 session(s) when the home agent needs to inform the mobile DSMIPv6 session(s) when the home agent needs to inform the mobile
node that its binding registration has been revoked, e.g. for an node that its binding registration has been revoked, e.g. for an
administrative reason. This mechanism enables the home domain to administrative reason. This mechanism enables the home domain to
dynamically allow the user to act upon the revocation message in dynamically allow the user to act upon the revocation message in
order to not have an unexpectedly interrupted mobile IPv6 services. order to not have an unexpectedly interrupted mobile IPv6 services.
In this case, the home agent sends a BRI message to indicate to the In this case, the home agent sends a BRI message to indicate to the
mobile node that its current mobile IPv6 binding has been revoked and mobile node that its current mobile IPv6 binding has been revoked and
it no longer can receive IP mobility service. The home agent it no longer can receive IP mobility service. The home agent
includes the mobile node home address in HoA option in the includes the mobile node home address in Type 2 header as used in
destination option header as used in [RFC3775] and sets the [RFC3775] and sets the Revocation Trigger field to a proper value,
Revocation Trigger field to a proper value, e.g. Administrative e.g. Administrative Reason. In the case of DSMIPv6 session, the
Reason. In the case of DSMIPv6 session, the home agent may home agent may additionally include the mobile node assigned IPv4
additionally include the mobile node assigned IPv4 Home Address Home Address Option. When the mobile node receives the BRI message,
Option. When the mobile node receives the BRI message, it sends a it sends a BRA message as described in Section 11.2 to the home
BRA message as described in Section 11.2 to the home agent. Figure 1 agent. Figure 1 illustrates the message sequencing when home agent
illustrates the message sequencing when home agent revokes a mobile revokes a mobile node binding registration.
node binding registration.
MN HA MN HA
| | | |
| HoA in Dest. Opt. Hdr + BRI[seq.#, A bit] | | HoA in Type 2 Hdr + BRI [seq.#, A bit] |
|<------------------------------------------| |<------------------------------------------|
| | | |
| | | |
| | | |
| BRA[seq.#] | | HoA in Destination Option BRA[seq.#] |
|------------------------------------------>| |------------------------------------------>|
| | | |
| | | |
Figure 1: Home Agent Revokes a Mobile Node Binding Registration Figure 1: Home Agent Revokes a Mobile Node Binding Registration
3.3. Multi-Care of Addresses (Monami6) Use Case 3.3. Multi-Care of Addresses (Monami6) Use Case
In the case of Monami6 protocol, a mobile node is able to register In the case of Monami6 protocol, a mobile node is able to register
multiple care-of addresses for the same home address [ID-MCoA]. multiple care-of addresses for the same home address [ID-MCoA].
skipping to change at page 7, line 25 skipping to change at page 7, line 25
In the case of multiple care-of addresses, the home agent maintains In the case of multiple care-of addresses, the home agent maintains
different binding for each pair of care-of address and home address. different binding for each pair of care-of address and home address.
These bindings are also indexed and identified during the mobile node These bindings are also indexed and identified during the mobile node
registration using a Binding ID mobility option [ID-MCoA]. In this registration using a Binding ID mobility option [ID-MCoA]. In this
case, the HA may revoke any binding, more than one binding, or all of case, the HA may revoke any binding, more than one binding, or all of
the bindings for the same mobile node home address. the bindings for the same mobile node home address.
In the case when home agent revokes a single binding for a mobile In the case when home agent revokes a single binding for a mobile
node with multiple care-of addresses registration, the home agent node with multiple care-of addresses registration, the home agent
sends a BRI message to the mobile node with the corresponding BID sends a BRI message to the mobile node with the corresponding BID
option included and the HoA option in the destination option header. option included and the HoA is in the Type 2 header. If the home
If the home agent needs to revoke more than one of the mobile node agent needs to revoke more than one of the mobile node registered
registered care-of addresses, the home agent includes all the care-of addresses, the home agent includes all the corresponding
corresponding BID options which reference these care-of addresses in Binding ID options which reference these care-of addresses in the
the same BRI message. Figure 2 illustrates the message flow when the same BRI message. Figure 2 illustrates the message flow when the HA
HA revokes two registered Care-of addresses for the same MN in a revokes two registered Care-of addresses for the same MN in a single
single BRI message. The home agent can revoke any registered BRI message. The home agent can revoke any registered binding(s) by
binding(s) by sending a BRI message to the respective mobile node. sending a BRI message to the respective mobile node.
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]
| BRI [seq.#, A bit, BID1, BID4 options] | MN-BID4 [CoA4+HoA] | BRI [seq.#, A bit, BID1, BID4 options] | MN-BID4 [CoA4+HoA]
|<------------------------------------------| |<------------------------------------------|
| | | |
| | | |
| | | |
| BRA [seq.#, Cause] | | BRA [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
3.3.2. Termination of All Care-of Addresses Bindings 3.3.2. Termination of All Care-of Addresses Bindings
The home agent may revoke all of the mobile node registered bindings, The home agent may revoke all of the mobile node registered bindings,
by sending a BRI message without including any BID options while the by sending a BRI message without including any BID options while the
HoA option is included in the destination options header. Figure 1 HoA is included in the Type 2 header. Figure 1 illustrates the
illustrates the message flow when the home agent revokes all message flow when the home agent revokes all registered Care-of
registered Care-of addresses bindings for a MN in a single BRI addresses bindings for a MN in a single BRI message.
message.
3.4. Proxy MIPv6 Use Case 3.4. Proxy MIPv6 Use Case
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 Binding in the case of PMIPv6, there are many scenarios where 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, e.g. MAG and LMA, are always synchronized the mobility entities, e.g. MAG and LMA, are always synchronized
with respect to the status of the existing proxy mobile IPv6 with respect to the status of the existing proxy mobile IPv6
bindings. The binding revocation mechanism is generic enough that bindings. The binding revocation mechanism is generic enough that
can be used in all applicable PMIPv6 scenarios and deployment can be used in all applicable PMIPv6 scenarios and deployment
skipping to change at page 9, line 36 skipping to change at page 9, line 35
| | PBA | | | PBA |
| |<---------------------------| | |<---------------------------|
| | | | | |
| | | | | |
| BRI [seq.#, R. Trigger, P, A bits, NAI] | | BRI [seq.#, R. Trigger, P, A bits, NAI] |
|<-----------------------------------------| |<-----------------------------------------|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| BRA [seq.#, Cause, P bit] | | BRA [seq.#, Status, P bit] |
|----------------------------------------->| |----------------------------------------->|
| | | | | |
| | | | | |
Figure 3: LMA Revokes a MN Registration During Inter-MAG Handoff Figure 3: LMA Revokes a MN Registration During Inter-MAG Handoff
3.4.2. Local Mobility Anchor Revokes Bulk PMIPv6 Bindings 3.4.2. Local Mobility Anchor Revokes Bulk PMIPv6 Bindings
The LMA sends a BRI message to indicate that all bindings which are The LMA sends a BRI message to indicate that all bindings which are
hosted by the peer MAG and registered with the LMA are being revoked hosted by the peer MAG and registered with the LMA are being revoked
skipping to change at page 10, line 34 skipping to change at page 10, line 34
Additionally, in the case when the LMA receives a BRI which indicates Additionally, in the case when the LMA receives a BRI which indicates
a bulk termination, i.e., the (G) bit is set, the LMA MUST verify a bulk termination, i.e., the (G) bit is set, the LMA MUST verify
that the MAG sending the binding revocation indication message is that the MAG sending the binding revocation indication message is
authorized to invoke Global revocation. authorized to invoke Global revocation.
5. Exchanging Binding Revocation Messages over an IPv4 Transport 5. Exchanging Binding Revocation Messages over an IPv4 Transport
Network Network
In some deployments, the network between the MAG and the LMA may only In some deployments, the network between the MAG and the LMA may only
supports IPv4 transport. In this case, the Binding Revocation support IPv4 transport. In this case, the Binding Revocation
messages (BRI and BRA) are tunneled over IPv4. If the Proxy Binding messages (BRI and BRA) are tunneled over IPv4. If the Proxy Binding
Update and Proxy Binding Acknowledgment messages are sent using UDP Update and Proxy Binding Acknowledgment messages are sent using UDP
encapsulation to traverse NATs, then the Binding Revocation messages encapsulation to traverse NATs, then the Binding Revocation messages
are sent using the same UDP encapsulation. The same UDP port that are sent using the same UDP encapsulation. The same UDP port that
was used for the Proxy Binding Update and Proxy Binding was used for the Proxy Binding Update and Proxy Binding
Acknowledgement messages will also be used when transporting Binding Acknowledgement messages will also be used when transporting Binding
Revocation messages over IPv4 using UDP encapsulation. For more Revocation messages over IPv4 using UDP encapsulation. For more
details on tunneling Proxy Mobile IPv6 signaling messages over IPv4, details on tunneling Proxy Mobile IPv6 signaling messages over IPv4,
see [ID-PMIP6-IPv4]. see [ID-PMIP6-IPv4].
skipping to change at page 13, line 11 skipping to change at page 13, line 11
1 Unspecified. 1 Unspecified.
2 Administrative Reason. 2 Administrative Reason.
3 Inter-MAG Handoff - same Access Types. 3 Inter-MAG Handoff - same Access Types.
4 Inter-MAG Handoff - different Access Types. 4 Inter-MAG Handoff - different Access Types.
5 Inter-MAG - Unknown Handoff. 5 Inter-MAG - Unknown Handoff.
6 Per-Peer Policy. 6 Per-Peer Policy.
7 Revoking Node Local Policy. 7 Revoking Node Local Policy.
8 User Initiated Session(s) Termination. 8 User Initiated Session(s) Termination.
9 Access Network Session(s) Termination. 9 Access Network Session(s) Termination.
10 Possible Out-of Sync BCE State. 10 IPv4 HoA Binding ONLY.
11 Possible Out-of Sync BCE State.
250-255 Reserved For Testing Purposes only. 250-255 Reserved For Testing Purposes only.
All other values are Reserved. 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 sending mobility node to
match a returned Binding Revocation Acknowledgement with this match a returned Binding Revocation Acknowledgement with this
Binding Revocation Indication. Binding Revocation Indication.
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 sending mobility node to
indicate that the revoked binding is a proxy MIPv6 binding. indicate that the revoked binding(s) is a proxy MIPv6 binding.
Acknowledge (A) Acknowledge (A)
The Acknowledge (A) bit is set by the sending mobility node, e.g. The Acknowledge (A) bit is set by the sending mobility node, e.g.
LMA, HA, or MAG, to request a Binding Revocation Acknowledgement LMA, HA, or MAG, to request a Binding Revocation Acknowledgement
be returned upon receipt of the Binding Revocation Indication as be returned upon receipt of the Binding Revocation Indication as
in Section 8.1, Section 9.1.1, and Section 10.2.1. in Section 8.1, Section 9.1.1, and Section 10.2.1.
Global (G) Global (G)
skipping to change at page 14, line 10 skipping to change at page 14, line 11
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 receiving mobility entity to identify
the specific binding or bindings that the sending mobility entity the specific binding or bindings that the sending mobility entity
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 is mandatory o Home Network Prefix option [RFC5213]. This option MAY be used
when the (P) bit is set. when the (P) bit is set. This option MUST be present when the BRI
is used to revoke a single PMIP binding cache entry.
o Mobile Node Identifier Option [RFC4283]. This option is mandatory o Mobile Node Identifier Option [RFC4283]. This option is mandatory
when the (P) bit is set. Additionally, If the (G) bit is set by when the (P) bit is set. Additionally, If the (G) bit is set by
the mobile access gateway, this option carries the MAG identity. the mobile access gateway, this option carries the MAG identity.
o Binding ID mobility option [ID-MCoA]. This option is mandatory if o Binding ID mobility option [ID-MCoA]. This option is mandatory if
the sending mobility entity request to terminate one binding of a the sending mobility entity request to terminate one binding of a
multi care-of addresses bindings for the same mobile node. The multi care-of addresses bindings for the same mobile node. The
sending mobility entity may include more than one of the BID sending mobility entity may include more than one of the Binding
mobility options. ID 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 [ID-DSMIP6]. address [ID-DSMIP6].
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.2. Binding Revocation Acknowledgement Message 6.2. Binding Revocation Acknowledgement Message
skipping to change at page 16, line 27 skipping to change at page 16, line 27
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. In the case contains zero or more TLV-encoded mobility options. In the case
when the Status field is set to success, no mobility option is when the Status field is set to success, no mobility option is
required. The mobility option(s) is usually used to communicate required. The mobility option(s) is usually used to communicate
information of the bindings that failed the revocation procedure. information of the bindings that failed the revocation procedure.
The following options are valid in a Binding Revocation The following options are valid in a Binding Revocation
Acknowledgement: Acknowledgement:
o Home Network Prefix option [RFC5213]. This option is mandatory o Home Network Prefix option [RFC5213]. This option MAY be included
when the P bit is set. when the (P) bit is set.
o Mobile Node Identifier Option [RFC4283]. This option SHOULD be o Mobile Node Identifier Option [RFC4283]. This option MAY be
included if the Home Network Prefix option is included. included when the (P) bit is set. This option SHOULD be included
if the Home Network Prefix option is included.
o Binding ID mobility option [ID-MCoA]. This option MAY be included o Binding ID mobility option [ID-MCoA]. This option MAY be included
to indicate the specific Binding ID that the receiving node failed to indicate the specific Binding ID that the receiving node failed
to revoke. to revoke.
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.
7. Binding Revocation Process Considerations 7. Binding Revocation Process Considerations
skipping to change at page 19, line 11 skipping to change at page 19, line 11
o The Acknowledge (A) bit MAY be set in the BRI to request the o The Acknowledge (A) bit MAY be set in the BRI to request the
mobile node to send a Binding Revocation Acknowledgement upon mobile node to send a Binding Revocation Acknowledgement upon
receipt of the BRI. receipt of the BRI.
o The Revocation Trigger field MUST be set in the Binding Revocation o The Revocation Trigger field MUST be set in the Binding Revocation
Indication to indicate to the mobile node the reason for revoking Indication to indicate to the mobile node the reason for revoking
its IP mobility binding with the home agent. The Revocation its IP mobility binding with the home agent. The Revocation
Trigger may be used by the mobile node to take further steps if Trigger may be used by the mobile node to take further steps if
necessary. necessary.
o The packet MUST contain a Home Address destination option, which o The Binding Revocation Indication MUST be sent using a type 2
contains the mobile node's registered home address for the binding routing header which contains the mobile node's registered home
being revoked. address for the binding being revoked.
o The care-of address for the binding MUST be used as the Source o The care-of address for the binding MUST be used as the
Address in the packet's IPv6 header, unless an Alternate Care-of destination address in the packet's IPv6 header, unless an
Address mobility option is included in the Binding Revocation Alternate Care-of Address mobility option is included in the
Indication. Binding Revocation Indication.
o The packet MAY contain a Home Address option which contains the o The packet MAY contain an IPv4 Home Address option which contains
mobile node's registered IPv4 home address for the binding being the mobile node's registered IPv4 home address for the binding
revoked. being revoked.
The Acknowledge (A) bit in the Binding Revocation Indication requests The Acknowledge (A) bit in the Binding Revocation Indication requests
the mobile node to return a Binding Revocation Acknowledgement in the mobile node to return a Binding Revocation Acknowledgement in
response to this Binding Revocation Indication. As described in response to this Binding Revocation Indication. As described in
Section 7.3, the home agent SHOULD retransmit this Binding Revocation Section 7.3, the home agent SHOULD retransmit this Binding Revocation
Indication to the mobile node before terminating its IP connection Indication to the mobile node before terminating its IP connection
until it receives a matching Binding Revocation Acknowledgement or until it receives a matching Binding Revocation Acknowledgement or
the BRIMaxRetransmitNumber has been reached. the BRIMaxRetransmitNumber has been reached.
When the home agent send a BRI to the mobile node, the home agent When the home agent send a BRI to the mobile node with the (A) bit is
sets a flag in the mobile node BCE to indicate that revocation is in set, the home agent sets a flag in the mobile node BCE to indicate
progress and starts the MINDelayBRIs timer. The home agent maintain that revocation is in progress and starts the MINDelayBRIs timer.
the mobile node BCE in this state until it receives a Binding The home agent maintains the mobile node BCE in this state until it
Revocation Acknowledgement or the BRIMaxRetransmitNumber is reached. receives a Binding Revocation Acknowledgement or the
BRIMaxRetransmitNumber is reached.
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 Multi Care-of address registration bindings that were created using Multi Care-of address registration
as in [ID-MCoA], the home agent MUST use the mobile node home address as in [ID-MCoA], the home agent MUST include all the related Binding
in the Home Address destination option and include all the related ID options that identify these bindings in the Binding Revocation
Binding ID options that identify these bindings. In the case when Indication message. In the case when the home agent needs to revoke
the home agent needs to revoke all of the mobile node bindings, the all of the mobile node bindings, the home agent MUST NOT include any
home agent MUST use the mobile node home address in the Home Address of the Binding ID options.
destination option and MUST NOT include any Binding ID option.
The home agent MUST use the IPsec security association that has been The home agent MUST use the IPsec security association that has been
used during the MIPv6 binding registration with the HA to secure the used during the MIPv6 binding registration with the HA to secure the
BRI and BRA messages transmission with the mobile node. BRI and BRA messages transmission with the mobile node.
8.2. Receiving Binding Revocation Acknowledgement 8.2. Receiving Binding Revocation Acknowledgement
When the home agent receives a packet carrying a valid BRA that was When the home agent receives a packet carrying a valid BRA that was
successfully processed as in Section 7.2, the home SHOULD examine the successfully processed as in Section 7.2, the home agent SHOULD
Status field as follows: examine the Status field as follows:
o If the Status field indicates that the Binding Revocation o If the Status field indicates that the Binding Revocation
Indication was processed successfully, the home agent delete the Indication was processed successfully, the home agent deletes the
MINDelayBRIs timer and the mobile node bindings and all related MINDelayBRIs timer and the mobile node bindings and all related
resources. resources.
o If the Status field indicates any value other than success, the o If the Status field indicates any value other than success, the
home agent SHOULD examine any mobility options included in the home agent SHOULD examine any mobility options included in the
Binding Revocation Acknowledgement. The home agent MAY log the Binding Revocation Acknowledgement. The home agent MAY log the
appropriate event to reflect the status of the received BRA. appropriate event to reflect the status of the received BRA.
9. Local Mobility Anchor Operation 9. Local Mobility Anchor Operation
skipping to change at page 21, line 11 skipping to change at page 21, line 11
o The Proxy Mobile IP (P) bit MUST be set in the BRI message to o The Proxy Mobile IP (P) bit MUST be set in the BRI message to
indicate that the binding being revoked is a proxy Mobile IPv6 indicate that the binding being revoked is a proxy Mobile IPv6
binding. binding.
o The Revocation Trigger field MUST be set in the Binding Revocation o The Revocation Trigger field MUST be set in the Binding Revocation
Indication to indicate to the mobile access gateway the reason for Indication to indicate to the mobile access gateway the reason for
removing the specified mobile node proxy mobile IPv6 binding at removing the specified mobile node proxy mobile IPv6 binding at
the LMA. The Revocation Trigger may be used by the mobile access the LMA. The Revocation Trigger may be used by the mobile access
gateway node to learn the mobile node latest movement. gateway node to learn the mobile node latest movement.
o The Global (G) bit MUST be set and the Revocation Trigger MUST o In case of revoking all Per-Peer bindings, the Global (G) bit MUST
contain a value of "Per-Peer Policy" in the Binding Revocation be set and the Revocation Trigger MUST contain a value of "Per-
Indication to request the mobile access gateway to remove all Per- Peer Policy" in the Binding Revocation Indication to request the
Peer bindings that are registered with the LMA and hosted at this mobile access gateway to remove all Per-Peer bindings that are
MAG. registered with the LMA and hosted at this MAG.
o Whenever the Global (G) bit is set in the BRI, the Acknowledge (A) o Whenever the Global (G) bit is set in the BRI, the Acknowledge (A)
bit MUST be set to request the mobile access gateway to send a bit MUST be set to request the mobile access gateway to send a
Binding Revocation Acknowledgement upon receipt of the BRI. Binding Revocation Acknowledgement upon receipt of the BRI.
o The packet MUST contain the Mobile Node Identifier, MN-ID, option o The packet MUST contain the Mobile Node Identifier, MN-ID, option
which contains the mobile node's NAI that was used in the proxy which contains the mobile node's NAI that was used in the proxy
Binding Update during the mobile node registration. Binding Update during the mobile node registration.
o The packet MUST contain a Home Network Prefix option, which o The packet MUST contain a Home Network Prefix option, which
contains the mobile node's registered HNP for the binding being contains the mobile node's registered HNP for the binding being
revoked. revoked.
o The care-of address for the binding MAY be used as the Source o The care-of address for the binding MAY be used as the destination
Address in the packet's IPv6 header, unless an Alternate Care-of address in the packet's IPv6 header, unless an Alternate Care-of
Address mobility option is included in the Binding Revocation Address mobility option is included in the Binding Revocation
Indication message. Indication message.
The Acknowledge (A) bit in the Binding Revocation Indication requests The Acknowledge (A) bit in the Binding Revocation Indication requests
the mobile access gateway to return a Binding Revocation the mobile access gateway to return a Binding Revocation
Acknowledgement in response to this Binding Revocation Indication. Acknowledgement in response to this Binding Revocation Indication.
As described in Section 7.3, the LMA SHOULD retransmit this BRI to As described in Section 7.3, the LMA SHOULD retransmit this BRI to
the MAG before deleting the mobile node IP tunnel to the mobile the MAG before deleting the mobile node IP tunnel to the mobile
access gateway until it receives a matching Binding Revocation access gateway until it receives a matching Binding Revocation
Acknowledgement or the BRIMaxRetransmitNumber is reached. The local Acknowledgement or the BRIMaxRetransmitNumber is reached. The local
mobility anchor MAY delete the mobile node(s) IP tunnel immediately mobility anchor MAY delete the mobile node(s) IP tunnel immediately
after sending the Binding Revocation Indication and before receiving after sending the Binding Revocation Indication and before receiving
the BRA message. the BRA message.
When the local mobility anchor send 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 MINDelayBRIs timer. that revocation is in progress and starts the MINDelayBRIs timer.
The local mobility anchor SHOULD maintain the mobile node proxy BCE The local mobility anchor SHOULD maintain the mobile node proxy BCE
in this state until it receives a Binding Revocation Acknowledgement in this state until it receives a Binding Revocation Acknowledgement
or the BRIMaxRetransmitNumber is reached. In the case when the local or the 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
indicate inter-MAG handover, the local mobility anchor MAY switch the indicate inter-MAG handover, the local mobility anchor MAY switch the
mobile node IP tunnel to the target mobile access gateway before mobile node IP tunnel to the target mobile access gateway before
sending a Binding Revocation Indication to the sources mobile access sending a Binding Revocation Indication to the sources mobile access
skipping to change at page 22, line 41 skipping to change at page 22, line 41
gateway to remove all bindings of the specified mobile node NAI in gateway to remove all bindings of the specified mobile node NAI in
the MN-ID option. the MN-ID option.
When the mobile node is registered with an IPv4 proxy home address in When the mobile node is registered with an IPv4 proxy home address in
addition to the Home Network Prefix where both of the IPv4 pHoA and addition to the Home Network Prefix where both of the IPv4 pHoA and
HNP are bound to the same proxy CoA, the local mobility anchor MAY HNP are bound to the same proxy CoA, the local mobility anchor MAY
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 LMA decides to revoke the mobile node IPv4 proxy HoA ONLY, the the LMA decides to revoke the mobile node IPv4 proxy HoA ONLY, the
LMA MUST sends a BRI message following the procedure in Section 7.1 LMA MUST send a BRI message following the procedure in Section 7.1
and the following rules: and the following rules:
o The Acknowledge (A) bit MUST be set in the BRI to request the MAG o The Acknowledge (A) bit MUST be set in the BRI to request the MAG
to send a BRA message. to send a BRA message.
o The Revocation Trigger field MUST be set to "IPv4 HoA Binding o The Revocation Trigger field MUST be set to "IPv4 HoA Binding
ONLY". ONLY".
o The IPv4 Home Address option MUST be included with the mobile node o The IPv4 Home Address option MUST be included with the mobile node
IPv4 home address that to be released in addition to the MN-ID IPv4 home address that to be released in addition to the MN-ID
skipping to change at page 24, line 31 skipping to change at page 24, line 31
mobile node which have a proxy CoA that is used as the source mobile node which have a proxy CoA that is used as the source
of the IPv6 packet that carried the BRI or in the Alternate of the IPv6 packet that carried the BRI or in the Alternate
Care-of-Address option in the BRI. Care-of-Address option in the BRI.
2. If the mobile node identifier, MN-ID, and the Home Network 2. If the mobile node identifier, MN-ID, and the Home Network
Prefix option are included, the local mobility anchor MUST Prefix option are included, the local mobility anchor MUST
only remove the specified proxy binding. only remove the specified 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 need to remove the mobile node bindings which are anchor MUST remove all bindings which are referenced by these
referenced in these multiple Home Network Prefixes for the multiple Home Network Prefixes for the specified mobile node
specified mobile node NAI. NAI. In case that these Home Network Prefixes are all the
allocated Home Network Prefixes for the mobile node BCE, the
LMA needs to remove the mobile node BCE.
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.
9.2.2. Sending Binding Revocation Acknowledgement 9.2.2. Sending Binding Revocation Acknowledgement
When the local mobility anchor receive a valid Binding Revocation When the local mobility anchor receive a valid Binding Revocation
Indication with the (A) bit is set and after processing the BRI Indication with the (A) bit is set and after processing the BRI
skipping to change at page 26, line 10 skipping to change at page 26, line 13
mobility options. However, if the (P) bit is set, this BRI MUST mobility options. However, if the (P) bit is set, this BRI MUST
only impact mobile nodes bindings that have the Proxy Mobile IP only impact mobile nodes bindings that have the Proxy Mobile IP
flag set. In this case, the MAG MUST send a BRA with the flag set. In this case, the MAG MUST send a BRA with the
appropriate status code to the LMA. appropriate status code to the LMA.
o If the Global (G) bit is set and the Revocation Trigger field is o If the Global (G) bit is set and the Revocation Trigger field is
set to "Revoking Node Local Policy", the MAG MUST identify all set to "Revoking Node Local Policy", the MAG MUST identify all
bindings that are registered at the LMA and hosted at the MAG bindings that are registered at the LMA and hosted at the MAG
using the mobility option(s) included in the BRI. This Binding using the mobility option(s) included in the BRI. This Binding
Revocation Indication SHOULD include at least the MN-ID option, Revocation Indication SHOULD include at least the MN-ID option,
e.g. with a wild card NAI. e.g. with a wild card NAI. In this case, the MAG MUST send a BRA
with the appropriate status code to the LMA.
o If the Global (G) bit is set and the Revocation Trigger field is o If the Global (G) bit is set and the Revocation Trigger field is
set to "Revoking Node Local Policy", and no mobility options are set to "Revoking Node Local Policy", and no mobility options are
included in the Binding Revocation Indication message, the MAG included in the Binding Revocation Indication message or the MAG
MUST treat this as an error scenario. In this case, the MAG is not able to identify the impacted mobile nodes bindings based
SHOULD send a Binding Revocation Acknowledgement message with on the included mobility options, the MAG MUST treat this as an
status "CAN NOT Identify Binding". error scenario. In this case, the MAG SHOULD send a Binding
Revocation Acknowledgement message with status "CAN NOT Identify
Binding".
o If the Revocation Trigger field in the received BRI message is set o If the Revocation Trigger field value in the received Binding
to "Inter-MAG - Unknown Handoff", the MAG use the mobility Revocation Indication message indicates an inter-MAG handover and
option(s) included in the BRI message to identify the mobile node the (A) bit is set, the MAG use the mobility option(s) included in
binding and MUST validate that the mobile node is no longer the BRI message to identify the mobile node binding. The mobile
access gateway MAY validate that the mobile node is no longer
attached to the mobile access gateway before sending a successful
Binding Revocation Acknowledgement message to the LMA. However,
if the Revocation Trigger field is set to "Inter-MAG - Unknown
Handoff", the MAG MUST validate that the mobile node is no longer
attached to the MAG before sending a successful BRA message and attached to the MAG before sending a successful BRA message and
deleting the resources associated with the mobile node binding. deleting the resources associated with the mobile node binding.
o If the Revocation Trigger field in the received BRI message is set o If the Revocation Trigger field in the received BRI message is set
to "IPv4 HoA Binding ONLY", the MAG uses the MN-ID option to to "IPv4 HoA Binding ONLY", the MAG uses the MN-ID option to
identify the mobile node binding entry in the BUL. The MAG MUST identify the mobile node binding entry in the BUL. The MAG MUST
verify that the IPv4 address included in the IPv4 Home Address verify that the IPv4 address included in the IPv4 Home Address
option in the received BRI is the same as the IPv4 proxy HoA that option in the received BRI is the same as the IPv4 proxy HoA that
is assigned to the mobile node. After the MAG successfully is assigned to the mobile node. After the MAG successfully
validate the received IPv4 home address as the mobile node IPv4 validate the received IPv4 home address as the mobile node IPv4
skipping to change at page 27, line 5 skipping to change at page 27, line 16
HoA, the MAG MUST send a BRA with status field is set to "IPv4 HoA HoA, the MAG MUST send a BRA with status field is set to "IPv4 HoA
Binding Does NOT Exist". Binding Does NOT Exist".
The Revocation Trigger field value in the received BRI could be used The Revocation Trigger field value in the received BRI could be used
by the mobile access gateway to define what actions the MAG could do by the mobile access gateway to define what actions the MAG could do
to inform the mobile node that its IP connectivity to the current HNP to inform the mobile node that its IP connectivity to the current HNP
has been terminated. e.g. if the Revocation Trigger field is set to has been terminated. e.g. if the Revocation Trigger field is set to
"Administrative Reason", the mobile access gateway may send a RA "Administrative Reason", the mobile access gateway may send a RA
message after setting the Home Network Prefix lifetime to zero. message after setting the Home Network Prefix lifetime to zero.
If the Revocation Trigger field value in the received Binding
Revocation Indication message indicates an inter-MAG handover and the
(A) bit is set, the mobile access gateway MAY validate that the
mobile node is no longer attached to the mobile access gateway before
sending a successful Binding Revocation Acknowledgement message to
the LMA. However, if the Revocation Trigger field is set to "Inter-
MAG - Unknown Handoff", the MAG MUST validate that the mobile node is
no longer attached to the MAG before sending a successful BRA message
and deleting the resources associated with the mobile node binding.
10.1.2. Sending Binding Revocation Acknowledgement 10.1.2. Sending Binding Revocation Acknowledgement
When the mobile access gateway receive a valid Binding Revocation When the mobile access gateway receive a valid Binding Revocation
Indication with the (A) bit is set and after processing the BRI Indication with the (A) bit is set and after processing the BRI
message, the mobile access gateway sends a packet to the local message, the mobile access gateway sends a packet to the local
mobility anchor containing a Binding Revocation Acknowledgement mobility anchor containing a Binding Revocation Acknowledgement
according to the procedure in Section 7.1 and the following: according to the procedure in Section 7.1 and the following:
o The mobile access gateway MUST set the (P) bit in the Binding o The mobile access gateway MUST set the (P) bit in the Binding
Revocation Acknowledgement if it is set in the received BRI. Revocation Acknowledgement if it is set in the received BRI.
skipping to change at page 29, line 26 skipping to change at page 29, line 32
rejection. rejection.
11. Mobile Node Operation 11. Mobile Node Operation
11.1. Receiving Binding Revocation Indication 11.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 7.2 and the mobile node MUST validate the packet according to Section 7.2 and the
following tests: following tests:
o The mobile node MUST verify that the IP address in the Home o The mobile node MUST verify that the IP address in the type 2
Address option is its Home Address. routing header is its Home Address.
o If the Acknowledgement (A) bit is set in the Binding Revocation o If the Acknowledgement (A) bit is set in the Binding Revocation
Indication and the MN has the BCE in registered state, the mobile Indication and the MN has the BCE in registered state, the mobile
node MUST send a Binding Revocation Acknowledgement. However, in node MUST send a Binding Revocation Acknowledgement. However, in
all other cases when the (A) bit is set in the BRI, the mobile all other cases when the (A) bit is set in the BRI, the mobile
node SHOULD send a Binding Revocation Acknowledgement. In all node SHOULD send a Binding Revocation Acknowledgement. In all
cases, the mobile node MUST follow Section 11.2 when send a BRA cases, the mobile node MUST follow Section 11.2 when send a BRA
using the appropriate status code. using the appropriate status code.
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 silently discard the Binding Revocation
Indication message. Indication message.
o If the Revocation Trigger field value is "Administrative Reason", o If the Revocation Trigger field value is "Administrative Reason",
the mobile node MUST not try to re-register with the home agent the mobile node MUST NOT try to re-register with the home agent
before contacting its home operator. before contacting its home operator.
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 BRI message. If the revoked by examining the content of the BRI message. If the
mobile node received a Binding Revocation Indication with a single mobile node received a Binding Revocation Indication with a single
or more than one BID options and its home address is in the Home or more than one Binding ID options and its home address is
Address option, the mobile node MUST consider its bindings included in the type 2 routing header, the mobile node MUST
identified in the Binding ID options are being revoked. consider all of the care-of address(es) binding(s), identified in
the Binding ID options, with this home address are being revoked.
o If the mobile node has multi Care-of Addresses bindings with its o If the mobile node has multi Care-of Addresses bindings with its
home agent and received a Binding Revocation Indication, with only home agent and received a Binding Revocation Indication, without
its home address in the Home Address option, the mobile node MUST any Binding ID option included and its home address was included
consider all of its registered care-of addresses bindings with in the type 2 routing header, the mobile node MUST consider all of
this home address have been revoked. its registered care-of addresses bindings with this home address
are being revoked.
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.
11.2. Sending Binding Revocation Acknowledgement 11.2. Sending Binding Revocation Acknowledgement
When the mobile node receive a valid Binding Revocation Indication When the mobile node receive a valid Binding Revocation Indication
with the (A) bit is set from its home agent and while having this BCE with the (A) bit is set from its home agent and while having this BCE
skipping to change at page 30, line 32 skipping to change at page 30, line 41
agent containing a Binding Revocation Acknowledgement according to agent containing a Binding Revocation Acknowledgement according to
the procedure in Section 7.1 and the following: the procedure in Section 7.1 and the following:
o The mobile node MUST set the status field to successful to reflect o The mobile node MUST set the status field to successful to reflect
that it has received the Binding Revocation Indication and that it has received the Binding Revocation Indication and
acknowledge that its IP connectivity with its home agent has been acknowledge that its IP connectivity with its home agent has been
revoked. revoked.
o The destination IP address of the IPv6 packet of the Binding o The destination IP address of the IPv6 packet of the Binding
Revocation Acknowledgement is set to the source IP address of the Revocation Acknowledgement is set to the source IP address of the
received Binding Revocation Indication. received IPv6 packet of the Binding Revocation Indication. The
Mobile Node MUST include its home address in the Home Address
option in the Destination Option.
o If the mobile node receives a Binding Revocation Indication from a o If the mobile node receives a Binding Revocation Indication from a
home agent which the mobile node does not have a registered home agent which the mobile node does not have a registered
binding with, the mobile node SHOULD silently discard the BRI binding with, the mobile node SHOULD silently discard the BRI
message. The mobile node should continue to use its assigned HoA message. The mobile node should continue to use its assigned HoA
to access its IP mobility service. to access its IP mobility service.
12. Protocol Configuration Variables 12. 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
skipping to change at page 32, line 9 skipping to change at page 32, line 13
Cazavet, Domagoj Premec for their review and comments of this draft Cazavet, Domagoj Premec 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. effort.
16. References 16. References
16.1. Normative References 16.1. Normative References
[ID-DSMIP6] [ID-DSMIP6]
Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", draft-ietf-mext-nemo-v4traversal-04 (work in Routers", draft-ietf-mext-nemo-v4traversal-06 (work in
progress), June 2008. progress), November 2008.
[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-08 (work in progress), draft-ietf-monami6-multiplecoa-10 (work in progress),
May 2008. November 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-03 Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-05
(work in progress), May 2008. (work in progress), September 2008.
[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.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[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.
skipping to change at page 33, line 40 skipping to change at page 33, line 40
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
30 International Place 30 International Place
Tewksbury, MA 01876 Tewksbury, MA 01876
USA USA
Email: kchowdhury@starentnetworks.com Email: kchowdhury@starentnetworks.com
Parviz Yegani Parviz Yegani
Cisco Systems Juniper Networks
170 West Tasman Drive 1194 North Mathilda Avenue
San Jose, CA 95134 Sunnyvale, CA 94089
USA USA
Email: pyegani@cisco.com Email: pyegani@juniper.net
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 46 change blocks. 
119 lines changed or deleted 124 lines changed or added

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