draft-ietf-httpbis-rfc5987bis-00.txt   draft-ietf-httpbis-rfc5987bis-01.txt 

HTTP Working Group J. Reschke HTTP Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Obsoletes: 5987 (if approved) October 2, 2015 Obsoletes: 5987 (if approved) March 4, 2016
Intended status: Standards Track Intended status: Standards Track
Expires: April 4, 2016 Expires: September 5, 2016
Indicating Character Encoding and Language for HTTP Header Field Indicating Character Encoding and Language for HTTP Header Field
Parameters Parameters
draft-ietf-httpbis-rfc5987bis-00 draft-ietf-httpbis-rfc5987bis-01
Abstract Abstract
By default, message header field parameters in Hypertext Transfer By default, message header field parameters in Hypertext Transfer
Protocol (HTTP) messages cannot carry characters outside the ISO- Protocol (HTTP) messages cannot carry characters outside the ISO-
8859-1 character set. RFC 2231 defines an encoding mechanism for use 8859-1 character set. RFC 2231 defines an encoding mechanism for use
in Multipurpose Internet Mail Extensions (MIME) headers. This in Multipurpose Internet Mail Extensions (MIME) headers. This
document specifies an encoding suitable for use in HTTP header fields document specifies an encoding suitable for use in HTTP header fields
that is compatible with a profile of the encoding defined in RFC that is compatible with a profile of the encoding defined in RFC
2231. 2231.
Editorial Note (To be removed by RFC Editor before publication) Editorial Note (To be removed by RFC Editor before publication)
Discussion of this draft takes place on the HTTPBIS working group Discussion of this draft takes place on the HTTPBIS working group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
<https://lists.w3.org/Archives/Public/ietf-http-wg/>. <https://lists.w3.org/Archives/Public/ietf-http-wg/>.
Working Group information can be found at Working Group information can be found at <http://httpwg.github.io/>;
<https://tools.ietf.org/wg/httpbis/> and <http://httpwg.github.io/>;
source code and issues list for this draft can be found at source code and issues list for this draft can be found at
<https://github.com/httpwg/http-extensions>. <https://github.com/httpwg/http-extensions>.
The changes in this draft are summarized in Appendix C. The changes in this draft are summarized in Appendix C.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 4, 2016. This Internet-Draft will expire on September 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 5 skipping to change at page 3, line 37
Appendix C. Change Log (to be removed by RFC Editor before Appendix C. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 14 publication) . . . . . . . . . . . . . . . . . . . . 14
C.1. Since RFC5987 . . . . . . . . . . . . . . . . . . . . . . 14 C.1. Since RFC5987 . . . . . . . . . . . . . . . . . . . . . . 14
C.2. Since draft-reschke-rfc5987bis-00 . . . . . . . . . . . . 14 C.2. Since draft-reschke-rfc5987bis-00 . . . . . . . . . . . . 14
C.3. Since draft-reschke-rfc5987bis-01 . . . . . . . . . . . . 14 C.3. Since draft-reschke-rfc5987bis-01 . . . . . . . . . . . . 14
C.4. Since draft-reschke-rfc5987bis-02 . . . . . . . . . . . . 14 C.4. Since draft-reschke-rfc5987bis-02 . . . . . . . . . . . . 14
C.5. Since draft-reschke-rfc5987bis-03 . . . . . . . . . . . . 14 C.5. Since draft-reschke-rfc5987bis-03 . . . . . . . . . . . . 14
C.6. Since draft-reschke-rfc5987bis-04 . . . . . . . . . . . . 14 C.6. Since draft-reschke-rfc5987bis-04 . . . . . . . . . . . . 14
C.7. Since draft-reschke-rfc5987bis-05 . . . . . . . . . . . . 14 C.7. Since draft-reschke-rfc5987bis-05 . . . . . . . . . . . . 14
C.8. Since draft-reschke-rfc5987bis-06 . . . . . . . . . . . . 14 C.8. Since draft-reschke-rfc5987bis-06 . . . . . . . . . . . . 14
Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 14 C.9. Since draft-ietf-httpbis-rfc5987bis-00 . . . . . . . . . . 14
Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
By default, message header field parameters in HTTP ([RFC2616]) By default, message header field parameters in HTTP ([RFC2616])
messages cannot carry characters outside the ISO-8859-1 coded messages cannot carry characters outside the ISO-8859-1 coded
character set ([ISO-8859-1]). RFC 2231 ([RFC2231]) defines an character set ([ISO-8859-1]). RFC 2231 ([RFC2231]) defines an
encoding mechanism for use in MIME headers. This document specifies encoding mechanism for use in MIME headers. This document specifies
an encoding suitable for use in HTTP header fields that is compatible an encoding suitable for use in HTTP header fields that is compatible
with a profile of the encoding defined in RFC 2231. with a profile of the encoding defined in RFC 2231.
skipping to change at page 8, line 17 skipping to change at page 8, line 17
3.2.3. Examples 3.2.3. Examples
Non-extended notation, using "token": Non-extended notation, using "token":
foo: bar; title=Economy foo: bar; title=Economy
Non-extended notation, using "quoted-string": Non-extended notation, using "quoted-string":
foo: bar; title="US-$ rates" foo: bar; title="US-$ rates"
Extended notation, using the Unicode character U+00A3 (POUND SIGN): Extended notation, using the Unicode character U+00A3 ("£", POUND
SIGN):
foo: bar; title*=utf-8'en'%C2%A3%20rates foo: bar; title*=utf-8'en'%C2%A3%20rates
Note: the Unicode pound sign character U+00A3 was encoded into the Note: the Unicode pound sign character U+00A3 was encoded into the
octet sequence C2 A3 using the UTF-8 character encoding, then octet sequence C2 A3 using the UTF-8 character encoding, then
percent-encoded. Also, note that the space character was encoded as percent-encoded. Also, note that the space character was encoded as
%20, as it is not contained in attr-char. %20, as it is not contained in attr-char.
Extended notation, using the Unicode characters U+00A3 (POUND SIGN) Extended notation, using the Unicode characters U+00A3 ("£", POUND
and U+20AC (EURO SIGN): SIGN) and U+20AC ("€", EURO SIGN):
foo: bar; title*=UTF-8''%c2%a3%20and%20%e2%82%ac%20rates foo: bar; title*=UTF-8''%c2%a3%20and%20%e2%82%ac%20rates
Note: the Unicode pound sign character U+00A3 was encoded into the Note: the Unicode pound sign character U+00A3 was encoded into the
octet sequence C2 A3 using the UTF-8 character encoding, then octet sequence C2 A3 using the UTF-8 character encoding, then
percent-encoded. Likewise, the Unicode euro sign character U+20AC percent-encoded. Likewise, the Unicode euro sign character U+20AC
was encoded into the octet sequence E2 82 AC, then percent-encoded. was encoded into the octet sequence E2 82 AC, then percent-encoded.
Also note that HEXDIG allows both lowercase and uppercase characters, Also note that HEXDIG allows both lowercase and uppercase characters,
so recipients must understand both, and that the language information so recipients must understand both, and that the language information
is optional, while the character encoding is not. is optional, while the character encoding is not.
skipping to change at page 14, line 45 skipping to change at page 14, line 45
C.7. Since draft-reschke-rfc5987bis-05 C.7. Since draft-reschke-rfc5987bis-05
Update status of Firefox support in HTTP Link Header field. Update status of Firefox support in HTTP Link Header field.
C.8. Since draft-reschke-rfc5987bis-06 C.8. Since draft-reschke-rfc5987bis-06
Update status with respect to Safari 6. Update status with respect to Safari 6.
Started work on update with respect to RFC 723x. Started work on update with respect to RFC 723x.
C.9. Since draft-ietf-httpbis-rfc5987bis-00
Editorial changes; introducing non-ASCII characters into author's
address, acknowledgements, and examples.
Appendix D. Acknowledgements Appendix D. Acknowledgements
Thanks to Martin Duerst and Frank Ellermann for help figuring out Thanks to Martin Dürst and Frank Ellermann for help figuring out
ABNF details, to Graham Klyne and Alexey Melnikov for general review, ABNF details, to Graham Klyne and Alexey Melnikov for general review,
to Chris Newman for pointing out an RFC 2231 incompatibility, and to to Chris Newman for pointing out an RFC 2231 incompatibility, and to
Benjamin Carlyle, Roar Lauritzsen, Eric Lawrence, and James Manger Benjamin Carlyle, Roar Lauritzsen, Eric Lawrence, and James Manger
for implementer's feedback. for implementer's feedback.
Author's Address Author's Address
Julian F. Reschke Julian F. Reschke
greenbytes GmbH greenbytes GmbH
Hafenweg 16 Hafenweg 16
Muenster, NW 48155 Münster, NW 48155
Germany Germany
EMail: julian.reschke@greenbytes.de EMail: julian.reschke@greenbytes.de
URI: http://greenbytes.de/tech/webdav/ URI: http://greenbytes.de/tech/webdav/
 End of changes. 13 change blocks. 
13 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.43. The latest version is available from http://tools.ietf.org/tools/rfcdiff/