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: rfc-editor(_at_)rfc-editor(_dot_)org
To: ietf-announce(_at_)ietf(_dot_)org, rfc-dist(_at_)rfc-editor(_dot_)org
CC: rfc-editor(_at_)rfc-editor(_dot_)org
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: dcrocker(_at_)bbiw(_dot_)net,
paul(_dot_)overell(_at_)thus(_dot_)net
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