5.

Mobile IP
Mobile IP Basics
• A Mobile Node is assigned a visiting, or Care-Of-Address, at the
networks it visits
– Application sessions still use to original Home IP address
– Normal IP Routing forwards packets to the Home Network
– Mobile IP then forwards packets from the Home Network to the
Mobile Nodes current Foreign Network Foreign Network (for X.b)
Home Network (for X.b)

Z.a
X.a Internet

X.b Router
Router
X.z
Z.z
HA
FA HomeIP: X.b
Router: Y.z COA: Z.t
FA

Y.e Y.f
HomeIP: X.b
COA: Y.m

Foreign Network (for X.b)

 Mobile IP Components

• Nodes (or Hosts):

– Mobile Node (MN): a node that uses Mobile IP or system that can change
the point of connection to the network without changing its IP address
– Correspondent Node (CN): a node that communicates with a MN (may or
may not use Mobile IP)
 it is called communication partner
• Home Network
– Every node has a single Home Network; the network in which the host is
assigned its normal IP address
– From a nodes point of view, all networks other than the Home Network are
Foreign Networks
• Home Agent (HA)
– A server on the Home Network that keeps track of where the Mobile Nodes
associated with that Home Network are.
– System in the home network of the MN, typically a router
– Registers the location of the MN, tunnels IP datagrams to the COA
– Maintains a Mobility Binding Table: for its own MNs, records their current COA
Implemented on a router in the Home Network
• Foreign Agent (FA)
– A server that keeps track of Mobile Nodes visiting its network,
providing the necessary addresses and forwarding for those visiting
Mobile Nodes
– System in the current foreign network of the MN, typically a router
– Forwards the tunneled datagrams to the MN, typically also the default
router for the MN
– Maintains a Visitors List: for the visiting MNs, records their Home IP,
Home Agent and Layer 2 address
 Implemented on a router in a Foreign Network
• Home IP Address
– The IP address assigned to the MN in its Home Network
– The Home IP address is within the Home Network address range
• E.g. home network: 25.105.0.0/16; home address: 25.105.23.88/16
• Care-of-Address (COA)

– An IP address assigned to MN visiting a Foreign Network

– The COA is an IP address within the Foreign Network address range
• E.g. foreign network: 172.16.37.0/24; COA: 172.16.37.65/24
– The IP address of FA may be assigned as the COA of visiting MN
• E.g. FA 172.16.37.1/24; COA: 172.16.37.1/24
– address of the current tunnel end-point for the MN (at FA or MN)
– actual location of the MN from an IP point of view
 Mobile IP Forwarding
• Correspondent Node to Mobile • Mobile Node to Correspondent Node
Node – MN sends packets to CN (e.g.
– CN is not aware that MN is Z.a) via the local FA
“mobile” – Source Address is MN’s Home IP
– Sends packets to Home IP, e.g. (e.g. X.b)
X.b Foreign Network (for X.b)
– HA intercepts and realises the Home Network (for X.b)

MN is not home, and forwards to Z.a

CN
Foreign Network where MN is X.a
Router
X.b Router
visiting X.z
HA
Z.z
FA
Router: Y.z
FA

Y.e Y.f
HomeIP: X.b
COA: Y.m

Foreign Network (for X.b)

 Mobile IP Issues
• First Registration (in a Foreign Network)
– When a MN visits a Foreign Network it must inform the FA and its HA
• Mobile IP Registration
– BUT how does a MN know it is in a Foreign Network
• Mobile IP Agent Discovery
• Forwarding from HA to FA
– For packets sent from the CN to HA, the HA must then forward the packets to
the current FA
• Mobile IP Tunnelling
• Handover between Foreign Networks
– As a MN moves from one Foreign Network to another Foreign Network, need to
inform HA of change AND “cleanup” at the old FA
• Mobile IP Handover
• Minimising the Delay
– Routing from CN to HA then to FA can be wasteful
• Mobile IP Route Optimisation
– Handovers can take a long time (discovering new FA, informing HA)
• Mobile IP Handover Smoothing
 Mobile IP Registration
• First Registration (for example, Mobile Node powers on in a new Foreign Network)
1. MN discovers it is in a Foreign Network (see Agent Discovery)
2. MN sends a Mobile IP Registration Request to the FA
– Source IP: Home IP; Dest IP = FA
– Registration Request contains the IP address of the MN’s HA
– Note FA is configured to receive Mobile IP messages from nodes with an IP
address not on the local network
3. FA notes the MNs Home IP and allocates a COA
4. FA sends Registration Request to HA (including the allocated COA)
5. HA authenticates the MN, updates its Mobility Binding Table and returns a
Registration Reply to FA
6. Upon receipt of positive Registration Reply, FA updates its Visitors List, and
forwards reply to MN. FA will now service the MN
 2. Registration Request 4. Registration Request

6. Registration Reply 5. Registration Reply

Mobile Node Foreign Agent Home Agent
 Registration Summary
