Proxy Mobile IPv6 (PMIPv6)

Youn-Hee Hanyhhan@kut.ac.kr

Korea University of Technology and EducationInternet Computing Laboratory

http://icl.kut.ac.kr

KRnet 20072/25

Background

PMIPv6 (Proxy Mobile IPv6) Overview

PMIPv6 Features

IPv4 Support for PMIPv6

PMIPv6 and MIPv6 (Mobile IPv6) Interworking

Summary

Outline

KRnet 20073/25

Background

KRnet 20074/25

BackgroundHost-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 pagesRFC 3775 (MIPv6): 165 pages

Battery problemWaste of air resource

No Stable MIPv4/v6 stack executed in Microsoft Windows CE OS

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 theWLSM through your Layer 3 core network. No changes to the client devices or the underlying infrastructure are required

Background

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.

63th IETF (2005.7)The first NetLMM BoF

64th IETF (2005.11)The second NetLMM BoF

65th IETF (2006.03) The first NetLMM WG

66th,67th,68thIETF (2006.07, 2006.11, 2007.03)The one of very active WGs in IETF meetingsAlmost 150~200 persons usually participates in the NetLMM WGProxy Mobile IPv6 adopted as WG item

Background

KRnet 20077/25

IETF NetLMM WG History

NetLMM DT solution (draft-giaretta-netlmm-dt-protocol) : designed from the scratchCisco’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)

KRnet 20078/25

IETF PMIPv6 Drafts HistoryIndividual

