Advance Computer Networks

INT311

Mobile IP, IPv6 and QoS mechanisms

Copyright © The McGraw-Hill Companies, Inc.

 20-1 INTERNETWORKING

In this chapter, we will discuss internetworking,

connecting networks together to make an internetwork
or an internet.

20.2
 Figure 20.1 Links between two hosts

20.3
 Figure 20.2 Network layer in an internetwork

20.4
 Figure 20.3 Network layer at the source, router, and destination

20.5
 Figure 20.3 Network layer at the source, router, and destination (continued)

20.6
Packet Switching

 Data transmitted in small packets

 Typically less than 1500 bytes

 Longer messages split into series of packets

 Each packet contains a portion of user data

plus some control info

 Control info
 Routing (addressing) info

 Packets are received, stored briefly (buffered)

and past on to the next node
 Store and forward
Use of Packets
Switching Technique

 Station breaks long message into

packets
 Packets are sent one at a time to
the network
 Packets are handled in two ways
 Datagram
 Virtual circuit
Datagram

 Each packet is treated

independently
 Packets can take any practical
route
 Packets may arrive out of order
 Packets may go missing
 Up to receiver to re-order packets
and recover from missing packets
Datagram
Diagram
Virtual Circuit

 Preplanned route established before any

packets sent
 Call request and call accept packets
establish connection (handshake)
 Each packet contains a virtual circuit
identifier instead of destination address
 No routing decisions required for each
packet
 Clear request to drop circuit
Virtual
Circuit
Diagram
Virtual Circuits vs
Datagram
Virtual circuits
Network can provide sequencing and error control
 Packets are forwarded more quickly

No routing decisions to make
 Less reliable


Loss of a node looses all circuits through that node
 Datagram
 No call setup phase


Better if few packets
 More flexible


Routing can be used to avoid congested parts of
the network
 Note

Switching at the network layer in the

Internet uses the datagram approach for
packet switching.

20.15
 Mobile IP
 Mobile and personal computers, such as
notebooks and smartphones have become
increasingly popular, we need to think about
mobile IP.
 It is an extension of IP protocol that allows mobile
computers to be connected to the Internet at any
location where the connection is possible.

14.16
 Addressing
 The main problem that must be solved in
providing mobile communication using the IP
protocol is addressing.
 Stationary Hosts
 The IP addresses are designed to work with

stationary hosts because part of the address

defines the network to which the host is
attached.
 Mobile Hosts
 Changing the Address

 Two Addresses

14.17
 Why Mobile IP
 It will be very nice if mobility does not affect
internet sessions.
 For example, we should be able to take a
laptop computer from our workplace to home
without noticing any change in the internet
connectivity
 Mobility of the computer should be
completely transparent to the applications
running on the computer

20.18
  For example, the user should continue to
receive emails and keep connected to the
internet.
 Mobile IP makes mobility completely
transparent to applications running on a
mobile computer
 The applications feel that the mobile computer
is connected to its usual IP address even if it is
far away from its home network.
20.19
 The problem with Internet
Protocol (IP)
 IP routes packets to their destinations according
to IP addresses.

 An IP address is associated with a fixed network

location.

 When a user moves, each new point of

attachment has a new IP address. Hence it is very
difficult to keep mobility transparent
20.20
 How TCP works
 Most internet connections use TCP. A good
example is email clients.
 A TCP connection is uniquely identified by
four components :
<IP_source, port_source,IP_dest, port_dest>
 If we change any one of these four
components, the connection will be broken.

20.21
  If a packet has to be delivered to a mobile
node’s current point of attachment, we need
to change the destination IP address and port
number
 It is impossible to do so once a connection
has been established.
 Mobile IP allows a mobile node to use two
different IP addresses.

20.22
 Changing the Address

 One simple solution is to let the mobile host change

its address as it goes to the new network.
 The host can use DHCP to obtain a new address to
associate it with the new network.
 This approach has several drawbacks.
 The configuration files would need to be

changed.
 The DNS tables need to be revised so that every

other host in the Internet is aware of the change.

 If the host roams from one network to another

