Foundations
What the Internet is, the layered models (OSI and TCP/IP), encapsulation, and the access-network families that make up the last mile.
Networking is a layered subject by design — each layer hides the details below it and provides a clean interface above. The Foundations topic walks the layered model from both sides (OSI's seven, TCP/IP's four), shows what 'encapsulation' actually is at the packet level, and surveys the access technologies (DSL, cable, fiber, cellular) that connect end hosts to the network. A short history of the Internet and a tour of the standards bodies (IETF, IANA, ICANN) and the RFC process round out the picture — knowing how the spec is governed is part of knowing the spec.
Internalise the envelope metaphor — each layer wraps the previous in its own header — and the layer ordering. Almost every networking question is either 'what does this layer do' or 'how does this layer talk to its peers'.
Key concepts
- The Internet is an internet — many networks (ASes) connected by a common IP contract
- Layered architecture: each layer talks peer-to-peer, hides its details from neighbours
- OSI has seven layers (textbook); TCP/IP has four (real)
- Encapsulation = each layer adds a header on send, strips it on receive
- Access networks differ in physical medium and bandwidth shape, not in IP semantics
- Standards live in RFCs and are governed by IETF/IANA/ICANN — the Internet runs on rough consensus and running code
Reference template
// Reasoning about a packet
1. What layer am I in? (application / transport / network / link)
2. What's the header at this layer? (and the relevant fields)
3. Who's the peer? (same layer on the other end)
4. What does the layer below give me? (the abstraction I rely on)
5. What does the layer above need? (the abstraction I provide)Adapt to your problem; the structure is the load-bearing part.
Common pitfalls
- Memorising the OSI seven layers without internalising why we usually deploy four
- Mixing up 'TCP/IP layer' and 'OSI layer' numbering
- Treating encapsulation as a metaphor when it's literally what happens on the wire
- Skipping access networks — the bottleneck is usually the last mile
Related topics
Items (8)
- What Is the Internet?
An internet of internets — autonomous systems, end hosts, routers, the IP datagram contract that holds it together.
Concept Foundational - A Brief History of the Internet
ARPANET → NSFNET → commercial Internet. The forty-year arc and the design decisions that ossified into today's stack.
Concept Foundational - Internet Standards — RFCs, IETF, IANA, ICANN
Who actually governs the Internet? The bodies, the RFC process, the registries — how a protocol becomes interoperable.
Concept Foundational - The OSI Reference Model
Seven layers, what each one is for, why nobody actually deploys all seven, and where the model still helps reasoning.
Concept Foundational - The TCP/IP Model
Four layers (link, internet, transport, application) and the reason the Internet runs on them instead of OSI.
Concept Foundational - Encapsulation, Headers, and the Envelope Metaphor
How a packet picks up headers on the way down and sheds them on the way up — the mental model for every layered protocol.
Concept Foundational - Access Networks — DSL, Cable, FTTH, Cellular
How end hosts get on the Internet — the last-mile technologies, their bandwidth shapes, and where they're going.
Concept Foundational - Network Types — by Medium, Distance, and Topology
Guided vs unguided media, LAN/MAN/WAN/PAN, and the standard topologies (bus, ring, star, mesh) you'll still meet in datacenters.
Concept Foundational