Week 3 · Lesson 3

TCP/IP Protocol

Lesson 02 showed you where each protocol sits. This lesson zooms in on what each one actually does — the core Internet protocols (IP, ICMP, ARP, TCP, UDP) and the application protocols you use every day. By the end you will know each protocol’s job and whether it is reliable.

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

The big picture: a relay team

The TCP/IP suite is a relay team. An application protocol such as HTTP produces the data; a transport protocol (TCP or UDP) delivers it to the right application; IP moves it across networks; and the network access layer puts it on the local link. Two protocols — IP and TCP — carry most of the world’s traffic, which is why the whole family is named after them.

Application

Produces the data and names the service: HTTP, DNS, SMTP, DHCP, FTP, SSH, SNMP.

Transport

Delivers it to the right application, using port numbers. TCP or UDP.

Internet

Addresses and routes it across networks: IP, ICMP, ARP.

Network access

Puts it on the wire with MAC addresses: Ethernet, WLAN, PPP.

The relay team · select a stage
Sender host your PC Application HTTP · DNS · SMTP Transport TCP · UDP Internet IP · ICMP · ARP Network access Ethernet · WLAN data travels down the stack and back up at the receiver

Notice that each stage only understands its own neighbour. The Application protocol does not know or care whether the packet crosses one LAN or twenty networks; it simply hands a message down and expects a response. That is the modularity of Lesson 02 in action.

Part 2

IP: logical addressing and best-effort delivery

The Internet Protocol (IPv4 and IPv6) sits at the Internet layer. It does two critical things: it gives every host a logical address, and it delivers packets between networks. It does both on a surprising promise: best effort.

Logical addressing. IP assigns each host a hierarchical address (32-bit for IPv4, 128-bit for IPv6) that is independent of the hardware. This address identifies the host and the network it belongs to, which is what lets routers send traffic across the world.
Best-effort delivery. IP does not guarantee that a packet arrives, arrives once, or arrives in order, and it does not correct errors. It is connectionless and unreliable. Reliability, when it is needed, is added by TCP above it. IP is also media independent: it can run over copper, fibre, or wireless without change.

An IP packet consists of a header and a payload. The header carries the information routers need.

Header fieldWhat it does
Source and destination IP addressesIdentify the sending and receiving hosts. They stay the same for the whole journey across the Internet.
Time-to-Live (TTL)Decreased by one at every router, so a routing loop cannot keep a packet alive forever. When it reaches zero the packet is discarded and an ICMP message is sent back.
ProtocolSays which upper-layer protocol the payload belongs to — TCP (6), UDP (17), or ICMP (1).
Total lengthThe size of the whole packet, header included, so the receiver knows where the packet ends.
Header checksumAn IPv4-only field that protects the header itself from corruption. IPv6 removes it, relying on the layers below instead.
Exam tip. “Best effort” does not mean “bad”; it means IP makes no promises. If a test asks what happens when a packet is lost, the answer is: IP itself does nothing — recovery is the job of a higher layer (TCP) or is simply acceptable (UDP).
Part 3

ICMP and ARP: the Internet layer’s helpers

Two smaller protocols sit alongside IP at the Internet layer. ICMP is IP’s messaging assistant — it reports problems and provides testing. ARP supplies the link between an IP address and the MAC address needed to build the frame.

ICMP: reporting and testing

The Internet Control Message Protocol is not used to carry application data. ICMP messages travel inside IP packets, and they do three common jobs:

For IPv6, ICMPv6 plays the same error and testing role and additionally powers neighbour discovery (IPv6’s replacement for ARP).

Note. ICMP is neither TCP nor UDP — it is a separate protocol carried directly by IP. That is why tools like ping and traceroute measure the network itself rather than a particular application.
ICMP messages · select one
Sender host or router IP packet ICMP message Receiver host or router encapsulated delivered ICMP rides inside IP, so it has an IP header and can cross networks

ARP: from IP to MAC

When a host sends a packet on a local network, it needs both an IP address (to identify the destination) and a MAC address (to actually address the Ethernet frame). ARP, the Address Resolution Protocol, resolves a known IPv4 address to a MAC address on the local link.

  1. The sender broadcasts an ARP request: “Who has IP address 192.168.10.20? Tell 192.168.10.10.”
  2. The device that owns that IP answers with a unicast ARP reply containing its MAC address.
  3. The sender stores the pairing in its ARP table (also called the ARP cache) so it does not have to ask again right away. You can view it with arp -a.

ARP only works within the local network — broadcasts do not cross a router. To reach a host on another network, a device ARPs for the default gateway instead, and the router forwards the packet onward. IPv6 does not use ARP; it uses Neighbor Discovery (ND) via ICMPv6.

Exam tip. Remember the pairing: ARP = IPv4 address to MAC address, local link only. DNS = name to IP address. The two are often confused because both are called “resolution”.
Part 4

TCP: reliable, connection-oriented

The Transmission Control Protocol is the workhorse of the Transport layer. It is connection-oriented and reliable, at the cost of more overhead. Its data unit is a segment.

Connection setup: the three-way handshake

Before any data is sent, TCP establishes a connection with a three-step exchange. Step through it below.

The three-way handshake · step through it
Client Server 1. SYN (seq = x) 2. SYN-ACK (seq = y, ack = x+1) 3. ACK (ack = y+1) connection established — data transfer begins

How TCP keeps its promises

