Scribd
Upload
11 views13 pages

Chapter 03-b

Uploaded by

Nosheen Fatima
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views13 pages

Chapter 03-b

Uploaded by

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

Chapter 3 outline

3.1 transport-layer 3.5 connection-oriented


services transport: TCP
3.2 multiplexing and ▪ segment structure
demultiplexing ▪ reliable data transfer
3.3 connectionless ▪ flow control
transport: UDP ▪ connection management
3.4 principles of reliable 3.6 principles of congestion
data transfer control
3.7 TCP congestion control

Transport Layer 3-1


UDP: User Datagram Protocol [RFC 768]
❖ “no frills,” “bare bones” ❖ UDP use:
Internet transport ▪ streaming multimedia
protocol apps (loss tolerant, rate
❖ “best effort” service, sensitive)
UDP segments may be: ▪ DNS
▪ lost ▪ SNMP
▪ delivered out-of-order ❖ reliable transfer over
to app
UDP:
❖ connectionless:
▪ add reliability at
▪ no handshaking application layer
between UDP sender,
receiver ▪ application-specific error
recovery!
▪ each UDP segment
handled independently
of others
Transport Layer 3-2
UDP: segment header
length, in bytes of
32 bits UDP segment,
source port # dest port # including header

length checksum
why is there a UDP?
❖ no connection
application establishment (which can
data add delay)
(payload) ❖ simple: no connection
state at sender, receiver
❖ small header size
UDP segment format ❖ no congestion control:
UDP can blast away as
fast as desired

Transport Layer 3-3


Chapter 3 outline
3.1 transport-layer 3.5 connection-oriented
services transport: TCP
3.2 multiplexing and ▪ segment structure
demultiplexing ▪ reliable data transfer
3.3 connectionless ▪ flow control
transport: UDP ▪ connection management
3.4 principles of reliable 3.6 principles of congestion
data transfer control
3.7 TCP congestion control

Transport Layer 3-4


Reliable Data Transfer

Transport Layer 3-5


Building a Reliable Data Transfer Protocol
❖ Reliable Data Transfer over a Perfect Channel
without errors (rdt1.0)
▪ Sender (Makes a packet → Send to a Receiver)
▪ Receiver (Extract Data → Deliver it to App)
❖ Reliable Data Transfer over a Channel with Bit
Errors (rdt2.0~2.2)
▪ Error Detection (Checksum)
▪ Feedback (ACK/NACK)
• NACK is eliminated in ver rdt2.2
• Ack could still get corrupted 
– Sequence number is introduced to resolve this
▪ Retransmission
❖ Reliable Data Transfer over a Lossy Channel with
Bit Errors (rdt3.0)
▪ Timout (for lost ACK)
Transport Layer 3-6
Operation of rdt3.0 (contd..)

Transport Layer 3-7


Operation of rdt3.0

Transport Layer 3-8


Rdt3.0: Stop and wait Protocol
❖ rdt3.0 is stop and wait protocol.
▪ Poor performance in today’s high-speed network.

Transport Layer 3-9


Solution: Pipelining
❖ Pipelining protocol.
▪ Better performance in today’s high-speed network.

Transport Layer 3-10


Pipelining (1) Go-Back-N (GBN)

1. Multiple packets in pipeline


2. Sequence numbers
3. Window of packets
4. Acknowledge behavior
5. Handling Losses
▪ Wait for the lost packet (timeout)
6. Receiver Side
▪ Accept packets in order

Transport Layer 3-11


Pipelining (2) Selective Repeat (SR)
❖ Error Handling
▪ Retransmits only necessay missing packets
❖ Ack: individual Acks for each packets
❖ Windows Synchronization
▪ The windows view of sender and receiver might not always
be aligned

Transport Layer 3-12


Pipelining (2) Selective Repeat (SR)

Transport Layer 3-13

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy