IETF 84 - HTTPbis -20 Changes Overview
Julian Reschke, greenbytes
History
- -16: published August 2011 (after IETF 81)
- -17: published November 2011 (before IETF 82, WG did not meet)
- -18: published January 2012
- -19: published March 2012 (before IETF 83)
- -20: published July 2012 (before IETF 84)
Working Group Last Call for Parts 4, 5, 6, and 7 ended April 12, 2012
Changes - General
Part 1
- make IANA policy definitions consistent (Ticket 346)
- clarify connection header field values are case-insensitive (Ticket 359)
- Reference to ISO-8859-1 is informative (Ticket 374)
Part 2
- should there be a permanent variant of 307 (Ticket 312)
- clarify that 201 can imply *multiple* resources were created (Ticket 347)
- Capturing more information in the method registry (Ticket 364) (...but what about LINK and UNLINK...?)
Part 4 - WGLC
- Need to clarify eval order/interaction of conditional headers (Ticket 241)
- Required headers on 304 and 206 (Ticket 345)
- Optionality of Conditional Request Support (Ticket 350)
- ETags and Conditional Requests (Ticket 354)
- Rare cases (Ticket 363)
- Conditional Request Security Considerations (Ticket 365)
- If-Modified-Since lacks definition for method != GET (Ticket 371)
- refactor conditional header field descriptions (Ticket 372)
Part 5 - WGLC
Part 6 - WGLC
- untangle Cache-Control ABNF (Ticket 307)
- Multiple values in Cache-Control header fields (Ticket 353)
- Case sensitivity of header fields in CC values (Ticket 355)
- Spurious "MAYs" (Ticket 356)
- enhance considerations for new cache control directives (Ticket 360)
- broken prose in description of "Vary" (Ticket 373)
- "Most Conservative" (Ticket 375) (in -21)
Part 7 - WGLC