Indicating Character Encoding and Language for HTTP Header Field Parameters
draft-ietf-httpbis-rfc5987bis-00

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Author Julian Reschke 
Last updated 2015-10-14 (latest revision 2015-10-02)
Replaces draft-reschke-rfc5987bis
Stream Internent Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Mark Nottingham
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTP Working Group                                            J. Reschke
Internet-Draft                                                greenbytes
Obsoletes: 5987 (if approved)                            October 2, 2015
Intended status: Standards Track
Expires: April 4, 2016

    Indicating Character Encoding and Language for HTTP Header Field
                               Parameters
                    draft-ietf-httpbis-rfc5987bis-00

Abstract

   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
   2231.

Editorial Note (To be removed by RFC Editor before publication)

   Discussion of this draft takes place on the HTTPBIS working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   <https://lists.w3.org/Archives/Public/ietf-http-wg/>.

   Working Group information can be found at
   <https://tools.ietf.org/wg/httpbis/> and <http://httpwg.github.io/>;
   source code and issues list for this draft can be found at
   <https://github.com/httpwg/http-extensions>.

   The changes in this draft are summarized in Appendix C.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Reschke                   Expires April 4, 2016                 [Page 1]
Internet-Draft      Charset/Language Encoding in HTTP       October 2015

   This Internet-Draft will expire on April 4, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  4
   3.  Comparison to RFC 2231 and Definition of the Encoding  . . . .  4
     3.1.  Parameter Continuations  . . . . . . . . . . . . . . . . .  5
     3.2.  Parameter Value Character Encoding and Language
           Information  . . . . . . . . . . . . . . . . . . . . . . .  5
       3.2.1.  Definition . . . . . . . . . . . . . . . . . . . . . .  5
       3.2.2.  Historical Notes . . . . . . . . . . . . . . . . . . .  7
       3.2.3.  Examples . . . . . . . . . . . . . . . . . . . . . . .  8
     3.3.  Language Specification in Encoded Words  . . . . . . . . .  8
   4.  Guidelines for Usage in HTTP Header Field Definitions  . . . .  9
     4.1.  When to Use the Extension  . . . . . . . . . . . . . . . .  9
     4.2.  Error Handling . . . . . . . . . . . . . . . . . . . . . .  9
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Changes from RFC 5987 . . . . . . . . . . . . . . . . 13
   Appendix B.  Implementation Report . . . . . . . . . . . . . . . . 13
   Appendix C.  Change Log (to be removed by RFC Editor before
                publication)  . . . . . . . . . . . . . . . . . . . . 14
     C.1.  Since RFC5987  . . . . . . . . . . . . . . . . . . . . . . 14
     C.2.  Since draft-reschke-rfc5987bis-00  . . . . . . . . . . . . 14
     C.3.  Since draft-reschke-rfc5987bis-01  . . . . . . . . . . . . 14
     C.4.  Since draft-reschke-rfc5987bis-02  . . . . . . . . . . . . 14
     C.5.  Since draft-reschke-rfc5987bis-03  . . . . . . . . . . . . 14
     C.6.  Since draft-reschke-rfc5987bis-04  . . . . . . . . . . . . 14
Show full document text