[Fwd: STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF]
Dave Crocker <[email protected]>
| Newsgroups | gmane.ietf.rfc822,gmane.ietf.apps-discuss |
|---|---|
| Organization | Brandenburg InternetWorking |
| Message-ID | <[email protected]> |
FYI. (Sorry for the cross-posting, but I can't think of a single-best list to post to.) -------- Original Message -------- Subject: STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF Date: Thu, 31 Jan 2008 17:24:14 -0800 (PST) From: [email protected] To: [email protected], [email protected] CC: [email protected] A new Request for Comments is now available in online RFC libraries. STD 68 RFC 5234 Title: Augmented BNF for Syntax Specifications: ABNF Author: D. Crocker, Ed., P. Overell Status: Standards Track Date: January 2008 Mailbox: [email protected], [email protected] Pages: 16 Characters: 26359 Obsoletes: RFC4234 See Also: STD0068 I-D Tag: draft-crocker-rfc4234bis-01.txt URL: http://www.rfc-editor.org/rfc/rfc5234.txt 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] This is now a Standard Protocol. -- Dave Crocker Brandenburg InternetWorking bbiw.net