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

The IESG <> Mon, 06 February 2017 15:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B1746129E67 for <>; Mon, 6 Feb 2017 07:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jDzOlJbFB1C8 for <>; Mon, 6 Feb 2017 07:27:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 24348129E7B for <>; Mon, 6 Feb 2017 07:27:35 -0800 (PST)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1cal9p-0005fK-8Y for; Mon, 06 Feb 2017 15:24:45 +0000
Resent-Date: Mon, 06 Feb 2017 15:24:45 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1cal9h-0005e5-Fv for; Mon, 06 Feb 2017 15:24:37 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <>) id 1cal9b-0005eb-F7 for; Mon, 06 Feb 2017 15:24:32 +0000
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 98EA6129E63; Mon, 6 Feb 2017 07:24:04 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Sender: <>
Message-ID: <>
Date: Mon, 06 Feb 2017 07:24:04 -0800
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-7.2
X-W3C-Hub-Spam-Report: AWL=0.884, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1cal9b-0005eb-F7 b7d5204746e50804bb3a9adcb23a63d5
Subject: Last Call: <draft-ietf-httpbis-rfc5987bis-04.txt> (Indicating Character Encoding and Language for HTTP Header Field Parameters) to Proposed Standard
Archived-At: <>
X-Mailing-List: <> archive/latest/33447
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

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 mailing lists by 2017-02-20. Exceptionally, comments may be
sent to 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.