RFC 8187 on Indicating Character Encoding and Language for HTTP Header Field Parameters
rfc-editor@rfc-editor.org Thu, 14 September 2017 19:34 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8F5133064 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 Sep 2017 12:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AT0gYUNZtJwv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 Sep 2017 12:34:08 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E74B132ED7 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 14 Sep 2017 12:34:07 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1dsZqA-0006f3-Pg for ietf-http-wg-dist@listhub.w3.org; Thu, 14 Sep 2017 19:30:22 +0000
Resent-Date: Thu, 14 Sep 2017 19:30:22 +0000
Resent-Message-Id: <E1dsZqA-0006f3-Pg@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1dsZpx-0005ob-Sv for ietf-http-wg@listhub.w3.org; Thu, 14 Sep 2017 19:30:09 +0000
Received: from rfc-editor.org ([4.31.198.49]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1dsZpw-0007e6-Uv for ietf-http-wg@w3.org; Thu, 14 Sep 2017 19:30:09 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id BFF30B8011D; Thu, 14 Sep 2017 12:29:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Message-Id: <20170914192932.BFF30B8011D@rfc-editor.org>
Date: Thu, 14 Sep 2017 12:29:32 -0700
Received-SPF: pass client-ip=4.31.198.49; envelope-from=wwwrun@rfc-editor.org; helo=rfc-editor.org
X-W3C-Hub-Spam-Status: No, score=-6.4
X-W3C-Hub-Spam-Report: AWL=0.760, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1dsZpw-0007e6-Uv b524492bea43eb87d3d1fba1d699d9a2
X-Original-To: ietf-http-wg@w3.org
Subject: RFC 8187 on Indicating Character Encoding and Language for HTTP Header Field Parameters
Archived-At: <http://www.w3.org/mid/20170914192932.BFF30B8011D@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/34452
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 8187
Title: Indicating Character Encoding and Language
for HTTP Header Field Parameters
Author: J. Reschke
Status: Standards Track
Stream: IETF
Date: September 2017
Mailbox: julian.reschke@greenbytes.de
Pages: 13
Characters: 28118
Obsoletes: RFC 5987
I-D Tag: draft-ietf-httpbis-rfc5987bis-05.txt
URL: https://www.rfc-editor.org/info/rfc8187
DOI: 10.17487/RFC8187
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.
This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC