Mobile IP

Mobile IPv4 (MIPv4) Mobile IPv6 (MIPv6) MIP Extensions: FMIP & HMIP Proxy MIP (PMIP)

Mobile IP and its Variants

Mobile IPv4 (MIPv4) MIPv4

Low-Latency Handover for MIPv4 (FMIPv4)

Regional Registration for MIPv4 (HMIPv4) Mobile IPv6 (MIPv6) MIPv6 Fast Handover for MIPv6 (FMIPv6) Hierarchical MIPv6 (HMIPv6)

CNP

2/50

IETF RFCs
MIP MIPv4: RFC 3344 (2002)

MIPv6: RFC 3775 (2004)

FMIP (Fast Handover for MIP FMIPv6: RFC 4068 (2005) Fast Handovers for Mobile IPv6

FMIPv4: RFC 4881 (2007)

Low-Latency Handoffs in Mobile IPv4 HMIP (Hierarchical MIP) HMIPv6: RFC 4140 (2005) Hierarchical Mobile IPv6 HMIPv4: RFC 4857 (2007) Mobile IPv4 Regional Registration
CNP 3/50

MIPv4: Overview
MIPv4 Nodes MN (Mobile Node): Host

CN (Correspondent Node): Host

HA (Home Agent): Router FA (Foreign Agent): Router MIPv4 Address HoA (Home Address): MN CoA (Care-of-Address): FA

CNP

4/50

Home Address (HoA) and Care-of Address (CoA)

CNP

5/50

Note:
The home address is permanent; the care-of address changes as the mobile host moves from one network to another.

CNP

6/50

MIPv4 Agents
Home Agent (HA) & Foreign Agent (FA)

CNP

7/50

Protocols Operation
Agent Discovery Registration

Data Transfer

CNP

8/50

MIPv4: Control Operations

Agent Discovery MN FA (CoA)

ICMP Agent Solicitation & Advertisement

Registration to HA (via FA) MN FA HA Over UDP (destination port 434) Data Tunneling CN => HA (HoA) => FA (CoA) => MN IP-in-IP Tunneling, ..

CNP

9/50

MIPv4: Control & Data Flows

CNP

10/50

Agent advertisement
MIP does not use a new packet type for agent advertisement; it uses the router advertisement packet of ICMP, and

appends an agent advertisement message.

CNP

11/50

Agent Solicitation Mobile IP does not use a new packet type for agent solicitation;

it uses the router solicitation packet of ICMP.

CNP

12/50

Registration request and reply

CNP

13/50

Note:
A registration request or reply is sent by UDP using the well-known port 434.

CNP

14/50

Registration request format

CNP

15/50

Registration reply format

CNP

16/50

Data transfer

CNP

17/50

Key Objective of MIP

The movement of the mobile host is transparent to the rest of the Internet.

CNP

18/50

Mobile IPv6 (MIPv6)

MIPv6 = MIPv4 + IPv6 Major Differences from MIPv4

FA in MN
No FA for MIPv6 CoA: IP address of MN By DHCPv6 or IPv6 Stateless Auto-Configuration

Route Optimization
To solve the Triangular Routing Problem Provided by default MN CN

CNP

19/50

MIP: Triangular Routing Problem

CNP

20/50

MIPv6: Route Optimization

CNP

21/50

MIPv6: Binding Update

Binding Update to HA Using IPSEC: MN and HA have a security association

AH (Authentication Header)
ESP (Encapsulating Security Payload) Binding Update to CN Return Routability (RR) procedure For Security Binding Update (BU) procedure Route Optimization

CNP

22/50

MIPv6: Binding Update

CNP

23/50

MIPv6: RR (Return Routability)

CNP

24/50

MIPv6: Changes to IPv6

New IPv6 Protocol (Header) Mobility Header: a new IPv6 extension header

To carry MIPv6 Binding Update messages

How is in the MIPv4 ? New Option in Destination Option Header Home Address Option New Type in Routing Header Type 2 Routing Header New ICMP Messages

ICMP HA Address Discovery Request/Reply

ICMP Mobile Prefix Solicitation/ Advertisement

CNP

25/50

MIPv6: IPv6 Header

CNP

26/50

MIPv6: Mobility Header

A New Extension Header of IPv6 Messages for Return Routability

Home Test Init Message

Care-of Test Init Message Home Test Message Care-of Test Message Messages for Binding Update Binding Update Message Binding Acknowledgement Message Binding Error Message Binding Refresh Request Message

CNP

27/50

MIP Extensions
Mobile IPv4 (MIPv4) Low-Latency Handover for MIPv4 (FMIPv4)

Regional Registration for MIPv4 (HMIPv4)

Mobile IPv6 (MIPv6) Fast Handover for MIPv6 (FMIPv6) Hierarchical MIPv6 (HMIPv6)

CNP

28/50

FMIPv6: Fast Handover for MIPv6

CN

PAR

NAR

signaling MN

signaling

CNP

29/50

FMIPv6: Operations
Handover Initiation L2 Triggers, RtSolPr, PrRtAdv

Between MN and AR
Tunnel Establishment HI (Handover Initiate) and HACK Between PAR and NAR Packet Forwarding PAR => NAR (data buffering at NAR) FBU, FBack

NAR => MN:

FNA (Fast NA)

CNP

30/50

FMIPv6: Operational Flows

CNP

31/50

HMIPv6: Overview
Motivations Localized (Regional) Mobility Management

Hierarchical
MIP: MN HA HMIP: MN MAP HA MAP: Mobility Anchor Point IP Address (CoA) RCoA (Regional CoA): in the MAP region LCoA (On-Link CoA): in the AR region

CNP

32/50

HMIPv6: Architecture

HA
CN

MAP

RCoA

AR1
LCoA_1

AR2

LCoA_2

MN
CNP

Movement

33/50

HMIPv6: Operations
MN When entering an AR region in the MAP domain,

it gets LCoA (AR region) and RCoA (MAP region)

RCoA does not change in the MAP domain Local Binding Update (LBU) to MAP Bind LCoA & RCoA to MAP MAP (Acting as a local HA) Only the RCoA need to be registered with CN/HA Relay all packets between MN and HA/CN

CNP

34/50

HMIPv6: MAP Tunnel (MAP MN)

HA CN MAP

AR1
MN

AR2

Outer header
LCoA MAP

Inner header RCoA CN Home Addr

35/50

CNP

MIP in Real World: 3GPP2 (CDMA)

CNP

36/50

MIP in 3GPP2

CNP

37/50

Proxy MIPv6 (PMIPv6)

Network-based Localized Mobility Management

Why Network-based?
Host-based MIPv4/v6 has not been yet deployed that much. Why host-based MIP is not deployed yet?

Too heavy specification for 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 OS

CNP

39/50

PMIPv6
IETF NETLMM WG Internet Draft

Proxy Mobile IPv6,

draft-ietf-netlmm-proxymip6-00.txt (2007)

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.

CNP

40/50

Technical Background
Host-based vs. Network-based Mobility

HA

HA

Route Update

Route Update

AR

AR

Movement

Movement

Host-based Mobility
CNP

Network-based Mobility

41/50

Proxy MIPv6 Overview

LMA: Localized Mobility Agent MAG: Mobile Access Gateway IP Tunnel
A IPinIP tunnel LMA and MAG.

MNs Home Network Prefix (MN-HNP) CAFE:1:/64

LMA MAG1

Home Network
MNs Home Network (Topological Anchor Point)

Host A

LMA Address (LMAA)

MAG2
MNs Home Network Prefix (MN-HNP) CAFE:2:/64

LMM (Localized Mobility Management) Domain

That will be the tunnel entrypoint.

Proxy Binding Update (PBU)

Host B

Control message sent out by MAG to LMA to register its correct location

MN Home Address (MN-HoA)

MN continues to use it as long as it roams within a same domain

Proxy Care of Address (Proxy-CoA)

The address of MAG. That will be the tunnel end-point.

CNP

42/50

Proxy MIPv6 Overview

No host stack change for IP mobility Avoiding tunneling overhead over the air

Re-use of Mobile IPv6

PMIPv6 is based on Mobile IPv6 [RFC3775] Only supports Per-MN-Prefix model Unique home network prefix assigned for each MN. The prefix follows the MN.

CNP

43/50

Proxy MIPv6 Overview

Overall Procedures 1. 3. 4. 5. 6. MN moves and attaches to an access router MAG obtains MNs profile containing the Home Address ..etc MAG sends the Proxy Binding Update to LMA on behalf of MN MAG receives the Proxy Binding Ack. from LMA MAG sends Router Advertisements containing MNs home network prefix Stateless Case: MN will still configure (or maintain) the same as its home address. Stateful Case: the network will ensure that it always gets its home address.

2. After authentication, MAG (access router) identifies MN

CNP

44/50

Proxy MIPv6 Overview

DHCP Relay Agent MN MAG
Access to a new IP link MN-Identifier MN-Identifier AAA Request AAA Reply + Policy Profile Proxy Binding Update

AAA Server (Policy Store)

DHCP Server

LMA

In case that profile store does not have MN Home Prefix

MAG emulates the MNs home link Router Advertisement

Proxy Binding Ack. (MN Home Prefix)

Tunnel Setup

DHCP Request DHCP Request DHCP Response DHCP Response

This can be omitted when stateless configuration is used.

CNP

45/50

Proxy MIPv6
Proxy Registration LMA needs to understand the Proxy Registration.

Proxy Binding Update

Proxy Binding Acknowledgement

CNP

46/50

Proxy MIPv6
Tunnel Management 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. LMAs Prefix-based Routing LMA will add prefix routes to MNs home network prefix over the tunnel.

CNP

47/50

Proxy MIPv6
MAG Operation It emulates the home link for each MN.

After the access authentication, MAG will obtain MNs profile which contains:
MNs home address MNs home network prefix

LMA address ..etc.

It establishes a IPv6/IPv6 tunnel with the LMA. All the packets from MN are reverse tunneled to its LMA All the packets from the tunnel are routed to MN. Router Advertisement should be UNICASTed to an MN It will contain MNs Home Network Prefix (MN-HNP)
CNP 48/50

Proxy MIPv6
MN Operation 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. When MN attaches to a new AR, it receives a Router Advertisement message from the AR with its home prefix.

Throughout the PMIP domain, MN using DHCP procedure or in stateless address configuration mode, will obtain the same home address.

CNP

49/50

Proxy MIPv6
Data Transport LMA-MAG Tunneling/Reverse Tunneling

MN
MN sends a packet to CN

MAG
MAG forwards to LMA

LMA

CN

LMA sends to CN CN sends packet to MN

MAG sends to MN

LMA forwards to MAG

IPv6 header (src=MAG_ADDR, dst=LMA_ADDR) IPv6 header (src=MN_ADDR, dst=CN_ADDR)

IPv6 header (src=LMA_ADDR, dst=MAG_ADDR) IPv6 header (src=CN_ADDR, dst=MN_ADDR) Paylaod

Payload

CNP

50/50