INTERNET DRAFT Mohamed M Khalil Category: Standards Track Emad Qaddoura Title: draft-ietf-mobileip-gnaie-05.txt Haseeb Akhtar Date: October 2001 Nortel Networks Expires: March 2002 Pat R. Calhoun Black Storm Networks Generalized NAI (GNAI) Extension for Mobile IPv4 Status of this Memo This document is a submission by the mobile-ip Working Group of the Internet Engineering Task Force (IETF). Comments should be submitted to the mobile-ip@sunroof.eng.sun.com mailing list. Distribution of this memo is unlimited. 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. Copyright (C) The Internet Society 2001. All Rights Reserved. Abstract The IP Mobility Support for IPv4, revised [4] specification defines a new extension header format, that is intended to extend the Mobile IP extension address space. This document defines the Generalized Network Access Identifier (GNAI) extension, which SHOULD be used by any Mobile IP extension specifying an extension containing an NAI. Khalil, Qaddoura, Akhtar, Calhoun [Page 1]
INTERNET DRAFT October 2001 Table of Contents 1.0 Introduction 2.0 Specification Language 3.0 Generalized NAI (GNAI) Extension 3.1 Processing Of the GNAI Extension 4.0 IANA Considerations 5.0 Security Considerations 6.0 References 7.0 Authors' Address 8.0 Full Copyright Statement 1.0 Introduction The IP Mobility Support for IPv4, revised specification [4] defines a new extension header format, that is intended to extend the Mobile IP extension address space. The use of a Network Access Identifier for Mobile Nodes for Mobile IPv4 is specified in [2]. This work extends this idea by specifying NAIs for other Mobile IPv4 network elements such as the Foreign Agent and the Home agent in an extension format that optimizes the number space for new extensions. This specification does not define a sub-type to carry a Mobile Node's NAI, since this is already defined in [2]. 2.0 Specification Language 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]. 3.0 A Generalized NAI (GNAI) Extension This section defines the GNAI Extension, used by any extension that must carry data in the format of an NAI [2]. This extension may be carried by Registration Request and Reply messages. 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 | Sub-Type | NAI ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type (Type to be assigned by IANA) (skippable) [4] Length 8-bit unsigned integer. Length of the extension, in octets, excluding the extension Type and the extension Length fields. This field MUST be set to 1 plus the total length of the NAI field. Khalil, Qaddoura, Akhtar, Calhoun [Page 2]
INTERNET DRAFT October 2001 Sub-Type This field describes the type of the entity which owns the NAI. The following subtypes are defined: 1 HA_NAI 2 FA_NAI NAI Contains the NAI [3] in a string format. 3.1 Processing of GNAI Extension When a mobile node or home agent adds a GNAI extension to a registration message, the extension MUST appear prior to any authentication extensions. In the event the Foreign Agent adds an GNAI extension to a registration message, the extension MUST appear prior to any authentication extensions added by the FA. 4.0 IANA Considerations The value assigned to the Generalized NAI extension, specified in section 3.0, MUST be from the IANA number space for mobile IPv4 skippable extensions. This value MUST NOT conflict with any value assigned to RFC 3024[6] RFC 2356 [7], RFC 3012 [8], RFC 3115 [9]. 5.0 Security Considerations This specification introduces new Mobile IP extensions that are used to carry mobility agent identities, in the form of Network Access Identifiers. It is assumed that the Mobile IP messages that would carry these extensions would be authenticated in the manner that is described in [4], or any follow-on authentication mechanisms. Therefore, this specification does not lessen the security of Mobile IP messages. It should be noted, that the identities sent in the extensions specified herein MAY be sent in the clear over the network. However, the authors do not envision that this information would create any Khalil, Qaddoura, Akhtar, Calhoun [Page 3]
INTERNET DRAFT October 2001 security issues. 6.0 References [1] Scott Bradner. Key words for use in RFCs to Indicate Requirement Levels. RFC 2119, March 1997. [2] Calhoun, Perkins. Mobile IP Network Access Identifier Exten- sion for IPv4. RFC 2794, March 2000. [3] Aboba, Beadles. The Network Access Identifier. RFC 2486, January 1999 [4] C. Perkins, editor. IP Mobility Support for IPv4, revised draft-ietf-mobileip-rfc2002-bis-08.txt, 19 September 2001. [5] J. Reynolds, J. Postel. Assigned Numbers. STD 2, RFC 1700, USC/Information Sciences Institute, October 1994. [6] G. Montenegro. Reverse Tunneling for Mobile IP, revised. RFC RFC3024, January 2001. [7] G. Montenegro, V. Gupta. Sun's SKIP Firewall Traversal for Mobile IP. RFC 2356, June 1998. [8] C. Perkins, P. Calhoun. Mobile IPv4 Challenge/Response Extensions. RFC 3012 , November 2000. [9] G. Dommety, K. Leung. Mobile IP Vendor/Organization-Specific Extensions. RFC 3115, April 2001. [10] T. Narten, H, Alvestrand. Guidelines for Writing an IANA Con- siderations Section in RFCs. BCP 26, RFC 2434, October 1998 Khalil, Qaddoura, Akhtar, Calhoun [Page 4]
INTERNET DRAFT October 2001 7.0 Authors' Address Questions about this memo can be directed to: Mohamed M Khalil Wireless Technology Labs Nortel Networks 2221 Lakeside Blvd. Richardson, TX 75082-4399 USA Phone: 1-972-685-0564 E-Mail: mkhalil@nortelnetworks.com Emad Qaddoura Wireless Technology Labs Nortel Networks 2221 Lakeside Blvd. Richardson, TX 75082-4399 USA Phone: 1-972-684-2705 E-Mail: emadq@nortelnetworks.com Haseeb Akhtar Wireless Technology Labs Nortel Networks 2221 Lakeside Blvd. Richardson, TX 75082-4399 USA Phone: 1-972-684-8850 E-Mail: haseeb@nortelnetworks.com Pat R. Calhoun Black Storm Networks 250 Cambridge Avenue, Suite 200 Palo Alto, California, 94306 USA Phone: +1 650-617-2932 Email: pcalhoun@bstormnetworks.com Fax: +1 650-786-6445 Khalil, Qaddoura, Akhtar, Calhoun [Page 5]
INTERNET DRAFT October 2001 8.0 Full Copyright Statement Copyright (C) The Internet Society (2001). 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 docu- ment 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 develop- ing 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 lim- ited 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 DIS- CLAIMS 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. Khalil, Qaddoura, Akhtar, Calhoun [Page 6]
