1. IPv6 이동성기술 표준화 동향 - 네트워크 기반 이동성 관리 기술 중심 - Youn-Hee Han yhhan@kut.ac.kr Korea University of Technology and Education Laboratory of Intelligent Networks http://link.kut.ac.kr 2010.08.31

2. Horizontal Handover Vertical Handover Multiple Interface Management Multiple Flow Management A handover is initiated when mobile device exits the boundaries of an administrative domain. Single interface is used. A mobile device does need to move in order to initiate a handover. Multiple interfaces are required, but use one interface at a time. Simultaneous use of multiple interfaces and access networks. Association of an application with an interface Ability to split individual flows between links with respect to the requirements of the flows and the user preferences Complexity Level Host-based IP Mobility Network-based IP Mobility Mobility Support in IPv6 [RFC 3775, June 2004] Hierarchical Mobile IPv6 [RFC 4140, Aug. 2005] Mobile IPv6 Support for Dual Stack Hosts and Routers [RFC 5555, June 2009] Fast Handovers for Mobile IPv6 [RFC 4068, July 2005] Multiple Care-of Addresses Registration [RFC 5648, Oct. 2009] Flow Bindings in Mobile IPv6 and NEMO Basic Support [draft-ietf-mext-flow-binding-14] Traffic Selectors for Flow Binding [draft-ietf-mext-binary-ts-04] Proxy Mobile IPv6 [RFC 5213, Aug. 2008] IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-14] Logical Interface Support for multi- mode IP Hosts [draft-melia-netext-logical-interface- support-01] Multiple Care-of Addresses Registration & Flow Bindings in Proxy Mobile IPv6 [draft-bernardos-netext-pmipv6- flowmob-00] [ 관련 WG: MEXT, MIPSHOP, NETEXT - 2010 년 8 월 현재 ] IETF Core Standards for IP Mobility Management 2/24

3. MIPv6/DSMIPv6 Deployment Host-based IP Mobility (MIPv4/MIPv6/DSMIPv6) has not been widely deployed due to several factors Implementation issues  IPsec and IKEv1  Too heavy specification to be implemented at a small terminal RFC 3344 (MIPv4): 99 pages, RFC 3775 (MIPv6): 165 pages Deployment issues  Negligible deployment of IPv6  No stable MIPv4/v6 stack executed in Microsoft Windows OS Operational issues  Battery problem  Layer 3 signalling via radio link  waste of air resource Layer 8 issues (Financial/Human/Political/FUD/…)  Many operators elected to create their own protocols (eg. GTP), or They picked other IETF mobility protocols (Proxy MIP etc.)  Money! 3/24

4. Recent IETF Activity of Host-based IP Mobility Criticism about Mobile IPv6 Create “Simplified Mobile IPv6” (?) 4/24 “Several SDOs have considered MIP6 and DSMIP6 as a solution for interworking and mobility between different access technologies and only 3GPP has adopted it in a very limited manner for Rel 8 (for use on the S2c interface) with the likelihood of it being actually deployed quite low (IMO).” - IETF MEXT WG chair (2010.03.04) “My opinion as a result of implementation experience is that MIP6/DSMIP6 can be significantly simplified, especially the security architecture.” - IETF MEXT WG chair (2010.03.04)

5. Proxy Mobile IPv6 (PMIPv6) Proxy Mobile IPv6 [IETF RFC 5213, August 2008] LMM (Localized Mobility Management) Domain MAG LMA Proxy Binding Update/Ack. (PBU/PBA) Control messages exchanged by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA Home Network Proxy Care of Address (Proxy-CoA) The address of MAG That will be the tunnel end-point IP Tunnel IP-in-IP tunnel between LMA and MAG MAG LMA: Localized Mobility Agent MAG: Mobile Access Gateway LMA Address (LMAA) MN’ Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain That will be the tunnel entry-point MN’s Home Network (Topological Anchor Point) MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 movement 5/24

6. RA*: MN 의 Prefix 를 Policy Store 에서 수신한 경우의 Router Advertisement RA**: MN 의 Prefix 를 LMA 에서 수신한 경우의 Router Advertisement MNMAGAAA&Policy StoreLMACN MN Attachment AAA Query with MN-ID AAA Reply with Profile RA* PBU with MN-ID, Home Network Prefix option, Timestamp option PBA with MN-ID, Home Network Prefix option RA** [MN-HoA:CN](data) [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data) Tunnel Setup PBU: Proxy Binding Update PBA: Proxy Binding Ack. DHCP Server DHCP Request DHCP Response DHCP Request DHCP Response Optional 6/24 PMIPv6 Operation Flow

