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
- 2008-01-01
- Status Note
- Internet Standard
- DOI
10.17487/RFC5234- Link
- https://doi.org/10.17487/RFC5234
- Author(s)
- Dave CrockerPaul Overell
- Keyword(s)
- ABNF, BNF, Encoding
Latest version of IETF RFC 5234
Document Versions — IETF RFC 5234
-
▶ IETF RFC 5234 (2008-01-01)THIS DOC [ACTIVE] [AMENDED] [LATEST VERSION]
Normative Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
Bibliographic Reference(s)
- IETF RFC 733 [Superseded*]
- IETF RFC 822 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5234.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 5234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC5234
Snippet:
IETF RFC 5234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC5234
HTML (ISO 690 compliant)
Preview:
IETF RFC 5234, Augmented BNF for Syntax Specifications: ABNF. Available at https://doi.org/10.17487/RFC5234
Snippet:
<span class="citation"><cite>IETF RFC 5234</cite>, Augmented BNF for Syntax Specifications: ABNF. Available at <a href="https://doi.org/10.17487/RFC5234" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5234</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5234, Augmented BNF for Syntax Specifications: ABNF
doi: 10.17487/RFC5234
url: https://doi.org/10.17487/RFC5234
doi: 10.17487/RFC5234
url: https://doi.org/10.17487/RFC5234
Snippet:
<li> <cite id="bib-rfc5234">IETF RFC 5234</cite>, Augmented BNF for Syntax Specifications: ABNF <span class="doi">10.17487/RFC5234</span> </li>
Referenced By
- IETF RFC 5098 [Active*]
- IETF RFC 5122 [Active*]
- IETF RFC 5147 [Active*]
- IETF RFC 5191 [Active*]
- IETF RFC 5198 [Active*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5335 [Superseded*]
- IETF RFC 5336 [Superseded*]
- IETF RFC 5424 [Active*]
- IETF RFC 5425 [Active*]
- IETF RFC 5456 [Active*]
- IETF RFC 5545 [Active*]
- IETF RFC 5617 [Active*]
- IETF RFC 5646 [Active*]
- IETF RFC 5657 [Active*]
- IETF RFC 5888 [Active*]
- IETF RFC 5939 [Active*]
- IETF RFC 5971 [Active*]
- IETF RFC 5987 [Superseded*]
- IETF RFC 5989 [Active*]
- IETF RFC 6012 [Active*]
- IETF RFC 6020 [Active*]
- IETF RFC 6068 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6152 [Active*]
- IETF RFC 6230 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 6265 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6350 [Active*]
- IETF RFC 6408 [Active*]
- IETF RFC 6415 [Active*]
- IETF RFC 6454 [Active*]
- IETF RFC 6455 [Active*]
- IETF RFC 6531 [Active*]
- IETF RFC 6532 [Active*]
- IETF RFC 6533 [Active*]
- IETF RFC 6570 [Active*]
- IETF RFC 6690 [Active*]
- IETF RFC 6733 [Active*]
- IETF RFC 6749 [Active*]
- IETF RFC 6750 [Active*]
- IETF RFC 6838 [Active*]
- IETF RFC 6854 [Active*]
- IETF RFC 6874 [Superseded*]
- IETF RFC 6901 [Active*]
- IETF RFC 6920 [Active*]
- IETF RFC 6929 [Active*]
- IETF RFC 7159 [Superseded*]
- IETF RFC 7230 [Superseded*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7232 [Superseded*]
- IETF RFC 7233 [Superseded*]
- IETF RFC 7234 [Superseded*]
- IETF RFC 7235 [Superseded*]
- IETF RFC 7252 [Active*]
- IETF RFC 7254 [Active*]
- IETF RFC 7273 [Active*]
- IETF RFC 7302 [Superseded*]
- IETF RFC 7405 [Active*]
- IETF RFC 7462 [Active*]
- IETF RFC 7540 [Superseded*]
- IETF RFC 7542 [Active*]
- IETF RFC 7564 [Superseded*]
- IETF RFC 7613 [Superseded*]
- IETF RFC 7615 [Superseded*]
- IETF RFC 7616 [Active*]
- IETF RFC 7617 [Active*]
- IETF RFC 7636 [Active*]
- IETF RFC 7807 [Superseded*]
- IETF RFC 7838 [Active*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 7951 [Active*]
- IETF RFC 7952 [Active*]
- IETF RFC 7972 [Active*]
- IETF RFC 8040 [Active*]
- IETF RFC 8075 [Active*]
- IETF RFC 8141 [Active*]
- IETF RFC 8187 [Active*]
- IETF RFC 8259 [Active*]
- IETF RFC 8285 [Active*]
- IETF RFC 8288 [Active*]
- IETF RFC 8323 [Active*]
- IETF RFC 8398 [Superseded*]
- SMPTE AG 25 [Active, Versionless]
- SMPTE RP 2079:2013 [Superseded]
- SMPTE RP 2079:2017 [Superseded]
- SMPTE RP 2079:2018 [Active, Stabilized]
- SMPTE RP 2092-1:2015 [Active, Amended]
- SMPTE ST 2071-1:2012 [Superseded]
- SMPTE ST 2071-1:2014 [Superseded]
- SMPTE ST 2071-1:2016 [Active, Stabilized]
- SMPTE ST 377-4:2012 [Superseded*]
- SMPTE ST 428-24:2024-11 [Active]
- SMPTE ST 429-16:2014 [Superseded]
- SMPTE ST 429-16:2023-09 [Active]