1. Logical Interface and Flow Mobility Technology Laboratory of Intelligent Networks (LINK) @ KUT Youn-Hee Han http://link.kut.ac.kr November 26, 2010 Global IPv6 Summit in Korea 2010

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-11] Traffic Selectors for Flow Binding [draft-ietf-mext-binary-ts-05] 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] Multiple Care-of Addresses Registration & Flow Bindings in Proxy Mobile IPv6 [draft-trung-netext-flow-mobility- support-01 & draft-bernardos-netext- pmipv6-flowmob-01] [Related WG: MEXT, MIPSHOP, NETEXT – November 2010] IETF Core Standards for IPv6 Mobility Management 2 Per-flow Mobility Management

3. PMIPv6 and Flow Mobility Problems 3

4. 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 4

5. No Change to Host Stack IP Mobility handled by the network, and transparent to the host Any MN is just a IPv6 host 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 M:1 Tunnel LMA-MAG tunnel is a shared tunnel among many MNs. One tunnel is associated to multiple MNs’ Binding Caches. IPv4 Support RFC 5844 (May 2010) PMIPv6 Features 5

6. MNMAGAAA&Policy StoreLMACN MN Attachment AAA Query with MN-ID AAA Reply with Profile PBU with MN-ID, Home Network Prefix option (all zero), Timestamp option PBA with MN-ID, Home Network Prefix option Router Advertisement (Home Network Prefix) [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 PMIPv6 Operation 6

7. Flow Mobility Problems Case 1 Create additional mobility sessions on demand  e.g., additional connection for a particular service A new mobility session with a new prefix is created WiMax MAG LMA PBU MAG 3G MN 3GWiBro MAG LMA PBU MAG MN 3GWiBro WiMax3G Mobile IPTV flow VoIP flow Mobile IPTV flow VoIP flow HTTP flow 7

8. Case 2 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 MAG LMA PBU MAG LMA MAG MN 3G MN 3GWiBro VoIP flow Mobile IPTV flow WiMax3GWiMax3G WiBro Mobile IPTV flow VoIP flow PBU Flow Mobility Problems 8

9. Case 3 Without any attachment event, LMA can move a flow due to network status change and better QoS support. MAG LMA PBU MAG 단말 3GWiBro WiMax3G Mobile IPTV flow VoIP flow Flow Mobility Problems 9 MAG LMA MAG 단말 3GWiBro WiMax3G Mobile IPTV flow VoIP flow

10. Flow, Session, Traffic Selector, and Flow Binding 10

11. What is Flow? Flow A sequence of packets matching a flow description An interior attribute of a flow is a “direction” Flow Description: a 5-tuple   The followings can be optionally used Differentiated Services (Traffic Class in IPv6), IPSEC SPI, Flow Label (IPv6 Only) Two types of flows  MN manages “Outbound flow” MN decides which MAG the outbound flow is sent to.  LMA manages “Inbound flow” LMA decides which MAG the inbound flow is sent to. 11 MN MAG Inbound flow MN MAG Outbound flow

12. What is Session ? Session A Pair of two symmetrically congruent 5-tuples or, a flow (unidirectional session) All sessions are anchored by the LMA We assume that the two flows in a session are delivered via a same type of access technology. 12 Inbound flow: Outbound flow:

13. What is Traffic Selector? Traffic Selector An information used for traffic filtering a 5-tuple (allows the asterisk mark)  (3ffe::1, *, 20, *, UDP)  (*, *, *, *, TCP)  (*, *, *, 15792, UDP) Where does the traffic selector information come from?  The local policy profile in MN Keeps the traffic selector of outbound flow.  The remote policy profile in LMA (come from Policy Profile) Keeps the traffic selector of inbound flow for every MN. 13

14. Flow Binding Information Outbound Flow Binding Assume that MN has a functionality that controls the priority list of physical interfaces for a flow selector The information is saved at the MN local policy profile We call the above “Outbound flow binding” 14 (3G  WL) Flow selectorA Priority List

15. Flow Binding Information Inbound Flow Binding Remote policy profile at LMA (come from Policy Profile) Assume that the policy server contains the priority list of technologies for a flow selector  Maybe, a user can manage and control the priority in the remote policy profile LMA contacts the policy server and get the technology list information. We call the above “Inbound flow binding” [NOTE] The two information of local and remote policy profiles should be symmetrically congruent.  MN’s local binding change will be notified to policy profile by out-of-band signal 15 (3G  WL) Flow SelectorA Priority List

16. Flow Mobility Design 16

17. Flow Mobility Scenario Three types of flow mobility initiation and What is the exact meaning of the network-based flow mobility? 1) [Flow Mobility by a New Connection/Disconnection] MN makes a connection to a new access technology with a new interface. At this time, LMA (and/or MN) initiates the flow mobility at the same time based on its local policy. 2) [Flow Mobility by LMA’s Decision at a Time] Network (e.g., LMA) can determine the status of wired and wireless links.  Link’s availability  Congestion  Number of MN (or Flows) Serviced Therefore, LMA can control flow distribution at any time and it can initiate flow mobility with perfect freedom. 17

