GATE CS - COMPUTER NETWORKS:Transport Layer
Mastering transport layer concepts and implementation.
Transport Layer for GATE CS
GATE Transport questions favour TCP vs UDP properties, port roles, and sliding-window / stop-and-wait utilization numericals.
TCP vs UDP
| TCP | UDP | |
|---|---|---|
| Connection | Connection-oriented | Connectionless |
| Reliability | ACK, retransmit, ordered | Best-effort |
| Overhead | Higher | Lower |
| Congestion / flow control | Yes | No (app responsibility) |
UDP for DNS/video-style needs; TCP for byte-stream reliability.
Stop-and-Wait utilization
Frame size bits, bandwidth bps, propagation delay .
Transmission time .
Utilization ≈ when ACK is tiny and no errors (stop-and-wait).
Worked
bits, bps, ms = 0.1 s.
s.
.
Sliding window of size multiplies throughput (idealized) by up to until the bandwidth-delay product saturates.
TCP mechanics (exam level)
Three-way handshake; sequence/ACK numbers; flow control (receiver window); congestion control phases named (slow start, congestion avoidance) when options list them. GATE rarely asks you to implement Reno — know the vocabulary and what grows cwnd.