Skip to main content

Indicating Character Encoding and Language for HTTP Header Field Parameters
RFC 8187

Revision differences

Document history

Date Rev. By Action
2018-12-20
05 (System)
Received changes through RFC Editor sync (changed abstract to 'By default, header field values in Hypertext Transfer Protocol (HTTP) messages cannot easily carry characters outside …
Received changes through RFC Editor sync (changed abstract to '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.')
2017-09-14
05 (System)
Received changes through RFC Editor sync (created alias RFC 8187, changed abstract to 'By default, header field values in Hypertext Transfer Protocol (HTTP) messages …
Received changes through RFC Editor sync (created alias RFC 8187, changed abstract to '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.', changed pages to 13, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-09-14, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-httpbis-rfc5987bis and RFC 5987)
2017-09-14
05 (System) RFC published
2017-09-13
05 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2017-08-25
05 (System) RFC Editor state changed to AUTH48 from AUTH
2017-04-17
05 (System) RFC Editor state changed to AUTH from RFC-EDITOR
2017-04-14
05 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2017-03-07
05 (System) RFC Editor state changed to EDIT
2017-03-07
05 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2017-03-07
05 (System) Announcement was received by RFC Editor
2017-03-06
05 (System) IANA Action state changed to No IC from In Progress
2017-03-06
05 (System) IANA Action state changed to In Progress
2017-03-06
05 Amy Vezza IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2017-03-06
05 Amy Vezza IESG has approved the document
2017-03-06
05 Amy Vezza Closed "Approve" ballot
2017-03-06
05 Amy Vezza Ballot approval text was generated
2017-03-02
05 Cindy Morgan IESG state changed to Approved-announcement to be sent from IESG Evaluation
2017-03-02
05 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko
2017-03-01
05 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2017-03-01
05 Suresh Krishnan [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan
2017-03-01
05 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2017-03-01
05 Ben Campbell [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell
2017-03-01
05 Kathleen Moriarty [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty
2017-03-01
05 Stephen Farrell [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell
2017-02-28
05 Terry Manderson [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson
2017-02-28
05 Deborah Brungard [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard
2017-02-28
05 Mirja Kühlewind [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind
2017-02-28
05 Alissa Cooper [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper
2017-02-27
05 Spencer Dawkins [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins
2017-02-27
05 Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2017-02-23
05 Stewart Bryant Request for Last Call review by GENART Completed: Ready. Reviewer: Stewart Bryant. Sent review to list.
2017-02-23
05 Tero Kivinen Request for Last Call review by SECDIR Completed: Ready. Reviewer: Dacheng Zhang.
2017-02-21
05 Jouni Korhonen Request for Last Call review by OPSDIR Partially Completed: Ready. Reviewer: Jouni Korhonen. Sent review to list.
2017-02-20
05 Cindy Morgan New revision available
2017-02-20
05 Alexey Melnikov IESG state changed to IESG Evaluation from Waiting for Writeup
2017-02-20
04 Alexey Melnikov Ballot has been issued
2017-02-20
04 Alexey Melnikov [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov
2017-02-20
04 Alexey Melnikov Created "Approve" ballot
2017-02-20
04 Alexey Melnikov Ballot writeup was changed
2017-02-20
04 (System) IESG state changed to Waiting for Writeup from In Last Call
2017-02-16
04 (System) IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed
2017-02-16
04 Sabrina Tanamal
(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 …
(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
2017-02-10
04 Jean Mahoney Request for Last Call review by GENART is assigned to Stewart Bryant
2017-02-10
04 Jean Mahoney Request for Last Call review by GENART is assigned to Stewart Bryant
2017-02-09
04 Tero Kivinen Request for Last Call review by SECDIR is assigned to Dacheng Zhang
2017-02-09
04 Tero Kivinen Request for Last Call review by SECDIR is assigned to Dacheng Zhang
2017-02-07
04 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Jouni Korhonen
2017-02-07
04 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Jouni Korhonen
2017-02-06
04 Amy Vezza IANA Review state changed to IANA - Review Needed
2017-02-06
04 Amy Vezza
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 …
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.




2017-02-06
04 Amy Vezza IESG state changed to In Last Call from Last Call Requested
2017-02-06
04 Amy Vezza Last call announcement was changed
2017-02-04
04 Alexey Melnikov Placed on agenda for telechat - 2017-03-02
2017-02-04
04 Alexey Melnikov Last call was requested
2017-02-04
04 Alexey Melnikov Last call announcement was generated
2017-02-04
04 Alexey Melnikov Ballot approval text was generated
2017-02-04
04 Alexey Melnikov Ballot writeup was generated
2017-02-04
04 Alexey Melnikov IESG state changed to Last Call Requested from AD Evaluation
2017-02-04
04 Alexey Melnikov IESG state changed to AD Evaluation from Publication Requested
2017-02-01
04 Mark Nottingham
# Shepherd Writeup for RFC5987bis

## 1. Summary

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

By default, header field values …
# 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.
2017-01-31
04 Mark Nottingham
# Shepherd Writeup for RFC5987bis

## 1. Summary

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

By default, header field values …
# 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.
2017-01-31
04 Mark Nottingham Responsible AD changed to Alexey Melnikov
2017-01-31
04 Mark Nottingham IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2017-01-31
04 Mark Nottingham IESG state changed to Publication Requested
2017-01-31
04 Mark Nottingham IESG process started in state Publication Requested
2017-01-31
04 Mark Nottingham Notification list changed to mnot@mnot.net
2017-01-31
04 Mark Nottingham Changed document writeup
2017-01-31
04 Patrick McManus Changed consensus to Yes from Unknown
2017-01-31
04 Patrick McManus Change intended status to proposed standard based on wg consensus from
https://lists.w3.org/Archives/Public/ietf-http-wg/2017JanMar/0025.html
and
https://github.com/httpwg/http-extensions/issues/271
2017-01-31
04 Patrick McManus Intended Status changed to Proposed Standard from Internet Standard
2016-11-20
04 Cindy Morgan New revision available
2016-11-20
04 Mark Nottingham IETF WG state changed to WG Consensus: Waiting for Write-Up from WG Document
2016-11-13
03 Patrick McManus Added to session: IETF-97: httpbis  Tue-1330
2016-07-08
03 Cindy Morgan New revision available
2016-07-08
02 Cindy Morgan New revision available
2016-03-04
01 Cindy Morgan New revision available
2015-10-14
00 (System) Notify list changed from "Mark Nottingham"  to (None)
2015-10-02
00 Mark Nottingham Notification list changed to "Mark Nottingham" <mnot@pobox.com>
2015-10-02
00 Mark Nottingham Document shepherd changed to Mark Nottingham
2015-10-02
00 Mark Nottingham Intended Status changed to Internet Standard from None
2015-10-02
00 Mark Nottingham This document now replaces draft-reschke-rfc5987bis instead of None
2015-10-02
00 Julian Reschke New version available: draft-ietf-httpbis-rfc5987bis-00.txt