7. 7/24 Home in Any Place MAG sends the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters MAG will emulate the home link on its access link. RA Unicast RA should be UNICASTed to an MN It will contain MN’s Home Network Prefix  Per-MN Prefix Any MN is just a IPv6 host Any MN is just a IPv6 host with its protocol operation consistent with the base IPv6 specification. M:1 Tunnel LMA-MAG tunnel is a shared tunnel among many MNs. One tunnel is associated to multiple MNs’ Binding Caches. PMIPv6 Features

8. PMIPv6 in 3GPP LTE/EPC Proxy Mobile IPv6 over LTE AAA/ Policy Server UE S-GW/(MAG) GTP-U Tunnel P-GW/LMA IP-in-IP Tunnel eNodeB P-GW: access gateway towards Packet Data Networks (similar to the GGSN) - PMIPv6 will be mainly used for inter-system handovers (i.e. handovers between 3GPP and non-3GPP accesses) Ref.] I. Guardini et al., “Mobile IPv6 deployment opportunities in next generation 3GPP networks,” 16 th IST Mobile&Wireless Communication Summit, Budapest, Hungary 1-5, July 2007 Optional! 8/24

9. LMA Proxy Mobile IPv6 over LTE Vertical handover scenario PMIPv6 in 3GPP LTE/EPC 9/24

10. Dual-Stack Support in Proxy MIPv6 IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] PMIPv6 기반 IPv6/IPv4 Transport 지원 + IPv6/IPv4 Home Address Mobility 지원 DS-MIPv6 와 같은 설계 목표와 원칙 DS(Dual Stack)-PMIPv6 가 고려하는 시나리오 Dual Stack Support in PMIPv6 Cellular IP network WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 Private IPv4 NAT AAA DS-PMIPv6 LMA IPv4 IPv6 IPv4 Application (VoD, IP-Phone…) IPv6 Application (VoD, IP-Phone…) MN 10/24 DS-PMIPv6 MAG

11. Operation of DS-PMIPv6 PMIPv6’s Dual-Stack Support Dual Stack LMA Only-IPv6 enabled (LMMAv6) Dual Stack MN or IPv4 MN PBU (HoAv6, Proxy CoAv6, HoAv4) HoAv4 and HoAv6 Proxy CoAv6 [Mobility Binding] IPv6 Tunnel (LMAAv6  Proxy CoAv6) IPv4 traffic CNv4  HoAv4 IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv6 enabled (Proxy CoAv6) Dual Stack LMA Only-IPv4 enabled (LMAAv4) Dual Stack MN or IPv4 MN PBU (HoAv6, Proxy CoAv4, HoAv4) HoAv4 and HoAv6 Proxy CoAv4 [Mobility Binding] IPv4 Tunnel (LMAAv4  Proxy CoAv4) IPv4 traffic CNv4  HoAv4 IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv4 enabled (Proxy CoAv4) 11/24

12. DS-PMIPv6 테스트베드 -1 MN has Dual Stack and both addresses are always enabled ETRI (2007,2008) SSID: PMIP1 SSID: PMIP2 SSID: PMIP3 MAG1 ra0) 192.168.101.1 3ffe:1:1::1/64 fe80::1 eth0) 3ffe:1::2/64 MAG2 ra0) 192.168.102.1 3ffe:1:2::1/64 fe80::1 eth0) 192.168.1.2 ra0) 10.0.1.1 3ffe:1:3::1/64 fe80::1 eth0) 10.0.0.1 V6 network V4 network 초기 실행 : v6 VoD Client 초기 실행 : v4 VoD Client LMA CN NAT 192.168.1.3 eth0) 192.168.1.1 3ffe:1::1/64 eth1) 192.168.2.1 3ffe:2::1/64 eth0) 192.168.2.2 3ffe:2::2/64 V4/V6 network Private V4 network MAG3 LMA 가 MN 에게 할당할 Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 v4/v6 VoD Server 12/24

13. KT (2007): DS-PMIPv6 with Only Private IPv4 Network and IPv4 Application LMA (PC0) VoD (PC4) Subnet 4 NAT1 NAT2 MAG1 (PC1) MAG2 (PC2) Subnet 1Subnet 2 MAG3 (PC3) Subnet 3 Notebook1Notebook2Notebook1 802.11g802.11a 192.168.1.2 192.168.3.2 192.168.1.1 192.168.3.1 192.168.4.1192.168.4.2 10.0.1.110.0.2.1 10.0.1.210.0.2.2 10.0.1.1 10.0.1.2 10.0.101.110.0.102.1 10.0.101.1 192.168.5.1 192.168.5.2 192.168.5.1 DS-PMIPv6 테스트베드 -2 13/24

14. Test Results with Heavy Traffic (presented at MobiWorld 2008 conference)  Encoding Rate: 2Mbps UDP Throughput of MIPv6UDP Throughput of PMIPv6 Test: MIPv6 vs. PMIPv6 14/24

