source: wg_materials/ietf80/ietf-80-rfc5987bis.xhtml @ 1248

Last change on this file since 1248 was 1220, checked in by julian.reschke@…, 9 years ago

update approval status for C-D

  • Property svn:executable set to *
File size: 2.8 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4  <head>
5    <title>IETF 80 - RFC5987bis</title>
6    <style type="text/css">
7body {
8  color: black;
9  font-family: verdana, helvetica, arial, sans-serif;
10  font-size: 18pt;
11}
12h1 {
13  font-size: 36pt;
14}
15li {
16  margin-top: 0.5em;
17}
18q {
19  font-style: italic; 
20}
21del {
22  color: red;
23  text-decoration: line-through;
24}
25ins {
26  color: green;
27  text-decoration: underline;
28}
29.break {
30  page-break-before: always;
31}
32@page {
33  size: a4 landscape;
34}
35@page {
36  @bottom-left {
37       content: "Julian Reschke, greenbytes";
38  }
39  @bottom-right {
40       content: counter(page);
41  }
42  @top-center {
43       content: "IETF 80 - RFC5987bis";
44  }
45}
46    </style>
47  </head>
48  <body>
49    <h1>IETF 80 - RFC5987bis</h1>
50    <p>
51      <a href="mailto:julian.reschke@greenbytes.de">Julian Reschke</a>, greenbytes
52    </p>
53 
54    <h2 class="break">History</h2>
55    <ul>
56      <li>
57        RFC 2231 defined I18N for header field parameters in MIME messages,
58        was partly supported in HTTP consumers for filename parameters in
59        Content-Disposition header fields.
60      </li>
61      <li>
62        <a href="http://greenbytes.de/tech/webdav/rfc5987.html">RFC 5987</a>, published in August 2010, profiles RFC 2231 for use in HTTP
63        messages.
64      </li>
65      <li>
66        Used in <a href="http://greenbytes.de/tech/webdav/rfc5989.html">RFC 5988</a> (Web Linking) and
67        <a href="http://greenbytes.de/tech/webdav/draft-ietf-httpbis-content-disp-latest.html">draft-ietf-httpbis-content-disp</a>
68        ("Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)",
69        <del>in the hands of the IESG</del><ins>approved Monday, 2011-03-28</ins>).
70      </li>
71      <li>
72        Currently a Proposed Standard.
73      </li>
74      <li>
75        Since publication of RFC 5987, Internet Explorer and Chrome added
76        support. Firefox, Konqueror, and Opera had it long before. Safari
77        does not implement it.
78      </li>
79    </ul>
80
81    <h2 class="break">Proposed Next Steps</h2>
82    <ul>
83      <li>
84        Create implementation report, based on a subset of the Content-Disposition
85        tests at
86        <a href="http://greenbytes.de/tech/tc2231/">http://greenbytes.de/tech/tc2231/</a>.
87      </li>
88      <li>
89        Potentially further profile it (Microsoft's IE team didn't want to support ISO-8859-1,
90        only UTF-8).
91      </li>
92      <li>
93        Submit revision for publication as Draft Standard.
94      </li>
95      <li>
96        Reference from HTTPbis' "Considerations for new header fields"?
97      </li>
98      <li>
99        WG work item? (RFC 5987 was not).
100      </li>
101    </ul>
102
103  </body>
104</html>
Note: See TracBrowser for help on using the repository browser.