TCP/IP Model: Duties of Each Layer (Application, Transport, Internet, Link)

The TCP/IP model is a four-layer protocol suite used to structure how data moves from applications on a source host to applications on a destination host. Each layer has distinct duties and (together) they enable end-to-end communication across heterogeneous networks:

• The Application layer prepares application data and uses application protocols.
• The Transport layer provides host-to-host delivery for applications (e.g., reliability, ordering, multiplexing via ports).
• The Internet layer provides logical addressing, routing, and forwarding using IP.
• The Link/Network Access layer delivers frames over the local network hop-by-hop using MAC addressing and framing.

Key layers and terms you’ll use throughout:

• TCP/IP model
• Encapsulation
• Decapsulation
• Protocol suite

Application Layer (Top Layer): Duties

The Application layer is where networking meets the user’s software. It provides the protocols that define what information is sent (e.g., web pages, DNS lookups, email). In practice, it:

1. Supplies application data to the transport layer (often after session-related setup and data formatting).
2. Selects which transport protocol to use (commonly TCP or UDP) based on the service’s needs.
3. Hosts well-known protocols such as HTTP (web), DNS (name resolution), SMTP/IMAP (mail), and others. 2

How it fits in the stack: the application creates the “meaningful” content, and lower layers add reliability, addressing, and hop delivery.

Core concepts:

• Application protocol
• Session management
• Data representation

Typical example: A browser sends an HTTP request—application-layer logic packages the request and hands it to the transport layer for delivery. 2

Note: In the strict TCP/IP model, “presentation” and “session” concerns (often separate in OSI) are typically folded into the Application layer.

Transport Layer (Layer 3 in TCP/IP): Duties

The Transport layer is responsible for end-to-end communication between applications on hosts. It provides mechanisms for delivering data while meeting performance and correctness goals.

What the transport layer does

1. Segmentation and reassembly: Breaks application data into segments on send; reassembles at the destination.
2. Multiplexing/demultiplexing via ports: Determines which application process receives incoming data.
3. Reliability and ordering (TCP-specific): TCP supports reliable, ordered delivery using acknowledgments and retransmissions. 2
4. Flow/congestion behaviors: Transport protocols manage delivery behavior; TCP includes congestion control and other mechanisms that can increase delay but improve reliability. 2
5. Best-effort delivery (UDP-specific): UDP is connectionless and does not provide the same reliability/ordering guarantees; it’s often used when low latency is more important than perfect delivery. 2

TCP vs UDP summary (transport duty choices):

• TCP
• UDP
• Flow control
• Congestion control

Pro Tip: When an application needs reliable in-order delivery (e.g., file transfer), TCP is usually the correct default; when an application prioritizes timeliness over perfect delivery (e.g., real-time media), UDP is commonly used. 2

Internet Layer (Network/Layer 3): Duties

The Internet layer enables communication across multiple networks using logical addressing and routing. Its central responsibilities include:

1. IP addressing: Identifying the source and destination using IP addresses.
2. Packet forwarding: Moving packets toward the next hop based on routing decisions. 2
3. Routing (path selection): Choosing routes so packets can traverse intermediate routers until reaching the destination network. 2
4. Supporting protocols used with IP: ICMP for error/control messaging and ARP for address resolution to reach the next hop on a local link. 2

Core terms:

• IP (Internet Protocol)
• Routing
• Packet forwarding

Forwarding intuition: routers consult destination IP address information, consult routing/forwarding tables, and send the packet onward to the chosen next hop. 2

Warning: Link-layer delivery is usually limited to a local hop. If the destination is on a different network, routing at the Internet layer becomes essential for reaching the next hop toward the destination. 2

Link/Network Access Layer (Layer 2-ish): Duties

The Link (Network Access) layer handles communication over the local network medium (e.g., Ethernet, Wi‑Fi). Its primary duties are hop-by-hop:

1. Framing: Wrap IP packets inside link-layer frames so receivers can detect boundaries and validate integrity. 2
2. MAC addressing (local delivery): Use MAC addresses to deliver frames to the correct device on the same local segment. 2
3. Error detection on the hop: Frames include integrity checks (e.g., FCS/CRC) so corrupted frames can be detected and discarded. 2
4. Media access control: Coordinate how devices use a shared physical medium to send frames (particularly relevant for LAN technologies). 2

Core terms:

• MAC address
• Frame
• FCS/CRC
• ARP

A typical send/receive flow across Layer 2:

• The sender resolves the next hop’s MAC address using ARP.
• The IP packet becomes the frame payload.
• The frame is transmitted over Ethernet/Wi‑Fi.
• The receiver validates the frame and passes the payload upward.

End-to-End Walkthrough: Duties Across Layers (One Packet)

Below is a conceptual view of what changes as data moves down to the wire and back up at the receiver:

Encapsulation/decapsulation is what allows the same “payload” to become richer and richer in metadata as it moves down the stack (ports/IP headers) and then be stripped back as it moves up. 2