Augmented BNF for Syntax Specifications: ABNF
RFC 4234

If Pekka is talking about parsers, my parser implements all of the features of this I-D.  I'm pretty sure that Harald's parser does a large subset.

Very minor concerns:

Should the "Changes in the latest version of this Internet Draft" section be removed or change to "Changes since RFC 2234"?

Section 3.1 has "NOTE: NOTE: ...".

> 1.  INTRODUCTION
> 
>    Internet technical specifications often need to define a format
>    syntax and are free to employ whatever notation their authors deem
>    useful. 

surely s/format/formal/? (also in Abstract)

>    Changes in the latest version of this Internet Draft:
> 
>       In Section 3.7 the phrase: "That is, exactly <N>Ã occurrences of
>       <element>." was correct to: "That is, exactly <n>Ã occurrences of
>       <element>."
> 
>       Some continuation comment lines needed to be corrected to begin
>       with comment character (";").

should be flagged for removal by RFC-Ed

Where is list of changes from RFC 2234?

Isn't there an Ur-reference for ABNF prior to RFC 733? I remember seeing
ABNF used in the late 1960's in compiler land.

Comments from the OPS directorate by Pekka Savola (Mar 30 17:47:13 PST 2005):

Good that someone wants to push these kind of docs forward in the
standards track.  Maybe this should go for full standard later on?

substantial:
 - the implementation report lists documents which use all the
   features of ABNF (good), and points out two specific implementations
   of ABNF.  However, said two (or some other) implementations have not
   been analyzed whether they really implement the whole ABNF language.
   If they do, mention that in the implementation report.  If not, find
   new implementations which do or remove the feature(s).

 - the document should have a section, e.g., at the appendix, which
   explicitly describes the changes (or lack thereof) since RFC2234.

editorial:
 - in references, s/Descriptive/Informative/
 - add a dummy IANA considerations section
 - there are two non-ascii chars in the draft.  The 'Changes in the
   latest version of this Internet Draft' in Introduction should be
   clearly marked to be removed by RFC-editor prior to publication.