IETF NETLMM Working Group Vijay Raman Internet Draft Anand Bedekar Ajoy Singh Suresh Kalyanasundaram draft-raman-netlmm-additional-req-00.txt Motorola Expires: August 2006 February 2006 A Proposal for a Requirement for IP Local Mobility 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 To view the list of Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2006). Abstract In draft-kempf-netlmm-nohost-req-01.txt, a set of requirements for a protocol for localized mobility management has been described. In this draft, we propose to include an additional requirement that components of existing IETF protocols should be reused wherever possible to avoid extensive standardization activity and to enable reuse of existing IETF-compliant protocol implementations. Raman Expires August 27, 2006 [Page 1] Internet-Draft Requirement for IP Local Mobility February 2006 TABLE OF CONTENTS 1. ADDITIONAL NETLMM REQUIREMENT..................................2 2. SECURITY CONSIDERATIONS........................................3 3. IANA CONSIDERATIONS............................................3 4. NORMATIVE REFERENCES...........................................3 5. INFORMATIVE REFERENCES.........................................3 6. AUTHORS' ADDRESSES.............................................3 IPR STATEMENTS....................................................4 Disclaimer of Validity............................................5 COPYRIGHT NOTICE..................................................5 Acknowledgment....................................................5 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]. 1. ADDITIONAL NETLMM REQUIREMENT In draft-kempf-netlmm-nohost-req-01.txt [2], a set of requirements for a protocol for localized mobility management has been described. We propose that the following requirement be added as an additional requirement for the localized mobility management protocol. We also propose that the gap analysis of existing global mobility management protocols in Section 3 of [2] should take into consideration the following requirement. Use of IETF-standardized components (Requirement #10) In many ways, the functionality expected of a protocol for local mobility management is very similar to existing protocols that have already been the subject of considerable work in IETF, such as, Mobile IPv6 [3], Fast Mobile IPv6 [4], and Hierarchical Mobile IPv6 [5]. While these protocols may not, in their entirety, satisfy the requirements being laid out in [2], components of these protocols and functional entities defined therein should be used wherever applicable, to the extent possible, in order to avoid duplicating the work that has already been done. The requirement is that a local mobility management solution should use protocols (or components of protocols) and functional elements Raman Expires August 27, 2006 [Page 2] Internet-Draft Requirement for IP Local Mobility February 2006 that have already been defined in an IETF RFC to the extent possible. Preference should be given to components of protocols that are defined in IETF standards-track or internet standard RFCs. 2. SECURITY CONSIDERATIONS None. 3. IANA CONSIDERATIONS None. 4. NORMATIVE REFERENCES [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] J. Kempf et al., " Requirements and Gap Analysis for IP Local Mobility ", draft-kempf-netlmm-nohost-req-01.txt, January 2006. 5. INFORMATIVE REFERENCES [3] D. Johnson et al., "Mobility Support in IPv6", RFC 3775, June 2004 [4] R. Koodli, Ed., "Fast Handovers for Mobile IPv6", RFC 4068, July 2005 [5] H. Soliman et al., "Hierarchical Mobile IPv6 Mobility Management (HMIPv6)", RFC 4140, August 2005 6. AUTHORS' ADDRESSES Vijay Raman Motorola India Electronics Limited 66/1, Plot No. 5, Bagmane Tech Park CV Raman Nagar Post Bangalore 560093 Phone: +91-80-26012308 Email: vijayraman@motorola.com Anand Bedekar Motorola Inc 1501 West Shure Dr, Arlington Heights, IL 60004, Raman Expires August 27, 2006 [Page 3] Internet-Draft Requirement for IP Local Mobility February 2006 USA Phone: +1 847-632-3046 Email: anand.bedekar@motorola.com Ajoy Singh Motorola Inc 1501 West Shure Dr, Arlington Heights, IL 60004, USA Phone: +1 847-632-6941 Email: asingh1@email.mot.com Suresh Kalyanasundaram Motorola India Electronics Limited 66/1, Plot No. 5, Bagmane Tech Park CV Raman Nagar Post Bangalore 560093 Phone: +91-80-26012308 Email: Suresh.Kalyanasundaram@motorola.com IPR STATEMENTS 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. Raman Expires August 27, 2006 [Page 4] Internet-Draft Requirement for IP Local Mobility February 2006 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 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 NOTICE "Copyright (C) The Internet Society (2006). All Rights Reserved. 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 translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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." Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Raman Expires August 27, 2006 [Page 5]