W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: Protocol Action: 'Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters' to Proposed Standard

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 30 Apr 2010 16:00:30 +0200
Message-ID: <4BDAE27E.6090503@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
(FYI)

On 30.04.2010 15:58, The IESG wrote:
> The IESG has approved the following document:
>
> - 'Character Set and Language Encoding for Hypertext Transfer Protocol
>     (HTTP) Header Field Parameters '
>     <draft-reschke-rfc2231-in-http-12.txt>  as a Proposed Standard
>
> This document has been reviewed in the IETF but is not the product of an
> IETF Working Group.
>
> The IESG contact person is Alexey Melnikov.
>
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-reschke-rfc2231-in-http-12.txt
>
> Technical Summary
>
>     This specification defines a simplified mechanism for encoding
>     arbitrary (e.g. non-ASCII) characters in HTTP header field parameters.
>
>     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.
>
>     There are multiple HTTP header fields that already use RFC 2231
>     encoding in practice (Content-Disposition) or might use it in the
>     future (Link).  The purpose of this document is to provide a single
>     place where the generic aspects of RFC 2231 encoding in HTTP header
>     fields are defined.
>
> Working Group Summary
>
>     This document is an individual submission, but has been reviewed
>     on the HTTP mailing list.
>
> Document Quality
>
>     This document is a clarification and simplification of an existing
>     protocol specification, and reviewers indicate the simplifications
>     are well-judged and match practical use in HTTP.
>
>     Also, the draft claims that, as of January 2010, there were at least
>     three independent implementations of the encoding defined in Section
>     3.2: Konqueror (trunk), Mozilla Firefox, and Opera.
>
> Personnel
>
>     Graham Klyne is the Document Shepherd for this document.
>     Alexey Melnikov is the Responsible Area Director
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>
Received on Friday, 30 April 2010 14:01:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:18 GMT