• Registration used by a MN to inform the FA that it is visiting.
– The new care of address of the MN is sent to the HA.
Registration expires, duration is negotiated during registration
Mobile must re-register before it expires
– All registrations are authenticated
 The MN sends a regristration request in to the FA which passes it
along to the home agent. The HA responds to the FA which then
informs the MN that all is in order and registration is complete.
 Mobile IP Agent Discovery
• How does a MN know the IP address of the FA?
– When it first powers up?
– When it performs a handover from an old FA to a new FA?
• Agent Advertisement/Discovery: consists of broadcast messages used
by mobiles to detect that they have moved and are required to register
with a new FA.
– FAs send agent advertisements
– MNs can solicit for agents if they have not heard an agent
advertisement in awhile or use some other mechanism to obtain a
COA or temp. IP address (e.g. DHCP).
– MNs know they are home when they recognize their HA.
 Mobile IP Tunnelling
• CN sends IP datagrams to the Home IP address
• When HA receives datagram, it checks Mobility Binding Table: if
destination node is mobile, then encapsulate original datagram in
another IP datagram
– Source: HA; Destination: COA
• FA will receive datagram, check its Visitors Table, decapsulate the IP datagram sent by CN (Z.a)

datagram, and send original datagram to MN Src: Z.a Dst: X.b Data

X.b Z.a
Router Tunnel CN
Router
X.z
Z.z
HA
IP datagram tunnelled by HA (X.z) FA
Src: X.z Dst: Y.m Src: Z.a Dst: X.b Data
Router: Y.z
FA
IP datagram received by MN (X.b)
Src: Z.a Dst: X.b Data

HomeIP: X.b
COA: Y.m
• Routing/Encapsulation/Tunneling: consists of the delivery of
the packets to the mobile node at its current care of address.
– Sender does not need to know that the destination is a MN.
– HA intercepts all packets for the MN and passes them along
to MN using a tunnel.
– MN communicates directly with the CN.
– Referred to as Triangle Routing
 Mobile IP Route Optimisation
• Routing via the HA all the time can be inefficient
– Triangular Routing Problem
– If CN and MN are “near each other”, but HA is “far away”
• E.g. CN is in Toshiba Bangkadi; MN from Toshiba US is visiting SIIT
– CN (in Bangkadi) sends to HA in US, which then sends to
FA/MN in Bangkadi
• Route Optimisation is an extension of original Mobile IP that allows CN to
send directly to MN’s COA
– MN’s and FA’s may sending Binding Warnings to HA if they see a need
for route optimisation
– HA sends Binding Updates to CN, informing the CN of the MN’s
current COA (a lifetime is associated with this COA)
 – CN maintains a Binding Cache, storing the COA of MN’s
• If COA exists in Binding Cache, CN sends with destination set to COA
• If COA does not exist, CN sends with destination set to Home IP
• Reduces delay of triangular routing, but:
– Requires CN to maintain Binding Cache (not supported in some nodes)
– Need to have security association between HA and CN
– Some security techniques that filter packets that “come from the wrong
network” may not allow the packets (ingress filtering)
 Mobility approaches
□ Two Main approaches:
♦ indirect routing: communication from
correspondent to mobile goes through home
agent, then forwarded to remote
♦ direct routing: correspondent gets foreign
address of mobile, sends directly to mobile

12-17
 Mobility via Indirect Routing
foreign agent
receives packets,
home agent intercepts forwards to mobile
packets, forwards to visited
foreign agent network
home
network
3
wide area
network
2
1
correspondent 4
addresses packets
mobile replies
using home address of
directly to
mobile
correspondent

12-18
 Indirect Routing: comments
□ Mobile uses two addresses:
♦ permanent address: used by correspondent (hence mobile
location is transparent to correspondent)
♦ care-of-address: used by home agent to forward datagrams
to mobile
□ Foreign agent functions may be done by mobile itself
□ Triangle routing: correspondent-home-visited
♦ inefficient when correspondent, mobile are in same network

12-19
 Indirect Routing: moving between networks
□ Suppose mobile user moves to another network
♦ registers with new foreign agent
♦ new foreign agent registers with home agent
♦ home agent updates care-of-address for mobile
♦ packets continue to be forwarded to mobile (but with new care-of-
address)

□ Mobility, changing foreign networks transparent: ongoing connections can

be maintained!

12-20
 Mobility via Direct Routing
foreign agent
receives packets,
correspondent forwards forwards to mobile
to foreign agent visited
network
home
network 4
wide area
2 network
3 5

correspondent 1
mobile replies
requests, receives
directly to
foreign address of
correspondent
mobile

12-21
 Mobility via Direct Routing: comments
□ Overcomes triangle routing problem
□ Non-transparent to correspondent: correspondent must
get care-of-address from home agent
♦ what if mobile changes visited network?

12-22
Accommodating mobility with direct routing
□ anchor foreign agent: FA in first visited network
□ data always routed first to anchor FA
□ when mobile moves: new FA arranges to have data
forwarded from old FA (chaining)

foreign net visited

at session start
anchor
foreign
wide area agent
2
network
1 4
3
5
new
correspondent foreign
new foreign
agent network
correspondent agent
12-23