Network Working Group Jayshree. Bharatia Internet-Draft Nortel Networks Expires: January 7, 2006 Kuntal. Chowdhury Starent Networks Avi. Lior Bridgewater Systems Lila. Madour Ericsson Canada July 6, 2005 MIPv4 Extension for Configuration Options Exchange draft-bharatia-mip4-gen-ext-00.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. This Internet-Draft will expire on January 7, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract IP Mobility support for IPv4 [RFC3344] defines a short and skippable extension header format intended to extend the Mobile IP extension address space. Based on the format presented in RFC3344, this draft Bharatia, et al. Expires January 7, 2006 [Page 1] Internet-Draft July 2005 defines a Mobile IP extension for configuration options, which should be used by any Mobile IP entity to exchange information of the network entities like DNS server address, previous Foreign Agent (FA) address etc. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Glossary of Terms . . . . . . . . . . . . . . . . . . . . 3 1.2 Conventions used in this document . . . . . . . . . . . . 3 2. Mobile IP Extension for Configuration Options Exchange . . . . 4 3. Processing of Configuration Options Extension . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . 11 Bharatia, et al. Expires January 7, 2006 [Page 2] Internet-Draft July 2005 1. Introduction This draft uses short and skippable extension header format defined by [RFC3344] and offers a generalized solution to exchange information like address of DNS server, address of previous FA etc. 1.1 Glossary of Terms FA Foreign Agent HA Home Agent MN Mobile Node HA Home Agent DNS Domain Name Server DHCP Dynamic Host Configuration Protocol SIP Session Initiation Protocol 1.2 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 [RFC2119]. Bharatia, et al. Expires January 7, 2006 [Page 3] Internet-Draft July 2005 2. Mobile IP Extension for Configuration Options Exchange The Mobile IP extension SHALL have the format shown in this section to carry information like IPv4 address. Note that this extension MAY be included as a part of Mobile IP Registration Request. If this extension is requested in the Registration Request, the network entity (mentioned in the Entity-Type field) SHOULD provide requested information in the Registration Reply. If multiple Sub-Types are needed in the same message, the configuration options header SHOULD be repeated for each Sub-Type. 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 | Length | Entity-Type | Sub-Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Data +-+-+-+-+-+-... Figure 1: Configuration Options Exchange Extension Type IPV4-CONF-OPTIONS-EXT-TYPE=TBD. This extension value will be assigned by IANA from the numbering space defined in [RFC3344] for skippable extensions. Length Represents 8-bit unsigned integer (in octets). Length of the extension includes the extension type and the extension Length fields. This field MUST be set to 1 plus the total length of the Data and Entity-Type fields. Sub-Type This field describes the type of entity, whose information is requested from the network entities (mentioned in Entity-Type field) when used in a configuration options extension for Registration Request. But it describes the type of entity, whose information is included in Data field when used in a configuration options extension for Registration Reply. Currently the following types are defined: PRIMARY-DNS-SERVER = TBD SECONDARY-DNS-SERVER = TBD Bharatia, et al. Expires January 7, 2006 [Page 4] Internet-Draft July 2005 PREVIOUS-FOREIGN-AGENT = TBD PRIMARY-SIP-SERVER = TBD SECONDARY-SIP-SERVER = TBD DHCP-SERVER = TBD MULTIMEDIA-MESSAGING-SERVER = TBD BROADCAST-MULTICAST-CONTROL-SERVER = TBD Entity-Type This field in a configuration options extension for Registration Request includes the type of the network entity from whom the information is requested. When this field is included in the configuration options extension for Registration Reply, it refers to the network entity that inserts the Data field. Currently the following types are defined: HOME-AGENT = TBD FOREIGN-AGENT = TBD Data This field is inserted in a Registration Reply by the network entity mentioned in the Entity-Type of the Registration Request. This field represents the data of the network entity mentioned in the Sub-Type. Bharatia, et al. Expires January 7, 2006 [Page 5] Internet-Draft July 2005 3. Processing of Configuration Options Extension When a network entity (mentioned in the extension format of the Entity-Type) adds a configuration options extension to a Registration Request or Registration Reply message, this extension MUST appear prior to any authentication extensions added by that entity. Bharatia, et al. Expires January 7, 2006 [Page 6] Internet-Draft July 2005 4. IANA Considerations This draft defines new Mobile IPv4 extension of types IPV4-CONF- OPTIONS-EXT-TYPE as defined in Section 2 of this document. This value MUST be assigned by IANA from the Mobile IP numbering space for skippable extensions. Additionally, unique values MUST be assigned to each member of the Sub-Type and Entity-Type fields. Bharatia, et al. Expires January 7, 2006 [Page 7] Internet-Draft July 2005 5. Security Considerations There are no additional security aspects imposed by this document in addition to the one defined in [RFC3344]. Bharatia, et al. Expires January 7, 2006 [Page 8] Internet-Draft July 2005 6. Acknowledgments Authors like to thank Curtis Provost and Tom Hiller for their valuable input to this document. 7. References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002. Authors' Addresses Jayshree Bharatia Nortel Networks 2221, Lakeside Blvd Richardson, TX 75082 Phone: +1 972-684-5767 Email: jayshree@nortelnetworks.com Kuntal Chowdhury Starent Networks 30 International Place Tewksbury, MA 01876 Phone: +1 214-550-1416 Email: kchowdhury@starentnetworks.com Avi Lior Bridgewater Systems 303 Terry Fox Drive, Suite 100 Ottawa, Ontario, Canada K2K 3J1 Phone: +1 613-591-6655 Email: avi@bridgewatersystems.com Bharatia, et al. Expires January 7, 2006 [Page 9] Internet-Draft July 2005 Lila Madour Ericsson Canada 8400 Decarie, TMR Quebec, Canada H4P 2N2 Phone: +1 514-345-7900 Email: Lila.Madour@ericsson.ca Bharatia, et al. Expires January 7, 2006 [Page 10] Internet-Draft July 2005 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 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 (2005). 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. Bharatia, et al. Expires January 7, 2006 [Page 11]