15. PMIPv6 Handover Optimization 네트워크 기반의 IP Handover 기술 및 최적화 Basic Standard  Proxy Mobile IPv6 (PMIPv6) – RFC 5213 Base Protocol IETF 의 네트워크 기반 핸드오버 최적화 기술  Fast Handovers for Proxy Mobile IPv6 (F-PMIPv6) draft-ietf-mipshop-pfmipv6-14.txt (May 2010) 핸드오버시 라우터간 터널링 기술  Transient Binding for Proxy Mobile IPv6 (TB-PMIPv6) draft-ietf-mipshop-transient-bce-pmipv6-05.txt (Jan 2010) Make-before-break 핸드오버시 두 개의 인터페이스를 동시에 사용할 수 있는 기술 L2 handover MD ( 필요없음 ), DAD ( 생략가능 ), Network-based BU time Layer 2+3 Latency [PMIPv6] 15/24

16. F-PMIPv6 Procedure Fast Handover for PMIPv6 Access technology specific (out of scope) Tunnel Setup NMAG requests PMAG to forward or buffer the packets & Tunnel Setup (When?  out of scope) Forwarding (Optionally Buffering at NMAG) Access technology specific (out of scope) 16/24

17. PMIPv6 vs. F-PMIPv6 Fast Handover for PMIPv6 HO-INITIATE HO-COMPLETE (Link-UP) Link-specific Handover MN PBUPBAck LMA Old MAG New MAG Total Handover Latency Link-specific Handover MN PBUPBAck LMA Old MAG New MAG Total Handover Latency HI HAck Buffering PMIPv6 F-PMIPv6 HO-INITIATE HO-COMPLETE (Link-UP) 17/24

18. Multihoming Scenario Works in Host-based MIPv6 “draft-ietf-mext-flow-binding-14”  It allows a mobile node (MN)/mobile router (MR) to bind a particular flow to a particular CoA with HA and CN. “draft-ietf-mext-binary-ts-04”  It defines the formats for IPv4 and IPv6 Traffic Selector sub-options defined in “draft-ietf-mext-flow-binding-06.txt”. 18/24

19. Supported Scenario Scenario 1: Setting up Mobility Sessions on Demand  Create additional mobility sessions via a new interface on demand  A new mobility session with a new prefix is created Scenarios for Network-based Flow Mobility 19/24 WiBro MAG LMA PBU (HI=1) MAG 3G MN 3GWiBro MAG LMA PBU (HI=1) MAG MN 3GWiBro 3G 다른 인터페이스의 스위치 를 올려서 단순하게 접속만 시도했군 ! 세션이동성은 없고 … Mobile IPTV flow VoIP flow Mobile IPTV flow VoIP flow HTTP flow

20. Supported Scenario Scenario 2: Move some of flows to a new interface  If another access is enabled on the MN, some of the existing flows could be moved over, to achieve, e.g., load balancing and better user experience Scenarios for Network-based Flow Mobility 20/24 MAG LMA PBU (HI=2) MAG LMA PBU (HI=1) MAG MN 3G 새로운 인터페이스로 세션을 이동하고 있네 ? Vertical 핸드오버군 ! MN 3GWiBro VoIP flow Mobile IPTV flow WiBro3GWiBro3G WiBro Mobile IPTV flow VoIP flow

21. Logical Interface over Multiple Physical Interfaces draft-melia-netext-logical-interface-support-01 Virtual Interface: term in implementation perspective Features  It provide a single interface view to the layers above IP. Therefore, it also allow hiding access technology changes or movement from host IP layer.  Resolve the problem that each physical interface should be assigned different IP addresses. That is, only logical interface is assigned all addresses Logical Interface 21/24 PI1 [IEEE 802.11]PI2 [3GPP]PI3 [IEEE 802.16]… Data Link Layer Virtual InterfaceFlow Interface Manager Virtual Interface Layer Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Transport Layer (TCP, UDP…) Application Layer Logical Interface Layer

22. Document draft-bernardos-netext-pmipv6-flowmob-00, July 2010 Proposed procedure Current flow mobility Proposal of NetExt WG 22/24 [New Messages] - FMI (Flow Mobility Initiation) - FMA (Flow Mobility Ack.)

23. Binding and Flow Binding States After flow mobility… Current flow mobility Proposal of NetExt WG 23/24

24. IETF Standards of Network-based Mobility Management Open Issues Not Yet Complete - Flow Mobility Design Implement and Validate It! Proposals  Implementation and Validation Tool: NS3 (http://www.nsnam.org/) Summary & Conclusions 24/24 1) Proxy Mobile IPv6 [RFC 5213, Aug. 2008] 2) IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] 3) Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-14] 4) Logical Interface Support for multi-mode IP Hosts [draft-melia-netext-logical-interface- support-01] 5) Proxy Mobile IPv6 Extensions to Support Flow Mobility [draft-bernardos-netext-pmipv6- flowmob-00]