Scribd
Upload
63 views4 pages

Mobile Ip

- Mobile hosts obtain a care-of address from a foreign agent when away from their home network and register this address with their home agent. - The home agent maintains the care-of address for the mobile host and intercepts and tunnels packets to the care-of address when the mobile host is away. - Authentication of registration and binding update messages involves shared secrets, MD5 checksums, sequence numbers, and nonces to prevent replay and establish trust between nodes.

Uploaded by

Eithu Thutun
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
63 views4 pages

Mobile Ip

- Mobile hosts obtain a care-of address from a foreign agent when away from their home network and register this address with their home agent. - The home agent maintains the care-of address for the mobile host and intercepts and tunnels packets to the care-of address when the mobile host is away. - Authentication of registration and binding update messages involves shared secrets, MD5 checksums, sequence numbers, and nonces to prevent replay and establish trust between nodes.

Uploaded by

Eithu Thutun
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Mobile-IP Basic

Mobile Host (MH) obtain care-of (C/O)address - foreign agent: router or BS that is willing to route - temporary IP (i.e. DHCP) register with home agent Home Agent (HA) maintain C/O address for MH away from home network intercept packets for MH (proxy-ARP) encapsulate and tunnel to C/O address Foreign Agent (FA) Advertisement: (i.e. extending ICMP-router advertisement) Decapsulate packet and deliver to MH

1 of 4

Route Optimization
Binding home address --> care-of address life time: timeout Cache Agent maintain location cache: direct tunneling ush out or request update entries that timeout binding update from HA: update cache binding advise: request new binding from HA Home Agent send binding update upon receiving normal IP for MH back-off to prevent lack of cache agent at sender

2 of 4

Authentication
Registration (MH to HA) message includes: MD-5 checksum with pre-established shared secret sequence number => prevent replay Binding Update (HA to CH) message: nonce: random number used only once trusted nodes along the path (IP trust level) MH - FA: upon registration, establish shared key (clear text) when move away, send binding update to old FA with MD-5
checksum

3 of 4

{registration} MD5

encap, tunnel
HA FA

decap
MH share secret

normal IP-routing

{binding request & update} nonce

{bind update} MD5

optimized tunnel
new FA

CH

$A

MH

4 of 4

You might also like