ze-rfc

To convert an RFC text file into an implementation summary, read the source RFC text and generate a structured markdown document. This summary includes wire formats, encoding rules, validation, algorithms, and compatibility sections to guide engineering work.

An RFC implementation summary should include metadata, wire formats, encoding and decoding rules, validation, MUST/SHOULD/MAY requirements, errors, state, timers, constants, algorithms, pitfalls, and compatibility to ensure comprehensive engineering coverage.

Verify RFC implementation accuracy by cross-referencing the generated summary against the original RFC text and checking published errata. This strict verification ensures consistency, accuracy, and traceability for the implementation.

Generating an RFC implementation summary requires direct RFC reading to ensure strict section coverage. Reading the entire source text directly prevents missing critical MUST/SHOULD/MAY requirements, state definitions, and algorithm specifications.

The best way to document wire formats and encoding rules from an RFC is extracting them into a dedicated architecture markdown file. This organizes validation logic, decoding rules, and constants into a structured, implementation-oriented reference.