1. Proxy Mobile IPv6 (PMIPv6) Youn-Hee Han yhhan@kut.ac.kr Korea University of Technology and Education Internet Computing Laboratory http://icl.kut.ac.kr

2. KRnet 20072/25 Background PMIPv6 (Proxy Mobile IPv6) Overview PMIPv6 Features IPv4 Support for PMIPv6 PMIPv6 and MIPv6 (Mobile IPv6) Interworking Summary Outline

3. KRnet 20073/25 Background

4. KRnet 20074/25 Background Host-based Mobile IPv4/v6 (RFC 3344/3775) has not been yet deployed that much. Why host-based MIP is not deployed yet?  Too heavy specification to be implemented at a small terminal RFC 3344 (MIPv4): 99 pages RFC 3775 (MIPv6): 165 pages  Battery problem  Waste of air resource  No Stable MIPv4/v6 stack executed in Microsoft Windows CE OS

5. KRnet 20075/25 WLAN switch device starts to provide link specific and proprietary solution for IP handover. No change in MN protocol stack required! The solution works by tunneling traffic from the access point to the WLSM through your Layer 3 core network. No changes to the client devices or the underlying infrastructure are required Background

6. KRnet 20076/25 3GPP, 3GPP2 and WiMAX operators are now showing their STRONG interests for network-based IP mobility solution They are even now deploying their non-standardized network-based IP mobility solution (not Mobile IPv4/v6!). IETF NetLMM WG started to standardize a network-based mobility management protocol. 63 th IETF (2005.7)  The first NetLMM BoF 64 th IETF (2005.11)  The second NetLMM BoF 65 th IETF (2006.03)  The first NetLMM WG 66 th,67 th,68 th IETF (2006.07, 2006.11, 2007.03)  The one of very active WGs in IETF meetings  Almost 150~200 persons usually participates in the NetLMM WG  Proxy Mobile IPv6 adopted as WG item Background

7. KRnet 20077/25 IETF NetLMM WG History NetLMM DT solution (draft-giaretta-netlmm-dt-protocol) : designed from the scratch Cisco’s solution (draft-ietf-netlmm-proxymip6) : Proxy Mobile IPv6 (leverage MIPv6) Motorola’s solution (draft-singh-netlmm-protocol) WG Chair (James Kempf, NTT) resigned after 67th meeting → Vidya Narayanan (Qualcomm) WG Chair (Phil Roberts, Motorola) resigned after 68th meeting → Jonne Soininen (Nokia)

