Lecture 10: Transport Layer

1
Lecture 10 Transport Layer

• Prev. summary
• Now we have completed the network layer
• Services
• Routing
• IP addressing
• Internet Routing

Application
Transport
Network
Link

• Todays lecture
• Transport Layer
• Intro to Reliable Transport Layer

2
Transport Layer

• Overview
• transport layer services
• multiplexing/demultiplexing
• connectionless transport UDP
• principles of reliable data transfer
• connection-oriented transport TCP
• reliable transfer
• flow control
• connection management
• principles of congestion control
• TCP congestion control

• Goals
• understand principles behind transport layer
  services
• multiplexing/demultiplexing
• reliable data transfer
• flow control
• congestion control
• instantiation and implementation in the Internet

3
Transport vs. network layer

• network layer logical communication between
  hosts
• transport layer logical communication between
  processes
• relies on, enhances, network layer services

• Household analogy
• 12 kids sending letters to 12 kids
• processes kids
• app messages letters in envelopes
• hosts houses
• transport protocol Ann and Bill
• network-layer protocol postal service

4
Multiplexing/demultiplexing
gathering data from multiple app processes,
enveloping data with header (later used for
demultiplexing)
delivering received (TPDUs) to correct
application layer processes
receiver
P3
P4
application-layer data
segment header
P1
P2
segment
H
t
M
segment

• segment TPDU (transport protocol data unit)

5
Port Numbers Multiplexing/Demultiplexing
WWW server B
WWW client host A
port use WWW server
host A
server B
WWW client host C
( port use telnet app )
6
Multiplexing/Demultiplexing

• transport layer needs port s in each TPDU
• recall that socket API needs IP addresses and
  port numbers

32 bits
source port
dest port
other header fields
application data (message)
TCP/UDP segment format
7
Transport Layer Protocols

• Internet transport services
• UDP unreliable (best-effort), unordered
  delivery
• TCP reliable, in-order delivery

8
Internet transport protocols

• TCP service
• connection-oriented setup required bw client,
  server
• reliable transport acks, retransmissions
• flow control sender wont overwhelm receiver
• congestion control for benefit of the Internet
• does not provide timing, minimum bandwidth
  guarantees

• UDP service
• unreliable data transfer between sending and
  receiving process
• does not provide connection setup, reliability,
  flow control, congestion control, timing, or
  bandwidth guarantee

9
Principles of Reliable data transfer

• important in app., transport, link layers
• top-10 list of important networking topics!

• characteristics of unreliable channel will
  determine complexity of reliable data transfer
  protocol (rdt)

10
Reliable data transfer getting started
send side
receive side
11
Reliable data transfer getting started

• Well
• incrementally develop sender, receiver sides of
  reliable data transfer protocol (rdt)
• consider only unidirectional data transfer
• but control info will flow on both directions!
• use finite state machines (FSM) to specify
  sender, receiver

event causing state transition
actions taken on state transition
state when in this state next state uniquely
determined by next event
12
Rdt1.0 reliable transfer over a reliable channel

• underlying channel perfectly reliable
• no bit erros
• no loss of packets
• separate FSMs for sender, receiver
• sender sends data into underlying channel
• receiver read data from underlying channel

13
Rdt2.0 channel with bit errors

• underlying channel may flip bits in packet
• recall UDP checksum to detect bit errors
• the question how to recover from errors
• acknowledgements (ACKs) receiver explicitly
  tells sender that pkt received OK
• negative acknowledgements (NAKs) receiver
  explicitly tells sender that pkt had errors
• sender retransmits pkt on receipt of NAK
• human scenarios using ACKs, NAKs?
• new mechanisms in rdt2.0 (beyond rdt1.0)
• error detection
• receiver feedback control msgs (ACK,NAK)
  rcvr-gtsender

14
rdt2.0 FSM specification
sender FSM
receiver FSM
15
rdt2.0 in action (no errors)
sender FSM
receiver FSM
16
rdt2.0 in action (error scenario)
sender FSM
receiver FSM
17
rdt2.0 has a fatal flaw!

• What happens if ACK/NAK corrupted?
• sender doesnt know what happened at receiver!
• cant just retransmit possible duplicate
• What to do?
• sender ACKs/NAKs receivers ACK/NAK? What if
  sender ACK/NAK lost?
• retransmit, but this might cause retransmission
  of correctly received pkt!

• Handling duplicates
• sender adds sequence number to each pkt
• sender retransmits current pkt if ACK/NAK garbled
• receiver discards (doesnt deliver up) duplicate
  pkt

Sender sends one packet, then waits for receiver
response
18
rdt2.1 sender, handles garbled ACK/NAKs
19
rdt2.1 receiver, handles garbled ACK/NAKs
20
rdt2.1 discussion

• Sender
• seq added to pkt
• two seq. s (0,1) will suffice. Why?
• must check if received ACK/NAK corrupted
• twice as many states
• state must remember whether current pkt has 0
  or 1 seq.

• Receiver
• must check if received packet is duplicate
• state indicates whether 0 or 1 is expected pkt
  seq
• note receiver can not know if its last ACK/NAK
  received OK at sender

21
rdt2.2 a NAK-free protocol
sender FSM

• same functionality as rdt2.1, using ACKs only
• instead of NAK, receiver sends ACK for last pkt
  received OK
• receiver must explicitly include seq of pkt
  being ACKed
• duplicate ACK at sender results in same action as
  NAK retransmit current pkt

!
22
rdt3.0 channels with errors and loss

• New assumption underlying channel can also lose
  packets (data or ACKs)
• checksum, seq. , ACKs, retransmissions will be
  of help, but not enough
• Q how to deal with loss?
• sender waits until certain data or ACK lost, then
  retransmits
• yuck drawbacks?

• Approach sender waits reasonable amount of
  time for ACK
• retransmits if no ACK received in this time
• if pkt (or ACK) just delayed (not lost)
• retransmission will be duplicate, but use of
  seq. s already handles this
• receiver must specify seq of pkt being ACKed
• requires countdown timer

23
rdt3.0 sender
24
rdt3.0 in action
25
rdt3.0 in action
26
Performance of rdt3.0

• rdt3.0 works, but performance stinks
• example 1 Gbps link, 15 ms e-e prop. delay, 1KB
  packet

• 1KB pkt every 30 msec -gt 33kB/sec thruput over 1
  Gbps link
• network protocol limits use of physical
  resources!
• TCP makes use of pipelining to increase thruput