Chapters0/30 ▾
Chapter 3 · Lesson 2 of 5
TCP and UDP: handshake, flow control and real-time traffic
1 min read
TCP is connection-oriented. Before any data moves, the two ends run a three-way handshake: the client sends SYN with its initial sequence number, the server replies SYN-ACK with its own number and an acknowledgment, and the client finishes with ACK. FIN belongs to closing a connection, not opening one.
TCP flow control uses the window field. When a receiver's buffer fills, it advertises a smaller receive window, and the sender may not have more unacknowledged data outstanding than that window. This slows the sender without closing the connection. TTL, ICMP echo and DSCP markings play no part in it.
UDP is connectionless, with an 8-byte header and no handshake, acknowledgments or retransmission. TCP's minimum header is 20 bytes. Real-time voice uses UDP because a resent audio packet would arrive too late to play; a short glitch is better than a stall.
Example: in a call carrying 50 voice packets per second, each packet covers 20 ms of sound, so waiting for a retransmission would freeze the audio for longer than the packet is worth.
Check yourself
1. Which sequence of segments correctly describes how a TCP connection is established before any application data is sent?
2. A design team must choose a transport for real-time voice traffic in which a retransmitted packet would arrive too late to be played out. Which choice is appropriate, and why?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, IANA Service Name and Transport Protocol Port Number Registry, RFC 7766: DNS Transport over TCP
CompTIA Network+ cheat sheet: every key fact on one page →