Re: new issue: mismatch between RFC2616 and RFC4234 CHAR definition from Frank Ellermann on 2008-01-24 (ietf-http-wg@w3.org from January to March 2008)

From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Thu, 24 Jan 2008 16:05:39 +0100
To: ietf-http-wg@w3.org
Message-ID: <fna9fd$vg8$1@ger.gmane.org>

Ingo Struck wrote:

> the quoted-pair-construct should be able to
> quote any character, including NUL.

FWIW, in mail (RFC 2822) it used to be NO-WS-CTL,
WSP (HTAB or SP), and VCHAR, excluding NUL, CR,
and LF from ordinary <quoted-pair>s.  

The "missing" cases were collected in <obs-qp>
(MUST accept, MUST NOT generate).  In the last
2822upd draft NO-WS-CTL was also moved to "obs".

While RFC 2822 isn't directly relevant for HTTP
Alexey's attempt to update Digest-MD5 for SASL
ran into serious difficulties wrt <quoted-pair>s
in <qstr-val> - in essence the same construct as
in RFC 2617 and 2616, a <quoted-string> without
its quotes:

HTTP has to be clear what it is for Auth Digest.

 Frank

Received on Thursday, 24 January 2008 15:05:41 UTC