Fwd: I-D Action: draft-reschke-rfc5987bis-03.txt


FYI: I've been working on revising RFC 5987.

The issues list (incl links to resolved issues) is here:


At this point, I'm looking for feedback on 
-- should this wait for HTTPbis is done?

Also, I'd like to see feedback whether 
is helpful (it was added because I was planning to progress to Draft 
standard, but that standards level is now gone, and implementation 
reports aren't required anymore).

Best regards, Julian

-------- Original Message --------
Subject: I-D Action: draft-reschke-rfc5987bis-03.txt
Date: Thu, 08 Dec 2011 11:32:30 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 

	Title           : Indicating Character Encoding and Language for HTTP 
Header Field Parameters
	Author(s)       : Julian F. Reschke
	Filename        : draft-reschke-rfc5987bis-03.txt
	Pages           : 15
	Date            : 2011-12-08

    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

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

This Internet-Draft can be retrieved at:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Received on Thursday, 8 December 2011 19:37:25 UTC