Fundamentals of TCP/IP: Protocol Suite, Standardization Process, and Layered Model

1. TCP/IP Basics

TCP/IP (Transmission Control Protocol/Internet Protocol) is a suite of protocols that enables data transmission across heterogeneous networks, including FTP, SMTP, TCP, UDP, IP, and many others. The term refers to the entire protocol family, not only the TCP and IP protocols.

1.1 Standardization of TCP/IP

The standardization process of TCP/IP is characterized by openness and practicality. It is driven by the IETF, an organization that allows anyone to join mailing lists and participate in discussions. Protocols are standardized only after real‑world implementations prove their usefulness.

1.2 RFCs and Standards

Protocols that need standardization are documented as RFCs (Request For Comments). Each RFC receives a unique number; for example, IP is defined in RFC 791 and TCP in RFC 793. When a protocol evolves, a new RFC is issued, and the old one is superseded. To avoid proliferating RFC numbers, related RFCs can be grouped under a single STD number (e.g., STD 5 aggregates several RFCs for ICMP).

http://www.rfc-editor.org/rfc/

ftp://ftp.rfc-editor.org/in-notes/

1.3 Standardization Workflow

The TCP/IP standardization workflow consists of four stages: Internet Draft, Proposed Standard (after inclusion in an RFC), Draft Standard, and finally Internet Standard. Drafts are valid for six months and must be updated regularly; otherwise they are abandoned.

2. Internet Fundamentals

The Internet is composed of backbone networks and stub networks interconnected via Network Operation Centers (NOCs) and Internet Exchange Points (IXPs). Access is obtained through ISPs or regional networks, which may offer various service models such as unlimited or capped bandwidth.

3. TCP/IP Layered Model

3.1 Comparison with the OSI Model

The TCP/IP model consists of five layers:

Physical (Hardware) : Ethernet, telephone lines, etc.

Network Interface (Data Link) : Handles MAC addresses and driver interaction.

Internet (Network) : Uses IP for routing packets.

Transport : TCP provides reliable, connection‑oriented communication; UDP offers connection‑less, low‑overhead transmission.

Application : Implements protocols such as HTTP, SMTP, FTP, DNS, SNMP, etc., covering the OSI session, presentation, and application layers.

Each layer adds its own header to the data, containing addressing information (MAC, IP, ports) and protocol identifiers.

3.2 Communication Example

A sample email transmission illustrates the step‑by‑step processing:

Application creates the email and encodes it.

TCP adds a TCP header (source/destination ports, sequence number, checksum).

IP adds an IP header (source/destination IP addresses, protocol field).

ARP resolves the destination MAC address if needed.

The Ethernet driver adds an Ethernet header and trailer (including FCS) and transmits the frame.

The receiving host reverses these steps, stripping headers, verifying checksums, and finally delivering the payload to the appropriate application.

4. TCP/IP Understanding

4.1 Protocols Included in TCP/IP

Key protocols and their roles:

TCP : Reliable, connection‑oriented transport.

UDP : Simple, connection‑less transport.

IP : Unreliable, connection‑less routing of packets.

Application protocols such as HTTP/HTTPS, SSL/TLS, SMTP, MIME, IMAP, POP, FTP, NTP, DHCP, SNMP, LDAP, ICMP, PPTP, ARP, RARP, BOOTP.

4.2 Three‑Way Handshake

Establishing a TCP connection requires three packets: SYN (client → server), SYN‑ACK (server → client), and ACK (client → server). Sequence and acknowledgment numbers, along with the SYN and ACK flags, ensure both sides agree on initial sequence numbers.

4.3 Four‑Way Termination

Closing a TCP connection involves four packets: FIN (client → server), ACK (server → client), FIN (server → client), and final ACK (client → server). The FIN flag signals that a side has finished sending data, and the ACK flag confirms receipt.