IETF 87 - HTTPbis -23 Changes Overview

Julian Reschke, greenbytes

History

• -19: published March 2012 (before IETF 83)
• -20: published July 2012 (before IETF 84)
• -21: published October 2012 (before IETF 85)
• -22: published February 2013 (before IETF 86)
• -23: published July 2013 (before IETF 87)

First Working Group Last Call for Parts 4, 5, 6, and 7 ended April 12, 2012

First Working Group Last Call for Parts 1 & 2 ended November 25, 2012

Second Working Group Last Call for Parts 4, 5, 6, and 7 ended November 25, 2012

Another Working Group Last Call for all parts ended April 30, 2013

Design Changes

• BWS (Ticket 442) -- trailing WS in field values is "obsolete", not "bad"
• Ordering in Upgrade (Ticket 445) -- made significant
• Returning the freshest response (Ticket 453) -- Allow selecting headers to be smart about selecting a negotiated representation
• Registering x-gzip and x-deflate (Ticket 457)
• Via and gateways (Ticket 460) -- they do not need to add "Via"
• Vary and future requests (Ticket 471)

Editorial Changes

• Part1 should have a reference to TCP (RFC 793) (Ticket 435)
• explain list expansion in ABNF appendices (Ticket 436)
• incorrect example dates (Ticket 437)
• media type registration template issues (Ticket 438)
• terminology: mechanism vs framework vs scheme (Ticket 439)
• P1 editorial nits (Ticket 441)
• obs-fold language (Ticket 444)
• p1 editorial feedback (Ticket 446)
• HTTP and TCP name delegation (Ticket 447)
• Fallback for Accept-Language (Ticket 448)
• Receiving a higher minor HTTP version number (Ticket 449)
• HTTP(S) URIs and fragids (Ticket 451)
• Language-tag vs. language-range (Ticket 456)
• RFC2774 and method registrations (Ticket 459)
• Editorial suggestions (Ticket 462)
• Editorial suggestions (Ticket 463)
• placement of extension point considerations (Ticket 464)
• Mention 203 Non-Authoritative Information in p1 (Ticket 465)
• SHOULD and conformance (Ticket 476)
• Pipelining language (Ticket 477)
• proxy handling of a really bad Content-Length (Ticket 482)
• MUSTs and other feedback (Ticket 485)
• Selection based upon request target (Ticket 488)

Next Steps

Four more tickets closed: Milestone 24.

21 open tickets left, many of which editorial.

Resolve as many as possible soon, then IETF LC?