FWD: I-D Action:draft-reschke-rfc2231-in-http-09.txt


this draft addresses two issues that were brought up last week:

- there was a bug in the ABNF for (extended) attribute values, 
disallowing certain characters that should have been allowed, and 
allowing one character that shouldn't have been allowed

- it points out that "token" in HTTP and MIME are different in a subtle 
way, and clarifies that it's really using the HTTP token production

Best regards, Julian

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 	Title           : Application of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Header Fields
> 	Author(s)       : J. Reschke
> 	Filename        : draft-reschke-rfc2231-in-http-09.txt
> 	Pages           : 14
> 	Date            : 2010-02-08
> By default, message header field parameters in Hypertext Transfer
> Protocol (HTTP) messages can not carry characters outside the ISO-
> 8859-1 character set.  RFC 2231 defines an escaping mechanism for use
> in Multipurpose Internet Mail Extensions (MIME) headers.  This
> document specifies a profile of that encoding suitable for use in
> HTTP header fields.
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-reschke-rfc2231-in-http-09.txt
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> ------------------------------------------------------------------------
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Received on Monday, 8 February 2010 14:51:41 UTC