Week 1 · Lesson 14

OSI Model - Transport Layer

The transport layer is where the network stops thinking about wires and starts thinking about conversations between programs. It breaks application data into pieces, tags each piece with port numbers, decides whether reliability is needed, and puts the pieces back together at the far end. This lesson introduces it; Week 8 goes deep.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

The role of the transport layer

The transport layer is Layer 4 of the OSI model. It delivers data between application processes running on different hosts. Where the network layer worries about which host should receive a packet, the transport layer worries about which program on that host should receive it — and how the data should be carried.

Definition — transport layer. The OSI transport layer provides end-to-end transport between applications. It segments data into manageable pieces, identifies each application with a port number, and optionally provides reliability, ordering and flow control.

Segmentation

Split a large message into segments and rebuild it at the receiver.

Application identification

Use port numbers to deliver each segment to the correct program.

Reliability (optional)

Detect loss and reorder data when the chosen protocol demands it.

Flow control (optional)

Prevent a fast sender from overwhelming a slow receiver.

Note the phrase end-to-end. The transport layer runs on the two communicating hosts, not on the routers in between; the devices in the middle only need to look as high as the network layer. That is what makes the transport layer a matter between the endpoints.

Part 2

Segmentation and reassembly

Applications can produce data far larger than any single network frame can carry. The transport layer chops that data into segments (for TCP) or datagrams (for UDP), each small enough to travel through the network. Each piece is numbered so the receiver can put them back in the right order — even if they arrive out of order.

Reassembly is the reverse at the destination: collect the pieces, order them, and hand the original data up to the application. This is why a large download can complete even though no single network packet carried the whole file.

Segmenting and reassembling · step through
Message application data Segment 1 src port + dst port Segment 2 src port + dst port Segment 3 src port + dst port network Message reassembled

Step 1 of 4

PDU reminder. At Layer 4 the data unit is a segment when TCP is used and a datagram when UDP is used. Both are carried inside Layer 3 packets.
Part 3

Port numbers and multiplexing

A host runs many programs at once: a browser, a mail client, a game, a file transfer. When segments arrive, the transport layer must know which program each belongs to. It does this with port numbers — a 16-bit number (0–65535) identifying an application endpoint.

A socket is the pairing of an IP address and a port number, for example 192.0.2.10:443. A conversation is uniquely identified by the source socket and the destination socket together, which is how one server can serve thousands of clients at the same time. Sharing one connection among many applications this way is called multiplexing.

Build a socket pair · choose a service

Part 4

Port ranges (IANA)

The Internet Assigned Numbers Authority (IANA) divides the 16-bit port space into three ranges:

RangeNameUse
0–1023Well-known portsAssigned to standard services (for example HTTP, DNS, SSH). Usually require privileges to bind.
1024–49151Registered portsAssigned by IANA to specific, often vendor, applications on request.
49152–65535Dynamic / private (ephemeral) portsUsed automatically by clients as temporary source ports for a connection.
Exam tip. Memorise the boundaries: well-known 0–1023, registered 1024–49151, dynamic/private 49152–65535. A client’s source port is usually an ephemeral port from the top range; the server’s destination port is usually a well-known port from the bottom range.
Port-range classifier · drag to any port number
0 65535

Part 5

Common well-known ports

These are the values you are expected to know. All are correct well-known assignments from the IANA registry.

ServicePortTransport
FTP (data)20TCP
FTP (control)21TCP
SSH22TCP
Telnet23TCP
SMTP25TCP
DNS53UDP/TCP
DHCP (server / client)67 / 68UDP
HTTP80TCP
POP3110TCP
IMAP4143TCP
HTTPS443TCP
Two useful hints. FTP uses two ports — 21 for control commands and 20 for the actual data transfer. DHCP uses 67 on the server and 68 on the client.
Part 6

TCP vs UDP

The transport layer offers two principal protocols, with opposite design goals: TCP for reliability, UDP for speed and simplicity.

FeatureTCPUDP
ConnectionConnection-oriented (handshake first)Connectionless (just send)
ReliabilityReliable — acknowledgements and retransmissionBest-effort — no guarantee of delivery
OrderingData reassembled in the original orderNo ordering guarantee
Flow controlYes — protects a slow receiverNo
OverheadHigher (larger header, more state)Lower (small header, stateless)
Typical useWeb, email, file transfer, remote accessDNS queries, DHCP, TFTP, streaming, voice/video
TCP or UDP? · choose a protocol

The trade-off is simple to state: TCP spends bandwidth and time to guarantee that the data arrives complete and in order, while UDP sends datagrams and moves on, leaving any reliability to the application. Choose TCP when correctness matters more than latency; choose UDP when low delay matters more than the occasional lost packet.

Cross-reference. This lesson is only the introduction. The TCP three-way handshake, windowing and flow control, sequence/acknowledgement numbers, TCP and UDP header fields, ports in detail, and socket behaviour are all covered in depth in Week 8 (Transport Layer).
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key terms

Sources: RFC 1122 (Requirements for Internet Hosts — Communication Layers); the IANA Service Name and Transport Protocol Port Number Registry; ISO/IEC 7498-1; Cisco CCNA 200-301 exam topics.

Sources

Sources & references

  1. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), which defines TCP and UDP and the transport-layer requirements. rfc-editor.org/rfc/rfc1122.
  2. IANA. Service Name and Transport Protocol Port Number Registry (well-known, registered, and dynamic port ranges; per-service port assignments). iana.org.
  3. ISO/IEC 7498-1. Information technology — Open Systems Interconnection — Basic Reference Model, which describes the transport layer. iso.org.
  4. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.