source: wg_materials/ietf90/ietf-90-httpbis-progressing.xhtml @ 2730

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

update status of rfc 5987
  • Property svn:executable set to *
File size: 4.5 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 90 - Progressing Specs</title>
6    <style type="text/css">
7body {
8  color: black;
9  font-family: cambria, helvetica, arial, sans-serif;
10  font-size: 18pt;
11}
12tt {
13  font-family: consolas;
14}
15h1 {
16  font-size: 36pt;
17}
18li {
19  margin-top: 0.5em;
20}
21q {
22  font-style: italic; 
23}
24.break {
25  page-break-before: always;
26}
27@page {
28  size: a4 landscape;
29}
30@page {
31  @bottom-left {
32       content: "Julian Reschke, greenbytes";
33  }
34  @bottom-right {
35       content: counter(page);
36  }
37  @top-center {
38       content: "IETF 90 - Progressing Specs";
39  }
40}
41    </style>
42  </head>
43  <body>
44    <h1>IETF 90 - Progressing Specs</h1>
45    <p>
46      <a href="mailto:julian.reschke@greenbytes.de">Julian Reschke</a>, greenbytes
47    </p>
48
49    <h2 class="break">RFC 7230..5: HTTP/1.1 base specs</h2>
50    <p>
51      Status:
52    </p>
53    <ul>
54      <li>Published in June 2014 as <em>Proposed Standard</em> - due to the large amount of editorial changes from RFC 2616.</li>
55      <li>Of the six specs, HTTP/2 only replaces parts of one of these (wire format).</li>
56    </ul>
57    <p>
58      Goals:
59    </p>
60    <ul>
61      <li>Improve separation of wire format and all the other parts. Where needed, better accomodate HTTP/2.</li>
62      <li>Cherry-pick stuff from other specs that really should have been part of the base spec
63      (requires maturity level of "Proposed Standard"). <em>(slippery slope - we have IANA registries for a reason...)</em></li>
64    </ul>
65    <h2 class="break">RFC 7230..5: HTTP/1.1 base specs (continued)</h2>
66    <p>
67      Plan:
68    </p>
69    <ul>
70      <li>Proposed Standard &#x2192; Internet Standard.</li>
71      <li>Establish a venue where we can do more than just collecting errata. &#x2192; issue tracker, WG discussions leading
72      to proposed and agreed upon resolutions.</li>
73      <li>Start work on revised drafts after publication of HTTP/2.</li>
74    </ul>
75
76
77    <h2 class="break">RFC 7238: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)</h2>
78    <p>
79      Status:
80    </p>
81    <ul>
82      <li>
83        Approved early 2012, but published last month due to httpbis dependencies.
84      </li>
85      <li>
86        Implemented in many tools, plus Firefox, Safari, Chrome 36 (currently beta).
87      </li>
88    </ul>
89    <p>
90      Plan:
91    </p>
92    <ul>
93      <li>
94        Experimental &#x2192; Proposed Standard.
95      </li>
96      <li>
97        No content changes needed; publish new RFC or reclassify?
98      </li>
99      <li>
100        Tests: <a href="http://greenbytes.de/tech/tc/httpredirects/#l-308">http://greenbytes.de/tech/tc/httpredirects/#l-308</a>
101      </li>
102    </ul>
103
104    <h2 class="break">RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</h2>
105    <p>
106      aka <tt>*param=UTF-8''....</tt>
107    </p>
108    <p>
109      Status:
110    </p>
111    <ul>
112      <li>
113        Supported for "Content-Disposition" header field in all browsers (where IE only supports UTF-8 where the spec also requires ISO-8859-1).
114      </li>
115      <li>
116        Supported for "Link" in Firefox.
117      </li>
118    </ul>
119    <p>
120      Plan:
121    </p>
122    <ul>
123      <li>
124        Proposed Standard &#x2192; Internet Standard.
125      </li>
126      <li>
127        Drop ISO-8859-1 requirement.
128      </li>
129      <li>
130        Rewrite to be consistent with RFC 723*.
131      </li>
132      <li>
133        <a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc5987bis-07.html">draft-reschke-rfc5987bis-07</a>,
134        Tests: <a href="http://greenbytes.de/tech/tc2231/">http://greenbytes.de/tech/tc2231/</a>
135      </li>
136      <li>
137        Was a private submission. Revise as Working Group work item?
138      </li>
139    </ul>
140 
141    <h2 class="break">RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</h2>
142    <p>
143      Status:
144    </p>
145    <ul>
146      <li>
147        Supported in all browsers.
148      </li>
149    </ul>
150    <p>
151      Plan:
152    </p>
153    <ul>
154      <li>
155        Proposed Standard &#x2192; Internet Standard.
156      </li>
157      <li>
158        Only tiny edits required.
159      </li>
160      <li>
161        ...after RFC 5987bis is done.
162      </li>
163      <li>
164        Was a Working Group work item. Revise as Working Group work item?
165      </li>
166    </ul>
167
168  </body>
169</html>
Note: See TracBrowser for help on using the repository browser.