ProtoStackv0.1

Interactive Protocol Visualizer

Standards literacy

How to read an RFC

Reading the specification is the difference between knowing a protocol and knowing about it. This page is the method I would give a newcomer: what the document labels mean, where to look, and which traps catch almost everyone.

Every protocol page on this site lists its standards. Start with the simplest document in the list, not the longest.

What an RFC actually is

An RFC is a document in a permanent, numbered series. It is not automatically a standard: the series contains standards, operational guidance, vendor descriptions, April Fools jokes and historical records.

The label on the document tells you what you are holding. Internet-Drafts are works in progress with a six-month lifetime and no standing at all; only an RFC number is durable.

Different bodies publish in different series: the IETF through the RFC Editor, W3C as Recommendations, IEEE as numbered standards, 3GPP as Technical Specifications. The reading method below transfers; the document furniture does not.

The five labels that decide how much to trust a document

Standards Track

Proposed Standard → Internet Standard. A Proposed Standard is stable enough to implement; Internet Standard is the maturity level after widespread deployment. Most protocols you meet are Proposed Standards.

Best Current Practice (BCP)

Operational and process requirements rather than a wire protocol. BCP 14 defines the MUST/SHOULD keywords, for example.

Informational

Published for the record. It may describe a vendor protocol or a good idea; it is not a standard and does not oblige anyone to implement it.

Experimental

Proposed for experimentation, not recommended for production. Useful when reading research or early deployments.

Historic

Superseded or obsolete. Read it to understand legacy traffic, not to build something new.

MUST, SHOULD, MAY: read these literally

MUST / REQUIRED / SHALL
An absolute requirement. If you do not do this, you are not implementing the protocol.
MUST NOT / SHALL NOT
An absolute prohibition. This is where interoperability and security failures usually start.
SHOULD / RECOMMENDED
There may be valid reasons to deviate, but you must understand the consequences and be prepared to explain them.
SHOULD NOT / NOT RECOMMENDED
The behaviour is permitted but discouraged for good reasons.
MAY / OPTIONAL
Genuinely optional. A receiver must cope with peers that do not implement it.

The keywords are defined in RFC 2119, and RFC 8174 clarifies that only the UPPERCASE forms carry this meaning. A lowercase "must" in prose is just English, not a requirement.

Anatomy of a specification

1

Header block

Document number, category, publication date, authors, and the "Obsoletes" / "Updates" lines. Those lines are the first thing to check.

2

Status of This Memo

Repeats the category and explains the document's standing. A surprising number of "standards" turn out to be Informational here.

3

Abstract and Introduction

Two short sections that tell you what problem the document solves and what it replaces. Read these before anything else.

4

Terminology

Defines the keywords and protocol-specific terms. If a term is capitalised in the body, it is usually defined here.

5

The specification body

Packet formats, state machines, timers and procedures. Figures are usually ASCII art with bit offsets; read the offset columns, not the drawing.

6

IANA Considerations

Lists the registries the document creates or modifies (ports, protocol numbers, message types). This is how you find the current assigned values.

7

Security Considerations

Mandatory in IETF documents. It is often the most useful section for understanding why the design looks the way it does.

8

References

Normative references are required to implement the document. Informative references are background and can be skipped on a first read.

A seven-step reading method

  1. 1

    Check the status, date and the Obsoletes/Updates lines. If a newer RFC replaces it, stop and read that one.

  2. 2

    Read the abstract and introduction, then jump to Security Considerations. You now know the problem and the constraints.

  3. 3

    Skim the table of contents to build a map, but do not read linearly yet.

  4. 4

    Read the packet format and the state machine, ignoring everything else. Ask: what are the fields, and what changes state?

  5. 5

    Read the IANA Considerations to learn which values are registered and where the current registry lives.

  6. 6

    Only then read the procedures and edge cases, with the diagrams beside you.

  7. 7

    Check the RFC Editor errata page for that number. Errata are corrections that were accepted after publication.

Six traps that catch beginners

Reading an obsoleted RFC

The header says "Obsoleted by RFC XXXX". Always check before investing an hour.

Ignoring errata

Accepted errata correct real errors in the published text. Check the RFC Editor errata page for the number.

Treating Informational as a standard

A vendor protocol published as Informational is documented, not standardised. Interoperability is not guaranteed.

Reading only the abstract

The abstract describes intent. Fields, defaults and error behaviour live in the body.

Confusing the RFC with the registry

Assigned port numbers and message types live in IANA registries, which change independently of the RFC.

Skipping Security Considerations

It explains the threat model the design assumes, and often the reason a feature exists at all.

Where to look things up

Your first three documents

1. RFC 2119 — two pages, defines the keywords above. Read it once and the rest of the series becomes easier.

2. RFC 768 — the entire UDP specification fits in about three pages: an 8-byte header and a checksum. Compare it with the UDP lesson.

3. RFC 9293 — the consolidated TCP specification. Long, but now you know where the state machine and the options live.

How to cite a standard

Name the document, not just the protocol: "TCP (RFC 9293, Section 3.5)" is useful; "the TCP RFC" is not. For IEEE and ISO documents include the edition or year, because clauses move between editions.