source: draft-ietf-httpbis/21/p0-introduction.html @ 2726

Last change on this file since 2726 was 2726, checked in by julian.reschke@…, 9 years ago

update to latest version of rfc2629.xslt, regen all HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 28.0 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>Hypertext Transfer Protocol (HTTP/1.1): Introduction</title><script>
7var buttonsAdded = false;
8
9function initFeedback() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60
61    // docname
62    var docname = "draft-ietf-httpbis-p0-introduction-latest";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: cambria, helvetica, arial, sans-serif;
109  font-size: 11pt;
110  margin-right: 2em;
111}
112cite {
113  font-style: normal;
114}
115dl {
116  margin-left: 2em;
117}
118ul.empty {
119  list-style-type: none;
120}
121ul.empty li {
122  margin-top: .5em;
123}
124dl p {
125  margin-left: 0em;
126}
127dt {
128  margin-top: .5em;
129}
130h1 {
131  font-size: 130%;
132  line-height: 21pt;
133  page-break-after: avoid;
134}
135h1.np {
136  page-break-before: always;
137}
138h2 {
139  font-size: 120%;
140  line-height: 15pt;
141  page-break-after: avoid;
142}
143h3 {
144  font-size: 110%;
145  page-break-after: avoid;
146}
147h4, h5, h6 {
148  page-break-after: avoid;
149}
150h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
151  color: black;
152}
153img {
154  margin-left: 3em;
155}
156li {
157  margin-left: 2em;
158}
159ol {
160  margin-left: 2em;
161}
162ol.la {
163  list-style-type: lower-alpha;
164}
165ol.ua {
166  list-style-type: upper-alpha;
167}
168ol p {
169  margin-left: 0em;
170}
171p {
172  margin-left: 2em;
173}
174pre {
175  margin-left: 3em;
176  background-color: lightyellow;
177  padding: .25em;
178  page-break-inside: avoid;
179}
180pre.text2 {
181  border-style: dotted;
182  border-width: 1px;
183  background-color: #f0f0f0;
184  width: 69em;
185}
186pre.inline {
187  background-color: white;
188  padding: 0em;
189}
190pre.text {
191  border-style: dotted;
192  border-width: 1px;
193  background-color: #f8f8f8;
194  width: 69em;
195}
196pre.drawing {
197  border-style: solid;
198  border-width: 1px;
199  background-color: #f8f8f8;
200  padding: 2em;
201}
202table {
203  margin-left: 2em;
204}
205table.header {
206  border-spacing: 1px;
207  width: 95%;
208  font-size: 11pt;
209  color: white;
210}
211td.top {
212  vertical-align: top;
213}
214td.topnowrap {
215  vertical-align: top;
216  white-space: nowrap;
217}
218table.header td {
219  background-color: gray;
220  width: 50%;
221}
222td.reference {
223  vertical-align: top;
224  white-space: nowrap;
225  padding-right: 1em;
226}
227thead {
228  display:table-header-group;
229}
230ul.toc, ul.toc ul {
231  list-style: none;
232  margin-left: 1.5em;
233  padding-left: 0em;
234}
235ul.toc li {
236  line-height: 150%;
237  font-weight: bold;
238  margin-left: 0em;
239}
240ul.toc li li {
241  line-height: normal;
242  font-weight: normal;
243  font-size: 10pt;
244  margin-left: 0em;
245}
246li.excluded {
247  font-size: 0pt;
248}
249ul p {
250  margin-left: 0em;
251}
252.title, .filename, h1, h2, h3, h4 {
253  font-family: candara, helvetica, arial, sans-serif;
254}
255samp, tt, code, pre {
256  font: consolas, monospace;
257}
258ul.ind, ul.ind ul {
259  list-style: none;
260  margin-left: 1.5em;
261  padding-left: 0em;
262  page-break-before: avoid;
263}
264ul.ind li {
265  font-weight: bold;
266  line-height: 200%;
267  margin-left: 0em;
268}
269ul.ind li li {
270  font-weight: normal;
271  line-height: 150%;
272  margin-left: 0em;
273}
274.avoidbreak {
275  page-break-inside: avoid;
276}
277
278.comment {
279  background-color: yellow;
280}
281.center {
282  text-align: center;
283}
284.error {
285  color: red;
286  font-style: italic;
287  font-weight: bold;
288}
289.figure {
290  font-weight: bold;
291  text-align: center;
292  font-size: 10pt;
293}
294.filename {
295  color: #333333;
296  font-size: 75%;
297  font-weight: bold;
298  line-height: 21pt;
299  text-align: center;
300}
301.fn {
302  font-weight: bold;
303}
304.left {
305  text-align: left;
306}
307.right {
308  text-align: right;
309}
310.title {
311  color: green;
312  font-size: 150%;
313  line-height: 18pt;
314  font-weight: bold;
315  text-align: center;
316  margin-top: 36pt;
317}
318.warning {
319  font-size: 130%;
320  background-color: yellow;
321}
322.feedback {
323  position: fixed;
324  bottom: 1%;
325  right: 1%;
326  padding: 3px 5px;
327  color: white;
328  border-radius: 5px;
329  background: #a00000;
330  border: 1px solid silver;
331}
332.fbbutton {
333  margin-left: 1em;
334  color: #303030;
335  font-size: small;
336  font-weight: normal;
337  background: #d0d000;
338  padding: 1px 4px;
339  border: 1px solid silver;
340  border-radius: 5px;
341}
342
343@media print {
344  .noprint {
345    display: none;
346  }
347
348  a {
349    color: black;
350    text-decoration: none;
351  }
352
353  table.header {
354    width: 90%;
355  }
356
357  td.header {
358    width: 50%;
359    color: black;
360    background-color: white;
361    vertical-align: top;
362    font-size: 110%;
363  }
364
365  ul.toc a:nth-child(2)::after {
366    content: leader('.') target-counter(attr(href), page);
367  }
368
369  ul.ind li li a {
370    content: target-counter(attr(href), page);
371  }
372
373  .print2col {
374    column-count: 2;
375    -moz-column-count: 2;
376    column-fill: auto;
377  }
378}
379
380@page {
381  @top-left {
382       content: "Internet-Draft";
383  }
384  @top-right {
385       content: "October 2012";
386  }
387  @top-center {
388       content: "HTTP/1.1 Introduction";
389  }
390  @bottom-left {
391       content: "Fielding, et al.";
392  }
393  @bottom-center {
394       content: "Expires April 7, 2013";
395  }
396  @bottom-right {
397       content: "[Page " counter(page) "]";
398  }
399}
400
401@page:first {
402    @top-left {
403      content: normal;
404    }
405    @top-right {
406      content: normal;
407    }
408    @top-center {
409      content: normal;
410    }
411}
412</style><link rel="Contents" href="#rfc.toc">
413      <link rel="Author" href="#rfc.authors">
414      <link rel="Copyright" href="#rfc.copyrightnotice">
415      <link rel="Index" href="#rfc.index">
416      <link rel="Chapter" title="1 Introduction to the HTTP Document Series" href="#rfc.section.1">
417      <link rel="Chapter" title="2 What is HTTP?" href="#rfc.section.2">
418      <link rel="Chapter" href="#rfc.section.3" title="3 References">
419      <link href="p1-messaging.html" rel="next">
420      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
421      <link rel="schema.dct" href="http://purl.org/dc/terms/">
422      <meta name="dct.creator" content="Fielding, R.">
423      <meta name="dct.creator" content="Lafon, Y.">
424      <meta name="dct.creator" content="Nottingham, M.">
425      <meta name="dct.creator" content="Reschke, J. F.">
426      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
427      <meta name="dct.issued" scheme="ISO8601" content="2012-10-04">
428      <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
429      <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
430   </head>
431   <body onload="initFeedback();">
432      <table class="header">
433         <tbody>
434            <tr>
435               <td class="left">HTTPbis Working Group</td>
436               <td class="right">R. Fielding, Editor</td>
437            </tr>
438            <tr>
439               <td class="left">Internet-Draft</td>
440               <td class="right">Adobe</td>
441            </tr>
442            <tr>
443               <td class="left">Intended status: Standards Track</td>
444               <td class="right">Y. Lafon, Editor</td>
445            </tr>
446            <tr>
447               <td class="left">Expires: April 7, 2013</td>
448               <td class="right">W3C</td>
449            </tr>
450            <tr>
451               <td class="left"></td>
452               <td class="right">M. Nottingham, Editor</td>
453            </tr>
454            <tr>
455               <td class="left"></td>
456               <td class="right">Akamai</td>
457            </tr>
458            <tr>
459               <td class="left"></td>
460               <td class="right">J. Reschke, Editor</td>
461            </tr>
462            <tr>
463               <td class="left"></td>
464               <td class="right">greenbytes</td>
465            </tr>
466            <tr>
467               <td class="left"></td>
468               <td class="right">October 4, 2012</td>
469            </tr>
470         </tbody>
471      </table>
472      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Introduction<br><span class="filename">draft-ietf-httpbis-p0-introduction-latest</span></p>
473      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
474      <p>This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
475         known as HTTP/1.1.
476      </p>
477      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
478      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
479      </p>
480      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
481      </p>
482      <div id="rfc.status">
483         <h1><a href="#rfc.status">Status of This Memo</a></h1>
484         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
485         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
486            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
487         </p>
488         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
489            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
490            in progress”.
491         </p>
492         <p>This Internet-Draft will expire on April 7, 2013.</p>
493      </div>
494      <div id="rfc.copyrightnotice">
495         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
496         <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
497         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
498            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
499            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
500            BSD License.
501         </p>
502         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
503            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
504            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
505            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
506            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
507            it into languages other than English.
508         </p>
509      </div>
510      <hr class="noprint">
511      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
512      <ul class="toc">
513         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction to the HTTP Document Series</a></li>
514         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#wat">What is HTTP?</a></li>
515         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
516               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
517               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
518            </ul>
519         </li>
520         <li><a href="#rfc.index">Index</a></li>
521         <li><a href="#rfc.authors">Authors' Addresses</a></li>
522      </ul>
523      <div>
524         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction to the HTTP Document Series
525         </h1>
526         <p id="rfc.section.1.p.1">This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
527            known as HTTP/1.1.
528         </p>
529         <p id="rfc.section.1.p.2">The document series is organized as follows:</p>
530         <ul>
531            <li>HTTP/1.1 Introduction - this document</li>
532            <li><a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> HTTP/1.1 Message Routing and Syntax - How to parse a HTTP/1.1 (or below) message, and layer it onto connection-oriented protocols.
533               Also includes the HTTP and HTTPS URI schemes.
534            </li>
535            <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> HTTP/1.1 Semantics and Payloads - Protocol elements such as methods, status codes, and payload-specific header fields. Also
536               includes content negotiation mechanisms.
537            </li>
538            <li><a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> HTTP/1.1 Conditional Requests - An extension to make requests contingent upon their current state.
539            </li>
540            <li><a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a> HTTP/1.1 Range Requests - An extension to request that only a portion of a response be sent back.
541            </li>
542            <li><a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> HTTP/1.1 Caching - An extension to allow storage and reuse of responses.
543            </li>
544            <li><a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a> HTTP/1.1 Authentication Framework - extension enabling client authentication to proxy and origin servers
545            </li>
546         </ul>
547         <p id="rfc.section.1.p.4">The "core" of HTTP/1.1 is defined by the first two specifications. The remaining specifications in the series are generally
548            not mandatory for implementations, but might be required in some implementation or deployment scenarios; when this is the
549            case, it will be noted.
550         </p>
551         <p id="rfc.section.1.p.5">Collectively, these documents obsolete <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Note that many other specifications extend and refine the use of HTTP (generally, as protocol extensions, where allowed
552            by these specifications); they are not considered part of this series, but they are still "part of HTTP".
553         </p>
554      </div>
555      <div id="wat">
556         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#wat">What is HTTP?</a></h1>
557         <p id="rfc.section.2.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level request/response protocol that uses extensible semantics and
558            MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
559            Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource and relationships between resources.
560         </p>
561         <p id="rfc.section.2.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
562            by presenting a uniform interface to clients that is independent of the types of resources provided. Likewise, servers do
563            not need to be aware of each client's purpose: an HTTP request can be considered in isolation rather than being associated
564            with a specific type of client or a predetermined sequence of application steps. The result is a protocol that can be used
565            effectively in many different contexts and for which implementations can evolve independently over time.
566         </p>
567         <p id="rfc.section.2.p.3">HTTP is also designed for use as an intermediation protocol for translating communication to and from non-HTTP information
568            systems. HTTP proxies and gateways can provide access to alternative information services by translating their diverse protocols
569            into a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services.
570         </p>
571         <p id="rfc.section.2.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead,
572            we are limited to defining the syntax of communication, the intent of received communication, and the expected behavior of
573            recipients. If the communication is considered in isolation, then successful actions ought to be reflected in corresponding
574            changes to the observable interface provided by servers. However, since multiple clients might act in parallel and perhaps
575            at cross-purposes, we cannot require that such changes be observable beyond the scope of a single response.
576         </p>
577         <p id="rfc.section.2.p.5"><span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TODO: remove corresponding text from p1 Introduction.]</span>
578         </p>
579      </div>
580      <h1 id="rfc.references"><a id="rfc.section.3" href="#rfc.section.3">3.</a> References
581      </h1>
582      <h2 id="rfc.references.1"><a href="#rfc.section.3.1" id="rfc.section.3.1">3.1</a> Normative References
583      </h2>
584      <table>
585         <tr>
586            <td class="reference"><b id="Part1">[Part1]</b></td>
587            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), October&nbsp;2012.
588            </td>
589         </tr>
590         <tr>
591            <td class="reference"><b id="Part2">[Part2]</b></td>
592            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), October&nbsp;2012.
593            </td>
594         </tr>
595         <tr>
596            <td class="reference"><b id="Part4">[Part4]</b></td>
597            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), October&nbsp;2012.
598            </td>
599         </tr>
600         <tr>
601            <td class="reference"><b id="Part5">[Part5]</b></td>
602            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), October&nbsp;2012.
603            </td>
604         </tr>
605         <tr>
606            <td class="reference"><b id="Part6">[Part6]</b></td>
607            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), October&nbsp;2012.
608            </td>
609         </tr>
610         <tr>
611            <td class="reference"><b id="Part7">[Part7]</b></td>
612            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), October&nbsp;2012.
613            </td>
614         </tr>
615         <tr>
616            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
617            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
618            </td>
619         </tr>
620      </table>
621      <h2 id="rfc.references.2"><a href="#rfc.section.3.2" id="rfc.section.3.2">3.2</a> Informative References
622      </h2>
623      <table>
624         <tr>
625            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
626            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
627            </td>
628         </tr>
629      </table>
630      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
631      <p class="noprint"><a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
632      </p>
633      <div class="print2col">
634         <ul class="ind">
635            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
636                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#Part1"><b>3.1</b></a></li>
637                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#Part2"><b>3.1</b></a></li>
638                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1</a>, <a href="#Part4"><b>3.1</b></a></li>
639                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1</a>, <a href="#Part5"><b>3.1</b></a></li>
640                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#Part6"><b>3.1</b></a></li>
641                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">1</a>, <a href="#Part7"><b>3.1</b></a></li>
642               </ul>
643            </li>
644            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
645                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>3.2</b></a></li>
646                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2</a>, <a href="#RFC3986"><b>3.1</b></a></li>
647               </ul>
648            </li>
649         </ul>
650      </div>
651      <div class="avoidbreak">
652         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
653         <p><b>Roy T. Fielding</b>
654            (editor)
655            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
656         <p><b>Yves Lafon</b>
657            (editor)
658            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
659         <p><b>Mark Nottingham</b>
660            (editor)
661            <br>Akamai<br>Email: <a href="mailto:mnot@mnot.net">mnot@mnot.net</a><br>URI: <a href="http://www.mnot.net/">http://www.mnot.net/</a></p>
662         <p><b>Julian F. Reschke</b>
663            (editor)
664            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
665      </div>
666   </body>
667</html>
Note: See TracBrowser for help on using the repository browser.