Systems Foundations · core
Network Protocol Engineering
Packet flow across Ethernet, IP, TCP/QUIC, TLS, DNS, HTTP, load balancers, and application protocols.
Mental model
Networks are layered state machines under delay, loss, duplication, and reordering. Reliability comes from explicit framing, identity, timeouts, congestion control, and retry semantics.
How to study Network Protocol Engineering
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use RFC 9002: QUIC Loss Detection and Congestion Control, The QUIC Transport Protocol: Design and Internet-Scale Deployment (SIGCOMM '17), BBR: Congestion-Based Congestion Control (ACM Queue 2016) to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Network Protocol Engineering with Compute, Memory & Storage Hierarchy, Concurrency Design. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Design exercise: Network Protocol Engineering and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
- RFC 9002: QUIC Loss Detection and Congestion Control (doc)
- The QUIC Transport Protocol: Design and Internet-Scale Deployment (SIGCOMM '17) (doc)
- BBR: Congestion-Based Congestion Control (ACM Queue 2016) (doc)
- USENIX NSDI '18 — Copa: Practical Delay-Based Congestion Control for the Internet (video)
- RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport (paper)
- The Road to QUIC (Cloudflare) (article)
- High Performance Browser Networking (doc)
Practice and explain it back
Design exercise: Network Protocol Engineering
Packet flow across Ethernet, IP, TCP/QUIC, TLS, DNS, HTTP, load balancers, and application protocols. Implement designOutline() returning non-empty values for: protocolLayers, failureHandling, latencyBudget. Each value must name a concrete mechanism or decision.
Expected evidence: A design outline with protocolLayers, failureHandling, latencyBudget plus an explicit failure mode or trade-off.
Open the interactive drill →Review prompts
- A TCP connection is "reliable". Name two failures it does not protect you from.
Build evidence
Synthesize: Systems Foundations
Build a mechanism-first model from hardware and kernels through runtimes, networks, performance, and isolation. Produce one working system, benchmark, or evidence-backed design that integrates the path.
- Implements or precisely models the core mechanisms from all three milestones
- Includes at least one injected failure or adversarial case and demonstrates recovery
- Reports quality, latency, resource, reliability, or usability measurements relevant to the domain
- Ships a concise architecture note explaining decisions, trade-offs, and remaining risks