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

Last change on this file since 1207 was 1207, checked in by julian.reschke@…, 8 years ago

add RFC5987bis slides

  • Property svn:executable set to *
File size: 2.6 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}
21.break {
22  page-break-before: always;
23}
24@page {
25  size: a4 landscape;
26}
27@page {
28  @bottom-left {
29       content: "Julian Reschke, greenbytes";
30  }
31  @bottom-right {
32       content: counter(page);
33  }
34  @top-center {
35       content: "IETF 80 - RFC5987bis";
36  }
37}
38    </style>
39  </head>
40  <body>
41    <h1>IETF 80 - RFC5987bis</h1>
42    <p>
43      <a href="mailto:julian.reschke@greenbytes.de">Julian Reschke</a>, greenbytes
44    </p>
45 
46    <h2 class="break">History</h2>
47    <ul>
48      <li>
49        RFC 2231 defined I18N for header field parameters in MIME messages,
50        was partly supported in HTTP consumers for filename parameters in
51        Content-Disposition header fields.
52      </li>
53      <li>
54        <a href="http://greenbytes.de/tech/webdav/rfc5987.html">RFC 5987</a>, published in August 2010, profiles RFC 2231 for use in HTTP
55        messages.
56      </li>
57      <li>
58        Used in <a href="http://greenbytes.de/tech/webdav/rfc5989.html">RFC 5988</a> (Web Linking) and
59        <a href="http://greenbytes.de/tech/webdav/draft-ietf-httpbis-content-disp-latest.html">draft-ietf-httpbis-content-disp</a>
60        ("Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)",
61        in the hands of the IESG).
62      </li>
63      <li>
64        Currently a Proposed Standard.
65      </li>
66      <li>
67        Since publication of RFC 5987, Internet Explorer and Chrome added
68        support. Firefox, Konqueror, and Opera had it long before.
69      </li>
70    </ul>
71
72    <h2 class="break">Proposed Next Steps</h2>
73    <ul>
74      <li>
75        Create implementation report, based on a subset of the Content-Disposition
76        tests at
77        <a href="http://greenbytes.de/tech/tc2231/">http://greenbytes.de/tech/tc2231/</a>.
78      </li>
79      <li>
80        Potentially further profile it (Microsoft's IE team didn't want to support ISO-8859-1,
81        only UTF-8).
82      </li>
83      <li>
84        Submit revision for publication as Draft Standard.
85      </li>
86      <li>
87        Reference from HTTPbis' "Considerations for new header fields"?
88      </li>
89      <li>
90        WG work item? (RFC 5987 was not).
91      </li>
92    </ul>
93
94  </body>
95</html>
Note: See TracBrowser for help on using the repository browser.