IETF 90 - Progressing Specs
Julian Reschke, greenbytes
RFC 7230..5: HTTP/1.1 base specs
Status:
- Published in June 2014 as Proposed Standard - due to the large amount of editorial changes from RFC 2616.
- Of the six specs, HTTP/2 only replaces parts of one of these (wire format).
Goals:
- Improve separation of wire format and all the other parts. Where needed, better accomodate HTTP/2.
- Cherry-pick stuff from other specs that really should have been part of the base spec
(requires maturity level of "Proposed Standard"). (slippery slope - we have IANA registries for a reason...)
RFC 7230..5: HTTP/1.1 base specs (continued)
Plan:
- Proposed Standard → Internet Standard.
- Establish a venue where we can do more than just collecting errata. → issue tracker, WG discussions leading
to proposed and agreed upon resolutions.
- Start work on revised drafts after publication of HTTP/2.
RFC 7238: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
Status:
-
Approved early 2012, but published last month due to httpbis dependencies.
-
Implemented in many tools, plus Firefox, Safari, Chrome 36.
Plan:
RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
aka *param=UTF-8''....
Status:
-
Supported for "Content-Disposition" header field in all browsers (where IE only supports UTF-8 where the spec also requires ISO-8859-1).
-
Supported for "Link" in Firefox.
Plan:
RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Status:
-
Supported in all browsers.
Plan:
-
Proposed Standard → Internet Standard.
-
Only tiny edits required.
-
...after RFC 5987bis is done.
-
Was a Working Group work item. Revise as Working Group work item?