Scribd
Upload
82 views

Process-to-Process Delivery: Udp, TCP, and SCTP

Computer Networks

Uploaded by

Pikesh Patel
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
82 views

Process-to-Process Delivery: Udp, TCP, and SCTP

Computer Networks

Uploaded by

Pikesh Patel
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/ 40

Chapter 23

Process-to-Process Delivery:
UDP, TCP, and SCTP

23.1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
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 ranges

23.7
Figure 23.5 Socket address

23.8
Figure 23.6 Multiplexing and demultiplexing

23.9
Figure 23.7 Error control

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

23.11
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.12
Table 23.1 Well-known ports used with UDP

23.13
Figure 23.9 User datagram format

23.14
Note

UDP length
= IP length – IP header’s length

23.15
Figure 23.10 Pseudoheader for checksum calculation

23.16
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.17
Figure 23.11 Checksum calculation of a simple UDP user datagram

23.18
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.19
Table 23.2 Well-known ports used by TCP

23.20
Figure 23.13 Stream delivery

23.21
Figure 23.14 Sending and receiving buffers

23.22
Figure 23.15 TCP segments

23.23
Note

The bytes of data being transferred in


each connection are numbered by TCP.
The numbering starts with a randomly
generated number.

23.24
Note

The value in the sequence number field


of a segment defines the
number of the first data byte
contained in that segment.

23.25
Note

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.26
Figure 23.16 TCP segment format

23.27
Figure 23.17 Control field

23.28
Table 23.3 Description of flags in the control field

23.29
Figure 23.18 Connection establishment using three-way handshaking

23.30
Note

A SYN segment cannot carry data, but it


consumes one sequence number.

23.31
Note

A SYN + ACK segment cannot


carry data, but does consume one
sequence number.

23.32
Note

An ACK segment, if carrying no data,


consumes no sequence number.

23.33
Figure 23.19 Data transfer

23.34
Figure 23.20 Connection termination using three-way handshaking

23.35
Note

The FIN segment consumes one


sequence number if it does
not carry data.

23.36
Note

The FIN + ACK segment consumes


one sequence number if it
does not carry data.

23.37
Note

ACK segments do not consume


sequence numbers and are not
acknowledged.

23.38
Note

Data may arrive out of order and be


temporarily stored by the receiving TCP,
but TCP guarantees that no out-of-order
segment is delivered to the process.

23.39
Note

The receiver TCP delivers only ordered


data to the process.

23.40

You might also like