metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 2234: Augmented BNF for Syntax Specifications: ABNF

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4234.

Current document in this lineage: RFC 5234 — Augmented BNF for Syntax Specifications: ABNF

In plain English — editorial summary, not part of the RFC

In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, RFC733 and then RFC822 which have come to be the common citations for defining ABNF. The current document separates out that definition, to permit selective reference. Predictably, it also provides some modifications and enhancements. [STANDARDS-TRACK]

Document record

Document ID
RFC2234
Published
November 1997
Authors
D. Crocker; P. Overell
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
14
Also known as
—
Obsoleted by:
RFC 4234

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2234 (1997)
  2. RFC 4234 (2005)
  3. RFC 5234 (2008) ✓

Read the full history of Augmented BNF for Syntax Specifications: ABNF →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2234-augmented-bnf-for-syntax-specifications-abnf