draft-ietf-mip6-vsm-00.txt   draft-ietf-mip6-vsm-01.txt 
MIP6 Working Group V. Devarapalli MIP6 Working Group V. Devarapalli
Internet-Draft Azaire Networks Internet-Draft Azaire Networks
Intended status: Standards Track A. Patel Intended status: Standards Track A. Patel
Expires: June 14, 2007 K. Leung Expires: August 25, 2007 K. Leung
Cisco Cisco
December 11, 2006 February 21, 2007
Mobile IPv6 Vendor Specific Option Mobile IPv6 Vendor Specific Option
draft-ietf-mip6-vsm-00.txt draft-ietf-mip6-vsm-01.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 36 skipping to change at page 1, line 36
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 June 14, 2007. This Internet-Draft will expire on August 25, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
There is a need for vendor specific extensions to Mobility Header There is a need for vendor specific extensions to Mobility Header
messages so that Mobile IPv6 vendors are able to extend the protocol messages so that Mobile IPv6 vendors are able to extend the protocol
for research or deployment purposes. This document defines a new for research or deployment purposes. This document defines a new
vendor specific mobility option. vendor specific mobility option.
Table of Contents Table of Contents
skipping to change at page 3, line 26 skipping to change at page 3, line 26
specific extensions to Mobility Header messages so that vendors are specific extensions to Mobility Header messages so that vendors are
able to extend the Mobile IPv6 protocol for research or deployment able to extend the Mobile IPv6 protocol for research or deployment
purposes. purposes.
This document defines a new mobility option, the Vendor Specific This document defines a new mobility option, the Vendor Specific
Mobility option, which can be carried in any Mobility Header message. Mobility option, which can be carried in any Mobility Header message.
The Vendor Specific mobility option MUST be used only with a Mobility The Vendor Specific mobility option MUST be used only with a Mobility
Header message. Mobility options, by definition, can be skipped if Header message. Mobility options, by definition, can be skipped if
an implementation does not recognize the mobility option type [2]. an implementation does not recognize the mobility option type [2].
The messages defined in this document can also be used for NEMO The messages defined in this document can also be used for NEMO [3]
implementations [3]. and Proxy MIPv6 [4] since these protocols also use Mobility Header
messages.
Vendor specific extensions to protocols can cause serious Vendor specific extensions to protocols can cause serious
interoperability issues if they are not used carefully. The vendor interoperability issues if they are not used carefully. The vendor
specific extensions MUST be standardized in the IETF if they are to specific extensions MUST be standardized in the IETF if they are to
be deployed in a large scale or if multiple vendors are involved in a be deployed in a large scale or if multiple vendors are involved in a
particular system or deployment. Experience has shown that vendor particular system or deployment. Experience has shown that vendor
specific extensions benefit from IETF review and standardization. specific extensions benefit from IETF review and standardization.
2. Terminology 2. Terminology
skipping to change at page 5, line 26 skipping to change at page 5, line 26
[2] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [2] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
7.2. Informative References 7.2. Informative References
[3] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, [3] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
"Network Mobility (NEMO) Basic Support Protocol", RFC 3963, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
January 2005. January 2005.
[4] Gundavelli, S., "Proxy Mobile IPv6",
draft-sgundave-mip6-proxymip6-01 (work in progress),
January 2007.
Authors' Addresses Authors' Addresses
Vijay Devarapalli Vijay Devarapalli
Azaire Networks Azaire Networks
4800 Great America Pkwy 4800 Great America Pkwy
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Email: vijay.devarapalli@azairenet.com Email: vijay.devarapalli@azairenet.com
skipping to change at page 7, line 7 skipping to change at page 7, line 7
Kent Leung Kent Leung
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: kleung@cisco.com Email: kleung@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property 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
 End of changes. 9 change blocks. 
12 lines changed or deleted 17 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/