OSI 7-Layer & TCP/IP 4-Layer Reference Models

1. Application Layer (Layer 7)

Primary Function: Provides network interfaces and application protocols directly to end-user software applications. It does not represent the application program itself (e.g., Google Chrome), but rather the communication protocol services that the application relies on to transfer data across a network.

• Key Responsibilities: Resource availability identification, user authentication, service request formatting, and protocol synchronization.
• Protocol Data Unit (PDU): Data (Payload).
• Core Protocols: HTTP / HTTPS (Web), FTP / SFTP (File Transfer), SMTP / IMAP / POP3 (Email), DNS (Domain Resolution), SSH / Telnet (Remote Terminal), DHCP (IP Allocation).
• Exam Focus Note: Remember that Layer 7 is the closest layer to the end user. When a user enters a URL in a browser, HTTP initiates communication at Layer 7.

2. Presentation Layer (Layer 6)

Primary Function: Acts as the "translator" for the network. It ensures that data sent from the application layer of one system can be understood and read by the application layer of another system, regardless of differences in internal data representation or operating systems.

• Key Responsibilities:
  • Syntax Translation: Translating between different data encodings (e.g., EBCDIC to ASCII, UTF-8, Big-Endian vs Little-Endian).
  • Data Encryption & Decryption: Applying cryptographic protocols (TLS/SSL encryption) for secure transmission.
  • Data Compression: Compressing data payloads (e.g., gzip, zip, JPEG, MPEG, PNG) to optimize network bandwidth utilization.
• Protocol Data Unit (PDU): Data (Payload).
• Core Examples: TLS / SSL security wrappers, ASCII, Unicode, JPEG, GIF, PNG, MP3, MPEG, XML, JSON syntax standards.

3. Session Layer (Layer 5)

Primary Function: Establishes, manages, synchronizes, and terminates active communication dialogues (sessions) between distributed applications running on separate hosts.

• Key Responsibilities:
  • Session Establishment & Teardown: Opening active channels between client and server processes and tearing them down gracefully when complete.
  • Dialog Control: Determining whether communication runs in Simplex, Half-Duplex, or Full-Duplex session modes.
  • Checkpointing & Recovery: Inserting synchronization markers into long data streams. If a connection drops midway through a 1 GB file transfer, the session layer resumes transmission from the last verified checkpoint rather than restarting from 0 bytes.
• Protocol Data Unit (PDU): Data (Payload).
• Core Protocols / APIs: NetBIOS, RPC (Remote Procedure Call), Sockets API, PPTP, SQL Session negotiation.

6. Data Link Layer (Layer 2)

Primary Function: Responsible for hop-to-hop physical node delivery across a single physical link or local network segment. It converts packets into frames and handles physical MAC addressing and error detection.

• Sublayer Structure:
  • LLC (Logical Link Control - IEEE 802.2): Interfaces with Layer 3, manages protocol multiplexing, and controls frame sequencing.
  • MAC (Media Access Control - IEEE 802.3 / 802.11): Manages hardware 48-bit MAC addressing, frame creation, and media access control methods (CSMA/CD for Ethernet, CSMA/CA for Wi-Fi).
• Key Responsibilities: Physical MAC addressing (Source & Destination MAC), framing, Media Access Control, and Error Detection via Frame Check Sequence (FCS) CRC polynomials.
• Protocol Data Unit (PDU): Frame.
• Hardware Devices: Layer 2 Managed Switches, Network Interface Cards (NICs), Bridges, Wireless Access Points.
• Core Standards: Ethernet (802.3), Wi-Fi (802.11), PPP, HDLC, ARP, 802.1Q VLAN Tagging.

7. Physical Layer (Layer 1)

Primary Function: Transmits raw unstructured binary bits (1s and 0s) over a physical transmission medium (copper cable, optical fiber strand, or radio frequency wireless channel).

• Key Responsibilities: Bit representation (encoding binary values into electrical voltage levels, optical light pulses, or RF carrier phase shifts), bit synchronization, transmission rate (bit rate), physical topology layout, and hardware interface specifications.
• Protocol Data Unit (PDU): Bits.
• Hardware & Media: CAT5e / CAT6 Copper Cabling, Single-mode & Multi-mode Fiber Optics, RJ45 connectors, SFP Transceivers, Network Hubs, Repeaters.

TCP Header Format (20-60 Bytes)

TCP provides reliable, connection-oriented, ordered byte-stream delivery with flow control (sliding window) and error recovery.

+-------------------------------+-------------------------------+
|     Source Port (16 Bits)     |  Destination Port (16 Bits)   |
+-------------------------------+-------------------------------+
|                 Sequence Number (32 Bits)                     |
+-------------------------------+-------------------------------+
|              Acknowledgment Number (32 Bits)                  |
+-------+-------+---------------+-------------------------------+
| Data  | Resv  | Flags (6 Bits)|     Window Size (16 Bits)     |
| Offset|       |U|A|P|R|S|F|   |                               |
+-------+-------+---------------+-------------------------------+
|    Header Checksum (16 Bits)  |    Urgent Pointer (16 Bits)   |
+-------------------------------+-------------------------------+

Key TCP Control Flags: SYN (Synchronize), ACK (Acknowledge), FIN (Finish connection), RST (Reset connection), PSH (Push data immediately), URG (Urgent data pointer valid).

UDP Header Format (8 Bytes)

UDP provides lightweight, connectionless, unreliable datagram delivery without handshake overhead or retransmission delays.

+-------------------------------+-------------------------------+
|     Source Port (16 Bits)     |  Destination Port (16 Bits)   |
+-------------------------------+-------------------------------+
|      Length (16 Bits)         |     Checksum (16 Bits)        |
+-------------------------------+-------------------------------+

UDP Applications: VoIP, Live Video Streaming, DNS Query (Port 53), DHCP (Port 67/68), SNMP.