draft-reschke-rfc5987bis-07.txt   draft-reschke-rfc5987bis-latest.txt 
Network Working Group J. Reschke Network Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Obsoletes: 5987 (if approved) July 2, 2014 Obsoletes: 5987 (if approved) February 20, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: January 3, 2015 Expires: August 24, 2017
Indicating Character Encoding and Language for HTTP Header Field Indicating Character Encoding and Language for HTTP Header Field
Parameters Parameters
draft-reschke-rfc5987bis-07 draft-reschke-rfc5987bis-latest
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.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 January 3, 2015. This Internet-Draft will expire on August 24, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2017 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 25 skipping to change at page 3, line 25
3.2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . 8 3.2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . 8
3.3. Language Specification in Encoded Words . . . . . . . . . 8 3.3. Language Specification in Encoded Words . . . . . . . . . 8
4. Guidelines for Usage in HTTP Header Field Definitions . . . . 9 4. Guidelines for Usage in HTTP Header Field Definitions . . . . 9
4.1. When to Use the Extension . . . . . . . . . . . . . . . . 9 4.1. When to Use the Extension . . . . . . . . . . . . . . . . 9
4.2. Error Handling . . . . . . . . . . . . . . . . . . . . . . 9 4.2. Error Handling . . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Changes from RFC 5987 . . . . . . . . . . . . . . . . 12 Appendix A. Changes from RFC 5987 . . . . . . . . . . . . . . . . 13
Appendix B. Implementation Report . . . . . . . . . . . . . . . . 13 Appendix B. Implementation Report . . . . . . . . . . . . . . . . 13
Appendix C. Change Log (to be removed by RFC Editor before Appendix C. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 13 publication) . . . . . . . . . . . . . . . . . . . . 14
C.1. Since RFC5987 . . . . . . . . . . . . . . . . . . . . . . 13 C.1. Since RFC5987 . . . . . . . . . . . . . . . . . . . . . . 14
C.2. Since draft-reschke-rfc5987bis-00 . . . . . . . . . . . . 13 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. Open issues (to be removed by RFC Editor prior to Appendix D. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 14 publication) . . . . . . . . . . . . . . . . . . . . 15
D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
D.2. httpbis . . . . . . . . . . . . . . . . . . . . . . . . . 14 D.2. httpbis . . . . . . . . . . . . . . . . . . . . . . . . . 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 11, line 11 skipping to change at page 11, line 11
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.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, DOI 10.17487/
RFC2616, June 1999,
<http://www.rfc-editor.org/info/rfc2616>.
[RFC2978] Freed, N. and J. Postel, "IANA Charset Registration [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration
Procedures", BCP 19, RFC 2978, October 2000. Procedures", BCP 19, RFC 2978, DOI 10.17487/RFC2978,
October 2000, <http://www.rfc-editor.org/info/rfc2978>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629,
November 2003,
<http://www.rfc-editor.org/info/rfc3629>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax", "Uniform Resource Identifier (URI): Generic Syntax",
STD 66, RFC 3986, January 2005. STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, RFC 5234, Syntax Specifications: ABNF", STD 68, RFC 5234,
January 2008. DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for
Identifying Languages", BCP 47, RFC 5646, Identifying Languages", BCP 47, RFC 5646, DOI 10.17487/
September 2009. RFC5646, September 2009,
<http://www.rfc-editor.org/info/rfc5646>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Message Syntax and Transfer Protocol (HTTP/1.1): Message Syntax and
Routing", RFC 7230, June 2014. Routing", RFC 7230, DOI 10.17487/RFC7230, June 2014,
<http://www.rfc-editor.org/info/rfc7230>.
[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Semantics and Content", Transfer Protocol (HTTP/1.1): Semantics and Content",
RFC 7231, June 2014. RFC 7231, DOI 10.17487/RFC7231, June 2014,
<http://www.rfc-editor.org/info/rfc7231>.
[USASCII] American National Standards Institute, "Coded Character [USASCII] American National Standards Institute, "Coded Character
Set -- 7-bit American Standard Code for Information Set -- 7-bit American Standard Code for Information
Interchange", ANSI X3.4, 1986. Interchange", ANSI X3.4, 1986.
8.2. Informative References 8.2. Informative References
[Err1912] RFC Errata, "Errata ID 1912, RFC 2978", [Err1912] RFC Errata, "Errata ID 1912, RFC 2978",
<http://www.rfc-editor.org>. <http://www.rfc-editor.org>.
[ISO-8859-1] International Organization for Standardization, [ISO-8859-1] International Organization for Standardization,
"Information technology -- 8-bit single-byte coded "Information technology -- 8-bit single-byte coded
graphic character sets -- Part 1: Latin alphabet No. graphic character sets -- Part 1: Latin alphabet No.
1", ISO/IEC 8859-1:1998, 1998. 1", ISO/IEC 8859-1:1998, 1998.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) Part One: Format of Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies", RFC 2045, November 1996. Message Bodies", RFC 2045, DOI 10.17487/RFC2045,
November 1996,
<http://www.rfc-editor.org/info/rfc2045>.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail
Extensions) Part Three: Message Header Extensions for Extensions) Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996. Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047,
November 1996,
<http://www.rfc-editor.org/info/rfc2047>.
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and [RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and
Encoded Word Extensions: Character Sets, Languages, and Encoded Word Extensions: Character Sets, Languages, and
Continuations", RFC 2231, November 1997. Continuations", RFC 2231, DOI 10.17487/RFC2231,
November 1997,
<http://www.rfc-editor.org/info/rfc2231>.
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998. Languages", BCP 18, RFC 2277, DOI 10.17487/RFC2277,
January 1998, <http://www.rfc-editor.org/info/rfc2277>.
[RFC2388] Masinter, L., "Returning Values from Forms: multipart/ [RFC2388] Masinter, L., "Returning Values from Forms: multipart/
form-data", RFC 2388, August 1998. form-data", RFC 2388, DOI 10.17487/RFC2388,
August 1998, <http://www.rfc-editor.org/info/rfc2388>.
[RFC5987] Reschke, J., "Character Set and Language Encoding for [RFC5987] Reschke, J., "Character Set and Language Encoding for
Hypertext Transfer Protocol (HTTP) Header Field Hypertext Transfer Protocol (HTTP) Header Field
Parameters", RFC 5987, August 2010. Parameters", RFC 5987, DOI 10.17487/RFC5987,
August 2010, <http://www.rfc-editor.org/info/rfc5987>.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, DOI 10.17487/
RFC5988, October 2010,
<http://www.rfc-editor.org/info/rfc5988>.
[RFC6266] Reschke, J., "Use of the Content-Disposition Header [RFC6266] Reschke, J., "Use of the Content-Disposition Header
Field in the Hypertext Transfer Protocol (HTTP)", Field in the Hypertext Transfer Protocol (HTTP)",
RFC 6266, June 2011. RFC 6266, DOI 10.17487/RFC6266, June 2011,
<http://www.rfc-editor.org/info/rfc6266>.
[RFC6365] Hoffman, P. and J. Klensin, "Terminology Used in [RFC6365] Hoffman, P. and J. Klensin, "Terminology Used in
Internationalization in the IETF", BCP 166, RFC 6365, Internationalization in the IETF", BCP 166, RFC 6365,
September 2011. DOI 10.17487/RFC6365, September 2011,
<http://www.rfc-editor.org/info/rfc6365>.
URIs URIs
[1] <mailto:ietf-http-wg@w3.org> [1] <mailto:ietf-http-wg@w3.org>
[2] <mailto:ietf-http-wg-request@w3.org?subject=subscribe> [2] <mailto:ietf-http-wg-request@w3.org?subject=subscribe>
Appendix A. Changes from RFC 5987 Appendix A. Changes from RFC 5987
This section summarizes the changes compared to [RFC5987]: This section summarizes the changes compared to [RFC5987]:
 End of changes. 26 change blocks. 
32 lines changed or deleted 57 lines changed or added

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