Visual RFC.
ALL RFCs / RFC 8174
Read the RFC ↗
RFC 8174 / READING REQUIREMENTS

Read normative text without a key-word shortcut

04

Normative text specifies requirements. RFC 8174 explicitly says it need not use special key words; many requirements are expressed through plain prose, grammar or field definitions. An octet is an eight-bit byte.

DIAGRAMRead RFC section 2 ↗
RFC 8174 · § 2EXAMPLE
3 / 3
Read normative text without a key-word shortcutA fictional normative format defines a record as exactly two octets without any special key word. A later state stops the invalid inference that absence of MUST makes every length optional. The final state compares literal byte records0102 and010203, independently counting two and three octets: only the two-octet record satisfies the example definition. This illustrates RFC8174’s statement that normative text need not use key words, not a wire format defined by RFC8174 itself.Fictional format definition · not a new RFC format01 022 octets01 02 033 octetsmeets definitiondoes not meetRead the full rule, not just capitalsQuoted examples do not create protocol rules
03
Implement the actual format definition.

For this fictional format, 01 02 has two octets; 01 02 03 has three and does not meet the stated definition. The rule comes from the example specification, not from RFC 8174 defining a wire format.

Source for this drawing: RFC 8174 · Read RFC section 2 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Start with this guide; no earlier guide is needed for the overview.

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

Read the whole rule and its context, not just a case-sensitive word search.

  • Use of the RFC 2119 key words is not required. Text can be normative without any of those key words.
  • In this fictional normative format definition, a record contains exactly two octets. The example’s two-octet requirement does not disappear merely because the sentence has no MUST.
  • A scanner finding no special key word cannot conclude optional. Likewise, finding MUST in a quoted illustration does not by itself establish an actual protocol requirement; read the scope and complete text.
DETAILS

RFC 8174 §3 requires no IANA actions. Section 4 describes the document as purely procedural with no related security considerations; it adds no encryption or authorization mechanism. This guide’s parser illustration is a made-up teaching example, not an IANA-registered format or a claim that typography verifies conformance.

Read the RFC section ↗

All chapters in RFC 8174

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