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.
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.
The author has confirmed that to their direct, personal knowlege, all IPR related to this document has already been disclosed.
Note that this draft has non-ASCII content in it, and therefore needs to be published using the new, Unicode-enabled process.