Tangential: Does anyone know how to generate HTML docs such as this? It looks like a page in a book - with a header/footer and page number. And, surprisingly no one in 1991 imaged we would be reading it on a 4k widescreen - and here I am, and it is extremely readable (using SF Mono on macOS). I would love to know what tools can be used to generate almost paper-like HTML docs.<p>Edit: I found the answer, tiny link at the bottom: <a href="https://tools.ietf.org/tools/rfcmarkup/" rel="nofollow">https://tools.ietf.org/tools/rfcmarkup/</a>
Is there an up to errata to track what has changed in to 30(?) years?<p>This was quite easy to follow and worked up from basics. Don't really see such well written documentation these days.
Opening raw sockets in Linux is a fun way to bang out your own IP, ARP, and ICMP packets for experimenting. I remember the joys of packet spoofing/flooding in college. I think with WiFi you're limited to the AP you're attached to?<p>It'd be a fun hack to read and inject raw wifi or LTE frames to get a count of radios within range, when they transmit and other details of the low level protocols. It looks like with SDR, folks are able to get better access to the physical layer.<p><a href="https://www.crowdsupply.com/lime-micro/limesdr-mini/updates/wi-fi-analysis-with-gr-802-11-and-wireshark" rel="nofollow">https://www.crowdsupply.com/lime-micro/limesdr-mini/updates/...</a>
Related tangent: "Browser-based Networking" (O'Reilly) is a fantastic, reasonably modern and fairly thorough resource that, in encompassing some higher levels in the stack, can at least complement core reference materials for the foundation. Highly recommended.
I think this is a great example of how to take a fairly complicated topic that goes deep, and progressively build an understanding with successive refinement of examples. They way the paper goes from the "what" to "why" is really well thought-out.