during a transmission, the data exchange will be

interrupted.

14.23
 Two Addresses
 The approach that is more feasible is the use of
two addresses. The host has its original address,
called the home address, and a temporary
address, called the care-of address.
 The home address is permanent; it associates the
host with its home network, the network that is
the permanent home of the host. The care-of
address is temporary.
 When a host moves from one network to another,
the care-of address changes; it is associated with
the foreign network, the network to which the
host moves.

14.24
 Diagram of Mobile IP

20.25
 Home address and Care-of
Address

14.26
 Home Agent and Foreign Agent
 Home Agent
 The home agent is usually a router attached to the
home network of the mobile host. The home agent
acts on behalf of the mobile host when a remote host
sends a packet to the mobile host. The home agent
receives the packet and sends it to the foreign agent.
 Foreign Agent
 The foreign agent is usually a router attached to the
foreign network. The foreign agent receives and
delivers packets sent by the home agent to the mobile
host.
 When the mobile host acts as a foreign agent, the care-of
address is called a collocated care-of address.

14.27
 Home Agent and Foreign Agent

14.28
 Remote Host and Mobile Host
Communication

14.29
 Data transfer

20.30
 Problems: Triangular
delivery
• When the remote host sends a packet to the mobile host:
• The packet goes from the remote host to the home
agent and then to the mobile host.
• The packet travels the two sides of a triangle.

20.31
 Double Crossing

• When the remote host sends a

packet to the mobile host:
• The packet crosses the Internet twice.

20.32
 20-2 IPv4

The Internet Protocol version 4 (IPv4) is the delivery

mechanism used by the TCP/IP protocols.

20.33
 Figure 20.4 Position of IPv4 in TCP/IP protocol suite

20.34
 Note

IPv4 is an unreliable and connectionless

datagram protocol – a best effort
delivery
Best effort means that IPv4 provides no
error control (except for error detection
on the header) or flow control
IPv4 does its best to get a transmission
through to its destination, but with no
guarantees
20.35
 Figure 20.5 IPv4 datagram format

20.36
 Figure 20.6 Service type or differentiated services

20.37
 Table 20.1 Types of service

20.38
 Table 20.2 Default types of service

20.39
 Figure 20.8 Protocol field and encapsulated data

20.40
 Table 20.4 Protocol values

20.41
 20-3 IPv6

Although IPv4 is well designed, data communication

has evolved since the inception of IPv4 in the 1970s.
IPv4 has some deficiencies that make it unsuitable for
the fast-growing Internet.

20.42
 IPv4 and IPv6

 Currently, there are approximately 1.3 billion usable IPv4 addresses

available.
 IPv6 Address
Representation
 Format:
 x:x:x:x:x:x:x:x, where x is a 16-bit hexadecimal field.

Case-insensitive for hexadecimal A, B, C, D, E, and F
 Leading zeros in a field are optional.
 Successive fields of zeros can be represented as :: only once
per address.
 Examples:
 2031:0000:130F:0000:0000:09C0:876A:130B

Can be represented as 2031:0:130f::9c0:876a:130b

Cannot be represented as 2031::130f::9c0:876a:130b
 FF01:0:0:0:0:0:0:1 FF01::1
 0:0:0:0:0:0:0:1 ::1
 0:0:0:0:0:0:0:0 ::
IPv6 Address Types
 Unicast

Address is for a single interface.

IPv6 has several types (for example, global, reserved, and link-
local).
 Multicast

One-to-many.

Enables more efficient use of the network.

Uses a larger address range.
 Anycast

One-to-nearest (allocated from unicast address space).

Multiple devices share the same address.

All anycast nodes should provide uniform service.

Source devices send packets to anycast address.

Routers decide on closest device to reach that destination.

Suitable for load balancing and content delivery services.
IPv6 Unicast Addressing
 These are types of IPv6 unicast addresses.

Global: Starts with 2000::/3 and assigned by IANA

Reserved: Used by the IETF

Private: Link local (starts with FE80::/10)

Loopback (::1)

Unspecified (::)
 A single interface may be assigned multiple
