Document: draft-crocker-abnf-rfc2234bis-00.txt
Review: Suzanne Woolf 
Date: 31 mars 2005 


Intended Status: Draft Standard

I'd have no trouble saying this is ready to advance as Proposed
Standard. The absence of an IANA Considerations section bugs me a
little, but it would be just like the Security Considerations section
anyway, so why enslave the electrons to say so? 

However....I'm assuming it's flagged as Draft because RFC 2234 is
Proposed, but I share the concern of a couple of IESG members about
the lack of implementation report details. (It sounds like there is
one....)

It seems especially important to be able to assert there are multiple
parsers that handle ABNF as specified here. First it demonstrates that
the spec allows for self-consistent and interoperable implementations,
as required for Draft. But it seems even more important that we be
sure ABNF as documented here is powerful enough to support the use
intended, and serve as infrastructure for defining new protocol.

It's entirely possible the part that seems to be missing isn't really
and I just don't know where it is. But the concerns raised about the
requirements for Draft seem reasonable to me.