draft-ietf-httpbis-rfc5987bis-05.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) March 2, 2017 Obsoletes: 5987 (if approved) March 24, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: September 3, 2017 Expires: September 25, 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-05 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 7 skipping to change at page 2, line 7
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 September 3, 2017. This Internet-Draft will expire on September 25, 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 13 skipping to change at page 3, line 13
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 . . . . . . . . . 16 C.9. Since draft-ietf-httpbis-rfc5987bis-00 . . . . . . . . . 16
C.10. Since draft-ietf-httpbis-rfc5987bis-01 . . . . . . . . . 16 C.10. Since draft-ietf-httpbis-rfc5987bis-01 . . . . . . . . . 16
C.11. Since draft-ietf-httpbis-rfc5987bis-02 . . . . . . . . . 16 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 C.13. Since draft-ietf-httpbis-rfc5987bis-04 . . . . . . . . . 16
C.14. Since draft-ietf-httpbis-rfc5987bis-05 . . . . . . . . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
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
skipping to change at page 16, line 44 skipping to change at page 16, line 44
Include WG into Acknowledgements for this revision. Include WG into Acknowledgements for this revision.
Mention RFC 5987 in the abstract (<https://github.com/httpwg/http- Mention RFC 5987 in the abstract (<https://github.com/httpwg/http-
extensions/issues/271>). extensions/issues/271>).
C.13. Since draft-ietf-httpbis-rfc5987bis-04 C.13. Since draft-ietf-httpbis-rfc5987bis-04
Mention RFC8053 in Implementation Report. Mention RFC8053 in Implementation Report.
C.14. Since draft-ietf-httpbis-rfc5987bis-05
None yet.
Acknowledgements 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. 6 change blocks. 
4 lines changed or deleted 9 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/