draft-ietf-mip6-ha-switch-03.txt   draft-ietf-mip6-ha-switch-04.txt 
Mobile IPv6 B. Haley Mobile IPv6 B. Haley
Internet Draft Hewlett-Packard Internet Draft Hewlett-Packard
Document: draft-ietf-mip6-ha-switch-03.txt V. Devarapalli Document: draft-ietf-mip6-ha-switch-04.txt V. Devarapalli
Intended status: Standards Track Azaire Networks Intended status: Standards Track Azaire Networks
Expires: September, 2007 H. Deng Expires: April 26, 2008 H. Deng
Hitachi Hitachi
J. Kempf J. Kempf
DoCoMo USA Labs DoCoMo USA Labs
October 26, 2007
Mobility Header Home Agent Switch Message Mobility Header Home Agent Switch Message
draft-ietf-mip6-ha-switch-03.txt draft-ietf-mip6-ha-switch-04.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 43 skipping to change at page 2, line 5
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
Abstract Abstract
This document specifies a new Mobility Header message type that can This document specifies a new Mobility Header message type that can
be used between a home agent and mobile node to signal a mobile node be used between a home agent and mobile node to signal a mobile node
that it should acquire a new home agent. that it should acquire a new home agent.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1].
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. Scenarios......................................................2 2. Terminology....................................................2
2.1 Overloaded.................................................3 3. Scenarios......................................................3
2.2 Load Balancing.............................................3 3.1 Overloaded.................................................3
2.3 Maintenance................................................3 3.2 Load Balancing.............................................3
2.4 Functional Load Balancing..................................3 3.3 Maintenance................................................3
2.5 Home Agent Renumbering.....................................3 3.4 Functional Load Balancing..................................3
3. Home Agent Switch Message......................................4 3.5 Home Agent Renumbering.....................................4
4. Home Agent Operation...........................................6 4. Home Agent Switch Message......................................4
4.1 Sending Home Agent Switch Messages.........................6 5. Home Agent Operation...........................................6
4.2 Retransmissions............................................7 5.1 Sending Home Agent Switch Messages.........................6
4.3 Mobile Node Errors.........................................7 5.2 Retransmissions............................................7
5. Mobile Node Operation..........................................8 5.3 Mobile Node Errors.........................................7
5.1 Receiving Home Agent Switch Messages.......................8 6. Mobile Node Operation..........................................8
5.2 Selecting a Home Agent.....................................8 6.1 Receiving Home Agent Switch Messages.......................8
6. Operational Considerations.....................................9 6.2 Selecting a Home Agent.....................................8
7. Procotol Constants.............................................9 7. Operational Considerations.....................................9
8. IANA Considerations............................................9 8. Procotol Constants.............................................9
9. Security Considerations........................................9 9. IANA Considerations............................................9
10. References...................................................10 10. Security Considerations.......................................9
10.1 Normative References.....................................10 11. References...................................................10
10.2 Informative references...................................10 11.1 Normative References.....................................10
11.2 Informative references...................................10
Acknowledgments..................................................10 Acknowledgments..................................................10
Author's Addresses...............................................11 Author's Addresses...............................................10
1. Introduction 1. Introduction
RFC 3775 [2] contains no provision to allow a home agent to inform a RFC 3775 [2] contains no provision to allow a home agent to inform a
mobile node that it needs to stop acting as the home agent for the mobile node that it needs to stop acting as the home agent for the
mobile node. For example, a home agent may wish to handoff some of mobile node. For example, a home agent may wish to handoff some of
its mobile nodes to another home agent because it has become its mobile nodes to another home agent because it has become
overloaded or it is going offline. overloaded or it is going offline.
This protocol describes a signaling message type that can be used to This protocol describes a signaling message type that can be used to
send a handoff notification between a home agent and mobile node. send a handoff notification between a home agent and mobile node.
2. Scenarios 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1].
3. Scenarios
Here are some example scenarios where a home agent signaling message Here are some example scenarios where a home agent signaling message
would be useful. would be useful.
2.1 Overloaded 3.1 Overloaded
There are a number of reasons a home agent might be considered There are a number of reasons a home agent might be considered
overloaded. One might be that it is at, or near, its limit on the overloaded. One might be that it is at, or near, its limit on the
number of home bindings it is willing to accept. Another is that it number of home bindings it is willing to accept. Another is that it
has reached a pre-determined level of system resource usage - memory, has reached a pre-determined level of system resource usage - memory,
cpu cycles, etc. In either case, it would be desirable for a home cpu cycles, etc. In either case, it would be desirable for a home
agent to reduce the number of home bindings before a failure occurs. agent to reduce the number of home bindings before a failure occurs.
2.2 Load Balancing 3.2 Load Balancing
A home agent might know of other home agents that are not as heavily A home agent might know of other home agents that are not as heavily
loaded as itself, learned through some other mechanism outside the loaded as itself, learned through some other mechanism outside the
scope of this document. An operator may wish to try and balance this scope of this document. An operator may wish to try and balance this
load so a failure disrupts a smaller percentage of mobile nodes. load so a failure disrupts a smaller percentage of mobile nodes.
2.3 Maintenance 3.3 Maintenance
Most operators do periodic maintenance in order to maintain Most operators do periodic maintenance in order to maintain
reliability. If a home agent is being shutdown for maintenance, it reliability. If a home agent is being shutdown for maintenance, it
would be desirable to inform mobile nodes so they do not lose would be desirable to inform mobile nodes so they do not lose
mobility service. mobility service.
2.4 Functional Load Balancing 3.4 Functional Load Balancing
A Mobile IPv6 home agent provides mobile nodes with two basic A Mobile IPv6 home agent provides mobile nodes with two basic
services - a rendezvous server where correspondent nodes can find the services - a rendezvous server where correspondent nodes can find the
current care-of address for the mobile node, and as an overlay router current care-of address for the mobile node, and as an overlay router
to tunnel traffic to/from the mobile node at its current care-of to tunnel traffic to/from the mobile node at its current care-of
address. address.
A mobility service provider could have two sets of home agents to A mobility service provider could have two sets of home agents to
handle the two functions. The rendezvous function could be handled handle the two functions. The rendezvous function could be handled
by a machine specialized for high-speed transaction processing, while by a machine specialized for high-speed transaction processing, while
the overlay router function could be handled by a machine with high the overlay router function could be handled by a machine with high
data throughput. data throughput.
A mobile node would start on the rendezvous server home agent and A mobile node would start on the rendezvous server home agent and
stay there if it does route optimization. However, if the original stay there if it does route optimization. However, if the original
home agent detects that the mobile node is not doing route home agent detects that the mobile node is not doing route
optimization, but instead reverse-tunneling traffic, it could optimization, but instead reverse-tunneling traffic, it could
redirect the mobile node to a home agent with better data throughput. redirect the mobile node to a home agent with better data throughput.
2.5 Home Agent Renumbering 3.5 Home Agent Renumbering
Periodically, a mobility service provider may want to shut-down home Periodically, a mobility service provider may want to shut-down home
agent services at a set of IPv6 addresses and bring service back up agent services at a set of IPv6 addresses and bring service back up
at a new set of addresses. Note that this may not involve anything at a new set of addresses. Note that this may not involve anything
as complex as IPv6 network renumbering, it may just involve changing as complex as IPv6 network renumbering [3], it may just involve
the addresses of the home agents. With a signaling message, the changing the addresses of the home agents. With a signaling message,
service provider could inform mobile nodes to look for a new home the service provider could inform mobile nodes to look for a new home
agent. agent.
3. Home Agent Switch Message 4. Home Agent Switch Message
The Home Agent Switch message is used by the home agent to signal the The Home Agent Switch message is used by the home agent to signal the
mobile node that it needs to stop acting as the home agent for the mobile node that it needs to stop acting as the home agent for the
mobile node, and that it should acquire a new home agent. Home Agent mobile node, and that it should acquire a new home agent. Home Agent
Switch messages are sent as described in Section 4. Switch messages are sent as described in Section 5.
The message described below follows the Mobility Header format The message described below follows the Mobility Header format
specified in Section 6.1 of [2]: specified in Section 6.1 of [2]:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Proto | Header Len | MH Type | Reserved | | Payload Proto | Header Len | MH Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | | | Checksum | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
skipping to change at page 6, line 4 skipping to change at page 6, line 4
Home Agent Addresses Home Agent Addresses
A list of alternate home agent addresses for the mobile node. The A list of alternate home agent addresses for the mobile node. The
number of addresses present in the list is indicated by the "# of number of addresses present in the list is indicated by the "# of
Addresses" field in the Home Agent Switch message. Addresses" field in the Home Agent Switch message.
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 of more TLV-encoded mobility options. The encoding contains zero or more TLV-encoded mobility options. The encoding
and format of defined options MUST follow the format specified in and format of defined options MUST follow the format specified in
Section 6.2 of [2]. The receiver MUST ignore and skip any options Section 6.2 of [2]. The receiver MUST ignore and skip any options
with it does not understand. which it does not understand.
The Binding Refresh Advice mobility option defined in Section 6.2.4 The Binding Refresh Advice mobility option defined in Section 6.2.4
of [2] is valid for the Home Agent Switch message. of [2] is valid for the Home Agent Switch message.
If no home agent addresses and no options are present in this If no home agent addresses and no options are present in this
message, no padding is necessary and the Header Len field in the message, no padding is necessary and the Header Len field in the
Mobility Header will be set to 0. Mobility Header will be set to 0.
4. Home Agent Operation 5. Home Agent Operation
4.1 Sending Home Agent Switch Messages 5.1 Sending Home Agent Switch Messages
When sending a Home Agent Switch message, the sending node constructs When sending a Home Agent Switch message, the sending node constructs
the packet as it would any other Mobility Header, except: the packet as it would any other Mobility Header, except:
o The MH Type field MUST be set to (TBD). o The MH Type field MUST be set to (TBD).
o If alternative home agent addresses are known, the sending home o If alternative home agent addresses are known, the sending home
agent SHOULD include them in the list of suggested alternate agent SHOULD include them in the list of suggested alternate
home agents. The home agent addresses field should be home agents. The home agent addresses field should be
constructed as described in Section 10.5.1 of [2], which will constructed as described in Section 10.5.1 of [2], which will
skipping to change at page 6, line 42 skipping to change at page 6, line 42
the number of home agent addresses included in the message. If the number of home agent addresses included in the message. If
no addresses are present, the field MUST be set to zero, forcing no addresses are present, the field MUST be set to zero, forcing
the mobile node to perform home agent discovery by some other the mobile node to perform home agent discovery by some other
means. means.
o If the home agent is able to continue offering services to the o If the home agent is able to continue offering services to the
mobile node for some period of time, it MAY include a Binding mobile node for some period of time, it MAY include a Binding
Refresh Advice mobility option indicating the time (in units of Refresh Advice mobility option indicating the time (in units of
4 seconds) until the binding will be deleted. 4 seconds) until the binding will be deleted.
The Home Agent Switch message MUST be authenticated in one of the The Home Agent Switch message MUST use the home agent to mobile node
following ways: IPsec ESP authentication SA for integrity protection.
o The home agent to mobile node IPsec ESP authentication SA for
integrity protection.
o A home agent to mobile node authentication option, such as [3].
A home agent SHOULD send a Home Agent Switch message when a known A home agent SHOULD send a Home Agent Switch message when a known
period of unavailability is pending so the mobile node has sufficient period of unavailability is pending so the mobile node has sufficient
time to find another suitable home agent. time to find another suitable home agent.
The sending node does not need to be the current home agent for the The sending node does not need to be the current home agent for the
mobile node, for example as described in [4], but it MUST have a mobile node, for example as described in [4], but it MUST have a
security association with the mobile node so the message is not security association with the mobile node so the message is not
rejected. In this case, the Home Agent Switch message SHOULD only rejected. In this case, the Home Agent Switch message SHOULD only
contain the address of the home agent sending the message in the Home contain the address of the home agent sending the message in the Home
Agent Addresses field, which implies the mobile node should switch to Agent Addresses field, which implies the mobile node should switch to
using the sender as its new home agent. using the sender as its new home agent.
4.2 Retransmissions 5.2 Retransmissions
If the home agent does not receive a response from the mobile node - If the home agent does not receive a response from the mobile node -
either a Binding Update message to delete its home binding if it is either a Binding Update message to delete its home binding if it is
the current home agent, or a Binding Update message to create a home the current home agent, or a Binding Update message to create a home
binding if it is not the current home agent, then it SHOULD binding if it is not the current home agent, then it SHOULD
retransmit the message, until a response is received. The initial retransmit the message, until a response is received. The initial
value for the retransmission timer is INITIAL-HA-SWITCH-TIMEOUT. value for the retransmission timer is INITIAL-HA-SWITCH-TIMEOUT.
The retransmissions by the home agent MUST use an exponential back- The retransmissions by the home agent MUST use an exponential back-
off mechanism, in which the timeout period is doubled upon each off mechanism, in which the timeout period is doubled upon each
retransmission, until either the home agent gets a response from the retransmission, until either the home agent gets a response from the
mobile node to delete its binding, or the timeout period reaches the mobile node to delete its binding, or the timeout period reaches the
value MAX-HA-SWITCH-TIMEOUT. value MAX-HA-SWITCH-TIMEOUT. The home agent MAY continue to send
these messages at this slower rate indefinitely.
If the home agent included a Binding Refresh Advice mobility option, If the home agent included a Binding Refresh Advice mobility option,
then it SHOULD delay any retransmissions until at least one half of then it SHOULD delay any retransmissions until at least one half of
the time period has expired, or INITIAL-HA-SWITCH-TIMEOUT, whichever the time period has expired, or INITIAL-HA-SWITCH-TIMEOUT, whichever
value is less. value is less.
4.3 Mobile Node Errors 5.3 Mobile Node Errors
If a mobile node does not understand how to process a Home Agent If a mobile node does not understand how to process a Home Agent
Switch Message, it will send a Binding Error message as described in Switch Message, it will send a Binding Error message as described in
Section 5.1. Section 6.1.
If a mobile node is unreachable, in other words, it still has a home If a mobile node is unreachable, in other words, it still has a home
binding with the home agent after reaching the timeout period of MAX- binding with the home agent after reaching the timeout period of MAX-
HA-SWITCH-TIMEOUT, the home agent SHOULD NOT make any conclusions HA-SWITCH-TIMEOUT, the home agent SHOULD NOT make any conclusions
about its status. about its status.
In either case, the home agent SHOULD attempt to continue providing In either case, the home agent SHOULD attempt to continue providing
services until the lifetime of the binding expires. services until the lifetime of the binding expires.
Attempts by the mobile node to extend the binding lifetime with a Attempts by the mobile node to extend the binding lifetime with a
Binding Update message SHOULD be rejected, and a Binding Binding Update message SHOULD be rejected, and a Binding
Acknowledgement SHOULD be returned with status value 129 Acknowledgement SHOULD be returned with status value 129
(Administratively prohibited) as specified in Section 6.1.8 of [2]. (Administratively prohibited) as specified in Section 6.1.8 of [2].
5. Mobile Node Operation 6. Mobile Node Operation
5.1 Receiving Home Agent Switch Messages 6.1 Receiving Home Agent Switch Messages
Upon receiving a Home Agent Switch message, the Mobility Header MUST Upon receiving a Home Agent Switch message, the Mobility Header MUST
be verified as specified in [2], specifically: be verified as specified in [2], specifically:
o The Checksum, MH type, Payload Proto and Header Len fields o The Checksum, MH type, Payload Proto and Header Len fields
MUST meet the requirements of Section 9.2 of [2]. MUST meet the requirements of Section 9.2 of [2].
o The packet MUST be authenticated, either by the home agent to o The packet MUST be authenticated, either by the home agent to
mobile node IPsec ESP authentication SA for integrity mobile node IPsec ESP authentication SA for integrity
protection, or a home agent to mobile node authentication protection, or a home agent to mobile node authentication
option. option.
If the packet is dropped due to the above tests, the receiving node If the packet is dropped due to the above tests, the receiving node
MUST follow the processing rules as Section 9.2 of [2] defines. For MUST follow the processing rules as Section 9.2 of [2] defines. For
example, it MUST send a Binding Error message with the Status field example, it MUST send a Binding Error message with the Status field
set to 2 (unrecognized MH Type value) if it does not support the set to 2 (unrecognized MH Type value) if it does not support the
message type. message type.
Upon receipt of a Home Agent Switch message, the mobile node MUST Upon receipt of a Home Agent Switch message, the mobile node MUST
stop using its current home agent for services and MUST delete its stop using its current home agent for services and MUST delete its
home binding by sending a Binding Update message as described in [2]. home binding by sending a Binding Update message as described in
This acts as an acknowledgement of the Home Agent Switch message. Section 11.7.1 of [2]. This acts as an acknowledgement of the Home
Alternately, if the sender of the message is not the current home Agent Switch message. Alternately, if the sender of the message is
agent, sending a Binding Update message to create a home binding will not the current home agent, sending a Binding Update message to
act as an acknowledgement of the Home Agent Switch message. create a home binding will act as an acknowledgement of the Home
Agent Switch message. Retransmissions of Binding Update messages
MUST use the procedures described in Section 11.8 of [2].
If a Binding Refresh Advice mobility option is present, the mobile If a Binding Refresh Advice mobility option is present, the mobile
node MAY delay the deletion of its home binding and continue to use node MAY delay the deletion of its home binding and continue to use
its current home agent until the calculated time period has expired. its current home agent until the calculated time period has expired.
If the Home Agent Switch message contains a list of alternate home If the Home Agent Switch message contains a list of alternate home
agent addresses, the mobile node SHOULD select a new home agent as agent addresses, the mobile node SHOULD select a new home agent as
described in Section 5.2, and establish the necessary IPsec security described in Section 6.2, and establish the necessary IPsec security
associations with the new home agent by whatever means required as associations with the new home agent by whatever means required as
part of the mobile node/home agent bootstrapping protocol for the part of the mobile node/home agent bootstrapping protocol for the
home agent's mobility service provider. If no alternate home agent home agent's mobility service provider. If no alternate home agent
addresses are included in the list, the mobile node MUST first addresses are included in the list, the mobile node MUST first
perform home agent discovery. perform home agent discovery.
5.2 Selecting a Home Agent 6.2 Selecting a Home Agent
In most cases, the home agent addresses in the Home Agent Switch In most cases, the home agent addresses in the Home Agent Switch
message will be of other home agents on the home link of the mobile message will be of other home agents on the home link of the mobile
node. In this case, the mobile node SHOULD select a new home agent node (the computed prefix is the same). In this case, the mobile
from the addresses as they are ordered in the list. If the first node SHOULD select a new home agent from the addresses as they are
address in the list is unable to provide service, then the subsequent ordered in the list. If the first address in the list is unable to
addresses in the list should be tried in-order. provide service, then the subsequent addresses in the list should be
tried in-order.
In the case that the home agent addresses in the Home Agent Switch In the case that the home agent addresses in the Home Agent Switch
message are not all home agents on the home link of the mobile node message are not all home agents on the home link of the mobile node
(the computed prefix is different), the mobile node SHOULD select one (the computed prefix is different), the mobile node SHOULD select one
on the home link first, if available, followed by home agents not on its home network prefix first, if available, followed by home agents
the home link. Choosing a home agent not on the home link might with other prefixes. Choosing a home agent with a different prefix
require a change of the home address for the mobile node, which could might require a change of the home address for the mobile node, which
cause a loss of connectivity for any connections using the current could cause a loss of connectivity for any connections using the
home address. current home address.
6. Operational Considerations 7. Operational Considerations
This document does not specify how an operator might use the Home This document does not specify how an operator might use the Home
Agent Switch message in its network. However, it might be the case Agent Switch message in its network. However, it might be the case
that a home agent provides service for many thousands of mobile that a home agent provides service for many thousands of mobile
nodes. Care should be taken to reduce the signaling overhead nodes. Care should be taken to reduce the signaling overhead on the
required for handing off many mobile nodes to an alternate home network required for handing off many mobile nodes to an alternate
agent. home agent.
7. Procotol Constants 8. Procotol Constants
INITIAL-HA-SWITCH-TIMEOUT 5 seconds INITIAL-HA-SWITCH-TIMEOUT 5 seconds
MAX-HA-SWITCH-TIMEOUT 20 seconds MAX-HA-SWITCH-TIMEOUT 20 seconds
8. IANA Considerations 9. IANA Considerations
A new Mobility Header type is required for the following new message A new Mobility Header type is required for the following new message
described in Section 3: described in Section 4:
(TBD) Home Agent Switch message (TBD) Home Agent Switch message
9. Security Considerations 10. Security Considerations
The Home Agent Switch message MUST be authenticated by one of the
following methods:
o The home agent to mobile node IPsec ESP authentication SA for
integrity protection as described in [2].
o A home agent to mobile node authentication option, such as As with other messages in [2], the Home Agent Switch message MUST use
[3]. the home agent to mobile node ESP encryption SA for confidentiality
protection, and MUST use the home agent to mobile node ESP
authentication SA for integrity protection.
The Home Agent Switch message MAY use the IPsec ESP SA in place for The Home Agent Switch message MAY use the IPsec ESP SA in place for
Binding Updates and Acknowledgements as specified in Section 5.1 of Binding Updates and Acknowledgements as specified in Section 5.1 of
[2], in order to reduce the number of configured security [2], in order to reduce the number of configured security
associations. This also gives the message authenticity protection. associations. This also gives the message authenticity protection.
Some operators may not want to reveal the list of home agents to on- Some operators may not want to reveal the list of home agents to on-
path listeners. In such a case, the Home Agent Switch message should path listeners. In such a case, the Home Agent Switch message should
use the home agent to mobile node IPsec ESP encryption SA for use the home agent to mobile node IPsec ESP encryption SA for
confidentiality protection. confidentiality protection.
10. References 11. References
10.1 Normative References 11.1 Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Johnson, D., Perkins, C., and Arkko, J., "Mobility Support in [2] Johnson, D., Perkins, C., and Arkko, J., "Mobility Support in
IPv6", RFC 3775, June, 2004. IPv6", RFC 3775, June, 2004.
10.2 Informative references 11.2 Informative References
[3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and Chowdhury, K., [3] Baker, F., Lear, E., and Droms, R., "Procedures for Renumbering
"Authentication Protocol for Mobile IPv6", RFC 4285, January, an IPv6 Network without a Flag Day", RFC 4192, September, 2005.
2006.
[4] Wakikawa, R. (Editor), "Home Agent Reliability Protocol", draft- [4] Wakikawa, R. (Editor), "Home Agent Reliability Protocol", draft-
ietf-mip6-hareliability-01.txt, October, 2006. ietf-mip6-hareliability-02.txt, July, 2007.
Acknowledgments Acknowledgments
We would like to thank the authors of a number of previous drafts We would like to thank the authors of a number of previous drafts
that contributed content to this document: that contributed content to this document:
o draft-wakikawa-mip6-nemo-haha-spec-00.txt o draft-wakikawa-mip6-nemo-haha-spec-00.txt
o draft-deng-mip6-ha-loadbalance-02.txt o draft-deng-mip6-ha-loadbalance-02.txt
o draft-kempf-mip6-ha-alert-00.txt o draft-kempf-mip6-ha-alert-00.txt
o draft-haley-mip6-mh-signaling-00.txt o draft-haley-mip6-mh-signaling-00.txt
 End of changes. 45 change blocks. 
97 lines changed or deleted 98 lines changed or added

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