8. KRnet 20078/25 IETF PMIPv6 Drafts History Individual  S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-00, October 16, 2006.  S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), “Proxy Mobile IPv6,” draft- sgundave-mipv6-proxymipv6-01, January 5, 2007.  S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-02, March 5, 2007. Official WG Item  S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (Azaire Networks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-ietf-netlmm-proxymip6-00.txt, April 8, 2007. Internet Drafts of PMIPv6

9. KRnet 20079/25 Goal This protocol is for providing mobility support to any IPv6 host within a restricted and topologically localized portion of the network and without requiring the host to participate in any mobility related signaling. Goal of PMIPv6 PMIPv6 Scenario (being extended) registration

10. KRnet 200710/25 PMIPv6 Overview LMM (Localized Mobility Management) Domain MAG1 Host B Host A LMA Proxy Binding Update (PBU) Control message sent out by MAG to LMA to register its correct location Home Network MN’s Home Network (Topological Anchor Point) Proxy Care of Address (Proxy-CoA) The address of MAG. That will be the tunnel end-point. IP Tunnel A IPinIP tunnel LMA and MAG. MAG2 LMA: Localized Mobility Agent MAG: Mobile Access Gateway LMA Address (LMAA) That will be the tunnel entry- point. MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 MN’s Home Network Prefix (MN-HNP) CAFE:1:/64 MN Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain

11. KRnet 200711/25 PMIPv6 Overview New entities LMA (Local Mobility Anchor)  Home Agent for the mobile node in the PMIPv6 domain  Assigns MN's home prefix and manages the MN's reachability state MAG (Mobile Access Gateway)  Manages the mobility related signaling for a mobile node  Tracking the mobile node's attachment to the link and for signaling the MN's LMA Assumptions (or Restrictions) Link between MN and MAG is a point-to-point link (not shared link)  Logically exclusive layer 3 link between MN and MAG Per-MN Prefix model  unique home network prefix is assigned to MN Support both Steteless and Stateful address configuration modes

12. KRnet 200712/25 PMIPv6 Operation Flow 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

13. KRnet 200713/25 PMIPv6 Features Home in Any Place Network Entry (or Handover) Procedures  After MN attachment, MAG gets MN’s profile MN-Identity LMA address and other configuration parameters  Obtain MN’s home network prefix information Static Scheme Get it from Profile Dynamic Scheme Get it from LMA via PBU/PBA  Now MAG have enough information to emulate MN’s home link  Send the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters MN will always obtain its “home network prefix”, any where in the network. MAG runs on the access router will emulate the home link on its access link.  It will ensure that MN believes it is at its home.

14. KRnet 200714/25 PMIPv6 Features Proxy Registration LMA needs to understand the Proxy Registration RFC 3775 MIPv6 BU/Back Reuse PBU (Proxy Binding Update) PBA (Proxy Binding Acknowledgement)

15. KRnet 200715/25 PMIPv6 Features M:1 Tunnel LMA-MAG tunnel is a shared tunnel among many MNs.  1:1 relation  m:1 relation  One tunnel is associated to multiple MNs’ Binding Caches.  Life-time of a tunnel should not be dependent on the life time of any single BCE. LMA’s Prefix-based Routing LMA will add prefix routes to MN’s home network prefix over the tunnel. Routing State for a MN stored in LMA

16. KRnet 200716/25 PMIPv6 Features MAG establishes IPv6 in IPv6 tunnel with LMA RA (Router Advertisement) should be UNICASTed to an MN It will contain MN’s Home Network Prefix Routing State for a MN stored in MAG

17. KRnet 200717/25 PMIPv6 Features Any MN is just a IPv6 host Any MN is just a IPv6 host with its protocol operation consistent with the base IPv6 specification. All aspects of Neighbor Discovery Protocol will not change. IPv6 protocol parameter consideration  Lower default-router list cache timeout LLA: Link Local Address (e.g., MAC Address)

18. KRnet 200718/25 IPv4 Support for PMIPv6 Two functions supported IPv4 Transport Network Support  IPv6 in IPv4 tunnel, IPv4 in IPv4 tunnel, NAT Traversal IPv4 Home Address Mobility  An IPv4-only or dual-stack MN will be able to obtain an IPv4 address (IPv4- MN-HoA) and will be able to roam in that PMIPv6 domain using that address. The signaling protocol is based on Proxy Mobile IP6.

19. KRnet 200719/25 Leveraging the existing Dual Stack Mobile IPv6 (DSMIPv6) protocol Hesham Soliman (Ed.), “Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)”, draft-ietf-mip6-nemo-v4traversal-04.txt, March, 2007 The new WG draft for IPv4 support for PMIPv6 R. Wakikawa (Keio Univ.), S. Gundavelli (Cisco), “IPv4 Support for Proxy Mobile IPv6”, draft-ietf-netlmm-pmip6-ipv4-support-00.txt, May 2007 v4 Network IPv4 Packet IPv6 Packet HA v6 Network Movement NAT Tunneled to private IPv4 CoA Tunneled to IPv4 CoA Tunneled to IPv6 CoA Private v4 Network Movement CN IPv4 Support for PMIPv6

20. KRnet 200720/25 IPv4 Support for PMIPv6 PMIPv6’s IPv4 Support Dual Stack LMA Dual Stack MN or IPv4 MN PBU (V6 Addr., Proxy CoA v6, V4 Addr.) V4 Addr. and V6 Addr. Proxy CoAv6 [Mobility Binding] IPv6 Tunnel (LMAAv6->Proxy CoAv6) IPv4 traffic CNv4  V4 Addr. IPv6 traffic CNv6->V6 Addr. Dual Stack MAG Dual Stack LMA Dual Stack MN or IPv4 MN PBU (V6 Addr., Proxy CoA v6, V4 Addr.) V4 Addr. and V6 Addr. Proxy CoAv4 [Mobility Binding] IPv4 Tunnel (LMAAv4->Proxy CoAv4) IPv4 traffic CNv4  V4 Addr. IPv6 traffic CNv6->V6 Addr. Dual Stack MAG

