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



HTML version: 

Issues list: 

Diff from RFC 5987: 

This draft addresses the two comments brought up by James with respect 
to the syntax (essentially explaining that these decisions have been 
made when RFC 2231 was written, and we're not changing things due to 
backwards compatibility).

The remaining issue for now is whether to change the dependency from RFC 
2616 to HTTPbis:


My current thinking is that, yes, we should switch the dependency, and 
ship this spec back-to-back with HTTPbis...

Best regards, Julian

-------- Original Message --------
Subject: I-D Action: draft-reschke-rfc5987bis-04.txt
Date: Sun, 18 Dec 2011 09:13:23 -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-04.txt
	Pages           : 15
	Date            : 2011-12-18

    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 Sunday, 18 December 2011 17:19:13 UTC