Scribd
Upload
15 views

Data Communication

IPv4 is the delivery mechanism used by TCP/IP protocols. It has a variable length header and uses fragmentation. IPv6 was developed to replace IPv4 and has many advantages like a larger address space, simpler header format, extension headers, and security improvements.

Uploaded by

Basketball
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
15 views

Data Communication

IPv4 is the delivery mechanism used by TCP/IP protocols. It has a variable length header and uses fragmentation. IPv6 was developed to replace IPv4 and has many advantages like a larger address space, simpler header format, extension headers, and security improvements.

Uploaded by

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

IPv4

The Internet Protocol version 4 (IPv4) is the delivery


mechanism used by the TCP/IP protocols.
Position of IPv4 in TCP/IP protocol suite
IPv4 datagram format
• Version (VER): This 4-bit field defines the version of the IPv4 protocol.
Currently the version is 4. However, version 6 (or IPng) may totally replace
version 4 in the future.
• Header length (HLEN).:This 4-bit field defines the total length of the
datagram header in 4-byte words.
This field is needed because the length of the header is variable (between
20 and 60 bytes). When there are no options, the header length is 20 bytes,
and the value of this field is 5 (5 x 4 = 20). When the option field is at its
maximum size, the value of this field is 15 (15 x 4 = 60).
• Services: IETF has changed the interpretation and
name of this 8-bit field. This field, previously called
service type, is now called differentiated services

• Identification: This field is used in fragmentation


(discussed in the next section).
• Flags: This field is used in fragmentation (discussed in
the next section).
• Fragmentation offset: This field is used in
fragmentation (discussed in the next section).
Service type or differentiated services

Length of data=Total length –header length


• Precedence: This is a 3-bit subfield ranging from 0 (000 in
binary) to 7 (111 in binary).
The precedence defines the priority of the datagram in issues
such as congestion. If a router is congested and needs to
discard some datagrams, those datagrams with lowest
precedence are discarded first. Some datagrams in the Internet
are more important than others.

For example, a datagram used for network management


Table 20.1 Types of service
Table 20.2 Default types of service
Note

The total length field defines the total


length of the datagram including the
header.
Identification
• Identification: This 16-bit field identifies a datagram
originating from the source host.
• The combination of the identification and source IPv4
address must uniquely define a datagram as it leaves
the source host.
• To guarantee uniqueness, the IPv4protocol uses a
counter to label the datagrams.
• The counter is initialized to a positive number.
FLAGS
• Flags: This is a 3-bit field. The first bit is reserved.
• The second bit is called the do not fragment bit.
• If its value is 1, the machine must not fragment the datagram.
• If it cannot pass the datagram through any available physical
network, it discards the datagram and sends an ICMP error
message to the source host.
• If its value is 0, the datagram can be fragmented if necessary.

• The third bit is called the more fragment bit.


• If its value is 1, it means the datagram is not the last fragment;
there are more fragments after this one.
• If its value is 0, it means this is the last or only fragment.
• Fragmentation offset: This 13-bit field shows
the relative position of this fragment with respect
to the whole datagram.
• Time to live: A datagram has a limited lifetime
in its travel through an internet. This field was
originally designed to hold a timestamp.
Figure 20.8 Protocol field and encapsulated data
Table 20.4 Protocol values
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.
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.
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).
Example 20.4

An IPv4 packet has arrived with the first few hexadecimal


digits as shown.
0x45000028000100000102 . . .
How many hops can this packet travel before being
dropped? The data belong to what upper-layer protocol?

Solution
To find the time-to-live field, we skip 8 bytes. The time-to-
live field is the ninth byte, which is 01. This means the
packet can travel only one hop. The protocol field is the
next byte (02), which means that the upper-layer protocol
is IGMP.
Figure 20.9 Maximum transfer unit (MTU)
Table 20.5 MTUs for some networks
Figure 20.10 Flags used in fragmentation
Figure 20.11 Fragmentation example
Figure 20.12 Detailed fragmentation example
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.
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).
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.
Example 20.8

A packet has arrived in which the offset value is 100.


What is the number of the first byte? Do we know the
number of the last byte?

Solution
To find the number of the first byte, we multiply the offset
value by 8. This means that the first byte number is 800.
We cannot determine the number of the last byte unless
we know the length.
Example 20.9

A packet has arrived in which the offset value is 100, the


value of HLEN is 5, and the value of the total length field
is 100. What are the numbers of the first byte and the last
byte?
Solution
The first byte number is 100 × 8 = 800. The total length is
100 bytes, and the header length is 20 bytes (5 × 4), which
means that there are 80 bytes in this datagram. If the first
byte number is 800, the last byte number must be 879.
Example 20.10

Figure 20.13 shows an example of a checksum


calculation for an IPv4 header without options. The
header is divided into 16-bit sections. All the sections are
added and the sum is complemented. The result is
inserted in the checksum field.
Figure 20.13 Example of checksum calculation in IPv4
20-3 IPv6

The network layer protocol in the TCP/IP protocol suite


is currently IPv4. 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.

Topics discussed in this section:


Advantages
Packet Format
Extension Headers
20.32
Figure 20.15 IPv6 datagram header and payload

20.33
Figure 20.16 Format of an IPv6 datagram

20.34
Note

An IPv6 address is 128 bits long.

19.35
Figure 19.14 IPv6 address in binary and hexadecimal colon notation

19.36
Figure 19.15 Abbreviated IPv6 addresses

19.37
Example 19.11

Expand the address 0:15::1:12:1213 to its original.

Solution
We first need to align the left side of the double colon to the
left of the original pattern and the right side of the double
colon to the right of the original pattern to find how many
0s we need to replace the double colon.

This means that the original address is.

19.38
Table 20.6 Next header codes for IPv6

20.39
Table 20.7 Priorities for congestion-controlled traffic

20.40
Table 20.8 Priorities for noncongestion-controlled traffic

20.41
20.42
Table 20.9 Comparison between IPv4 and IPv6 packet headers

20.43

You might also like