= HTTPbis WG = This is the wiki home of the IETF HTTPbis Working Group. We're [http://www.ietf.org/html.charters/httpbis-charter.html chartered] to revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security. Additionally, we're starting to look at proposals for a protocol that could become HTTP/2.0, along with evaluating proposals for new authentication schemes. [[PageOutline(2,,inline)]] == HTTP/1.1 Deliverables == The HTTP/1.1 specification has been split up into several drafts for readability and modularity; see the [http://tools.ietf.org/wg/httpbis/ Drafts] directory for a current snapshot of all HTTP-related drafts. * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging/ p1: Messaging] - low-level message parsing and connection management ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p1-messaging.html work-in-progress in HTML format]) * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics p2: Semantics] - methods, status codes and headers ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p2-semantics.html work-in-progress in HTML format]) * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional p4: Conditional Requests] - e.g., If-Modified-Since ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p4-conditional.html work-in-progress in HTML format]) * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p5-range p5: Range Requests] - getting partial content ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p5-range.html work-in-progress in HTML format]) * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache p6: Caching] - browser and intermediary caches ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p6-cache.html work-in-progress in HTML format]) * WGLC: [http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth p7: Authentication] - HTTP authentication framework ([https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p7-auth.html work-in-progress in HTML format]) ''WGLC indicates a document in Working Group Last Call. p3 was folded into p2.'' Additionally, we're publishing: * [http://tools.ietf.org/html/draft-ietf-httpbis-security-properties/ Security Properties] - an explanation of the security properties of HTTP * [http://tools.ietf.org/html/draft-ietf-httpbis-method-registrations/ Method Registrations] - a document establishing the HTTP method registry's initial contents * [http://tools.ietf.org/html/draft-ietf-httpbis-authscheme-registrations/ Authentication Scheme Registrations] - a document establishing the HTTP authentication scheme registry's initial contents Past work includes: * [http://tools.ietf.org/html/rfc6266 RFC6266] - Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol ([http://greenbytes.de/tech/tc2231/ test cases]) Related material includes: * [http://trac.tools.ietf.org/wg/httpbis/trac/browser Subversion repository] * [http://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/diffs/ Document changes], also in [http://trac.tools.ietf.org/wg/httpbis/trac/timeline?ticket=on&changeset=on&milestone=on&max=50&daysback=90&format=rss RSS] and on [http://twitter.com/httpbis Twitter] Currently, the group doesn't officially work on new HTTP features, as that's outside the scope of [http://www.ietf.org/html.charters/httpbis-charter.html our charter]. However, they are often discussed informally on our list, because there are a large number of interested HTTP implementers, and because we may take on new work with a recharter in the future. We track these as PotentialWork. == HTTP/2.0 Deliverables == We're also chartered to work on a replacement for how HTTP is expressed "on the wire." This effort is known as "HTTP/2.0", although it is ''not'' a ground-up rewrite of the protocol. The basis of the work is [http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00 SPDY]. However, we will be collecting issues against this document, as well as confirming consensus over individual portions. == Issue Handling == Issues with the specifications are kept in our [http://trac.tools.ietf.org/wg/httpbis/trac/report ticket tracker]. We have two basic types of issues; Design ([http://trac.tools.ietf.org/wg/httpbis/trac/report/9 open issues]) and Editorial ([http://trac.tools.ietf.org/wg/httpbis/trac/report/10 open issues]). Design issues need to be discussed by the Working Group to reach consensus. This generally happens on the mailing list when the issue is raised, but the editors sometimes incorporate a proposed resolution to a design issue in a draft, so that the WG can see it in-situ. Such tickets aren't fully closed until the group confirms the proposal after it is published; you can see [http://trac.tools.ietf.org/wg/httpbis/trac/report/15 a list of such tickets here]. Editorial issues can be resolved by the editors without consultation with the group, although sometimes an editor will poll the group for advice. New issues can be raised by sending e-mail to the list (see below). It helps to call attention to them in the Subject line (e.g., "NEW ISSUE: ..."). Finally, for those documents in Working Group Last Call, we have a summary of [http://trac.tools.ietf.org/wg/httpbis/trac/report/20 WGLC issues]. [[TicketStats( height=250,daterange=36m,res_days=30)]] == Participate == As with all IETF Working Groups, almost all discussion and decisions are made on our [http://lists.w3.org/Archives/Public/ietf-http-wg/ mailing list]. Joining this list is "joining" the Working Group, and is the best way to participate. We meet at least twice a year at [http://www.ietf.org/meeting/ IETF meetings]; see also [http://trac.tools.ietf.org/wg/httpbis/trac/browser/wg_materials materials from past meetings]. During our official meetings, we use an XMPP (Jabber) channel at xmpp://httpbis@jabber.ietf.org?join ([http://jabber.ietf.org/logs/httpbis/ archives]) provided by the IETF. ALL contributors and participants in the Working Group (i.e., on the mailing list and in physical meetings) MUST read and understand the [http://www.ietf.org/NOTEWELL.html NOTE WELL] statement. == People == Many people have contributed to HTTP's development over the years, and likewise there are many people participating in HTTPbis. The people holding official positions in this effort are: * [http://www.mnot.net/ Mark Nottingham] - Working Group Chair, editor for p6 Caching * [http://www.julian-reschke.de/ Julian Reschke] - Editor, p1-p7, Method Registrations, Content-Disposition, Authentication Scheme Registrations * [http://roy.gbiv.com/ Roy Fielding] - Editor, p1-p7 * [http://www.w3.org/People/Lafon/ Yves Lafon] - Editor, p5 * [http://www.kingsmountain.com/people/Jeff.Hodges/ Jeff Hodges] - Editor, Security Properties * [http://internetmessagingtechnology.org/ Barry Leiba] - our current Area Director, who oversees the WG for the [http://www.iesg.org/ IESG] {{{ #!html }}}