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

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-ietf-httpbis-rfc5987bis-04.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: httpbis-chairs@ietf.org, draft-ietf-httpbis-rfc5987bis@ietf.org, mnot@mnot.net, ietf-http-wg@w3.org, alexey.melnikov@isode.com, mnot@pobox.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Indicating Character Encoding and Language for HTTP Header Field Parameters) to Proposed Standard


The IESG has received a request from the Hypertext Transfer Protocol WG
(httpbis) to consider the following document:
- 'Indicating Character Encoding and Language for HTTP Header Field
  Parameters'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-02-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.



The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-rfc5987bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-rfc5987bis/ballot/


No IPR declarations have been submitted directly on this I-D.

# Shepherd Writeup for RFC5987bis

## 1. Summary

Mark Nottingham is the Document Shepherd. The responsible AD is Alexey Melnikov.

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.

The intended status is Proposed Standard, unchanged from RFC5987. The Working Group felt that
promoting it to full Internet Standard would be inappropriate.


## 2. Review and Consensus

This is a bis document that seeks to revise a document the WG published in the past. Because of
that, it has received attention and review from a small set of active WG members. However, none of
the document changes are controversial.


## 3. Intellectual Property

The author has confirmed that to their direct, personal knowlege, all IPR related to this document
has already been disclosed.


### 4. Other Information

Note that this draft has non-ASCII content in it, and therefore needs to be published using the
new, Unicode-enabled process.

# Shepherd Writeup for RFC5987bis

## 1. Summary

Mark Nottingham is the Document Shepherd. The responsible AD is Alexey Melnikov.

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.

The intended status is Proposed Standard, unchanged from RFC5987. The Working Group felt that
promoting it to full Internet Standard would be inappropriate.


## 2. Review and Consensus

This is a bis document that seeks to revise a document the WG published in the past. Because of
that, it has received attention and review from a small set of active WG members. However, none of
the document changes are controversial.


## 3. Intellectual Property

The author has confirmed that to their direct, personal knowlege, all IPR related to this document
has already been disclosed.