Mobile IP Working Group Alpesh Patel INTERNET DRAFT Kent Leung 25 July 2003 Cisco Systems Experimental Message Types for Mobile IPv4 draft-patel-mobileip-experimental-messages-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. Abstract Mobile IPv4 message types range from 0 to 255. This document reserves a message type for use by an individual, company, or organization for experimental purpose, to evaluate enhancements to Mobile IPv4 messages before formal standards proposal. Patel, Leung Expires 25 January, 2004 [Page 1] Internet Draft Experimental Message Types 25 July 2003 Table of Contents 1. Introduction..............................................2 2. Terminology...............................................2 3. Experimental Message......................................2 4. Mobility Entity Considerations............................4 5. IANA Considerations.......................................4 6. Security Considerations...................................4 7. Intellectual Property Rights..............................4 8. Acknowledgements..........................................4 9. References................................................4 10. Contact Information......................................5 Full Copyright Statement.....................................5 1. Introduction Mobile IPv4 message types range from 0 to 255. This document reserves a message type for use by an individual, company, or organization for experimental purpose, to evaluate enhancements to Mobile IPv4 messages before formal standards proposal. Without experimental message capability, one would have to select a type value from the range defined for IANA assignment, which may result in collision. To eliminate the collision possibility among vendors, the new experimental message contains the vendor/organization identifier to maintain their own message space. 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 [1]. EXP-MSG-TYPE: A message in the range [0-255] TBD by IANA for experimental use. 3. Experimental Message Since the nature and purpose of an experimental message cannot be known in advance, the structure is designed to avoid vendor overlap and provide opaque payload, which can be properly interpreted by the entity defining the message. Patel, Leung Expires 25 January 2004 [Page 2] Internet Draft Experimental Message Types 25 July 2003 These messages will be used between the mobility entities (Home Agent, Foreign Agent, and Mobile Node). Experimental messages SHOULD be authenticated using any of the authentication mechanism defined for Mobile IP ([2], [5]). This message MAY contain extensions defined in Mobile IP, including vendor specific extensions [4]. IP fields: Source Address Typically the interface address from which the message is sent. Destination Address The address of the agent or the Mobile Node. UDP fields: Source Port variable Destination Port 434 Mobile IP fields shown below follow the UDP header: 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 | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor/Org-ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opaque ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type EXP-MSG-TYPE (To be assigned by IANA) Reserved Reserved for future use. MUST be set to 0 on sending, MUST be ignored on reception. Vendor/Org-ID The high-order octet is 0 and the low-order 3 octets are the SMI Network Management Private Enterprise Code of the Vendor in network byte order, as defined in the Assigned Numbers RFC [3]. Opaque The Opaque is zero or more octets. Patel, Leung Expires 25 January 2004 [Page 3] Internet Draft Experimental Message Types 25 July 2003 4. Mobility Entity Considerations Mobility entities can send and receive experimental messages. Implementations that don't understand the message type or the Vendor/Org-ID SHOULD silently discard the message. 5. IANA Considerations IANA services are required for this draft. Since a new message type is needed to be reserved as experimental, a value must be assigned for EXP-MSG-TYPE from Mobile IP control message space. 6. Security Considerations Like all Mobile IP control messages, the experimental messages SHOULD be authenticated with at least one authenticator. Messages without a valid authenticator SHOULD be discarded. 7. Intellectual Property Rights The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 8. Acknowledgements TBD 9. References Patel, Leung Expires 25 January 2004 [Page 4] Internet Draft Experimental Message Types 25 July 2003 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] Perkins, C., "IP Mobility Support", RFC 3344, August 2002. [3] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994. [4] G. Dommety, K. Leung, "Mobile IP Vendor/Organization-Specific Extensions" RFC 3115, April 2001 [5] C. Perkins, P. Calhoun, "Mobile IPv4 Challenge/Response Extensions", RFC 3012, November 2000 10. Contact Information Questions and comments about this draft should be directed at the Mobile IPv4 working group: mip4@ietf.org Questions and comments about this draft may also be directed to the authors: Alpesh Patel Kent Leung Cisco Systems Cisco Systems 170 W. Tasman Drive, 170 W. Tasman Drive, San Jose, CA 95134 San Jose, CA 95134 USA USA Email: alpesh@cisco.com Email: kleung@cisco.com Phone: +1 408-853-9580 Phone: +1 408-526-5030 Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. 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 Patel, Leung Expires 25 January 2004 [Page 5] Internet Draft Experimental Message Types 25 July 2003 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. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Patel, Leung Expires 25 January 2004 [Page 6]