RFC-grounded notes
Each topic starts with the relevant RFC sections, then narrows into terms, state machines, messages, and the parts that are easiest to misunderstand.
What this is
Learning infrastructure for protocols that run the Internet.
The studio keeps a narrow focus: routing, verification, packet-level observation, and notes that can be reproduced on a laptop.
Hands-on labs
Labs are designed around short command-line experiments, packet captures, and traces that show what actually changed on the wire.
Future tooling
Small tools may appear as the notes grow, especially around BGP visibility, RPKI checks, and protocol debugging workflows.
Coming next
BGP/RPKI learning track.
The first public track connects RFC reading to small, reproducible labs around route announcements and origin validation.
From one prefix announcement to a route you can explain.
The goal is not to memorize BGP. The goal is to read a small part of the protocol, run a tiny experiment, and explain what changed in the route.
Lab 01
ASNs, prefixes, route announcements, and why AS_PATH exists. First draft now under review.
Lab 02
UPDATE messages, NEXT_HOP, route withdrawal, and competing origins.
Lab 03
ROAs, RPKI origin validation, and what valid, invalid, and unknown mean.
Current track
BGP and RPKI first.
The first path is deliberately close to operational routing: ASNs, prefixes, UPDATE messages, AS_PATH, ROAs, and origin validation.
track/bgp-01 read: RFC 4271 sections 1, 3, 4 observe: AS, prefix, NEXT_HOP, AS_PATH lab: trace how a prefix announcement becomes a route status: first draft under review next: route withdrawal and RPKI origin validation url: /notes/bgp-01.html
Public status
Small, slow, and reproducible.
Now
The first BGP lab note is public as an overview while the hands-on command sequence is checked.
Next
The BGP track will turn RFC reading into short labs with packet captures, diagrams, and review questions.
Later
DNS, TCP, TLS, HTTP, and QUIC tracks can join the same format after the routing track is useful enough to stand on its own.
Contact
Protocol notes, corrections, and references are welcome.
Send short notes, RFC pointers, or corrections to the public contact address.