# About ToastRFC

ToastRFC makes the internet's standards studyable. RFCs are a graph, not a
book — "obsoleted by 9110", "updated by", "see Section 4.2" — and the official
text, while authoritative, is punishing to learn from. ToastRFC shows the graph:
every requirement keyword is tappable, every cited RFC is linked, a glossary
tracks each term across the spec and across the versions that redefined it,
and a "what governs this today" resolver follows the obsolete chain for you.

Built on study-engine, the shared apparatus behind
ToastScripture and
ToastWen.

## What's in Phase 0 — the HTTP core

3 RFCs · 2106 units · 12 concepts · 154 edges · 4 paths · 19 cards — built 2026-09-01.

- RFC 9110 — HTTP Semantics · RFC 9111 — HTTP Caching · RFC 9112 —
HTTP/1.1 — the three June-2022 Internet Standards, ingested in full from the
RFC Editor's structured XML.
- Everything they replaced (RFC 7230–7235, 2616, 2818, …) is here as metadata so
the lineage resolves.
- Concept glossary — the requirement keywords (MUST / SHOULD / MAY), safe and
idempotent methods, cacheability, resource vs. representation, intermediaries,
conditional requests, content negotiation, authority. Where RFC 9110 refined an
earlier spec (e.g. safe from 7231, HTTPS identity from 2818), both readings
are shown side by side.
- 4 learning paths, 19 self-test cards.

## What's coming

The plaintext parser (for the pre-2019 classics: DNS 1034/1035, IP 791, TCP/UDP,
TLS 8446, ARP, DHCP), a proper cross-reference graph view, and the Net+ / NSE
blueprint mapping.

## Sources & licensing

RFC text is © the IETF Trust and reproduced under the
Trust Legal Provisions
(the RFC series is freely redistributable). Metadata and the update/obsolete
graph come from the RFC Editor. The concept notes,
paths, and cards are editorial, written for this site.

Contact: [email protected]