18. Design Approach Prefix Allocation Policy Instead of physical interfaces, the logical interface is actually assigned the whole prefixes. 18 MAG MN WLAN3G PI2PI1 HNP1 HNP2 HNP1 HNP2 LMA LI: Logical Interface LI PI: Physical Interface

19. MN Stack Architecture MN’s Stacks including the Logical Interface Layer Logical Interface Layer  Logical Interface Just a Logical interface made by using the host’s “NetDevice”  Flow Binding Manager Manage “Flow Binding Information” Determine the proper physical interface (PI) for the “outbound packets” from MN 19 PI1 [IEEE 802.11]PI2 [3GPP]PI3 [IEEE 802.16]… Data Link Layer Logical InterfaceFlow Binding Manager Logical Interface Layer Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Transport Layer (TCP, UDP…) Application Layer New Layer

20. MN Stack Architecture Flow Binding Manager in Logical Interface Layer FBM’s role  Gather the mapping information from the MN local policy or inbound packets  Mapping a flow to the one of physical interfaces (PIs) Determine the physical interface for the outbound packets  Mirroring Leaning and Action 20 PI1 [IEEE 802.11]PI2 [3GPP]PI3 [IEEE 802.16]… Data Link Layer Logical InterfaceFlow Binding Manager Logical Interface Layer Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Transport Layer (TCP, UDP…) Application Layer Local Policy PI1 [IEEE 802.11]PI2 [3GPP]PI3 [IEEE 802.16]… Data Link Layer Logical InterfaceFlow Binding Manager Logical Interface Layer Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Transport Layer (TCP, UDP…) Application Layer Inbound packetsOutbound packets LearningAction

21. LMA Stack Architecture LMA’s stacks including the Flow Binding Manager Flow Binding Manager in PMIPv6  Manage a “Binding Cache” and “Flow Binding List” for each MN  Gather the mapping information from the service policy or outbound packets  Mapping a flow to the one of bindings Determine the proper tunnel for the “inbound packets” from a CN 21 Tunnel #1 (to MAG1)Tunnel #2 (to MAG2)Tunnel #3 (to MAG3)… Data Link Layer Network Layer (PMIPv6) Flow Binding Manager Tunnel #1 (to MAG1)Tunnel #2 (to MAG2)Tunnel #3 (to MAG3)… Data Link Layer Network Layer (PMIPv6) Flow Binding Manager Tunnel #1 (to MAG1)Tunnel #2 (to MAG2)Tunnel #3 (to MAG3)… Data Link Layer Network Layer (PMIPv6) Flow Binding Manager “(remote) policy profile” Outbound packetsInbound packets

