new issue: mismatch between RFC2616 and RFC4234 CHAR definition

Hi,

I just realized that the "CHAR" core rules in RFC2616 and RFC4234 
differ, in that RFC2616 includes NUL:

     CHAR           = <any US-ASCII character (octets 0 - 127)>

(<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.2.2>)

CHAR is only used in two places:

     token          = 1*<any CHAR except CTLs or separators>

and

     quoted-pair    = "\" CHAR

(same section).

Are these productions really intended to allow NUL?

BR, Julian