RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

rfc-editor@rfc-editor.org Fri, 13 August 2010 15:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD1913A6A18 for <ietf-announce@core3.amsl.com>; Fri, 13 Aug 2010 08:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.036
X-Spam-Level:
X-Spam-Status: No, score=-102.036 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rnABOILRWG1 for <ietf-announce@core3.amsl.com>; Fri, 13 Aug 2010 08:47:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id ECA313A6A1D for <ietf-announce@ietf.org>; Fri, 13 Aug 2010 08:47:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B58BE06E4; Fri, 13 Aug 2010 08:48:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
From: rfc-editor@rfc-editor.org
Message-Id: <20100813154821.4B58BE06E4@rfc-editor.org>
Date: Fri, 13 Aug 2010 08:48:21 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Aug 2010 15:47:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5987

        Title:      Character Set and Language Encoding 
                    for Hypertext Transfer Protocol (HTTP) Header 
                    Field Parameters 
        Author:     J. Reschke
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    julian.reschke@greenbytes.de
        Pages:      10
        Characters: 20108
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-reschke-rfc2231-in-http-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5987.txt

By default, message header field parameters in Hypertext Transfer
Protocol (HTTP) messages cannot carry characters outside the ISO-
8859-1 character set.  RFC 2231 defines an encoding mechanism for use
in Multipurpose Internet Mail Extensions (MIME) headers.  This
document specifies an encoding suitable for use in HTTP header fields
that is compatible with a profile of the encoding defined in RFC
2231.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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