Augmented BNF for Syntax Specifications: ABNF
RFC 2234

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    drums mailing list <drums@cs.utk.edu>, drums chair <cnewman@iplanet.com> 
Subject: Protocol Action: 'Augmented BNF for Syntax Specifications: 
         ABNF' to Draft Standard 

The IESG has approved the following document:

- 'Augmented BNF for Syntax Specifications: ABNF '
  RFC 2234 as a Draft Standard

This document is the product of the Detailed Revision/Update of Message 
Standards Working Group. 

The IESG contact persons are Scott Hollenbeck and Ted Hardie.

Technical Summary
 
Internet technical specifications often need to define a format
syntax and are free to employ whatever notation their authors deem
useful.  Over the years, a modified version of Backus-Naur Form
(BNF), called Augmented BNF (ABNF), has been popular among many
Internet specifications.  It balances compactness and simplicity,
with reasonable representational power.  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.
 
Working Group Summary
 
Multiple IETF last call comments were received in favor of
advancing the document to draft standard status.  There were
no last call comments received that objected to advancing the
document.  There are errata documented for this RFC that need
to be incorporated.
 
Protocol Quality
 
Scott Hollenbeck has reviewed the spec for the IESG.

RFC Editor Note

Please incorporate the documented errata for RFC 2234 with the
exception of the item listed for section 3.9.