IETF 80 - RFC5987bis

Julian Reschke, greenbytes

History

• RFC 2231 defined I18N for header field parameters in MIME messages, was partly supported in HTTP consumers for filename parameters in Content-Disposition header fields.
• RFC 5987, published in August 2010, profiles RFC 2231 for use in HTTP messages.
• Used in RFC 5988 (Web Linking) and draft-ietf-httpbis-content-disp ("Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)", in the hands of the IESGapproved Monday, 2011-03-28).
• Currently a Proposed Standard.
• Since publication of RFC 5987, Internet Explorer and Chrome added support. Firefox, Konqueror, and Opera had it long before. Safari does not implement it.

Proposed Next Steps

• Create implementation report, based on a subset of the Content-Disposition tests at http://greenbytes.de/tech/tc2231/.
• Potentially further profile it (Microsoft's IE team didn't want to support ISO-8859-1, only UTF-8).
• Submit revision for publication as Draft Standard.
• Reference from HTTPbis' "Considerations for new header fields"?
• WG work item? (RFC 5987 was not).