Changes between Version 103 and Version 104 of WikiStart


Ignore:
Timestamp:
01/08/14 07:58:55 (9 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v103 v104  
    22= HTTPbis WG =
    33
    4 This is the wiki home of the IETF HTTPbis Working Group. We're [http://www.ietf.org/html.charters/httpbis-charter.html chartered] to:
    5 
    6 * Revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security, and
    7 * Develop the next version of HTTP -- [http://http2.github.io/ HTTP/2].
    8 
    9 
    10 {{{
    11 #!html
    12 <div style="font-face: sans-serif; padding: 1em;  background-color: #fcc; colour: black">
    13 <strong>Looking for HTTP/2?</strong><br/>
    14 See the <a href="http://http2.github.io/">HTTP/2 Home Page</a>.<br/>
    15 </div>
    16 }}}
    17 
    18 == HTTP/1.1 Revision ==
    19 
    20 This Working Group was originally chartered to revise RFC2616, the specification of HTTP/1.1, folding in errata, implementation experience, and generally clarifying the specification. The result of that process was a a set of specifications, split up for readability as well as modularity:
    21 
    22  * RFC7230 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7230.html HTTP/1.1: Message Syntax and Routing] - low-level message parsing and connection management
    23  * RFC7231 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7231.html HTTP/1.1: Semantics and Content] - methods, status codes and headers
    24  * RFC7232 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7232.html HTTP/1.1: Conditional Requests] - e.g., If-Modified-Since
    25  * RFC7233 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html HTTP/1.1: Range Requests] - getting partial content
    26  * RFC7234 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7234.html HTTP/1.1: Caching] - browser and intermediary caches
    27  * RFC7235 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7235.html HTTP/1.1: Authentication] - HTTP authentication framework
    28  * RFC7236 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7236.html Initial HTTP Method Registrations] - a document establishing the HTTP method registry's initial contents
    29  * RFC7237 - [http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7237.html Initial HTTP Authentication Scheme Registrations] - a document establishing the HTTP authentication scheme registry's initial contents
    30  * RFC6266 - [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])
    31 
    32 See also:
    33  * [http://trac.tools.ietf.org/wg/httpbis/trac/browser Subversion repository for the HTTP/1.1 specs]
    34  * [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]
    35 
    36 
    37 
    38 == Other HTTP-Related Work ==
    39 
    40 We track other items for potential work (as allowed by our [http://www.ietf.org/html.charters/httpbis-charter.html our charter]) as PotentialWork.
    41 
    42 
    43 == Participate ==
    44 
    45 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.
    46 
    47 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].
    48 
    49 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.
    50 
    51 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.
    52 
    53 
    54 
    55 
    56 {{{
    57 #!html
    58 <script>
    59 jQuery(document).ready(function () {
    60   setTimeout(function() {
    61     jQuery(#narrow_menu).hide();
    62   }, 5000);
    63 });
    64 </script>
    65 }}}
     4See [http://httpwg.github.io/ the WG home page].