S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (AzaireNetworks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-00, October 16, 2006.

S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (AzaireNetworks), K. Chowdhury (Starent Networks), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-01, January 5, 2007.

S. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (AzaireNetworks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-sgundave-mipv6-proxymipv6-02, March 5, 2007.

Official WG ItemS. Gundavelli (CISCO), K. Leung (CISCO), and V. Devarapalli (AzaireNetworks), K. Chowdhury (Starent Networks), B. Patil (Nokia), “Proxy Mobile IPv6,” draft-ietf-netlmm-proxymip6-00.txt, April 8, 2007.

Internet Drafts of PMIPv6

KRnet 20079/25

GoalThis 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

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 NetworkMN’s Home Network (Topological Anchor Point)

Proxy Care of Address (Proxy-CoA)The address of MAG. That will be the tunnel end-point.

IP TunnelA IPinIP tunnel LMA and MAG.

MAG2

LMA: Localized Mobility AgentMAG: 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

KRnet 200711/25

PMIPv6 OverviewNew entities

LMA (Local Mobility Anchor)Home Agent for the mobile node in the PMIPv6 domainAssigns MN's home prefix and manages the MN's reachability state

MAG (Mobile Access Gateway)Manages the mobility related signaling for a mobile nodeTracking 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

KRnet 200712/25

PMIPv6 Operation Flow

RA*: MN의 Prefix를 Policy Store에서 수신한 경우의 Router AdvertisementRA**: MN의 Prefix를 LMA에서 수신한 경우의 Router Advertisement

MN MAG AAA&Policy Store LMA CN

MN Attachment AAA Query with MN-ID

AAA Reply with ProfileRA*

PBU with MN-ID, Home Network Prefix option, Timestamp option

PBA with MN-ID, Home Network Prefix optionRA**

[MN-HoA:CN](data)[Proxy-CoA:LMAA][MN-HoA:CN](data)

[MN-HoA:CN](data)

Tunnel Setup

PBU: Proxy Binding UpdatePBA: Proxy Binding Ack.

DHCP ServerDHCP Request

DHCP Response

DHCP Request

DHCP Response

Optional

KRnet 200713/25

PMIPv6 FeaturesHome in Any Place

Network Entry (or Handover) ProceduresAfter MN attachment, MAG gets MN’s profile

MN-IdentityLMA address and other configuration parameters

Obtain MN’s home network prefix informationStatic Scheme

Get it from ProfileDynamic Scheme

Get it from LMA via PBU/PBA

Now MAG have enough information to emulate MN’s home linkSend 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.

KRnet 200714/25

PMIPv6 FeaturesProxy Registration

LMA needs to understand the Proxy RegistrationRFC 3775 MIPv6 BU/Back Reuse

PBU (Proxy Binding Update)

PBA (Proxy Binding Acknowledgement)

KRnet 200715/25

PMIPv6 FeaturesM:1 Tunnel

LMA-MAG tunnel is a shared tunnel among many MNs.1:1 relation m:1 relationOne 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 RoutingLMA will add prefix routes to MN’s home network prefix over the tunnel.

Routing State for a MN stored in LMA

KRnet 200716/25

PMIPv6 FeaturesMAG establishes IPv6 in IPv6 tunnel with LMA

RA (Router Advertisement) should be UNICASTed to an MNIt will contain MN’s Home Network Prefix

Routing State for a MN stored in MAG

KRnet 200717/25

PMIPv6 FeaturesAny 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)

KRnet 200718/25

IPv4 Support for PMIPv6

Two functions supportedIPv4 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.

KRnet 200719/25

Leveraging the existing Dual Stack Mobile IPv6 (DSMIPv6) protocolHesham 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

v4 Network

IPv4 Packet

IPv6 Packet

HA

v6 Network

v6 Network Movement

NAT

Tunneled to private IPv4 CoA

Tunneled to IPv4 CoA

Tunneled to IPv6 CoA

Private v4 Network

Movement

CN

CN

IPv4 Support for PMIPv6

KRnet 200720/25

IPv4 Support for PMIPv6PMIPv6’s IPv4 Support

Dual Stack LMA

Dual Stack MNor

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 trafficCNv4 V4 Addr.

IPv6 trafficCNv6->V6 Addr.

Dual Stack MAG

<MN in IPv6 domain>

Dual Stack LMA

Dual Stack MNor

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 trafficCNv4 V4 Addr.

IPv6 trafficCNv6->V6 Addr.

Dual Stack MAG

<MN in IPv4 domain>

KRnet 200721/25

V. Devarapalli (Azaire Network), S. Gundavelli (Cisco), K. Chowdhury (StarentNetworks), 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 movementthe MN and MIPv6 HA are not aware of the movement.

In case of inter-domain movementIt 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

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

HoAHoA CoACoA

Binding Cache

Proxy FlagProxy Flag

MNMN--HoAHoA #1#1 MAG#1MAG#1--11’’s s AddrAddr.. 11

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

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-1 MAG #1-2

In the interior of MN, MIPv6-CoA is still not needed since all MAGs will emulate the home link.

HoAHoA CoACoA

Binding Cache

Proxy FlagProxy Flag

MNMN--HoAHoA #1#1 MAG#1MAG#1--22’’s s AddrAddr.. 11

Case #2. Movement in a Home Domain

PMIPv6 and MIPv6 Interworking

KRnet 200724/25

PMIPv6 Domain #2 Non-PMIPv6 Domain

Both MIPv6 and PMIPv6 are operated!MN obtains MN-HoA #2

LMA #2MIPv6 BU

MIPv6-Home Agent = LMA #1

PMIPv6 Domain #1(Mobile IPv6 Home Domain)

MAG #2-1

MAG #2-2

HoAHoA CoACoA

Binding Cache

Proxy FlagProxy Flag

MNMN--HoAHoA #1#1 MNMN--HoAHoA #2#2 00

Proxy BUHoAHoA CoACoA

Binding Cache

Proxy FlagProxy Flag

MNMN--HoAHoA #2#2 MAG#2MAG#2--11’’s s AddrAddr.. 11

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

KRnet 200725/25

PMIPv6 can be a way to facilitate the deployment of IP mobilityReuse deployed infrastructure & Mobile IPv6 functionalityFavorable to ISPsPMIPv6 is New Idea?

Absolutely No!, but new trend!. It’s a turn for the better!

PMIP is a good example of compromiseUntil now, long confrontation

Telecommunication Operators Internet Developers and UsersIt is still RFC 3775 MIP-based one.But, it follows telco’s favoritism!

More Studies NeededRoute Optimization in PMIPv6Fast Handover in PMIPv6PMIPv6 over IEEE 802.16/WiBro (Cross-layering Issues)

New Research Areas using PMIPv6Network-based Global MobilityPMIPv6-based NeMo (MANEMO)PMIPv6-based 6LowPAN Sensor Node Mobility

Summary