draft-ietf-httpbis-rfc5987bis-04.txt   draft-ietf-httpbis-rfc5987bis-latest.txt 
HTTP Working Group J. Reschke HTTP Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Obsoletes: 5987 (if approved) January 9, 2017 Obsoletes: 5987 (if approved) February 20, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: July 13, 2017 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-ietf-httpbis-rfc5987bis-04 draft-ietf-httpbis-rfc5987bis-latest
Abstract Abstract
By default, header field values in Hypertext Transfer Protocol (HTTP) By default, header field values in Hypertext Transfer Protocol (HTTP)
messages cannot easily carry characters outside the US-ASCII coded messages cannot easily carry characters outside the US-ASCII coded
character set. RFC 2231 defines an encoding mechanism for use in character set. RFC 2231 defines an encoding mechanism for use in
parameters inside Multipurpose Internet Mail Extensions (MIME) header parameters inside Multipurpose Internet Mail Extensions (MIME) header
field values. This document specifies an encoding suitable for use field values. This document specifies an encoding suitable for use
in HTTP header fields that is compatible with a simplified profile of in HTTP header fields that is compatible with a simplified profile of
the encoding defined in RFC 2231. the encoding defined in RFC 2231.
skipping to change at page 2, line 6 skipping to change at page 2, line 6
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 July 13, 2017. This Internet-Draft will expire on August 24, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
skipping to change at page 3, line 29 skipping to change at page 3, line 29
4.2. Error Handling . . . . . . . . . . . . . . . . . . . . . . 10 4.2. Error Handling . . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 12 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Changes from RFC 5987 . . . . . . . . . . . . . . . . 13 Appendix A. Changes from RFC 5987 . . . . . . . . . . . . . . . . 13
Appendix B. Implementation Report . . . . . . . . . . . . . . . . 14 Appendix B. Implementation Report . . . . . . . . . . . . . . . . 14
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 . . . . . . . . . . . . . . . . . . . . . . 15
C.2. Since draft-reschke-rfc5987bis-00 . . . . . . . . . . . . 14 C.2. Since draft-reschke-rfc5987bis-00 . . . . . . . . . . . . 15
C.3. Since draft-reschke-rfc5987bis-01 . . . . . . . . . . . . 15 C.3. Since draft-reschke-rfc5987bis-01 . . . . . . . . . . . . 15
C.4. Since draft-reschke-rfc5987bis-02 . . . . . . . . . . . . 15 C.4. Since draft-reschke-rfc5987bis-02 . . . . . . . . . . . . 15
C.5. Since draft-reschke-rfc5987bis-03 . . . . . . . . . . . . 15 C.5. Since draft-reschke-rfc5987bis-03 . . . . . . . . . . . . 15
C.6. Since draft-reschke-rfc5987bis-04 . . . . . . . . . . . . 15 C.6. Since draft-reschke-rfc5987bis-04 . . . . . . . . . . . . 15
C.7. Since draft-reschke-rfc5987bis-05 . . . . . . . . . . . . 15 C.7. Since draft-reschke-rfc5987bis-05 . . . . . . . . . . . . 15
C.8. Since draft-reschke-rfc5987bis-06 . . . . . . . . . . . . 15 C.8. Since draft-reschke-rfc5987bis-06 . . . . . . . . . . . . 15
C.9. Since draft-ietf-httpbis-rfc5987bis-00 . . . . . . . . . . 15 C.9. Since draft-ietf-httpbis-rfc5987bis-00 . . . . . . . . . . 15
C.10. Since draft-ietf-httpbis-rfc5987bis-01 . . . . . . . . . . 15 C.10. Since draft-ietf-httpbis-rfc5987bis-01 . . . . . . . . . . 15
C.11. Since draft-ietf-httpbis-rfc5987bis-02 . . . . . . . . . . 15 C.11. Since draft-ietf-httpbis-rfc5987bis-02 . . . . . . . . . . 16
C.12. Since draft-ietf-httpbis-rfc5987bis-03 . . . . . . . . . . 16 C.12. Since draft-ietf-httpbis-rfc5987bis-03 . . . . . . . . . . 16
C.13. Since draft-ietf-httpbis-rfc5987bis-04 . . . . . . . . . . 16
Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 16 Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
Use of characters outside the US-ASCII coded character set Use of characters outside the US-ASCII coded character set
([RFC0020]) in HTTP header fields ([RFC7230]) is non-trivial: ([RFC0020]) in HTTP header fields ([RFC7230]) is non-trivial:
o The HTTP specification discourages use of non-US-ASCII characters o The HTTP specification discourages use of non-US-ASCII characters
in field values, placing them into the "obs-text" ABNF production in field values, placing them into the "obs-text" ABNF production
([RFC7230], Section 3.2). ([RFC7230], Section 3.2).
skipping to change at page 13, line 29 skipping to change at page 13, line 29
[RFC7578] Masinter, L., "Returning Values from Forms: [RFC7578] Masinter, L., "Returning Values from Forms:
multipart/form-data", RFC 7578, DOI 10.17487/ multipart/form-data", RFC 7578, DOI 10.17487/
RFC7578, July 2015, RFC7578, July 2015,
<http://www.rfc-editor.org/info/rfc7578>. <http://www.rfc-editor.org/info/rfc7578>.
[RFC7616] Shekh-Yusef, R., Ed., Ahrens, D., and S. Bremer, [RFC7616] Shekh-Yusef, R., Ed., Ahrens, D., and S. Bremer,
"HTTP Digest Access Authentication", RFC 7616, "HTTP Digest Access Authentication", RFC 7616,
DOI 10.17487/RFC7616, September 2015, DOI 10.17487/RFC7616, September 2015,
<http://www.rfc-editor.org/info/rfc7616>. <http://www.rfc-editor.org/info/rfc7616>.
[RFC8053] Oiwa, Y., Watanabe, H., Takagi, H., Maeda, K.,
Hayashi, T., and Y. Ioku, "HTTP Authentication
Extensions for Interactive Clients", RFC 8053,
DOI 10.17487/RFC8053, January 2017,
<http://www.rfc-editor.org/info/rfc8053>.
[XMLHttpRequest] WhatWG, "XMLHttpRequest", [XMLHttpRequest] WhatWG, "XMLHttpRequest",
<https://xhr.spec.whatwg.org/>. <https://xhr.spec.whatwg.org/>.
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]:
o The document title was changed to "Indicating Character Encoding o The document title was changed to "Indicating Character Encoding
and Language for HTTP Header Field Parameters". and Language for HTTP Header Field Parameters".
skipping to change at page 14, line 7 skipping to change at page 14, line 11
o The document does not attempt to re-define a generic "parameter" o The document does not attempt to re-define a generic "parameter"
ABNF anymore (it turned out that there really isn't a generic ABNF anymore (it turned out that there really isn't a generic
definition of parameters in HTTP; for instance, there are subtle definition of parameters in HTTP; for instance, there are subtle
differences with respect to whitespace handling). differences with respect to whitespace handling).
o A note about defects in error handling in current implementations o A note about defects in error handling in current implementations
was removed, as it wasn't accurate anymore. was removed, as it wasn't accurate anymore.
Appendix B. Implementation Report Appendix B. Implementation Report
The encoding defined in this document currently is used for three The encoding defined in this document currently is used in four
different HTTP header fields: different HTTP header fields:
o "Authentication-Control", defined in [RFC8053],
o "Authorization" (as used in HTTP Digest Authentication, defined in o "Authorization" (as used in HTTP Digest Authentication, defined in
[RFC7616]), [RFC7616]),
o "Content-Disposition", defined in [RFC6266], and o "Content-Disposition", defined in [RFC6266], and
o "Link", defined in [RFC5988]. o "Link", defined in [RFC5988].
As the encoding is a profile/clarification of the one defined in As the encoding is a profile/clarification of the one defined in
[RFC2231] in 1997, many user agents already supported it for use in [RFC2231] in 1997, many user agents already supported it for use in
"Content-Disposition" when [RFC5987] got published. "Content-Disposition" when [RFC5987] got published.
skipping to change at page 16, line 19 skipping to change at page 16, line 29
Fixed one editorial issue. Updated XHR reference. Fixed one editorial issue. Updated XHR reference.
Fixed <https://github.com/httpwg/http-extensions/issues/266>: use of Fixed <https://github.com/httpwg/http-extensions/issues/266>: use of
now undefined term "parmname". now undefined term "parmname".
Include WG into Acknowledgements for this revision. Include WG into Acknowledgements for this revision.
Mention RFC 5987 in the abstract Mention RFC 5987 in the abstract
(<https://github.com/httpwg/http-extensions/issues/271>). (<https://github.com/httpwg/http-extensions/issues/271>).
C.13. Since draft-ietf-httpbis-rfc5987bis-04
Mention RFC8053 in Implementation Report.
Appendix D. Acknowledgements Appendix D. Acknowledgements
Thanks to Martin Dürst 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.
Furthermore thanks to the members of the IETF HTTP Working Group for Furthermore thanks to the members of the IETF HTTP Working Group for
the feedback specific to this update of RFC 5987. the feedback specific to this update of RFC 5987.
 End of changes. 11 change blocks. 
8 lines changed or deleted 21 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/