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

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

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 14 Aug 2010 09:44:36 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <C5917948-5CEA-41C4-85DD-1B25721B9B01@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
Thanks for doing this work, Julian.


On 14/08/2010, at 3:25 AM, Julian Reschke wrote:

> FYI (and thanks to everybody who provided feedback):
> 
> -------- Original Message --------
> Subject: RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
> Date: Fri, 13 Aug 2010 08:48:21 -0700 (PDT)
> From: rfc-editor@rfc-editor.org
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> CC: rfc-editor@rfc-editor.org
> 
> 
> 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
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> 


--
Mark Nottingham     http://www.mnot.net/
Received on Friday, 13 August 2010 23:45:13 GMT

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