Network Working Group J. Jee, Editor Internet-Draft ETRI Expires: March 18, 2006 S. Park Samsung Electronics J. Cha ETRI September 14, 2005 16ng Problem Statement draft-jee-16ng-problem-statement-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 March 18, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document describes the IPv6 over IEEE 802.16(e) networks (16ng) problem statement. Jee, Editor, et al. Expires March 18, 2006 [Page 1] Internet-Draft 16ng Problem Statement September 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Jee, Editor, et al. Expires March 18, 2006 [Page 2] Internet-Draft 16ng Problem Statement September 2005 1. Introduction Broadband Wireless Access Network was invented to overcome the low bandwidth wireless communication which was not appropriate for the user requirements such as high quality data/voice service, fast mobility, wide coverage and etc. To achieve these requirements, the IEEE 802.16 Working Group on Broadband Wireless Access Standards develops standards and recommended practices to support the development and deployment of broadband Wireless Metropolitan Area Networks [IEEE802.16]. In addition, IEEE 802.16e supports mobility over IEEE 802.16 [IEEE802.16e] as an amendment of the IEEE 802.16 specification. Recently, much work is in progress by the WiMAX Forum. In particular, its NWG (Network Working Group) is responsible for the IEEE 802.16(e) network architecture (e.g., IPv4, IPv6, Mobility, Interworking with different networks, AAA, etc). The NWG is thus taking on work at layers above those defined by IEEE 802 standard (typically limited to the physical and link layers only). IEEE 802.16(e) is significantly different from existing wireless access technology such as IEEE 802.11, and there are lots of considerable aspects to be resolved by IETF when applying Internet Protocol Version 6 [RFC1883] for IEEE 802.16(e) link. This document will describe the problems introduced in deploying IPv6 over IEEE 802.16(e) networks. 2. Requirements 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] . 3. Problem Statement The first problem introduced in deploying IPv6 over IEEE 802.16(e) networks is that an IEEE 802.16(e) network currently does not provide native multicasting for IPv6 packet transfer. The IEEE 802.16's connection is a unidirectional mapping between BS (Base Station) and SS (Subscriber Station) medium access control peers for the purpose of transporting a service flow's traffic in point-to-point manner [IEEE802.16]. This lacking of facility for native multicasting for IPv6 packet transfer results in inappropriateness in applying conventional host-side operation of the standard IPv6 Neighbor Discover protocol specially regarding, address resolution, router discovery, duplicated address detection. Jee, Editor, et al. Expires March 18, 2006 [Page 3] Internet-Draft 16ng Problem Statement September 2005 The second problem introduced in deploying IPv6 over IEEE 802.16(e) networks is applying the stateless auto-configuration mechanism which is a key feature of IPv6 standard. Even though network nodes in IEEE 802.16(e) can configure its link local address using the 48-bit MAC address, they undergo in guaranteeing the uniqueness of the configured address because the standard IPv6 stateless auto- configuration [RFC2462] mandates the multicasting DAD procedure. The third problem introduced in deploying IPv6 over IEEE 802.16(e) networks is applying the Fast Handovers for Mobile IPv6 [RFC4068] owing to the difficulty in utilizing the layer 2 handover information. From RFC 4068, mobile node is recommended to send FBU (Fast Binding Update) message to the PAR (Previous Access Router) based on the accurate target BS information on the connected link to operate as predictive mode. In IEEE 802.16e [IEEE 802.16e], the mobile subscriber station decides the ultimate target base station and sends the MOB_HO-IND message to the serving BS to notify the decided target BS information which results in disabling any IPv6 packet transfer on that link. Therefore, fast handover processing needs to intervene between the layer 2's target decision and the MOB_HO-IND message transfer. Note that, this kind of intervention can be achieved only through special implementations probably delaying layer 2 processing. 4. Security Considerations TBD. 5. Acknowledgment Authors would like to express special thanks to IETF Mobility Working Group members of KWISF (Korea Wireless Internet Standardization Forum) for their efforts on this work. 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 6.2. Informative References [IEEE802.16] IEEE Std 802.16-2004, "IEEE Standard for Local and Jee, Editor, et al. Expires March 18, 2006 [Page 4] Internet-Draft 16ng Problem Statement September 2005 metropolitan area networks, Part 16: Air Interface for Fixed Broadband Wireless Access Systems", October 2004. [IEEE802.16e] IEEE P802.16e/D10, "Draft IEEE Standard for Local and metropolitan area networks, Amendment for Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands", Auguest 2005. [RFC1883] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 1883, December 1995. [RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998. [RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address Autoconfiguration", RFC 2462, December 1998. [RFC4068] Koodli, R., "Fast Handovers for Mobile IPv6", RFC 4068, July 2005. Jee, Editor, et al. Expires March 18, 2006 [Page 5] Internet-Draft 16ng Problem Statement September 2005 Authors' Addresses Junghoon Jee ETRI 161 Gajeong-dong, Yuseong-gu Daejeon, 305-350 KOREA Phone: +82-42-860-5126 Email: jhjee@etri.re.kr Soohong Daniel Park Samsung Electronics 416 Maetan-3dong, Yeongtong-gu Suwon, 442-742 KOREA Phone: +82-31-200-4508 Email: soohong.park@samsung.com Jaesun Cha ETRI 161 Gajeong-dong, Yuseong-gu Daejeon, 305-350 KOREA Phone: +82-42-860-5587 Email: jscha@etri.re.kr Jee, Editor, et al. Expires March 18, 2006 [Page 6] Internet-Draft 16ng Problem Statement September 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. Jee, Editor, et al. Expires March 18, 2006 [Page 7]