source: draft-ietf-httpbis/latest/p0-introduction.xml @ 1781

Last change on this file since 1781 was 1776, checked in by julian.reschke@…, 7 years ago

spelling fixes

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 17.6 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY P0-ID-VERSION "latest">
15  <!ENTITY ID-VERSION "latest">
16  <!ENTITY ID-MONTH "July">
17  <!ENTITY ID-YEAR "2012">
18  <!ENTITY mdash "&#8212;">
19  <!ENTITY status-codes "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY header-cache-control "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21]>
22<?rfc toc="yes" ?>
23<?rfc symrefs="yes" ?>
24<?rfc sortrefs="yes" ?>
25<?rfc compact="yes"?>
26<?rfc subcompact="no" ?>
27<?rfc linkmailto="no" ?>
28<?rfc editing="no" ?>
29<?rfc comments="yes"?>
30<?rfc inline="yes"?>
31<?rfc rfcedstyle="yes"?>
32<?rfc-ext allow-markup-in-artwork="yes" ?>
33<?rfc-ext include-references-in-index="yes" ?>
34<rfc category="std" x:maturity-level="proposed"
35     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p0-introduction-&P0-ID-VERSION;"
36     xmlns:x='http://purl.org/net/xml2rfc/ext'>
37<x:link rel="next" basename="p1-messaging"/>
38<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
39<front>
40
41  <title abbrev="HTTP/1.1, Part 0">HTTP/1.1, part 0: Introduction</title>
42
43  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
44    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
45    <address>
46      <postal>
47        <street>345 Park Ave</street>
48        <city>San Jose</city>
49        <region>CA</region>
50        <code>95110</code>
51        <country>USA</country>
52      </postal>
53      <email>fielding@gbiv.com</email>
54      <uri>http://roy.gbiv.com/</uri>
55    </address>
56  </author>
57
58  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
59    <organization abbrev="W3C">World Wide Web Consortium</organization>
60    <address>
61      <postal>
62        <street>W3C / ERCIM</street>
63        <street>2004, rte des Lucioles</street>
64        <city>Sophia-Antipolis</city>
65        <region>AM</region>
66        <code>06902</code>
67        <country>France</country>
68      </postal>
69      <email>ylafon@w3.org</email>
70      <uri>http://www.raubacapeu.net/people/yves/</uri>
71    </address>
72  </author>
73
74  <author fullname="Mark Nottingham" initials="M." role="editor" surname="Nottingham">
75    <organization>Rackspace</organization>
76    <address>
77      <email>mnot@mnot.net</email>
78      <uri>http://www.mnot.net/</uri>
79    </address>
80  </author>
81
82  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
83    <organization abbrev="greenbytes">greenbytes GmbH</organization>
84    <address>
85      <postal>
86        <street>Hafenweg 16</street>
87        <city>Muenster</city><region>NW</region><code>48155</code>
88        <country>Germany</country>
89      </postal>
90      <email>julian.reschke@greenbytes.de</email>
91      <uri>http://greenbytes.de/tech/webdav/</uri>
92    </address>
93  </author>
94
95  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
96  <workgroup>HTTPbis Working Group</workgroup>
97
98<abstract>
99<t>
100   This document is the first in a series that, collectively, define the
101   HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.
102</t>
103</abstract>
104
105<note title="Editorial Note (To be removed by RFC Editor)">
106  <t>
107    Discussion of this draft takes place on the HTTPBIS working group
108    mailing list (ietf-http-wg@w3.org), which is archived at
109    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
110  </t>
111  <t>
112    The current issues list is at
113    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
114    documents (including fancy diffs) can be found at
115    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
116  </t>
117<!--  <t>
118    The changes in this draft are summarized in <xref target="changes.since.19"/>.
119  </t>-->
120</note>
121</front>
122<middle>
123
124<section title="Introduction to the HTTP Document Series">
125<t>
126   This document is the first in a series that, collectively, define
127   the HyperText Transfer Protocol, version 1.1; otherwise known as
128   HTTP/1.1.
129</t>
130<t>The document series is organized as follows:</t>
131<t><list style="symbols">
132   <t>HTTP/1.1 Introduction - this document</t>
133   <t><xref target="Part1"/> HTTP/1.1 Message Parsing, Connection Handling and
134   URIs - How to parse a HTTP/1.1 (or below) message, and layer it onto
135   connection-oriented protocols. Also includes the HTTP and HTTPS URI
136   schemes.</t>
137   <t><xref target="Part2"/> HTTP/1.1 Core Semantics - Protocol elements such
138   as methods, status codes, and payload-specific header fields. Also includes
139   content negotiation mechanisms.</t>
140   <t><xref target="Part4"/> HTTP/1.1 Conditional Requests - An extension to
141   make requests contingent upon their current state.</t>
142   <t><xref target="Part5"/> HTTP/1.1 Range Requests - An extension to
143   request that only a portion of a response be sent back.</t>
144   <t><xref target="Part6"/> HTTP/1.1 Caching - An extension to allow storage
145   and reuse of responses.</t>
146   <t><xref target="Part7"/> HTTP/1.1 Authentication Framework - extension
147   enabling client authentication to proxy and origin servers</t>
148</list></t>
149
150<t>The "core" of HTTP/1.1 is defined by the first two specifications. The
151remaining specifications in the series are generally not mandatory for
152implementations, but might be required in some implementation or deployment
153scenarios; when this is the case, it will be noted.</t>
154
155<t>Collectively, these documents obsolete <xref target="RFC2616"/>. Note that
156many other specifications extend and refine the use of HTTP (generally, as
157protocol extensions, where allowed by these specifications); they are not
158considered part of this series, but they are still "part of HTTP".</t>
159
160</section>
161
162<section title="What is HTTP?" anchor="wat">
163<t>
164   The Hypertext Transfer Protocol (HTTP) is an application-level
165   request/response protocol that uses extensible semantics and MIME-like
166   message payloads for flexible interaction with network-based hypertext
167   information systems. HTTP relies upon the Uniform Resource Identifier (URI)
168   standard <xref target="RFC3986"/> to indicate the target resource
169   and relationships between resources.
170</t>
171<t>
172   HTTP is a generic interface protocol for information systems. It is
173   designed to hide the details of how a service is implemented by presenting
174   a uniform interface to clients that is independent of the types of
175   resources provided. Likewise, servers do not need to be aware of each
176   client's purpose: an HTTP request can be considered in isolation rather
177   than being associated with a specific type of client or a predetermined
178   sequence of application steps. The result is a protocol that can be used
179   effectively in many different contexts and for which implementations can
180   evolve independently over time.
181</t>
182<t>
183   HTTP is also designed for use as an intermediation protocol for translating
184   communication to and from non-HTTP information systems.
185   HTTP proxies and gateways can provide access to alternative information
186   services by translating their diverse protocols into a hypertext
187   format that can be viewed and manipulated by clients in the same way
188   as HTTP services.
189</t>
190<t>
191   One consequence of HTTP flexibility is that the protocol cannot be
192   defined in terms of what occurs behind the interface. Instead, we
193   are limited to defining the syntax of communication, the intent
194   of received communication, and the expected behavior of recipients.
195   If the communication is considered in isolation, then successful
196   actions ought to be reflected in corresponding changes to the
197   observable interface provided by servers. However, since multiple
198   clients might act in parallel and perhaps at cross-purposes, we
199   cannot require that such changes be observable beyond the scope
200   of a single response.
201</t>
202<t>
203  <cref>TODO: remove corresponding text from p1 Introduction.</cref>
204</t>
205</section>
206
207
208
209
210</middle>
211<back>
212<references title="Normative References">
213
214<reference anchor="Part1">
215  <front>
216    <title>HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
217    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
218      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
219      <address><email>fielding@gbiv.com</email></address>
220    </author>
221    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
222      <organization abbrev="W3C">World Wide Web Consortium</organization>
223      <address><email>ylafon@w3.org</email></address>
224    </author>
225    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
226      <organization abbrev="greenbytes">greenbytes GmbH</organization>
227      <address><email>julian.reschke@greenbytes.de</email></address>
228    </author>
229    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
230  </front>
231  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
232  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
233</reference>
234
235<reference anchor="Part2">
236  <front>
237    <title>HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation</title>
238    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
239      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
240      <address><email>fielding@gbiv.com</email></address>
241    </author>
242    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
243      <organization abbrev="W3C">World Wide Web Consortium</organization>
244      <address><email>ylafon@w3.org</email></address>
245    </author>
246    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
247      <organization abbrev="greenbytes">greenbytes GmbH</organization>
248      <address><email>julian.reschke@greenbytes.de</email></address>
249    </author>
250    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
251  </front>
252  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
253  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
254</reference>
255
256<reference anchor="Part4">
257  <front>
258    <title>HTTP/1.1, part 4: Conditional Requests</title>
259    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
260      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
261      <address><email>fielding@gbiv.com</email></address>
262    </author>
263    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
264      <organization abbrev="W3C">World Wide Web Consortium</organization>
265      <address><email>ylafon@w3.org</email></address>
266    </author>
267    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
268      <organization abbrev="greenbytes">greenbytes GmbH</organization>
269      <address><email>julian.reschke@greenbytes.de</email></address>
270    </author>
271    <date month="&ID-MONTH;" year="&ID-YEAR;" />
272  </front>
273  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
274  <x:source basename="p4-conditional" href="p4-conditional.xml" />
275</reference>
276
277<reference anchor="Part5">
278  <front>
279    <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title>
280    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
281      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
282      <address><email>fielding@gbiv.com</email></address>
283    </author>
284    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
285      <organization abbrev="W3C">World Wide Web Consortium</organization>
286      <address><email>ylafon@w3.org</email></address>
287    </author>
288    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
289      <organization abbrev="greenbytes">greenbytes GmbH</organization>
290      <address><email>julian.reschke@greenbytes.de</email></address>
291    </author>
292    <date month="&ID-MONTH;" year="&ID-YEAR;" />
293  </front>
294  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
295  <x:source basename="p5-range" href="p5-range.xml" />
296</reference>
297
298<reference anchor="Part6">
299  <front>
300    <title>HTTP/1.1, part 6: Caching</title>
301    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
302      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
303      <address><email>fielding@gbiv.com</email></address>
304    </author>
305    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
306      <organization abbrev="W3C">World Wide Web Consortium</organization>
307      <address><email>ylafon@w3.org</email></address>
308    </author>
309    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
310      <organization>Rackspace</organization>
311      <address><email>mnot@mnot.net</email></address>
312    </author>
313    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
314      <organization abbrev="greenbytes">greenbytes GmbH</organization>
315      <address><email>julian.reschke@greenbytes.de</email></address>
316    </author>
317    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
318  </front>
319  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
320  <x:source href="p6-cache.xml" basename="p6-cache"/>
321</reference>
322
323<reference anchor="Part7">
324  <front>
325    <title>HTTP/1.1, part 7: Authentication</title>
326    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
327      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
328      <address><email>fielding@gbiv.com</email></address>
329    </author>
330    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
331      <organization abbrev="W3C">World Wide Web Consortium</organization>
332      <address><email>ylafon@w3.org</email></address>
333    </author>
334    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
335      <organization abbrev="greenbytes">greenbytes GmbH</organization>
336      <address><email>julian.reschke@greenbytes.de</email></address>
337    </author>
338    <date month="&ID-MONTH;" year="&ID-YEAR;" />
339  </front>
340  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
341  <x:source basename="p7-auth" href="p7-auth.xml" />
342</reference>
343
344<reference anchor="RFC3986">
345 <front>
346  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
347  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
348    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
349    <address>
350       <email>timbl@w3.org</email>
351       <uri>http://www.w3.org/People/Berners-Lee/</uri>
352    </address>
353  </author>
354  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
355    <organization abbrev="Day Software">Day Software</organization>
356    <address>
357      <email>fielding@gbiv.com</email>
358      <uri>http://roy.gbiv.com/</uri>
359    </address>
360  </author>
361  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
362    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
363    <address>
364      <email>LMM@acm.org</email>
365      <uri>http://larry.masinter.net/</uri>
366    </address>
367  </author>
368  <date month='January' year='2005'></date>
369 </front>
370 <seriesInfo name="STD" value="66"/>
371 <seriesInfo name="RFC" value="3986"/>
372</reference>
373
374</references>
375
376<references title="Informative References">
377
378<reference anchor="RFC2616">
379  <front>
380    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
381    <author initials="R." surname="Fielding" fullname="R. Fielding">
382      <organization>University of California, Irvine</organization>
383      <address><email>fielding@ics.uci.edu</email></address>
384    </author>
385    <author initials="J." surname="Gettys" fullname="J. Gettys">
386      <organization>W3C</organization>
387      <address><email>jg@w3.org</email></address>
388    </author>
389    <author initials="J." surname="Mogul" fullname="J. Mogul">
390      <organization>Compaq Computer Corporation</organization>
391      <address><email>mogul@wrl.dec.com</email></address>
392    </author>
393    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
394      <organization>MIT Laboratory for Computer Science</organization>
395      <address><email>frystyk@w3.org</email></address>
396    </author>
397    <author initials="L." surname="Masinter" fullname="L. Masinter">
398      <organization>Xerox Corporation</organization>
399      <address><email>masinter@parc.xerox.com</email></address>
400    </author>
401    <author initials="P." surname="Leach" fullname="P. Leach">
402      <organization>Microsoft Corporation</organization>
403      <address><email>paulle@microsoft.com</email></address>
404    </author>
405    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
406      <organization>W3C</organization>
407      <address><email>timbl@w3.org</email></address>
408    </author>
409    <date month="June" year="1999"/>
410  </front>
411  <seriesInfo name="RFC" value="2616"/>
412</reference>
413
414
415</references>
416</back>
417</rfc>
Note: See TracBrowser for help on using the repository browser.