TCP also uses port numbers to identify the application at each end, so several conversations can share one IP address. Week 8 covers TCP in depth; this lesson only introduces it.

Part 5

UDP and the application protocols

The User Datagram Protocol is TCP’s lightweight sibling. It is connectionless and offers no delivery guarantee. Its data unit is called a datagram.

UDP is the right choice when speed matters more than perfection, or when the application handles loss itself. Common users include DNS queries, DHCP, TFTP, VoIP, live video streaming, SNMP, and NTP.

Exam tip. The classic one-line contrast: TCP = reliable, connection-oriented, ordered, more overhead. UDP = best-effort, connectionless, unordered, low overhead. Remember that both use port numbers; the difference is in the guarantees, not the addressing.

Application protocols

These protocols sit at the Application layer and give users actual services. Know each one’s port and one-line job.

Port number reference

ProtocolPortTransportPurpose
FTP20 / 21TCPFile transfer (data / control)
SSH22TCPSecure remote access
Telnet23TCPRemote access (unencrypted)
SMTP25TCPSend email
DNS53UDP / TCPName-to-IP resolution
DHCP67 / 68UDPDynamic host configuration (server / client)
TFTP69UDPSimple file transfer
HTTP80TCPWeb (unencrypted)
POP3110TCPRetrieve email
IMAP143TCPRetrieve email (server-side)
SNMP161UDPNetwork device management
HTTPS443TCPSecure web (TLS)
Note. These are the well-known ports assigned by IANA (ports 0–1023). Port numbers identify which application should receive the data; the IP address identifies the host. Together, an IP address plus a port is a complete application address.

Protocol summary table

ProtocolLayerPurposeReliable?
IP (IPv4/IPv6)InternetLogical addressing and routing of packetsNo (best effort)
ICMPInternetError reporting and network testing (ping, traceroute)n/a
ARPInternetResolve an IPv4 address to a MAC address on the local linkn/a
TCPTransportReliable, ordered, connection-oriented delivery of segmentsYes
UDPTransportFast, connectionless delivery of datagramsNo
HTTP / HTTPSApplicationWeb requests and responses (HTTPS encrypted)Via TCP
DNSApplicationTranslate names to IP addressesNo (UDP)
DHCPApplicationAutomatically assign IP configurationNo (UDP)
FTPApplicationTransfer filesVia TCP
SMTPApplicationSend emailVia TCP
SSHApplicationSecure remote accessVia TCP
SNMPApplicationMonitor and manage network devicesNo (UDP)
Part 6

Choosing TCP or UDP

Neither TCP nor UDP is “better”; each fits a different need. Choose TCP when every bit must arrive, and in order — web pages, file downloads, email, and remote logins. Choose UDP when speed and low delay matter more than perfection — real-time voice and video, where a late packet is useless; or simple query/answer exchanges such as DNS; and when the application can retry a lost message itself.

Trade-off in one line — TCP trades speed for reliability; UDP trades reliability for speed. The reliability that TCP provides is not free: the handshake, acknowledgements, and retransmissions all add overhead and delay.
Transport choice and the frame on the wire

One web request, end to end

Put it all together. You type https://example.com. The data is wrapped, layer by layer, as it moves down the stack — an example of encapsulation (Lesson 05 of this week walks through encapsulation in full).

  1. DNS first resolves example.com to an IP address (UDP port 53).
  2. TCP performs the three-way handshake to port 443 on the server.
  3. The browser builds an HTTPS request; TCP encapsulates it as a segment with source and destination ports.
  4. IP encapsulates the segment as a packet with source and destination IP addresses.
  5. Ethernet encapsulates the packet as a frame with MAC addresses and an FCS, ready for the wire.
  6. At the server the process reverses (de-encapsulation), the request reaches the web application, and the response travels back the same way.

Key terms

TermMeaning
IPInternet Protocol; logical addressing and best-effort packet delivery at the Internet layer.
Best-effort deliveryNo guarantee of arrival, order, or error correction; recovery is left to higher layers.
Logical addressAn IP address that identifies a host and its network independently of hardware.
ICMPInternet Control Message Protocol; error reporting and testing, used by ping and traceroute.
ARPAddress Resolution Protocol; resolves an IPv4 address to a MAC address on the local link.
TCPTransmission Control Protocol; connection-oriented, reliable transport using segments, sequencing, and acknowledgements.
UDPUser Datagram Protocol; connectionless, best-effort transport using datagrams and low overhead.
SegmentTCP’s data unit at the Transport layer.
DatagramUDP’s data unit at the Transport layer; also an IP packet informally.
Three-way handshakeTCP’s SYN / SYN-ACK / ACK exchange that establishes a connection.
Port numberA number that identifies the application at each end of a transport connection.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Postel, J. RFC 792: Internet Control Message Protocol (1981). rfc-editor.org/rfc/rfc792.
  2. Plummer, D. RFC 826: An Ethernet Address Resolution Protocol (1982). rfc-editor.org/rfc/rfc826.
  3. Eddy, W. RFC 9293: Transmission Control Protocol (TCP) (2022, obsoletes RFC 793). rfc-editor.org/rfc/rfc9293.
  4. Postel, J. RFC 768: User Datagram Protocol (1980). rfc-editor.org/rfc/rfc768.
  5. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989). rfc-editor.org/rfc/rfc1122.
  6. Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
  7. IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
  8. IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.org.
  9. 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.