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

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

fix references/affiliations

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