Internet DRAFT - draft-zhang-mip6-find-reg-ha
draft-zhang-mip6-find-reg-ha
MIP6 Working Group Jian Zhang
Hongfei Chen
Internet Draft Huawei Technologies
Robert Jaksa
FutureWei Technologies
Expires: February 2007 August 14, 2006
Find the HA that MNs Registered in MIPv6
draft-zhang-mip6-find-reg-ha-01.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
any 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 aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Jian et al. Expires February 14, 2007 [Page 1]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
This Internet-Draft will expire on February 14, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006). All Rights Reserved.
Abstract
In mobile IPv6 networks, a mobile node must register its new care of
address with its home agent after changing its attachment point, so
that it can maintain connectivity with peers. In the deployment of
MIPv6, there may be multiple home agents for load balancing and/or
reliability. In the case of load balancing, some mobile nodes may
register their care of addresses with one home agent, and other
mobile nodes may register their care of addresses with other home
agents. Some applications may need to query the MIPv6 service status
of a mobile node from home agents, such as the care of address, the
life time of binding, or other information associated with mobile
node that is stored on home agents. In order to satisfy this
requirement, the first step is to locate which home agent the mobile
node belongs to, that is to say to confirm which home agent to query.
This document describes a protocol which can be used to locate the
home agent that a mobile node belongs to.
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 [RFC-2119].
Table of Contents
1. Introduction..................................................3
1.1. Retrieve Mobile IPv6 state for AAA service...............3
1.2. Retrieve Location information for Location service.......4
2. Terminology...................................................4
3. Protocol Overview.............................................5
4. Protocol Operations...........................................5
5. Message types and Modifications...............................7
5.1. Home agent located require message (HAlocReq)............8
5.2. Home agent location response message (HALocRes)..........9
5.3. Home agent solicitation message (HASol).................10
5.4. Home agent advertisement message (HAAdv)................11
5.5. New options.............................................13
5.5.1. Mobile node information option.....................13
6. Security Considerations......................................14
Zhang et al. Expires February 14, 2007 [Page 2]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
7. IANA Considerations..........................................14
8. Acknowledgments..............................................15
9. References...................................................16
9.1. Normative References....................................16
9.2. Informative References..................................16
Author's Addresses..............................................16
Intellectual Property Statement.................................17
Disclaimer of Validity..........................................17
Copyright Statement.............................................18
Acknowledgment..................................................18
1. Introduction
In mobile IPv6 networks, a mobile node must register its new care of
address with its home agent after changing attachment point, so that
it can maintain connectivity with peers. In the deployment of MIPv6,
there may be multiple home agents for load balancing and/or
reliability. In the case of load balancing, some mobile nodes may
register their care of addresses with one home agent, and other
mobile nodes may register their care of addresses with other home
agents. Some applications may need to query the MIPv6 service status
of a mobile node from home agents, such as the care of address, the
life time of binding, or other information associated with mobile
node that is stored on home agents. In order to satisfy this
requirement, the first step is to locate which home agent the mobile
node belongs to, that is to say to confirm which home agent to query.
Here are some example scenarios where locating the home agent that a
mobile node belongs to would be useful.
1.1. Retrieve Mobile IPv6 state for AAA service
In order to use mobile IPv6 service, a mobile node SHOULD be
authenticated and authorized by AAA server which is located in the
home network of mobile node. As stated in [GOALS], the AAAH server
SHOULD be able to retrieve the Mobile IPv6 state associated with a
specific MN from the correspondent HA. This MAY be useful to
periodically verify the Mobile IPv6 service status.
As stated in [DIAMETER], there are two issues:
1. How does the AAAH know which HA to contact to retrieve current
status of MN's Mobile IPv6 service in case of stateless MSP
architecture and several servicing AAA servers?
2. Once having the HA information, the AAAH SHOULD contact it to
verify the status of MN's Mobile IPv6 service. This could be
Zhang et al. Expires February 14, 2007 [Page 3]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
performed by Request/Response messages initiated by the AAAH
server.
1.2. Retrieve Location information for Location service
When mobile node is roaming on foreign networks, there maybe some
requirements to locate the position of mobile node, such as whether
the mobile node is in home network. To implement this function, the
location server needs to query the status of the mobile node.
This problem also has two issues:
1. How does the location server know which HA to contact to retrieve
current status of MN's Mobile IPv6 service in case of stateless
MSP architecture and several servicing AAA servers?
2. Once having the HA information, the location server SHOULD contact
it to verify the status of MN's Mobile IPv6 service. This could be
performed by Request/Response messages initiated by the location
server.
The location information may be the care-of address of MN, or some
other information that saved in the HA. If the location information
is care-of address, it is logical location information. If some
service wants to retrieve the geography location information from HA,
the geography location information MUST be stored in HA by some other
approach. It should be note that this service MUST not be used by CN
for privacy and security.
This document describes a protocol which can be used to locate the
home agent that a mobile node belongs to. How to retrieve the
information from home agent is out of scope of this document.
2. Terminology
Application Server Node (ASN)
A device that provides some application service. When determining
the mobile IPv6 state of a mobile node, it needs to know which
home agent to contact.
Zhang et al. Expires February 14, 2007 [Page 4]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
HA-Agent
This is the home agent that receives the home agent location
request message.
3. Protocol Overview
An operator can manage the mobile user effectively by querying the
mobile IPv6 state of a mobile node periodically. However, there may
be multiple home agents for load balancing and/or reliability
purposes in home networks when deploying mobile IPv6 service. After
roaming to a foreign network, a mobile node may choose one home agent
to register its mobile IPv6 service. When an application needs the
mobile IPv6 state of mobile node from its home agent, it should first
to confirm which home agent to contact in order to retrieve the
information that is needed. This document focuses on how to locate
the HA that an MN is registered to in MIPv6.
The steps describe as follow:
1. Application server node (ASN) sends a request message to home
agent in mobile node's home network to determine the home agent
that mobile node is registered to.
2. After received the request message, home agents determine which
home agent each mobile node is registered to. The queried home
agent then sends response message to ASN that includes which home
agent each mobile node is registered to.
After this procedure, the ASN knows which HA to contact to retrieve
current status of MN's Mobile IPv6 service. Then the ASN can contact
home agent to query the status of MN's mobile IPv6 service and can do
further actions.
4. Protocol Operations
When ASN sends HALocReq message to HA, the destination address of
request message is the anycast address of HA. One of HAs in home
network will receive the HALocReq message. If all of the MNs queried
in HALocReq message are registered to the HA that received the
message, this HA will respond the request message immediately.
Otherwise, this HA sends an HASol message to solicit the HA that MN
is registered to in the home network. After receiving an HASol
Zhang et al. Expires February 14, 2007 [Page 5]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
message, the HA that the queried MN belongs to will respond with an
HAAdv message. After receiving the HAAdv message, the HA that
initially received the request message will send an HALocRes to the
ASN.
The figure below shows the detail message flows for protocol.
MN HA1 HA2 ... HAn ASN
| | | | |
| | | | Request |
| | | |(HALocReq)|
| | | |<---------|
| | | | |
| | Who has MN?| |
| | |(HASol)| |
| |<---|<------| |
| | | | |
| | |It's me| |
| | |(HAAdv)| |
| |----------->| |
| | | | |
| | | | Response |
| | | |(HALocRes)|
| | | |--------->|
| | | | |
| | | | |
Figure 1: Operation procedure
When needed, the ASN sends an HALocReq message to the HA that in the
MN's home network. The destination address of HALocReq message is the
anycast address of HA. There may be one or more mobile node
information options that need to be queried. While awaiting a
response, the ASN SHOULD retransmit HALocReq message approximately
every RetransTimer_HALocReq milliseconds. Retransmissions MUST be
rate-limited to at most one request every RetransTimer_HALocReq
milliseconds. The value of RetransTimer_HALocReq MUST be greater or
equal to RetransTimer_HASol multiplied by MAX_HASOL_TIMES. If no
response is received after MAX_HALOCREQ_TIMES request, the HA
location has failed.
Because the destination address of the HALocReq message is the
anycast address of the HA, one of HA in home network will receive
HALocReq message. We refer to the HA that received the HALocReq
message as HA-Agent. The HA-Agent will determine whether all of the
Zhang et al. Expires February 14, 2007 [Page 6]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
MNs in HALocReq message are registered to itself. Based on the result,
there are two actions that HA-Agent will do.
1. If all of the MNs in the HALocReq message are registered to HA-
Agent, HA-Agent will send an HALocRes message to ASN with all of
the MN's mobile node information.
2. If there are some MNs that are not registered to HA-Agent, HA-
Agent will send an HASol message to other home agents in the home
network with MN's mobile node information options to solicit HA
information that the MNs are registered to.
While awaiting a response, the HA-Agent SHOULD retransmit HASol
message approximately every RetransTimer_HASol milliseconds.
Retransmissions MUST be rate-limited to at most one request every
RetransTimer_HASol milliseconds. There is a case that some MN's
information is received, and some MN's information is not received.
In this case, only the MNs that have not received a response SHOULD
be retransmitted. If some MN's information is not received after
MAX_HASOL_TIMES request, the HA solicitation for these MNs has failed,
and HA-Agent MUST indicate this in the mobile node information option
in HALocRes message.
After receiving the HASol message, HA in home network will check
whether there are some MNs in HASol message are registered to itself.
If there are some MNs registered to it, the HA will send an HAAdv
message to HA-Agent with mobile node information. Otherwise the HA
will do nothing.
After receiving all of mobile node information, or after
MAX_HASOL_TIMES, HA-Agent MUST send an HALocRes message to the ASN.
In the HALocRes message, HA-Agent MUST indicate whether there are HAs
that mobile nodes are registered to.
5. Message types and Modifications
There are four messages in this protocol, such as HALocReq, HALocRes,
HASol, and HAAdv. All of these messages are ICMPv6 message extended
for the protocol.
Zhang et al. Expires February 14, 2007 [Page 7]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
5.1. Home agent located require message (HAlocReq)
HALocReq message is used by an ASN to initiate the request procedure.
It is ICMPv6 message with mobile node information.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
. .
. Mobile Node Information Option .
. .
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Home agent located require message (HAlocReq)
Type
TBD
Code
0
Checksum
The ICMP checksum [ICMPv6].
Identifier
An identifier to aid in matching Home Agent Location Response
messages to this Home Agent Address Location Request message.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
Zhang et al. Expires February 14, 2007 [Page 8]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
The Source address of the Home Agent Location Require message packet
is typically the source address of the ASN. The destination address
of the Home Agent Location Require message packet is the anycast
address of HA. There may be one or more mobile nodes information
options in the message.
5.2. Home agent location response message (HALocRes)
HALocRes message is used by HA-Agent to send the response to the ASN.
It is ICMPv6 message with mobile node information.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
. .
. Mobile Node Information Option .
. .
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Home agent located respond message (HAlocRes)
Type
TBD
Code
0 - successful resolved all of MN's
1 - cannot resolved some mobile nodes
Checksum
The ICMP checksum [ICMPv6].
Zhang et al. Expires February 14, 2007 [Page 9]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
Identifier
An identifier to aid in matching Home Agent Location Response
messages to this Home Agent Address Location Request message.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
The Source address of the Home Agent Location Response message packet
is typically the source address of HA-Agent. The destination address
of the Home Agent Location Response message packet is the address of
ASN. The number of mobile node information options MUST be consistent
with the request message.
5.3. Home agent solicitation message (HASol)
HASol message is used by HA-Agent to send solicitation message to the
all other HAs in home network. It is ICMPv6 message with mobile node
information.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
. .
. Mobile Node Information Option .
. .
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Home agent solicit message (HASol)
Type
TBD
Zhang et al. Expires February 14, 2007 [Page 10]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
Code
0
Checksum
The ICMP checksum [ICMPv6].
Identifier
An identifier to aid in matching Home Agent Location Response
messages to this Home Agent Address Location Request message.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
The Source address of the Home Agent Solicitation message packet is
typically the source address of HA-Agent. The destination address of
the Home Agent solicitation message packet is all-routers multicast
address. There may be one or more mobile node information options
that are needed to solicit in the message.
5.4. Home agent advertisement message (HAAdv)
HAAdv message is used by HA to send advertisement message to HA-Agent.
It is ICMPv6 message with mobile node information.
Zhang et al. Expires February 14, 2007 [Page 11]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
. .
. Mobile Node Information Option .
. .
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Home agent advertisement message (HAAdv)
Type
1
Code
0
Checksum
The ICMP checksum [ICMPv6].
Identifier
An identifier to aid in matching Home Agent Location Response
messages to this Home Agent Address Location Request message.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
The Source address of the Home Agent Advertisement message packet is
typically the source address of HA. The destination address of the
Home Agent Advertisement message packet is the address of HA-Agent.
The number of mobile node information options MUST be consistent with
the solicitation message.
Zhang et al. Expires February 14, 2007 [Page 12]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
5.5. New options
There is a new mobile node information option used to carried the
mobile node and home agent address.
5.5.1. Mobile node information option
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ MN's Home Address +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Home Agent Address +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBD
Code
0 - successfully resolved the home agent that the mobile node
is registered to.
Zhang et al. Expires February 14, 2007 [Page 13]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
1 - unable to resolve the home agent that the mobile node is
registered to
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
MN's Home Address
Mobile node's address used to identify the mobile node that
needs it home agent located. In all messages, this field MUST
be present.
Home Agent Address
Home agent's address that mobile node registered to. In the
HALocReq and HASol message, this field MUST be zero. In HAAdv
message, this field MUST not be zero. In HALocRes message, if
the code field is 0, this field MUST not be zero; if the code
field is 1, this field MUST be zero.
6. Security Considerations
This document proposes new mobility message to resolve the HA that a
mobile node is registered to. The new messages are extended ICMPv6
message. All security provisions in [ICMPv6] apply equally to this
document.
7. IANA Considerations
IANA services are required for this document. The values for new
messages must be assigned from the ICMPv6 [ICMPv6] numbering space.
Type of Home agent located require message (HAlocReq)
Type of Home agent located response message (HAlocRes)
Type of Home agent solicitation message (HASol)
Type of Home agent advertisement message (HAAdv)
Zhang et al. Expires February 14, 2007 [Page 14]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
8. Acknowledgments
Zhang et al. Expires February 14, 2007 [Page 15]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
9. References
9.1. Normative References
[RFC-2119]Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[MIP6] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004.
[ICMPv6] A. Conta, and S. Deering, "Internet Control Message Protocol
(ICMPv6) for the Internet Protocol Version 6 (IPv6)", RFC
2463, December 1998
[ND] T. Narten, E. Nordmark, and W. Simpson, "Neighbor Discovery for
IP Version 6 (IPv6)", RFC 2461, December 1998
[ANYCAST] D. Johnson and S. Deering, "Reserved IPv6 Subnet Anycast
Addresses", RFC 2526, March 1999
9.2. Informative References
[GOALS] G. Giaretta, I. Guardini, E. Demaria, J. Bournelle, and R.
Lopez, "Goals for AAA-HA interface", draft-ietf-mip6-aaa-
ha-goals-00, (work in progress), April 2005
[DIAMETER] H. Tschofenig, T. Tsenov, G. Giaretta, and J. Bournelle,
"Mobile IPv6 Bootstrapping using Diameter", draft-
tschofenig-mip6-aaa-ha-diameter-01, October 23, 2005
[AUTH] Giaretta, G., "MIPv6 Authorization and Configuration based on
EAP", draft-giaretta-mip6-authorization-eap-02 (work in
progress), October 2004.
Author's Addresses
Jian Zhang
Huawei Technologies Co., LTD.
No. 3 Xinxi Road, Shangdi,
HaiDian District,
Beijing City,
The P.R.China
Email: hwzhj@huawei.com
Zhang et al. Expires February 14, 2007 [Page 16]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
Hongfei Chen
Huawei Technologies Co., LTD.
No. 3 Xinxi Road, Shangdi,
HaiDian District,
Beijing City,
The P.R.China
Email: chenhongfei@huawei.com
Robert Jaksa
FutureWei Technologies, Inc.
1700 Alma Drive, Suite 100
Plano, Texas 75075
Phone: +1 972-509-5599
Email: rjaksa@huawei.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
Zhang et al. Expires February 14, 2007 [Page 17]
Internet-Draft Find the HA that MNs Registered in MIPv6 August 2006
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Zhang et al. Expires February 14, 2007 [Page 18]