Protocols and Addressing
Protocols and addressing govern how devices on a network identify each other and exchange data. They define the layered rules (Ethernet, IP, TCP, UDP) and the numbering schemes (MAC addresses, IP addresses, port numbers) that let a packet travel from source to destination across interconnected networks.
itNetworking | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Protocols and Addressing
Network protocols are agreed rules that let devices exchange data without knowing each other's internal design. Addressing schemes give every device and service a reachable identity. Together, they solve the fundamental problem of networking: getting data from here to there, intact, across systems built by different people.
This course covers the protocol stack from physical framing through transport delivery, and the addressing at each layer that makes forwarding decisions possible.
Layered architecture
Network communication is organized in layers. Each layer has one job and relies on the layer below it for delivery.
The TCP/IP model uses four layers:
- Link layer. Moves frames between directly connected devices on a single network segment. Handles physical addressing (MAC), media access, and error detection for one hop.
- Internet layer. Moves packets across network boundaries using logical addressing (IP). Makes routing decisions to reach distant destinations.
- Transport layer. Provides end-to-end communication between applications. Adds port numbers, and optionally reliability and flow control.
- Application layer. Implements the actual service: HTTP, DNS, SMTP, SSH, and everything else a user or program interacts with.
The OSI seven-layer model provides finer distinctions (splitting the link layer into physical and data-link, and adding session and presentation layers), but TCP/IP is how the internet actually works. Use OSI vocabulary when it clarifies a specific boundary; use TCP/IP layers for operational thinking.
Encapsulation
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.rfc-editor.org/rfc/rfc1180
Supports
- TCP/IP four-layer model and encapsulation process
- Frame, packet, and segment relationships
- ARP operation for local and remote destinations
- End-to-end packet flow through routers
- https://www.rfc-editor.org/rfc/rfc791
Supports
- IPv4 addressing structure and 32-bit format
- TTL field decremented at each hop
- IP as connectionless best-effort delivery
- Fragmentation and MTU relationship
- https://www.rfc-editor.org/rfc/rfc793
Supports
- TCP three-way handshake for connection establishment
- Sequence numbers and acknowledgment for reliable delivery
- Port numbers for process multiplexing
- Five-tuple connection identification
- https://www.rfc-editor.org/rfc/rfc768
Supports
- UDP minimal header structure (8 bytes)
- Connectionless datagram delivery
- Port-based multiplexing without reliability
- https://www.rfc-editor.org/rfc/rfc1918
Supports
- Reserved private address ranges (10/8, 172.16/12, 192.168/16)
- Non-routability of private addresses on the public internet
- NAT as the mechanism for private-to-public communication
- https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13769-5.html
Supports
- Protocol stack operational overview
- MAC address scope limited to local segment
- Router re-encapsulation at each hop
- Broadcast domain and VLAN separation
