Domain 1Network FundamentalsINTRO

TCP/IP and OSI Models

Comparison of the OSI and TCP/IP models, detailing the functions of each layer and the encapsulation/decapsulation process.

Domain: Domain 1: Network Fundamentals•Updated: 2026-08-26
#OSI Model#TCP/IP Model#Encapsulation#Network Layers#PDU

Internet Protocol Suite (TCP/IP) and Layered Models

History and Standards Organizations

  • Protocol: A set of rules defining how data should be communicated between devices over a network.
  • Standard: An agreed-upon, vendor-neutral specification that describes how a protocol or technology should work, allowing multi-vendor interoperability.
  • Details:
    • 1969: ARPANET (Advanced Research Projects Agency Network) came online, initially using the NCP (Network Control Program) protocol.
    • 1974: Vint Cerf and Bob Kahn developed TCP (Transmission Control Program).
    • 1983 (Jan 1): ARPANET fully switched to the TCP/IP suite.
    • IEEE (Institute of Electrical and Electronics Engineers): Develops LAN standards. Defines physical specs and message formatting.
      • 802.3: Ethernet standards.
      • 802.11: Wi-Fi standards.
    • IETF (Internet Engineering Task Force): Open community defining Internet protocols (TCP, IP, UDP, HTTP, DNS). Publishes standards as RFCs (Requests for Comments).
    • RFC 791: The specific document that defines IP (Internet Protocol), published in 1981.

Things to note: TCP/IP won over proprietary and OSI models because it was published as open standards and could run over many different network types.

The 5-Layer TCP/IP Model

The TCP/IP model groups protocols into layers based on their specific jobs. Each layer provides services to the layer above and uses services from the layer below.

Layer 5: Application Layer

  • Concept: Where network communications meet applications. Defines how application processes format, send, and interpret data.
  • Details: Runs primarily on the end hosts (clients/servers). Network infrastructure devices (routers/switches) do not inspect this layer.
  • Protocols: HTTP/HTTPS (Web), FTP/TFTP (File Transfer), Telnet (Remote login), DNS (Domain Name System).

Layer 4: Transport Layer

  • Concept: Provides end-to-end (process-to-process) communication between application processes on different hosts.
  • Details: Uses Port Numbers to identify specific services/processes on a host. Runs primarily on the end hosts.
  • Protocols: TCP (Transmission Control Protocol) and UDP (User Datagram Protocol).
  • Key Ports Mentioned:
    • Port 80: Web server (HTTP).
    • Port 21: File server (FTP).

Things to note: A “port” at Layer 4 is a logical software number used to identify a process, not a physical physical interface on the back of a router.

Layer 3: Internet Layer

  • Concept: Provides end-to-end delivery between hosts across multiple networks (an internetwork).
  • Details: Uses IP Addresses to identify the source and destination hosts. Routers operate at this layer to forward traffic between networks.
  • Protocols: IPv4, IPv6, ICMP (Internet Control Message Protocol).
  • Example IP: 10.1.1.1 (Used in the video as the destination IP for SRV1).

Things to note: “Internet” in this context refers to an “internetwork” (multiple connected networks), not just the public Internet.

Layer 2: Local Network Layer

  • Concept: Provides hop-to-hop delivery of messages within a single Local Area Network (LAN).
  • Details: Uses MAC (Media Access Control) addresses to identify specific physical interfaces. Switches operate at this layer to forward frames within a LAN.
  • Protocols: Ethernet, Wi-Fi.
  • Hop Definition: One step along the path between two devices (e.g., Host to Router, Router to Router). Switches do not count as hops; they simply extend the LAN.

Layer 1: Physical Layer

  • Concept: Transmits and receives bits as electrical, optical, or radio signals over the physical medium.
  • Details: Defines cables (UTP, Fiber), connectors, signal levels, link speeds, and NICs (Network Interface Cards).

Data Flow: Encapsulation and Decapsulation

  • Encapsulation: The process of adding headers (and trailers) to data as it moves down the protocol stack on the sending host.
  • Decapsulation: The process of removing headers and trailers as data moves up the protocol stack on the receiving host.
  • Payload: The contents of a PDU (Protocol Data Unit). It is everything encapsulated inside the current layer’s header and trailer.

