Protocol in Code · Track
the course finale: naming the five recurring shapes across all prior tracks
Sessions
Five different tracks each built "a dict keyed by identity, holding a value stamped with the time it was created, read against now" — so what, exactly, is left of that shape once the protocol-specific names are stripped away, and where does it break?
BGP, OSPF, RIP, VRRP, and STP each hold an "election" among candidates that never actually votes — so what's really happening when a router "elects" a best path, a designated router, a preferred route, a master, or a root bridge?
Open Session 02RPKI, BFD, ARP, and DNSSEC each refused to model their central verdict as a boolean — so what is the third state actually buying each of them, and is it the same purchase every time?
Open Session 03BFD, VRRP, TCP keepalive, and NAT conntrack all infer failure from the absence of a signal, after a deadline — so once every deadline is converted to the same unit, what does the size of the gap between them actually tell you about the eras these protocols were designed in?
Open Session 04Twenty-two tracks, twenty-two protocols, twenty-two capstone files, each with its own event source — a BGP UPDATE, a DNS resolve() call, a clock tick, bytes off a pcap file — so what is actually left in common once every protocol-specific detail is stripped away, and can two of the most different capstones be shown, not just claimed, to share it?