About Network Layers

They are like layers, in a cake, but, like, in Networks. I, Simon Thibaudeau, have been in the IT industry for about 12 years in various positions, from VARs to Defence Contractors and Security Consultant firms. I now work at a regional ISP, but on the enterprise side of things.

It usually takes a long time for me to understand new things (not really), so I try to write about them to speed up the process or remember them.

The layered model of networking has always struck me as a convenient fiction. It helps us compartmentalize the chaos — physical cabling on one level, addressing on another, application protocols floating somewhere near the top. But anyone who has actually spent time troubleshooting a stubborn connection knows the layers blur together the moment something goes wrong. A misconfigured switch, a DNS hiccup, a firewall rule that makes no sense on paper yet blocks everything in practice — suddenly you're digging through all seven layers at once, wondering where the neat boundaries went. The model is useful, but it's a map, not the territory.

What fascinates me most about network infrastructure is how much of it runs on accumulated inertia. Protocols designed decades ago still carry the bulk of modern traffic, patched and extended and worked around until they resemble something their original authors would barely recognize. Companies build entire careers around the quirks of these aging standards, and entire industries form around managing their eccentricities. There's something almost geological about it — layer upon layer of technical sediment, each generation's decisions hardening into the foundation for the next. Understanding that history is often the fastest way to understand why a network behaves the way it does today.

For all the complexity, there's a strange elegance in watching packets find their way across a sprawling network. Every hop is a small decision, every router a tiny arbiter of direction. I write about these systems because they mirror so much of how we organize ourselves — hierarchies, redundancies, single points of failure, graceful degradation when things go wrong. The technical details matter, of course, but so do the human choices embedded in every configuration. This site is my space for exploring those intersections, one inconsequential observation at a time, in the spirit of the varia that fills these pages.