1) Introduction

2) Mobile IP Components

3) How Mobile IP works

4) IP v4 Header

5) IP v6 Header

6) Problems with mobile IPV4

7) IS IP v6 solution

8) Mobile Ipv6 Security Threats

9) Conclusion
 Allows routing of IP datagrams to mobile nodes .
 Mobile Nodes can roam across different IP sub-networks.
 Dynamic Routing Protocol.
 Designed for mobility.
 It chooses best available path routes and inserts them into the
routing table.
 Mobile IP builds its own links, known as tunnels, which are used for
routing.
 A Mobile IP deployment is characterized, at a minimum, by the
concepts of a Home Agent (HA), Foreign Agent (FA), Mobile Node
(MN), Home Network, Home Address, and Care-of-Address (CoA).
Postal service
Postal Service When you move
 Mobile
 Home Network
 Home Agent (HA)
 Foreign Network
 Foreign Agent (FA)
 Care-of address (CoA)
Mobile IP Components Overview
 Mobile Node: User is connected to one or more applications across
the internet, that the user’s point of attachment changes dynamically.

When a Mobile Node moves from one location to another, it must report
its movement to the Home Agent

 Home Address: A permanent fixed IP address of the mobile node

assigned by a particular network.

 Home Network: The home network of a mobile device is the network

belongs to its permanent IP address

 Foreign Network: When the associated network is not home due to

the movement of the device from its home network.
 Home Agent: Home agent is the home post-box of a mobile node.
Each node is associated to a home agent and maintains channeling of
its communication with other devices using home agent.

Messages are redirected to the Mobile Node in its current location

through Home Agent and are the prime responsibility of the Home
Agent.

 Care of address (CoA): The CoA is an IP address or network

address assigned by the foreign agent to a mobile.

The Mobile Node informs its Home Agent of his current CoA during
registration process with foreign agent.
 Foreign Agent (FA): It is usually a router attached to the access
link where the mobile node registers itself as a visiting node.
A foreign agent periodically advertises one of more COA for the
visiting nodes to request a registration with the FA.

 Correspondence Node (CN): A correspondence node is a node of

the mobile node associated with any network with which the mobile
node exchanges information in a particular instance.

A CN could be another Mobile Node or a fixed node in and outside

of its home network
 Version: 4 bits
IPv version number

 Internet Header Length: 4bits

Length of header. The minimum value is 160 bits.

 Type of service : 8 bits

This field referred as precedence, delay.

 Total length: 16bits

Total packet length.

 Identification: 16bits
A sequence number which is unique for source address, destination
address for the time during which the packet will remain in the
internet
 Flags: 3bits
Two bits are currently defined.
The MORE bit is indicate this is last fragment in the original
packet
The DON’T bit prohibits fragmentation when set.

 Fragment offset: 13 bits

When data units get fragmented, the protocol must identify where
each particular fragment belongs in the reassembled data unit.

 Time to live: 8 bits

How long, in seconds, a packet is allowed to remain in the
internet.

 Protocol: 8 bits
Next higher level protocol, which is to receive the data at destination.
 Header Checksum : 16 bits
An error detecting code applied to the header for detecting error after
transmit packet.

 Source Address: 32 bits

 Destination Address: 32 bits

 Options (Variable):
Includes security label, source routing.

 Padding(Variable);
To ensure that the packet header is multiple of 32 bits in length.
0001020304050607080910111213141516171819202122232425262728293031

Version Traffic Class Flow Label

Payload Length Next Header Hop Limit

Source address :::

Destination address :::

Data :::
 Version. 4 bits.
IP version number.

 Traffic Class. 8 bits.

Internet traffic priority delivery value.

 Flow Label. 20 bits.

Used for specifying special router handling from source to
destination(s) for a sequence of packets.

 Payload Length. 16 bits unsigned.

Specifies the length of the data in the packet. When cleared to zero,
the option is a hop-by-hop Jumbo payload.

 Next Header. 8 bits.

Specifies the next encapsulated protocol. The values are compatible
with those specified for the IPv4 protocol field.
 Hop Limit.
For each router that forwards the packet the hop limit is
decremented by 1. When the hop limit field reaches zero, the packet
is discarded. This replaces the TTL(time to live) field in the IPv4
header that was originally intended to be used as a time based hop
limit.

 Source address. 16 bytes.

The IPv6 address of the sending node.

 Destination address. 16 bytes.

The IPv6 address of the destination node.
 Triangle Routing Problem

Triangle routing problem delays the delivery of the datagrams and

places an unnecessary burden on networks and routers
 Less Address

The biggest problem with the Internet Protocol as it exists today is

that we are rapidly reaching a point where available network address
space is running out. IPv4 allows for about 2^32 or 4,294,967,296
addresses. Which has already been completely allocated and
therefore, leaves no room for growth
 IP SECURITY
The lack of real end-to-end security in the IP protocol is becoming a
problem today. As with mobility there are many great extensions to the
IPv4 protocol that provide security, such as IPsec and HTTPS, but
being that they are not part of IPv4 itself, these extensions are not
implemented pervasively.

MOBILITY SUPPORT
IPv4 was not initially designed with support for mobile users because
mobility was not an issue when the Internet began. Mobility was later
added as extensions to the IPv4 protocol.

Denial of Service Attack (DOS)

User floods with nuisance packets so that no one can accomplish their
tasks (TCP SYN flooding).
 Packets sent to a mobile node while away from home in Mobile
IPv6 are tunneled using an IPv6 routing header than IP
encapsulation whereas Mobile IPv4 must use encapsulation for all
packets.

 More address 2^128 340,282,366,920,938,463,463, 374,607,431,

768,211, 456 addresses. This seemingly limitless number of
addresses.

 No need to deploy special routers as “foreign agent” as are used in

mobile IPv4. Mobile IPv6 mobile nodes make use of the enhanced
feature’s of IPv6 such as neighbor discovery.

 Mobile IPv6 uses destination options which allow all mobile IPv6
control traffic to be piggybacked on any existing IPv6 packets.
ROUTE OPTIMIZATION
 MOBILE IPV6 SECURITY THREATS

1. FALSE BINDING UPDATE ATTACKS

2. MAN-IN-THE-MIDDLE ATTACK
FALSE BINDING UPDATE ATTACKS
MAN-IN-THE-MIDDLE ATTACK
The increasing demand for wireless services in recent years is driving
the need for a new version of IP that addresses the limitations of
the current IP protocol. This new version, called IPv6, with its many
advantages including increased address space, neighbor discovery, is a
promising technology to enable the mobile IP world of tomorrow.
The transition to IPv6 is now the obvious solution to a growing
problem and this transition process has already begun. And, although
Mobile IPv6 has recently been slowed down in standardization due to
security issues, these issues will have to continue to get attention, get
resolved and integrated into the protocol itself, making every device in
tomorrow’s Internet, a Mobile IPv6 device, and the Mobile Internet,
more efficient, robust, and secure.