RFC2252 wshp and other ABNF issues

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

RFC 2252, 4.1:
   space           = 1*" "
   whsp            = [ space ]

meaning that:

(2.5.18.1NAME'createTimestamp'EQUALITYgeneralizedTimeMatchORDERINGgeneralizedTimeOrderingMatchSYNTAX1.3.6.1.4.1.1466.115.121.1.24SINGLE-VALUENO-USER-MODIFICATIONUSAGEdirectoryOperation)

is valid!  Is there any implementation which correctly parses this?

I suggest most (but not all) uses of whsp be replaced by 'space'.
I say "not all" as there are some productions which have whsp
followed by whsp and space space would require two spaces.

I believe that some, but not all, uses of whsp should be changed
to space.  If folks concur in spirit, I put together a more
specific ABNF change proposal.

Also, I note that:
    dstring         = 1*utf8                              
    qdstring        = whsp "'" dstring "'" whsp

allows 'this ain't good'.  If whsp were replaced with space,
then 'this ain't good' would be parsable, but 'this is 'bad' too'.
Obviously there needs to be some restriction upon dstring and
possibly an escaping mechanism.

Kurt