IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-10-0061-02-srho Title: IETF NETEXT Overview and Relationship with 802.21c Date Submitted: May 10, 2010 Presented at IEEE 802.21 session #38 in Bangalore, India Authors or Source(s):  Juan Carlos Zuniga (InterDigital) Antonio de la Oliva, Carlos Bernardos (UC3M) Telemaco Melia (Alcatel-Lucent) Abstract: Overview of IETF activities in the NETEXT group and the relationship with current 802.21c activities 21-10-0061-02-srho

IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf>  21-10-0061-02-srho

IETF NETEXT Overview and Relationship with 802.21c 21-10-0061-02-srho

Proxy Mobile IP Proxy Mobile IP standardized in NETLMM Provides roaming within a PMIP domain without changing IP address It provides also a limited multi-homing support to multi-mode devices Initial assumption Changes in the IP stack are undesirable How do we provide more advance features while using PMIP, without changing the IP stack? Inter-access handover Flow mobility 21-10-0061-02-srho

NETEXT Working on PMIP extensions: Localized routing Bulk refresh LMA redirection Radius Extensions Hiding access technology changes from IP 21-10-0061-02-srho

Hiding L2 changes to the IP stack Layer 2 techniques hiding the actual physical interface being used by the IP layer Link layer support Logical interface Layer 2.5 Assumption: an IP layer interface is able to simultaneously and/or sequentially attach to different MAGs Applicability statement Draft bernardos http://tools.ietf.org/html/draft-bernardos-netext-ll-statement-01 21-10-0061-02-srho

Logical Interface Solutions bonding multiple interfaces so they appear to the IP layer as a single interface Application sockets are bond to this logical interface It allows: Simultaneous use of multiple interfaces Fail over mechanisms Simultaneous attachment to different media One Interface to rule them all! APP 1 APP 2 APP 3 TCP/IP Logical Interface WiFi WiMAX 3GPP 21-10-0061-02-srho

Active TCP/IP Interface Layer 2.5 Single Radio Handover application There is only one active interface at IP layer 802.21 can help PMIP when dealing with inter-access technology changes and mobile-based triggers APP 1 APP 2 APP 3 IEEE 802.21 Active TCP/IP Interface TCP/IP TCP/IP TCP/IP WiFi WiMAX 3GPP 21-10-0061-02-srho

Intersection between NETEXT and IEEE 802.21 802.21 can help PMIP for inter-access technology handovers Flow mobility is a network-based solution and the mobile can only be reactive to changes from the LMA 802.21c can be used as a tool to communicate link layer changes from the mobile to the LMA 802.21 + RFC5677 can provide the required link-layer information over a L3 transport A solution would greatly benefit the single radio handover work being carried out by 802.21c 21-10-0061-02-srho

PMIP+IEEE 802.21 (Future 802.21c?) PoS at LMA Mobility of the user can be managed in one central point, the LMA 802.21 can be used to transport link layer identifiers, link layer triggers, etc. One PoS located in the LMA Just one subscription is required for all interfaces and IP flows 21-10-0061-02-srho