22. Reference Stack Architecture & FBL/FIL 22 Tunnel #1 (to MAG1) Tunnel #2 (to MAG2)Tunnel #3 (to MAG3)… Data Link Layer Network Layer (PMIPv6) Flow Binding Manager Application Layer Transport Layer (TCP, UDP…) Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Logical Interface Layer Logical InterfaceFlow Interface Manager Data Link Layer PI1 [IEEE 802.11]PI2 [3GPP]PI3 [IEEE 802.16]… MAG1MAG2MAG3 LMA MN Flow ID Prio rity Traffic Selector Outbound Interfaces Type Lifet ime 5101 (IP3, IP2, 1001, 76, TCP) PI2 Dynamic t1 44(*, IP1, *, 21, *) PI3  PI2  PI1Static  33(*, *, *, *, TCP) PI1  PI2  PI3Static  22(*, FF02::/64, *, *, *) PI1, PI2, PI3Default  11(*, *, *, *, *) PI1Default  Flow ID Prio rity Traffic Selector Binding IDs Type Lifet ime 5101(IP2, IP3, 76, 1001, TCP) 2Dynamict1 44(IP1, *, 21, *, *) 321321Static  33(*, *, *, *, TCP) 123123Static  22(*, FF02::/64, *, *, *) 1, 2, 3Default  11(*, *, *, *, *) 1Default  Flow Binding List (FBL) Flow Interface List (FIL) Default From policy profile From local policy Symmetry in flow info. Binding ID PriorityHNPsMN-ID Proxy- CoA ATT MN-LL- ID 33HNP1,2MN#1PCoA35 (IEEE802.16)zzz 22HNP1,2MN#1PCoA22 (PPP)zzz 11 (The lowest)HNP1,2MN#1PCoA14 (IEEE802.11)zzz Binding Cache

23. Protocol Operation 23 Flow Mobility by a New Connection – Case 1 PBU[MN-ID,HI=1] CN LMA MAG#2MAG#1 New Connection MN if1 if2 flow X to HNP1:LIID flow Y to HNP2:LIID - Check the binding cache and flow binding information - Decide not to move any flow PBA[MN-ID,HNP=HNP4] RA[HNP4] LIID: Logical Interface ID RA[HNP1,HNP2,HNP3] flow Z to HNP3:LIID

24. Protocol Operation 24 Flow Mobility by a New Connection – Case 2 PBU[MN-ID,HI=1] CN LMA MAG#2MAG#1 New Connection MN if1 if2 flow X to HNP1:LIID flow Y to HNP2:LIID - Check the binding cache and flow binding information - Decide to move flow Y to the new attachment PBA[MN-ID,HNP=HNP2] RA[HNP2] flow Y to HNP2:LIID RA[HNP1,HNP2,HNP3] flow Z to HNP3:LIID

25. Protocol Operation 25 Flow Mobility by LMA’s Decision at a Time CN LMA MAG#2MAG#1 MN if2 - Decide to move flow Y to the interface if1 - Check the binding cache and flow binding information - Just move it! (because HNP2 has been allocated to the MAG#1) HUR: HNP Update Request HUA: HNP Update Ack. if1 flow X to HNP1:LIID flow Z to HNP3:LIID RA[HNP1,HNP2,HNP3] RA[HNP2] flow Y to HNP2:LIID HUR[MN-ID,HNP1,add] HUA[MNID,HNP1,add] flow X to HNP1:LIID RA[HNP1,HNP2] - Decide to move flow X to the interface if2 - Check the binding cache and flow binding information - Send FMI to the MAG#2 (because HNP1 has not been allocated to the MAG#2) flow Y to HNP2:LIID

26. Flow Mobility Verification in NS3 26

27. Why NS3? 27 Current Release ns-3.9 (August 20, 2010) Monthly download count of ns-3 releases

28. Why NS3? 28 Features Alignment with real systems sockets, device driver interfaces Standard input/output formats  e.g., pcap trace & wireshark ns-3 is adding support for running implementation code  e.g., Linux TCP code P2P link, shared link with CSMA. Routing, ARP A node can be equipped with multiple network interfaces. Support (nearly) complete IPv6 Can run real implementation of applications. Wireless  WiFi, WiMAX, UMTS (PPP)

29. Tested Network Topology 29 PBU Message Format implemented in NS3

30. Tested Network Topology 30 Network Topology

31. Tested Scenario 31 Test Scenario 1.0 sec.: MN attaches WLAN 1.3 sec.: UDP1 and UDP2 flows are served through WLAN 5.5 sec.: MN also attaches WiMax and only UDP2 flow is moved to WiMax 10.0 sec.: MN also attaches 3GPP network 12.0 sec.: new UDP3 flow is served through 3GPP 15.0 sec.: UDP1 flow is moved to WiMax from WLAN.

32. Throughput Change 32 Throughput Graph - 1

33. Throughput Change 33 Throughput Graph - 2