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

Document Type Active Internet-Draft (httpbis WG)
Last updated 2017-02-20 (latest revision 2016-11-20)
Replaces draft-reschke-rfc5987bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Mark Nottingham
Shepherd write-up Show (last changed 2017-02-01)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date On agenda of 2017-03-02 IESG telechat
Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Alexey Melnikov
Send notices to mnot@mnot.net
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
???

HTTP Working Group                                            J. Reschke
Internet-Draft                                                greenbytes
Obsoletes: 5987 (if approved)                            January 9, 2017
Intended status: Standards Track
Expires: July 13, 2017

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

Abstract

   By default, header field values in Hypertext Transfer Protocol (HTTP)
   messages cannot easily carry characters outside the US-ASCII coded
   character set.  RFC 2231 defines an encoding mechanism for use in
   parameters inside Multipurpose Internet Mail Extensions (MIME) header
   field values.  This document specifies an encoding suitable for use
   in HTTP header fields that is compatible with a simplified profile of
   the encoding defined in RFC 2231.

   This document obsoletes RFC 5987.

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

Reschke                   Expires July 13, 2017                 [Page 1]
Internet-Draft      Charset/Language Encoding in HTTP       January 2017

   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 13, 2017.

Copyright Notice

   Copyright (c) 2017 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.

Reschke                   Expires July 13, 2017                 [Page 2]
Internet-Draft      Charset/Language Encoding in HTTP       January 2017

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  4
   3.  Comparison to RFC 2231 and Definition of the Encoding  . . . .  5
     3.1.  Parameter Continuations  . . . . . . . . . . . . . . . . .  5
     3.2.  Parameter Value Character Encoding and Language
           Information  . . . . . . . . . . . . . . . . . . . . . . .  5
       3.2.1.  Definition . . . . . . . . . . . . . . . . . . . . . .  6
       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 . . . . . . . . . . . . . . . . . . . . . . 10
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Changes from RFC 5987 . . . . . . . . . . . . . . . . 13
   Appendix B.  Implementation Report . . . . . . . . . . . . . . . . 14
   Appendix C.  Change Log (to be removed by RFC Editor before
                publication)  . . . . . . . . . . . . . . . . . . . . 14
Show full document text