Protocol Data Units (PDUs)

Layer 5 (App):   [ Application Data ]
Layer 4 (Trans): [ L4 Header | Application Data ] = Segment (TCP) or Datagram (UDP)
Layer 3 (Net):   [ L3 Header | L4 Header | App Data ] = Packet
Layer 2 (Link):  [ L2 Header | Packet | L2 Trailer ] = Frame
Layer 1 (Phys):  [ Bits transmitted over wire ]
Layer PDU Name Header/Trailer Added
Layer 4 Segment (if TCP) or Datagram (if UDP) Layer 4 Header (Ports)
Layer 3 Packet Layer 3 Header (IP Addresses)
Layer 2 Frame Layer 2 Header (MACs) + Layer 2 Trailer (FCS/Error check)
Layer 1 Bits N/A (Converted to signals)

Things to note: You will never see a “packet” or “segment” traveling over a physical wire. They are always encapsulated inside a Frame at Layer 2 before being converted to bits at Layer 1.

Layer Interactions

  • Adjacent-Layer Interaction: How layers work together within the same device. Each layer provides a service to the layer directly above it and relies on the layer directly below it.
    • Example: Layer 3 uses Layer 2 to deliver a packet to the next hop.
  • Same-Layer Interaction: How a layer on one device communicates logically with the same layer on another device.
    • Example: Layer 3 on PC1 uses IP addresses to communicate logically with Layer 3 on SRV1. Layer 2 uses MAC addresses to communicate with the next hop’s Layer 2.
graph TD
    subgraph Sender Host
    A5[Layer 5: App Data] --> A4
    A4[Layer 4: Segment] --> A3
    A3[Layer 3: Packet] --> A2
    A2[Layer 2: Frame] --> A1
    A1[Layer 1: Bits]
    end
    
    subgraph Receiver Host
    B1[Layer 1: Bits] --> B2
    B2[Layer 2: Frame] --> B3
    B3[Layer 3: Packet] --> B4
    B4[Layer 4: Segment] --> B5
    B5[Layer 5: App Data]
    end

    A1 ==>|Physical Medium| B1
    
    A5 -.->|Same-Layer Interaction| B5
    A4 -.->|Same-Layer Interaction| B4
    A3 -.->|Same-Layer Interaction| B3
    A2 -.->|Same-Layer Interaction| B2

Model Comparison: TCP/IP vs. OSI

The OSI (Open Systems Interconnection) model is a 7-layer reference model created by the ISO (International Organization for Standardization). While TCP/IP won in the real world, the OSI model survives as a teaching tool, and its layer names are frequently borrowed.

OSI Layer OSI Name TCP/IP 5-Layer Name Primary Function / PDU
7 Application Application Network process to application (Data)
6 Presentation Application Data representation and encryption (Data)
5 Session Application Interhost communication/session management (Data)
4 Transport Transport End-to-end delivery / Ports (Segment/Datagram)
3 Network Internet Path determination / IP routing (Packet)
2 Data Link Local Network Media access / MAC addressing (Frame)
1 Physical Physical Binary transmission / Signals (Bits)

Things to note: In practice, network engineers just say “Layer 2”, “Layer 3”, etc. The CCNA exam focuses on the functions of the layers rather than strict naming conventions, but you must know the OSI names (Network, Data Link) as they are heavily used in the industry.

Command & Parameter Reference

Note: This specific video is conceptual and contains no router/switch CLI commands. Below is the consolidated reference of all technical parameters, ports, and identifiers mentioned in the transcript.

Key Ports

  • Port 21: FTP (File Transfer Protocol)
  • Port 80: HTTP (Web Server)

Key IP Addresses

  • 10.1.1.1: Example destination IP address for SRV1.

Key RFCs (Requests for Comments)

  • RFC 791: Defines the Internet Protocol (IP), published in 1981.

Key Standards

  • IEEE 802.3: Ethernet (Wired LAN)
  • IEEE 802.11: Wi-Fi (Wireless LAN)