draft-ietf-mip6-ha-switch-02.txt   draft-ietf-mip6-ha-switch-03.txt 
Mobile IPv6 B. Haley Mobile IPv6 B. Haley
Internet Draft Hewlett-Packard Internet Draft Hewlett-Packard
Document: draft-ietf-mip6-ha-switch-02.txt V. Devarapalli Document: draft-ietf-mip6-ha-switch-03.txt V. Devarapalli
Expires: June, 2006 Azaire Networks Intended status: Standards Track Azaire Networks
H. Deng Expires: September, 2007 H. Deng
Hitachi Hitachi
J. Kempf J. Kempf
DoCoMo USA Labs DoCoMo USA Labs
December 2006
Mobility Header Home Agent Switch Message Mobility Header Home Agent Switch Message
draft-ietf-mip6-ha-switch-02.txt draft-ietf-mip6-ha-switch-03.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 5, line 32 skipping to change at page 5, line 32
+ + + +
. . . .
. Mobility options . . Mobility options .
. . . .
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
# of Addresses # of Addresses
A 16-bit unsigned integer indicating the number of IPv6 home agent An 8-bit unsigned integer indicating the number of IPv6 home agent
addresses in the message. If set to zero, the mobile node MUST addresses in the message. If set to zero, the mobile node MUST
perform home agent discovery. perform home agent discovery.
Reserved Reserved
16-bit field reserved for future use. The value MUST be 8-bit field reserved for future use. The value MUST be initialized
initialized to zero by the sender, and MUST be ignored by the to zero by the sender, and MUST be ignored by the receiver.
receiver.
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 of 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. with 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.
skipping to change at page 10, line 26 skipping to change at page 10, line 26
confidentiality protection. confidentiality protection.
10. References 10. References
10.1 Normative References 10.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
[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
[3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and Chowdhury, K., [3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and Chowdhury, K.,
"Authentication Protocol for Mobile IPv6", RFC 4285, January, "Authentication Protocol for Mobile IPv6", RFC 4285, January,
2006. 2006.
10.2 Informative references
[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-01.txt, October, 2006.
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
skipping to change at page 11, line 15 skipping to change at page 11, line 15
Author's Addresses Author's Addresses
Brian Haley Brian Haley
Hewlett-Packard Company Hewlett-Packard Company
110 Spitbrook Road 110 Spitbrook Road
Nashua, NH 03062, USA Nashua, NH 03062, USA
Email: brian.haley@hp.com Email: brian.haley@hp.com
Vijay Devarapalli Vijay Devarapalli
Azaire Networks Azaire Networks
4800 Great America Pkwy 3121 Jay Street
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Email: vijay.devarapalli@azairenet.com Email: vijay.devarapalli@azairenet.com
James Kempf James Kempf
DoCoMo USA Labs DoCoMo USA Labs
181 Metro Drive 181 Metro Drive
Suite 300 Suite 300
San Jose, CA 95110 USA San Jose, CA 95110 USA
Email: kempf@docomolabs-usa.com Email: kempf@docomolabs-usa.com
Hui Deng Hui Deng
Research & Development Center Research & Development Center
Hitachi (China), Investment Ltd. Hitachi (China), Investment Ltd.
Beijing Fortune Bldg. 1701, 5 Dong San Huan Bei-Lu Beijing Fortune Bldg. 1701, 5 Dong San Huan Bei-Lu
Chao Yang District, Beijing 100004, China Chao Yang District, Beijing 100004, China
Email: hdeng@hitachi.cn Email: hdeng@hitachi.cn
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
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.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 12, line 11 skipping to change at page 12, line 24
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
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 Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 12 change blocks. 
31 lines changed or deleted 29 lines changed or added

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