Augmented BNF for Syntax Specifications: ABNF
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 16
- Abstract
- Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]
- Publication Date
- 2005-10-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC4234- Link
- https://doi.org/10.17487/RFC4234
- Author(s)
- Dave CrockerPaul Overell
- Keyword(s)
- ABNF, BNF, Encoding, Email
Latest version of IETF RFC 4234
Document Versions — IETF RFC 4234
-
▶ IETF RFC 4234 (2005-10-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
Bibliographic Reference(s)
- IETF RFC 733 [Superseded*]
- IETF RFC 822 [Superseded*]
- IETF RFC 2234 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4234.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC4234
Snippet:
IETF RFC 4234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC4234
HTML (ISO 690 compliant)
Preview:
IETF RFC 4234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC4234
Snippet:
<span class="citation"><cite>IETF RFC 4234</cite>, Augmented BNF for Syntax Specifications: ABNF. Available at <a href="https://doi.org/10.17487/RFC4234" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4234</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4234, Augmented BNF for Syntax Specifications: ABNF
doi: 10.17487/RFC4234
url: https://doi.org/10.17487/RFC4234
doi: 10.17487/RFC4234
url: https://doi.org/10.17487/RFC4234
Snippet:
<li> <cite id="bib-rfc4234">IETF RFC 4234</cite>, Augmented BNF for Syntax Specifications: ABNF <span class="doi">10.17487/RFC4234</span> </li>
Referenced By
- IETF RFC 3977 [Active*]
- IETF RFC 4240 [Active*]
- IETF RFC 4282 [Superseded*]
- IETF RFC 4284 [Active*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 4408 [Superseded*]
- IETF RFC 4422 [Active*]
- IETF RFC 4452 [Active*]
- IETF RFC 4474 [Superseded*]
- IETF RFC 4479 [Active*]
- IETF RFC 4505 [Active*]
- IETF RFC 4511 [Active*]
- IETF RFC 4512 [Active*]
- IETF RFC 4513 [Active*]
- IETF RFC 4514 [Active*]
- IETF RFC 4515 [Active*]
- IETF RFC 4516 [Active*]
- IETF RFC 4517 [Active*]
- IETF RFC 4519 [Active*]
- IETF RFC 4520 [Active*]
- IETF RFC 4521 [Active*]
- IETF RFC 4523 [Active*]
- IETF RFC 4566 [Superseded*]
- IETF RFC 4567 [Active*]
- IETF RFC 4568 [Active*]
- IETF RFC 4572 [Superseded*]
- IETF RFC 4582 [Superseded*]
- IETF RFC 4583 [Superseded*]
- IETF RFC 4616 [Active*]
- IETF RFC 4627 [Superseded*]
- IETF RFC 4642 [Active*]
- IETF RFC 4643 [Active*]
- IETF RFC 4644 [Active*]
- IETF RFC 4646 [Superseded*]
- IETF RFC 4647 [Active*]
- IETF RFC 4790 [Active*]
- IETF RFC 4823 [Active*]
- IETF RFC 4825 [Active*]
- IETF RFC 4871 [Superseded*]
- IETF RFC 4954 [Active*]
- IETF RFC 4964 [Active*]
- IETF RFC 4975 [Active*]
- IETF RFC 4976 [Active*]
- IETF RFC 5031 [Active*]
- IETF RFC 5049 [Active*]
- IETF RFC 5119 [Active*]
- IETF RFC 5657 [Active*]
- SMPTE ST 2029:2009 [Superseded]
- SMPTE ST 2029:2022 [Active]
- SMPTE ST 2029:2023 [Active]