Scribd
Upload
14 views44 pages

User Datagram Protocol

Uploaded by

hell1234
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
14 views44 pages

User Datagram Protocol

Uploaded by

hell1234
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/ 44

Chapter 23

Process-to-Process Delivery:
UDP, TCP, and SCTP
23-1 PROCESS-TO-PROCESS DELIVERY

The transport layer is responsible for process-to-


process delivery—the delivery of a packet, part of a
message, from one process to another. Two processes
communicate in a client/server relationship, as we will
see later.
Topics discussed in this section:
Client/Server Paradigm
Multiplexing and Demultiplexing
Connectionless Versus Connection-Oriented Service
Reliable Versus Unreliable
Three Protocols
23.2
Note

The transport layer is responsible for


process-to-process delivery.

23.3
Figure 23.1 Types of data deliveries

23.4
Figure 23.2 Port numbers

23.5
Figure 23.3 IP addresses versus port numbers

23.6
Figure 23.4 IANA (Internet Assigned Number Authority) ranges

23.7
Figure 23.5 Socket address

23.8
Figure 23.7 Error control

23.9
Figure 23.8 Position of UDP, TCP, and SCTP in TCP/IP suite

23.10
23-2 USER DATAGRAM PROTOCOL (UDP)

The User Datagram Protocol (UDP) is called a


connectionless, unreliable transport protocol. It does
not add anything to the services of IP except to provide
process-to-process communication instead of host-to-
host communication.
Topics discussed in this section:
Well-Known Ports for UDP
User Datagram
Checksum
UDP Operation
Use of UDP
23.11
Table 23.1 Well-known ports used with UDP

23.12
Figure 23.9 User datagram format

23.13
Note

UDP length
= IP length – IP header’s length

23.14
Figure 23.10 Pseudoheader for checksum calculation

23.15
Example 23.2

Figure 23.11 shows the checksum calculation for a very


small user datagram with only 7 bytes of data. Because
the number of bytes of data is odd, padding is added for
checksum calculation. The pseudoheader as well as the
padding will be dropped when the user datagram is
delivered to IP.

23.16
Figure 23.11 Checksum calculation of a simple UDP user datagram

23.17
Q. The following is a dump of a UDP header in hexadecimal form: 06 32

00 0D 00 1C E2 17

What is the
(a)Source port number
(b) Destination port number

(c) Total length of the UDP

(d) Length of the data

(e) Considering that an IP frame can have a maximum total length of 65 535

bytes, what is the maximum length of the data in a UDP frame?


23.18
The UDP header has four parts, each of two bytes. That means we get the

following interpretation of the header.

(a)Source port number = 0x0632 = 1586


(b) Destination port number = 0x000D= 13
(c)Total length = 0x001C = 28 bytes
(d)Since the header is 8 bytes the data length is 28 − 8 = 20 bytes.
(e)The IP header is minimum 20 bytes, which gives the maximum payload
65515 bytes. To fit a UDP frame in this with header of 8 bytes we get data

65515−8 = 65507 bytes

23.19
23-3 TCP

TCP is a connection-oriented protocol; it creates a


virtual connection between two TCPs to send data. In
addition, TCP uses flow and error control mechanisms
at the transport level.

Topics discussed in this section:


TCP Services
TCP Features
Segment
A TCP Connection
Flow Control
Error Control
23.20
Table 23.2 Well-known ports used by TCP

23.21
Figure 23.13 Stream delivery

23.22
Figure 23.14 Sending and receiving buffers

23.23
Figure 23.15 TCP segments

23.24
The bytes of data being transferred in
each connection are numbered by TCP.
The numbering starts with a randomly
generated number.

23.25
Example 23.3

The following shows the sequence number for each


segment:

23.26
The value in the sequence number field
of a segment defines the
number of the first data byte
contained in that segment.

23.27
The value of the acknowledgment field
in a segment defines
the number of the next byte a party
expects to receive.
The acknowledgment number is
cumulative.

23.28
Figure 23.16 TCP segment format

23.29
The following is a dump of a TCP header in hexadecimal format.

05320017 00000001 00000000 500207FF 00000000

a. What is the source port number?

b. What is the destination port number?

c. What is the sequence number?

d. What is the acknowledgment number?

e. What is the length of header?

f. What is the type of segment?


23.30
Solution:

• The source port number is 0x0532 (1330 in decimal).

• The destination port number is 0x0017 (23 in decimal).

• The sequence number is 0x00000001 (1 in decimal).

• The acknowledgment number is 0x00000000 (0 in decimal).

• The header length is 0x5 (5 in decimal). There are 5 × 4 or 20 bytes of

header.

• The control field is 0x002. This indicates a SYN segment used for

connection establishment.

• The window size field is 0x07FF (2047 in decimal).


23.31
Figure 23.17 Control field

23.32
Table 23.3 Description of flags in the control field

23.33
Figure 23.18 Connection establishment using three-way handshaking

23.34
Note

A SYN segment cannot carry data, but it


consumes one sequence number.

23.35
Note

A SYN + ACK segment cannot


carry data, but does consume one
sequence number.

23.36
Note

An ACK segment, if carrying no data,


consumes no sequence number.

23.37
Figure 23.19 Data transfer

23.38
Figure 23.20 Connection termination using three-way handshaking

23.39
Note

The FIN segment consumes one


sequence number if it does
not carry data.

23.40
Note

The FIN + ACK segment consumes


one sequence number if it
does not carry data.

23.41
Figure 23.21 Half-close

23.42
Figure 23.22 Sliding window

23.43
Note

A sliding window is used to make


transmission more efficient as well as
to control the flow of data so that the
destination does not become
overwhelmed with data.
TCP sliding windows are byte-oriented.

23.44

You might also like