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

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

fix SVN metadata and link metadata (see #326)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 17.6 KB
RevLine 
[1719]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 ought to take 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 organised 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 and Connection Handling
134   - How to parse a HTTP/1.1 (or below) message, and layer it onto
135   connection-oriented protocols.</t>
136   <t><xref target="Part2"/> HTTP/1.1 Core Semantics - Protocol elements such
137   as methods, status codes, and payload-specific headers. Also includes
138   content negotiation mechanisms.</t>
139   <t><xref target="Part4"/> HTTP/1.1 Conditional Requests - An extension to
140   make requests contingent upon their current state.</t>
141   <t><xref target="Part5"/> HTTP/1.1 Partial Content - An extension to
142   request that only a portion of a response be sent back.</t>
143   <t><xref target="Part6"/> HTTP/1.1 Caching - An extension to allow storage
144   and reuse of responses.</t>
145   <t><xref target="Part7"/> HTTP/1.1 Authentication Framework - extension
146   enabling client authentication to proxy and origin servers</t>
147</list></t>
148
149<t>The "core" of HTTP/1.1 is defined by the first two specifications. The
150remaining specifications in the series are generally optional, but may be
151required in some implementation or deployment scenarios; when this is the
152case, it will be noted.</t>
153
154<t>Collectively, these documents obsolete <xref target="RFC2616"/>. Note that
155many other specifications extend and refine the use of HTTP (generally, as
156protocol extensions, where allowed by these specifications); they are not
157considered part of this series, but they are still "part of HTTP".</t>
158
159</section>
160
161<section title="What is HTTP?" anchor="wat">
162<t>
163   The Hypertext Transfer Protocol (HTTP) is an application-level
164   request/response protocol that uses extensible semantics and MIME-like
165   message payloads for flexible interaction with network-based hypertext
166   information systems. HTTP relies upon the Uniform Resource Identifier (URI)
167   standard <xref target="RFC3986"/> to indicate the target resource
168   and relationships between resources.
169</t>
170<t>
171   HTTP is a generic interface protocol for information systems. It is
172   designed to hide the details of how a service is implemented by presenting
173   a uniform interface to clients that is independent of the types of
174   resources provided. Likewise, servers do not need to be aware of each
175   client's purpose: an HTTP request can be considered in isolation rather
176   than being associated with a specific type of client or a predetermined
177   sequence of application steps. The result is a protocol that can be used
178   effectively in many different contexts and for which implementations can
179   evolve independently over time.
180</t>
181<t>
182   HTTP is also designed for use as an intermediation protocol for translating
183   communication to and from non-HTTP information systems.
184   HTTP proxies and gateways can provide access to alternative information
185   services by translating their diverse protocols into a hypertext
186   format that can be viewed and manipulated by clients in the same way
187   as HTTP services.
188</t>
189<t>
190   One consequence of HTTP flexibility is that the protocol cannot be
191   defined in terms of what occurs behind the interface. Instead, we
192   are limited to defining the syntax of communication, the intent
193   of received communication, and the expected behavior of recipients.
194   If the communication is considered in isolation, then successful
195   actions ought to be reflected in corresponding changes to the
196   observable interface provided by servers. However, since multiple
197   clients might act in parallel and perhaps at cross-purposes, we
198   cannot require that such changes be observable beyond the scope
199   of a single response.
200</t>
201<t>
202  <cref>TODO: remove corresponding text from p1 Introduction.</cref>
203</t>
204</section>
205
206
207
208
209</middle>
210<back>
211<references title="Normative References">
212
213<reference anchor="Part1">
214  <front>
215    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
216    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
217      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
218      <address><email>fielding@gbiv.com</email></address>
219    </author>
220    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
221      <organization abbrev="W3C">World Wide Web Consortium</organization>
222      <address><email>ylafon@w3.org</email></address>
223    </author>
224    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
225      <organization abbrev="greenbytes">greenbytes GmbH</organization>
226      <address><email>julian.reschke@greenbytes.de</email></address>
227    </author>
228    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
229  </front>
230  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
231  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
232</reference>
233
234<reference anchor="Part2">
235  <front>
236    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
237    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
238      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
239      <address><email>fielding@gbiv.com</email></address>
240    </author>
241    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
242      <organization abbrev="W3C">World Wide Web Consortium</organization>
243      <address><email>ylafon@w3.org</email></address>
244    </author>
245    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
246      <organization abbrev="greenbytes">greenbytes GmbH</organization>
247      <address><email>julian.reschke@greenbytes.de</email></address>
248    </author>
249    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
250  </front>
251  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
252  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
253</reference>
254
255<reference anchor="Part4">
256  <front>
257    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
258    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
259      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
260      <address><email>fielding@gbiv.com</email></address>
261    </author>
262    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
263      <organization abbrev="W3C">World Wide Web Consortium</organization>
264      <address><email>ylafon@w3.org</email></address>
265    </author>
266    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
267      <organization abbrev="greenbytes">greenbytes GmbH</organization>
268      <address><email>julian.reschke@greenbytes.de</email></address>
269    </author>
270    <date month="&ID-MONTH;" year="&ID-YEAR;" />
271  </front>
272  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
273  <x:source basename="p4-conditional" href="p4-conditional.xml" />
274</reference>
275
276<reference anchor="Part5">
277  <front>
278    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
279    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
280      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
281      <address><email>fielding@gbiv.com</email></address>
282    </author>
283    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
284      <organization abbrev="W3C">World Wide Web Consortium</organization>
285      <address><email>ylafon@w3.org</email></address>
286    </author>
287    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
288      <organization abbrev="greenbytes">greenbytes GmbH</organization>
289      <address><email>julian.reschke@greenbytes.de</email></address>
290    </author>
291    <date month="&ID-MONTH;" year="&ID-YEAR;" />
292  </front>
293  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
294  <x:source basename="p5-range" href="p5-range.xml" />
295</reference>
296
297<reference anchor="Part6">
298  <front>
299    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
300    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
301      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
302      <address><email>fielding@gbiv.com</email></address>
303    </author>
304    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
305      <organization abbrev="W3C">World Wide Web Consortium</organization>
306      <address><email>ylafon@w3.org</email></address>
307    </author>
308    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
309      <organization>Rackspace</organization>
310      <address><email>mnot@mnot.net</email></address>
311    </author>
312    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
313      <organization abbrev="greenbytes">greenbytes GmbH</organization>
314      <address><email>julian.reschke@greenbytes.de</email></address>
315    </author>
316    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
317  </front>
318  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
319  <x:source href="p6-cache.xml" basename="p6-cache"/>
320</reference>
321
322<reference anchor="Part7">
323  <front>
324    <title abbrev="HTTP/1.1">HTTP/1.1, part 7: Authentication</title>
325    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
326      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
327      <address><email>fielding@gbiv.com</email></address>
328    </author>
329    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
330      <organization abbrev="W3C">World Wide Web Consortium</organization>
331      <address><email>ylafon@w3.org</email></address>
332    </author>
333    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
334      <organization abbrev="greenbytes">greenbytes GmbH</organization>
335      <address><email>julian.reschke@greenbytes.de</email></address>
336    </author>
337    <date month="&ID-MONTH;" year="&ID-YEAR;" />
338  </front>
339  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
340  <x:source basename="p7-auth" href="p7-auth.xml" />
341</reference>
342
343<reference anchor="RFC3986">
344 <front>
345  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
346  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
347    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
348    <address>
349       <email>timbl@w3.org</email>
350       <uri>http://www.w3.org/People/Berners-Lee/</uri>
351    </address>
352  </author>
353  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
354    <organization abbrev="Day Software">Day Software</organization>
355    <address>
356      <email>fielding@gbiv.com</email>
357      <uri>http://roy.gbiv.com/</uri>
358    </address>
359  </author>
360  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
361    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
362    <address>
363      <email>LMM@acm.org</email>
364      <uri>http://larry.masinter.net/</uri>
365    </address>
366  </author>
367  <date month='January' year='2005'></date>
368 </front>
369 <seriesInfo name="STD" value="66"/>
370 <seriesInfo name="RFC" value="3986"/>
371</reference>
372
373</references>
374
375<references title="Informative References">
376
377<reference anchor="RFC2616">
378  <front>
379    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
380    <author initials="R." surname="Fielding" fullname="R. Fielding">
381      <organization>University of California, Irvine</organization>
382      <address><email>fielding@ics.uci.edu</email></address>
383    </author>
384    <author initials="J." surname="Gettys" fullname="J. Gettys">
385      <organization>W3C</organization>
386      <address><email>jg@w3.org</email></address>
387    </author>
388    <author initials="J." surname="Mogul" fullname="J. Mogul">
389      <organization>Compaq Computer Corporation</organization>
390      <address><email>mogul@wrl.dec.com</email></address>
391    </author>
392    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
393      <organization>MIT Laboratory for Computer Science</organization>
394      <address><email>frystyk@w3.org</email></address>
395    </author>
396    <author initials="L." surname="Masinter" fullname="L. Masinter">
397      <organization>Xerox Corporation</organization>
398      <address><email>masinter@parc.xerox.com</email></address>
399    </author>
400    <author initials="P." surname="Leach" fullname="P. Leach">
401      <organization>Microsoft Corporation</organization>
402      <address><email>paulle@microsoft.com</email></address>
403    </author>
404    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
405      <organization>W3C</organization>
406      <address><email>timbl@w3.org</email></address>
407    </author>
408    <date month="June" year="1999"/>
409  </front>
410  <seriesInfo name="RFC" value="2616"/>
411</reference>
412
413
414</references>
415</back>
416</rfc>
Note: See TracBrowser for help on using the repository browser.