W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2017

Last Call: <draft-ietf-httpbis-rfc5987bis-04.txt> (Indicating Character Encoding and Language for HTTP Header Field Parameters) to Proposed Standard

From: The IESG <iesg-secretary@ietf.org>
Date: Mon, 06 Feb 2017 07:24:04 -0800
To: "IETF-Announce" <ietf-announce@ietf.org>
CC: httpbis-chairs@ietf.org, draft-ietf-httpbis-rfc5987bis@ietf.org, mnot@mnot.net, ietf-http-wg@w3.org, alexey.melnikov@isode.com, mnot@pobox.com
Message-ID: <148639464461.18983.10474508709421750212.idtracker@ietfa.amsl.com>

The IESG has received a request from the Hypertext Transfer Protocol WG
(httpbis) to consider the following document:
- 'Indicating Character Encoding and Language for HTTP Header Field
  <draft-ietf-httpbis-rfc5987bis-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-02-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   By default, header field values in Hypertext Transfer Protocol (HTTP)
   messages cannot easily carry characters outside the US-ASCII coded
   character set.  RFC 2231 defines an encoding mechanism for use in
   parameters inside Multipurpose Internet Mail Extensions (MIME) header
   field values.  This document specifies an encoding suitable for use
   in HTTP header fields that is compatible with a simplified profile of
   the encoding defined in RFC 2231.

   This document obsoletes RFC 5987.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.
Received on Monday, 6 February 2017 15:24:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:00 UTC