21. KRnet 200721/25 V. Devarapalli (Azaire Network), S. Gundavelli (Cisco), K. Chowdhury (Starent Networks), A. Muhanna (Nortel), “Proxy Mobile IPv6 and Mobile IPv6 Interworking”, draft-devarapalli-netlmm-pmipv6-mipv6-00.txt, April 2007. PMIPv6 is typically used for localized mobility management and MIPv6 is applied for global mobility management. In case of intra-domain movement the MN and MIPv6 HA are not aware of the movement. In case of inter-domain movement It acquires a new MN-HoA in the new domain It treats the new MN-HoA as the CoA of MIPv6. It treats the previous MN-HoA as the HoA of MIPv6. MN sends MIPv6 binding update with the pair (New MN-HoA, Prev. MN-HoA). PMIPv6 and MIPv6 Interworking

22. KRnet 200722/25  Case #1. MN in a Home Domain PMIPv6 Domain #1 (Mobile IPv6 Home Domain) MIPv6-HoA = MN-HoA #1 MIPv6-Home Agent = LMA #1 HoACoA Binding Cache Proxy Flag MN-HoA #1 MAG#1-1’s Addr. 1 PMIPv6 Domain #2 PMIPv6 Domain #3 MAG #1-2MAG #1-1 Proxy BU In the interior of MN, MIPv6-CoA is not needed since all MAGs will emulate the home link. PMIPv6 and MIPv6 Interworking

23. KRnet 200723/25 PMIPv6 Domain #2 Non-PMIPv6 Domain PMIPv6 is operated! Still… MIPv6-HoA = MN-HoA #1 Proxy BU MIPv6-Home Agent = LMA #1 PMIPv6 Domain #1 (Mobile IPv6 Home Domain) MAG #1-1MAG #1-2 In the interior of MN, MIPv6-CoA is still not needed since all MAGs will emulate the home link. HoACoA Binding Cache Proxy Flag MN-HoA #1 MAG#1-2’s Addr. 1  Case #2. Movement in a Home Domain PMIPv6 and MIPv6 Interworking

24. KRnet 200724/25 PMIPv6 Domain #2 Non-PMIPv6 Domain Both MIPv6 and PMIPv6 are operated! MN obtains MN-HoA #2 LMA #2 MIPv6 BU MIPv6-Home Agent = LMA #1 PMIPv6 Domain #1 (Mobile IPv6 Home Domain) MAG #2-1 MAG #2-2 HoACoA Binding Cache Proxy Flag MN-HoA #1 MN-HoA #2 0 Proxy BU HoACoA Binding Cache Proxy Flag MN-HoA #2 MAG#2-1’s Addr. 1 MN maintains two addresses - MIPv6-HoA = MN-HoA #1 - MIPv6-CoA = MN-HoA #2  Case #3. MN moves to a new domain PMIPv6 and MIPv6 Interworking

25. KRnet 200725/25 PMIPv6 can be a way to facilitate the deployment of IP mobility Reuse deployed infrastructure & Mobile IPv6 functionality Favorable to ISPs PMIPv6 is New Idea?  Absolutely No!, but new trend!. It’s a turn for the better! PMIP is a good example of compromise Until now, long confrontation  Telecommunication Operators  Internet Developers and Users It is still RFC 3775 MIP-based one. But, it follows telco’s favoritism! More Studies Needed Route Optimization in PMIPv6 Fast Handover in PMIPv6 PMIPv6 over IEEE 802.16/WiBro (Cross-layering Issues) New Research Areas using PMIPv6 Network-based Global Mobility PMIPv6-based NeMo (MANEMO) PMIPv6-based 6LowPAN Sensor Node Mobility Summary