TCP/IP Model: Layered Network Architecture and Critiques

The Internet protocol suite—often called TCP/IP—describes networking by grouping protocol functions into broad layers: application layer , transport layer , internet layer , and link (network access) layer.

A key teaching goal of the model is to explain encapsulation: data produced by an application is wrapped step-by-step with headers appropriate to each layer, then unwrapped at the destination. In practice, many real systems implement functions that do not align perfectly with strict boundaries—one reason the model is frequently critiqued (especially alongside the OSI reference model).

Footnotes

1. Internet protocol suite - Wikipedia - Describes TCP/IP as a framework for organizing Internet protocols by functional scopes and highlights RFC 1122/1123 and four-layer abstraction (link, IP, transport, application). ↩ ↩²

2. TCP/IP Model Explained: Layers, Protocols & Best Practices - Explains the four layers and critiques such as missing separate session/presentation layers and layer ambiguity/overlap. ↩

The four layers of the TCP/IP model (what each does)

Below is a functional view of the classic four-layer TCP/IP organization (as commonly described for instruction). The Internet protocol suite is defined by RFCs that outline these broad scopes of functionality rather than a rigorously specified “protocol-first then strict layering” framework.2

1) Link / Network Access layer

• Purpose: delivery over the local network link; converts packets into frames for the specific medium (e.g., Ethernet/Wi‑Fi).
• Typical functions: medium access, frame formatting, local link delivery, and handling of neighbor-to-neighbor communication.

2) Internet (IP) layer

• Purpose: internetworking—routing packets from a source host to a destination host across multiple networks.
• Typical functions: IP addressing, forwarding decisions, and routing scope managed by Internet Protocol (IP).

3) Transport layer

• Purpose: end-to-end communication between processes on hosts.
• Key protocols:
  • TCP for reliability/ordering (segments, retransmissions, flow/congestion control).
  • UDP for low overhead when reliability is handled elsewhere or not needed.

4) Application layer

• Purpose: network services exposed to applications.
• Typical functions: application protocol behaviors (e.g., HTTP-like request/response, DNS name resolution, mail transfer services).
• Notably, unlike OSI, TCP/IP does not define separate session/presentation layers; those responsibilities are typically handled inside application protocols/libraries.

Footnotes

1. Internet protocol suite - Wikipedia - Describes TCP/IP as a framework for organizing Internet protocols by functional scopes and highlights RFC 1122/1123 and four-layer abstraction (link, IP, transport, application). ↩ ↩² ↩³ ↩⁴

2. Internet protocol suite - Wikipedia - Notes that RFC 1122/1123 emphasize architectural principles and loosely define a four-layer model with layers as named scopes. ↩

3. TCP/IP Model Explained: Layers, Protocols & Best Practices - Explains the four layers and critiques such as missing separate session/presentation layers and layer ambiguity/overlap. ↩

PDU flow and encapsulation across layers

Encapsulation can be visualized as: application data → transport segment → internet packet → link frame.

This layered wrapping/unwrapping is the conceptual backbone of the TCP/IP model teaching approach.

Footnotes

1. Internet protocol suite - Wikipedia - Describes TCP/IP as a framework for organizing Internet protocols by functional scopes and highlights RFC 1122/1123 and four-layer abstraction (link, IP, transport, application). ↩

TCP/IP layer ↔ OSI layer mapping (approximate)

Because TCP/IP is based on protocol reality and broad functional scopes, comparisons to OSI are approximate rather than exact. A commonly cited mapping is:

This “bundling” is one reason TCP/IP is often judged as less cleanly separated than OSI for teaching/debugging conceptual boundaries.2

Footnotes

1. TCP/IP Model Explained: Layers, Protocols & Best Practices - Explains the four layers and critiques such as missing separate session/presentation layers and layer ambiguity/overlap. ↩ ↩²

2. OSI model - Wikipedia - Discusses that TCP/IP layering is less rigorous than OSI and references “Layering considered harmful,” plus comparative mapping being subset/approximate. ↩

Critiques of the TCP/IP model

Why people critique it

1. Layer boundaries are less strict / less “theoretically pure.”
   RFC-oriented descriptions of the Internet protocol suite emphasize architectural principles over strict hierarchical encapsulation purity, so the layering is not always aligned with textbook boundaries.

2. No explicit separate session and presentation layers (as in OSI).
   TCP/IP’s application layer typically “absorbs” session/presentation-style responsibilities, so concepts like presentation (data representation) and session management aren’t cleanly isolated as distinct layers in the model.2

   • Practical consequence: uniform separation of concerns can be harder to teach and troubleshoot compared with OSI’s more granular model.

3. Some protocols/functions do not fit cleanly into one layer.
   Functional overlap and ambiguous placement are common critiques: certain support protocols and cross-cutting behaviors can span more than one conceptual layer, complicating “which layer is responsible?” reasoning.

4. Different conceptual model than OSI; comparisons can mislead.
   Even when TCP/IP is compared to OSI for learning, TCP/IP’s model uses different layering concepts (derived from operating scopes of protocols), so “OSI layer numbers” may not correspond 1:1 to what implementers actually do.

Footnotes

1. Internet protocol suite - Wikipedia - Notes that RFC 1122/1123 emphasize architectural principles and loosely define a four-layer model with layers as named scopes. ↩

2. TCP/IP Model Explained: Layers, Protocols & Best Practices - Explains the four layers and critiques such as missing separate session/presentation layers and layer ambiguity/overlap. ↩ ↩²

3. OSI model - Wikipedia - Discusses that TCP/IP layering is less rigorous than OSI and references “Layering considered harmful,” plus comparative mapping being subset/approximate. ↩ ↩²