summarizing

10/8/07 University of Memphis 1

 Transport Layer
Our goals:
 understand  learn about transport
principles behind layer protocols in the
transport layer Internet:
services:  UDP: connectionless
 multiplexing/demult
transport
iplexing
 reliable data
 TCP: connection-
transfer oriented transport
 flow control
 congestion control

10/8/07 University of Memphis 2

 Transport services and protocols
 provide logical communication application
transport
between app processes network
data link
network
running on different hosts physical
data link
network physical

lo
 transport protocols run in end data link

gi
ca
physical
systems

le
network

nd
data link
 send side: breaks app

-e
physical network

n
data link

d
messages into segments, physical

tr
an
network
passes to network layer

sp
data link

or
physical
 rcv side: reassembles

t
segments into messages, application
transport
passes to app layer network
data link
physical
 more than one transport
protocol available to apps
 Internet: TCP and UDP

10/8/07 University of Memphis 4

 Internet transport-layer protocols
 unreliable, unordered application
transport

delivery: UDP network

data link
physical network
data link
 no-frills extension of “best- network physical

lo
data link

gi
effort” IP

ca
physical

le
network
reliable, in-order delivery

nd
 data link

-e
physical network

n
data link
(TCP)

d
physical

tr
an
network
 connection setup

sp
data link

or
physical

t
 congestion control
application
 flow control transport
network
data link
 services not available: physical

 delay guarantees
 bandwidth guarantees

10/8/07 University of Memphis 5

 Transport vs. network layer
 network layer: logical Household analogy:
communication 12 kids sending letters to
between hosts 12 kids
 transport layer: logical  processes = kids
 app messages = letters
communication
in envelopes
between processes  hosts = houses
 relies on, enhances,  transport protocol = Ann
network layer services and Bill
 network-layer protocol =
postal service

10/8/07 University of Memphis 6

 UDP: User Datagram Protocol [RFC
768]

 “no frills,” “bare bones”

Internet transport protocol
 “best effort” service, UDP
segments may be:
 lost
 delivered out of order to
app
 connectionless:
 no handshaking between
UDP sender, receiver
 each UDP segment
Why is there a UDP?
 no connection establishment
(which can add delay)
 simple: no connection state
at sender, receiver
 small segment header
 no congestion control: UDP
can blast away as fast as
desired

handled independently of
others

10/8/07 University of Memphis 7

 Thank you

10/8/07 University of Memphis 8