IPv6 addresses of any type: unicast, anycast,
or multicast.
 IPv6 addressing rules are covered by multiple
RFCs.

Architecture defined by RFC 4291
IPv6: Advantages

 Larger address space.

 Better header format.
 New options.
 Allowance for extensions.
 Support for resource allocation.
 Support for more security.
 Figure 20.15 IPv6 datagram header and payload

20.48
 Figure 20.16 Format of an IPv6 datagram

20.49
 Table 20.6 Next header codes for IPv6

20.50
 Table 20.7 Priorities for congestion-controlled traffic

20.51
 Table 20.8 Priorities for noncongestion-controlled traffic

20.52
 Table 20.9 Comparison between IPv4 and IPv6 packet headers

20.53
 Table 20.9 Comparison between IPv4 and IPv6 packet headers

• IPv4 is 32-Bit IP address whereas IPv6 is a 128-Bit IP address.

• IPv4 is a numeric addressing method whereas IPv6 is an alphanumeric
addressing method.
• IPv4 binary bits are separated by a dot(.) whereas IPv6 binary bits are
separated by a colon(:).
• IPv4 offers 12 header fields whereas IPv6 offers 8 header fields.
• IPv4 supports broadcast whereas IPv6 doesn’t support broadcast.
• IPv4 has checksum fields while IPv6 doesn’t have checksum fields
• IPv4 supports VLSM (Variable Length Subnet Mask) whereas IPv6
doesn’t support VLSM.
• IPv4 uses ARP (Address Resolution Protocol) to map to MAC address
whereas IPv6 uses NDP (Neighbor Discovery Protocol) to map to MAC
address.

20.54
 20-4 TRANSITION FROM IPv4 TO IPv6

Because of the huge number of systems on the

Internet, the transition from IPv4 to IPv6 cannot
happen suddenly. It takes a considerable amount of
time before every system in the Internet can move from
IPv4 to IPv6. The transition must be smooth to prevent
any problems between IPv4 and IPv6 systems.

20.55
 Figure 20.18 Three transition strategies

20.56
Dual stack

 Dual stack host can speak both IPv4

and IPv6
 communicate with IPv4 host by IPv4
 communicate with IPv6 host by IPv6
 Dual stack host look up DNS entry
by IPv4

57
 Figure 20.19 Dual stack

20.58
Cisco IOS Dual Stack
IPv4

IPv6

Dual stack is an integration method in which a node has

implementation and connectivity to both an IPv4 and IPv6
network.
Cisco IOS Dual Stack
(Cont.)

IPv4: 192.168.99.1
IPv6: 3ffe:b00:c18:1::3

When both IPv4 and IPv6 are configured on an interface, the

interface is considered dual-stacked.
IPv6 Tunneling

IPv6 IPv4 IPv6 IPv6

Tunneling is an integration method in which an IPv6

packet is encapsulated within another protocol, such as
IPv4. This method of encapsulation is IPv4.
 Includes a 20-byte IPv4 header with no options and an IPv6 header
and payload
 Requires dual-stack routers
 Figure 20.20 Tunneling strategy

20.62
IPv6 tunnel over IPv4

IPv4
Network
IPv6 IPv6
tunnel

IPv4 Header IPv6 Header Data

IPv6 Header Data IPv6 Header Data

63
 Tunneling
 IPv6 packets goes through IPv4
network
IPv6 IPv6
Host IPv6
IPv6R IPv4 R IPv6 Host

IPv4
IPv6

IPv6
Data

Data

Data
De-Cap En-Cap

• IPv4 packets goes through IPv6 network

IPv4 IPv4
Host IPv4 R IPv6 R IPv4 Host
IPv4

IPv6
IPv4

IPv4
Data

Data

Data
De-Cap En-Cap

64
 Figure 20.21 Header translation strategy

20.65
 Address Translation
 IPv6 packets goes through IPv4 network

IPv6 IPv4
Host IPv6 R IPv4 Host

Network Address
Translation (NAT)

IPv6

IPv4
Data

Data
Port
66
 Table 20.11 Header translation

20.67