0% found this document useful (0 votes)
164 views25 pages

The Internet Protocol Version 4 (Ipv4) Is The Delivery Mechanism Used by The Tcp/Ip Protocols

The document discusses IPv4, the network layer protocol in TCP/IP. It describes the IPv4 datagram format and header fields including version, header length, total length, fragmentation fields, time to live, protocol, checksum, and source/destination addresses. It provides examples of interpreting IPv4 packet fields. It also introduces IPv6, noting IPv4 deficiencies, and describes the IPv6 datagram header format and priority codes.

Uploaded by

Chhaya Nayak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
164 views25 pages

The Internet Protocol Version 4 (Ipv4) Is The Delivery Mechanism Used by The Tcp/Ip Protocols

The document discusses IPv4, the network layer protocol in TCP/IP. It describes the IPv4 datagram format and header fields including version, header length, total length, fragmentation fields, time to live, protocol, checksum, and source/destination addresses. It provides examples of interpreting IPv4 packet fields. It also introduces IPv6, noting IPv4 deficiencies, and describes the IPv6 datagram header format and priority codes.

Uploaded by

Chhaya Nayak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

IPV4

The Internet Protocol version 4


(IPv4) is the delivery mechanism
used
by the TCP/IP protocols.

20.1
Position of IPv4 in TCP/IP protocol
suite

20.2
IPv4 datagram format

20.3
IPv4 Header
 Variable length: 20-60 byte (multiple of 4)
 Contains routing information

20.4
IPv4 Format
 Version (4-bit): currently 4.
 Header length (4-bit): the length of the IP
header in 4-byte unit.
 Type of Services(TOS):
◦ This field was not used earlier because of
the lack of standard
◦ DiffServ uses this field for differentiate
packet types.

20.5
 Total length
◦ to defines the total length of the datagram
including the header in bytes.
◦ 16-bit number, the maximum IP size is
limited to 216 bytes, or 64 Kbytes.

20.6
Fields for Fragmentation
 Identification
◦ The source host generates the unique ID
 Flags (3-bits)
◦ Unused bit
◦ DF bit (Don’t Fragment)
 1-
 MF bit (More Fragment)
 1 – tell the destination whether or not more
fragments follow-
 Offset
◦ Unit of 8-byte (why?)
◦ Between the beginning of the packet to be
fragmented and the beginning of the fragment
20.7
 Time to Live (TTL)
◦ A packet has a limited lifetime in the
network .
◦ Designed to hold a timestamp, and
decreased by each router. A packet is
discarded by a router if TTL is zero.
◦ Revised to hold the maximum
number of hops the packet can travel
thru the network.
◦ Each router decrements it by one.
20.8
 Protocol
◦ To define payload protocol type
◦ 1 for ICMP
◦ 2 for IGMP
◦ 6 for TCP
◦ 17 for UDP
◦ 89 for OSPF

20.9
 Header checksum
◦ An IP header is slightly modified by
each router. At least TTL field.
◦ The checksum must be re-calculated
by routers which is a kind of general
computers with more than one
network interface.
◦ The checksum must be efficiently
calculated with no need of special
hardware.
20.10
 Source IP address and Destination IP
address
 Options
◦ Variable length
◦ For new protocols
 Padding
◦ To make the header a multiple of 32-bit words

20.11
Example 20.1

An IPv4 packet has arrived with the first 8 bits as


shown:
01000010
The receiver discards the packet. Why?
Solution
There is an error in this packet. The 4 leftmost bits
(0100) show the version, which is correct. The next
4 bits (0010) show an invalid header length (2 × 4
= 8). The minimum number of bytes in the header
must be 20. The packet has been corrupted in
transmission.
20.12
Example 20.2

In an IPv4 packet, the value of HLEN is 1000 in


binary. How many bytes of options are being
carried by this packet?

Solution
The HLEN value is 8, which means the total
number of bytes in the header is 8 × 4, or 32 bytes.
The first 20 bytes are the base header, the next 12
bytes are the options.

20.13
Example 20.3

In an IPv4 packet, the value of HLEN is 5, and the


value of the total length field is 0x0028. How many
bytes of data are being carried by this packet?

Solution
The HLEN value is 5, which means the total
number of bytes in the header is 5 × 4, or 20 bytes
(no options). The total length is 40 bytes, which
means the packet is carrying 20 bytes of data (40 −
20).

20.14
MTUs for some networks

20.15
Example 20.5

A packet has arrived with an M bit value of 0. Is


this the first fragment, the last fragment, or a
middle fragment? Do we know if the packet was
fragmented?
Solution
If the M bit is 0, it means that there are no more
fragments; the fragment is the last one. However,
we cannot say if the original packet was
fragmented or not. A non-fragmented packet is
considered the last fragment.

20.16
Example 20.6

A packet has arrived with an M bit value of 1. Is


this the first fragment, the last fragment, or a
middle fragment? Do we know if the packet was
fragmented?
Solution
If the M bit is 1, it means that there is at least one
more fragment. This fragment can be the first one
or a middle one, but not the last one. We don’t
know if it is the first one or a middle one; we need
more information (the value of the fragmentation
offset).
20.17
Example 20.7

A packet has arrived with an M bit value of 1 and a


fragmentation offset value of 0. Is this the first
fragment, the last fragment, or a middle fragment?

Solution
Because the M bit is 1, it is either the first
fragment or a middle one. Because the offset value
is 0, it is the first fragment.

20.18
IPv6

THE NETWORK LAYER PROTOCOL IN THE


TCP/IP PROTOCOL SUITE IS CURRENTLY
IPV4.. IPV4 HAS SOME DEFICIENCIES THAT
MAKE IT UNSUITABLE FOR THE FAST-
GROWING INTERNET

20.19
Figure 20.15 IPv6 datagram header and payload

20.20
Format of an IPv6 datagram

20.21
Table 20.6 Next header codes for IPv6

20.22
Table 20.7 Priorities for congestion-controlled traffic

20.23
Table 20.8 Priorities for noncongestion-controlled traffic

20.24
Table 20.9 Comparison between IPv4 and IPv6 packet headers

20.25

You might also like