source: draft-ietf-httpbis/latest/p7-auth.xml @ 120

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

Consistent short titles (only affect TXT versions)

  • Property svn:eol-style set to native
File size: 25.9 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 ID-VERSION "latest">
15  <!ENTITY ID-MONTH "December">
16  <!ENTITY ID-YEAR "2007">
17  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18]>
19<?rfc toc="yes" ?>
20<?rfc symrefs="yes" ?>
21<?rfc sortrefs="yes" ?>
22<?rfc compact="yes"?>
23<?rfc subcompact="no" ?>
24<?rfc linkmailto="no" ?>
25<?rfc editing="no" ?>
26<?rfc-ext allow-markup-in-artwork="yes" ?>
27<?rfc-ext include-references-in-index="yes" ?>
28<rfc obsoletes="2068, 2616" updates="2617" category="std"
29     ipr="full3978" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
30     xmlns:x='http://purl.org/net/xml2rfc/ext' xmlns:ed="http://greenbytes.de/2002/rfcedit">
31<front>
32
33  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
34
35  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
36    <organization abbrev="Day Software">Day Software</organization>
37    <address>
38      <postal>
39        <street>23 Corporate Plaza DR, Suite 280</street>
40        <city>Newport Beach</city>
41        <region>CA</region>
42        <code>92660</code>
43        <country>USA</country>
44      </postal>
45      <phone>+1-949-706-5300</phone>
46      <facsimile>+1-949-706-5305</facsimile>
47      <email>fielding@gbiv.com</email>
48      <uri>http://roy.gbiv.com/</uri>
49    </address>
50  </author>
51
52  <author initials="J." surname="Gettys" fullname="Jim Gettys">
53    <organization>One Laptop per Child</organization>
54    <address>
55      <postal>
56        <street>21 Oak Knoll Road</street>
57        <city>Carlisle</city>
58        <region>MA</region>
59        <code>01741</code>
60        <country>USA</country>
61      </postal>
62      <email>jg@laptop.org</email>
63      <uri>http://www.laptop.org/</uri>
64    </address>
65  </author>
66 
67  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
68    <organization abbrev="HP">Hewlett-Packard Company</organization>
69    <address>
70      <postal>
71        <street>HP Labs, Large Scale Systems Group</street>
72        <street>1501 Page Mill Road, MS 1177</street>
73        <city>Palo Alto</city>
74        <region>CA</region>
75        <code>94304</code>
76        <country>USA</country>
77      </postal>
78      <email>JeffMogul@acm.org</email>
79    </address>
80  </author>
81
82  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
83    <organization abbrev="Microsoft">Microsoft Corporation</organization>
84    <address>
85      <postal>
86        <street>1 Microsoft Way</street>
87        <city>Redmond</city>
88        <region>WA</region>
89        <code>98052</code>
90        <country>USA</country>
91      </postal>
92      <email>henrikn@microsoft.com</email>
93    </address>
94  </author>
95
96  <author initials="L." surname="Masinter" fullname="Larry Masinter">
97    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
98    <address>
99      <postal>
100        <street>345 Park Ave</street>
101        <city>San Jose</city>
102        <region>CA</region>
103        <code>95110</code>
104        <country>USA</country>
105      </postal>
106      <email>LMM@acm.org</email>
107      <uri>http://larry.masinter.net/</uri>
108    </address>
109  </author>
110 
111  <author initials="P." surname="Leach" fullname="Paul J. Leach">
112    <organization abbrev="Microsoft">Microsoft Corporation</organization>
113    <address>
114      <postal>
115        <street>1 Microsoft Way</street>
116        <city>Redmond</city>
117        <region>WA</region>
118        <code>98052</code>
119      </postal>
120      <email>paulle@microsoft.com</email>
121    </address>
122  </author>
123   
124  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
125    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
126    <address>
127      <postal>
128        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
129        <street>The Stata Center, Building 32</street>
130        <street>32 Vassar Street</street>
131        <city>Cambridge</city>
132        <region>MA</region>
133        <code>02139</code>
134        <country>USA</country>
135      </postal>
136      <email>timbl@w3.org</email>
137      <uri>http://www.w3.org/People/Berners-Lee/</uri>
138    </address>
139  </author>
140
141  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
142    <organization abbrev="W3C">World Wide Web Consortium</organization>
143    <address>
144      <postal>
145        <street>W3C / ERCIM</street>
146        <street>2004, rte des Lucioles</street>
147        <city>Sophia-Antipolis</city>
148        <region>AM</region>
149        <code>06902</code>
150        <country>France</country>
151      </postal>
152      <email>ylafon@w3.org</email>
153      <uri>http://www.raubacapeu.net/people/yves/</uri>
154    </address>
155  </author>
156
157  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
158    <organization abbrev="greenbytes">greenbytes GmbH</organization>
159    <address>
160      <postal>
161        <street>Hafenweg 16</street>
162        <city>Muenster</city><region>NW</region><code>48155</code>
163        <country>Germany</country>
164      </postal>
165      <phone>+49 251 2807760</phone>   
166      <facsimile>+49 251 2807761</facsimile>   
167      <email>julian.reschke@greenbytes.de</email>       
168      <uri>http://greenbytes.de/tech/webdav/</uri>     
169    </address>
170  </author>
171
172  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
173
174<abstract>
175<t>
176   The Hypertext Transfer Protocol (HTTP) is an application-level
177   protocol for distributed, collaborative, hypermedia information
178   systems. HTTP has been in use by the World Wide Web global information
179   initiative since 1990. This document is Part 7 of the seven-part specification
180   that defines the protocol referred to as "HTTP/1.1" and, taken together,
181   obsoletes RFC 2616.  Part 7 defines HTTP Authentication.
182</t>
183</abstract>
184
185<note title="Editorial Note (To be removed by RFC Editor)">
186  <t>
187    Discussion of this draft should take place on the HTTPBIS working group
188    mailing list (ietf-http-wg@w3.org). The current issues list is
189    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
190    and related documents (including fancy diffs) can be found at
191    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
192  </t>
193</note>
194</front>
195<middle>
196<section title="Introduction" anchor="introduction">
197<t>
198   This document will define aspects of HTTP related to access control and
199   authentication. Right now it only includes the extracted relevant sections
200   of <xref target="RFC2616" x:fmt="none">RFC 2616</xref> with only minor edits.
201</t>
202<t>
203   HTTP provides several &OPTIONAL; challenge-response authentication
204   mechanisms which can be used by a server to challenge a client
205   request and by a client to provide authentication information. The
206   general framework for access authentication, and the specification of
207   "basic" and "digest" authentication, are specified in "HTTP
208   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. This
209   specification adopts the definitions of "challenge" and "credentials"
210   from that specification.
211</t>
212
213<section title="Requirements" anchor="intro.requirements">
214<t>
215   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
216   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
217   document are to be interpreted as described in <xref target="RFC2119"/>.
218</t>
219<t>
220   An implementation is not compliant if it fails to satisfy one or more
221   of the &MUST; or &REQUIRED; level requirements for the protocols it
222   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
223   level and all the &SHOULD; level requirements for its protocols is said
224   to be "unconditionally compliant"; one that satisfies all the &MUST;
225   level requirements but not all the &SHOULD; level requirements for its
226   protocols is said to be "conditionally compliant."
227</t>
228</section>
229</section>
230
231<section title="Status Code Definitions">
232<section title="401 Unauthorized" anchor="status.401">
233  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
234  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
235<t>
236   The request requires user authentication. The response &MUST; include a
237   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
238   applicable to the requested resource. The client &MAY; repeat the
239   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
240   the request already included Authorization credentials, then the 401
241   response indicates that authorization has been refused for those
242   credentials. If the 401 response contains the same challenge as the
243   prior response, and the user agent has already attempted
244   authentication at least once, then the user &SHOULD; be presented the
245   entity that was given in the response, since that entity might
246   include relevant diagnostic information. HTTP access authentication
247   is explained in "HTTP Authentication: Basic and Digest Access
248   Authentication" <xref target="RFC2617"/>.
249</t>
250</section>
251<section title="407 Proxy Authentication Required" anchor="status.407">
252  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
253  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
254<t>
255   This code is similar to 401 (Unauthorized), but indicates that the
256   client must first authenticate itself with the proxy. The proxy &MUST;
257   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
258   challenge applicable to the proxy for the requested resource. The
259   client &MAY; repeat the request with a suitable Proxy-Authorization
260   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
261   in "HTTP Authentication: Basic and Digest Access Authentication"
262   <xref target="RFC2617"/>.
263</t>
264</section>
265</section>
266
267<section title="Header Field Definitions" anchor="header.fields">
268<t>
269   This section defines the syntax and semantics of HTTP/1.1 header fields
270   related to authentication.
271</t>
272
273<section title="Authorization" anchor="header.authorization">
274  <iref primary="true" item="Authorization header" x:for-anchor=""/>
275  <iref primary="true" item="Headers" subitem="Authorization" x:for-anchor=""/>
276<t>
277      A user agent that wishes to authenticate itself with a server--
278      usually, but not necessarily, after receiving a 401 response--does
279      so by including an Authorization request-header field with the
280      request.  The Authorization field value consists of credentials
281      containing the authentication information of the user agent for
282      the realm of the resource being requested.
283</t>
284<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
285       Authorization  = "Authorization" ":" credentials
286</artwork></figure>
287<t>
288      HTTP access authentication is described in "HTTP Authentication:
289      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
290      authenticated and a realm specified, the same credentials &SHOULD;
291      be valid for all other requests within this realm (assuming that
292      the authentication scheme itself does not require otherwise, such
293      as credentials that vary according to a challenge value or using
294      synchronized clocks).
295</t>
296<t>
297      When a shared cache (see &shared-and-non-shared-caches;) receives a request
298      containing an Authorization field, it &MUST-NOT; return the
299      corresponding response as a reply to any other request, unless one
300      of the following specific exceptions holds:
301</t>
302<t>
303  <list style="numbers">
304      <t>If the response includes the "s-maxage" cache-control
305         directive, the cache &MAY; use that response in replying to a
306         subsequent request. But (if the specified maximum age has
307         passed) a proxy cache &MUST; first revalidate it with the origin
308         server, using the request-headers from the new request to allow
309         the origin server to authenticate the new request. (This is the
310         defined behavior for s-maxage.) If the response includes "s-maxage=0",
311         the proxy &MUST; always revalidate it before re-using
312         it.</t>
313
314      <t>If the response includes the "must-revalidate" cache-control
315         directive, the cache &MAY; use that response in replying to a
316         subsequent request. But if the response is stale, all caches
317         &MUST; first revalidate it with the origin server, using the
318         request-headers from the new request to allow the origin server
319         to authenticate the new request.</t>
320
321      <t>If the response includes the "public" cache-control directive,
322         it &MAY; be returned in reply to any subsequent request.</t>
323  </list>
324</t>
325</section>
326
327<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
328  <iref primary="true" item="Proxy-Authenticate header" x:for-anchor=""/>
329  <iref primary="true" item="Headers" subitem="Proxy-Authenticate" x:for-anchor=""/>
330<t>
331   The Proxy-Authenticate response-header field &MUST; be included as part
332   of a 407 (Proxy Authentication Required) response. The field value
333   consists of a challenge that indicates the authentication scheme and
334   parameters applicable to the proxy for this Request-URI.
335</t>
336<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
337    Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
338</artwork></figure>
339<t>
340   The HTTP access authentication process is described in "HTTP
341   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
342   WWW-Authenticate, the Proxy-Authenticate header field applies only to
343   the current connection and &SHOULD-NOT;  be passed on to downstream
344   clients. However, an intermediate proxy might need to obtain its own
345   credentials by requesting them from the downstream client, which in
346   some circumstances will appear as if the proxy is forwarding the
347   Proxy-Authenticate header field.
348</t>
349</section>
350
351<section title="Proxy-Authorization" anchor="header.proxy-authorization">
352  <iref primary="true" item="Proxy-Authorization header" x:for-anchor=""/>
353  <iref primary="true" item="Headers" subitem="Proxy-Authorization" x:for-anchor=""/>
354<t>
355   The Proxy-Authorization request-header field allows the client to
356   identify itself (or its user) to a proxy which requires
357   authentication. The Proxy-Authorization field value consists of
358   credentials containing the authentication information of the user
359   agent for the proxy and/or realm of the resource being requested.
360</t>
361<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
362    Proxy-Authorization     = "Proxy-Authorization" ":" credentials
363</artwork></figure>
364<t>
365   The HTTP access authentication process is described in "HTTP
366   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
367   Authorization, the Proxy-Authorization header field applies only to
368   the next outbound proxy that demanded authentication using the Proxy-Authenticate
369   field. When multiple proxies are used in a chain, the
370   Proxy-Authorization header field is consumed by the first outbound
371   proxy that was expecting to receive credentials. A proxy &MAY; relay
372   the credentials from the client request to the next proxy if that is
373   the mechanism by which the proxies cooperatively authenticate a given
374   request.
375</t>
376</section>
377
378<section title="WWW-Authenticate" anchor="header.www-authenticate">
379  <iref primary="true" item="WWW-Authenticate header" x:for-anchor=""/>
380  <iref primary="true" item="Headers" subitem="WWW-Authenticate" x:for-anchor=""/>
381<t>
382   The WWW-Authenticate response-header field &MUST; be included in 401
383   (Unauthorized) response messages. The field value consists of at
384   least one challenge that indicates the authentication scheme(s) and
385   parameters applicable to the Request-URI.
386</t>
387<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
388    WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
389</artwork></figure>
390<t>
391   The HTTP access authentication process is described in "HTTP
392   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
393   agents are advised to take special care in parsing the WWW-Authenticate
394   field value as it might contain more than one challenge,
395   or if more than one WWW-Authenticate header field is provided, the
396   contents of a challenge itself can contain a comma-separated list of
397   authentication parameters.
398</t>
399</section>
400
401</section>
402
403<section title="IANA Considerations" anchor="IANA.considerations">
404<t>
405   TBD.
406</t>
407</section>
408
409<section title="Security Considerations" anchor="security.considerations">
410<t>
411   This section is meant to inform application developers, information
412   providers, and users of the security limitations in HTTP/1.1 as
413   described by this document. The discussion does not include
414   definitive solutions to the problems revealed, though it does make
415   some suggestions for reducing security risks.
416</t>
417
418<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
419<t>
420   Existing HTTP clients and user agents typically retain authentication
421   information indefinitely. HTTP/1.1. does not provide a method for a
422   server to direct clients to discard these cached credentials. This is
423   a significant defect that requires further extensions to HTTP.
424   Circumstances under which credential caching can interfere with the
425   application's security model include but are not limited to:
426  <list style="symbols">
427     <t>Clients which have been idle for an extended period following
428        which the server might wish to cause the client to reprompt the
429        user for credentials.</t>
430
431     <t>Applications which include a session termination indication
432        (such as a `logout' or `commit' button on a page) after which
433        the server side of the application `knows' that there is no
434        further reason for the client to retain the credentials.</t>
435  </list>
436</t>
437<t>
438   This is currently under separate study. There are a number of work-arounds
439   to parts of this problem, and we encourage the use of
440   password protection in screen savers, idle time-outs, and other
441   methods which mitigate the security problems inherent in this
442   problem. In particular, user agents which cache credentials are
443   encouraged to provide a readily accessible mechanism for discarding
444   cached credentials under user control.
445</t>
446</section>
447</section>
448
449<section title="Acknowledgments" anchor="ack">
450<t>
451  TBD.
452</t>
453</section>
454</middle>
455
456<back>
457
458<references title="Normative References">
459
460<reference anchor="Part6">
461  <front>
462    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
463    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
464      <organization abbrev="Day Software">Day Software</organization>
465      <address><email>fielding@gbiv.com</email></address>
466    </author>
467    <author initials="J." surname="Gettys" fullname="Jim Gettys">
468      <organization>One Laptop per Child</organization>
469      <address><email>jg@laptop.org</email></address>
470    </author>
471    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
472      <organization abbrev="HP">Hewlett-Packard Company</organization>
473      <address><email>JeffMogul@acm.org</email></address>
474    </author>
475    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
476      <organization abbrev="Microsoft">Microsoft Corporation</organization>
477      <address><email>henrikn@microsoft.com</email></address>
478    </author>
479    <author initials="L." surname="Masinter" fullname="Larry Masinter">
480      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
481      <address><email>LMM@acm.org</email></address>
482    </author>
483    <author initials="P." surname="Leach" fullname="Paul J. Leach">
484      <organization abbrev="Microsoft">Microsoft Corporation</organization>
485      <address><email>paulle@microsoft.com</email></address>
486    </author>
487    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
488      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
489      <address><email>timbl@w3.org</email></address>
490    </author>
491    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
492      <organization abbrev="W3C">World Wide Web Consortium</organization>
493      <address><email>ylafon@w3.org</email></address>
494    </author>
495    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
496      <organization abbrev="greenbytes">greenbytes GmbH</organization>
497      <address><email>julian.reschke@greenbytes.de</email></address>
498    </author>
499    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
500  </front>
501  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
502  <x:source href="p6-cache.xml" basename="p6-cache"/>
503</reference>
504
505<reference anchor="RFC2119">
506  <front>
507    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
508    <author initials="S." surname="Bradner" fullname="Scott Bradner">
509      <organization>Harvard University</organization>
510      <address><email>sob@harvard.edu</email></address>
511    </author>
512    <date month="March" year="1997"/>
513  </front>
514  <seriesInfo name="BCP" value="14"/>
515  <seriesInfo name="RFC" value="2119"/>
516</reference>
517
518<reference anchor="RFC2617">
519  <front>
520    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
521    <author initials="J." surname="Franks" fullname="John Franks">
522      <organization>Northwestern University, Department of Mathematics</organization>
523      <address><email>john@math.nwu.edu</email></address>
524    </author>
525    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
526      <organization>Verisign Inc.</organization>
527      <address><email>pbaker@verisign.com</email></address>
528    </author>
529    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
530      <organization>AbiSource, Inc.</organization>
531      <address><email>jeff@AbiSource.com</email></address>
532    </author>
533    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
534      <organization>Agranat Systems, Inc.</organization>
535      <address><email>lawrence@agranat.com</email></address>
536    </author>
537    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
538      <organization>Microsoft Corporation</organization>
539      <address><email>paulle@microsoft.com</email></address>
540    </author>
541    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
542      <organization>Netscape Communications Corporation</organization>
543    </author>
544    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
545      <organization>Open Market, Inc.</organization>
546      <address><email>stewart@OpenMarket.com</email></address>
547    </author>
548    <date month="June" year="1999"/>
549  </front>
550  <seriesInfo name="RFC" value="2617"/>
551</reference>
552
553</references>
554
555<references title="Informative References">
556
557<reference anchor="RFC2616">
558  <front>
559    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
560    <author initials="R." surname="Fielding" fullname="R. Fielding">
561      <organization>University of California, Irvine</organization>
562      <address><email>fielding@ics.uci.edu</email></address>
563    </author>
564    <author initials="J." surname="Gettys" fullname="J. Gettys">
565      <organization>W3C</organization>
566      <address><email>jg@w3.org</email></address>
567    </author>
568    <author initials="J." surname="Mogul" fullname="J. Mogul">
569      <organization>Compaq Computer Corporation</organization>
570      <address><email>mogul@wrl.dec.com</email></address>
571    </author>
572    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
573      <organization>MIT Laboratory for Computer Science</organization>
574      <address><email>frystyk@w3.org</email></address>
575    </author>
576    <author initials="L." surname="Masinter" fullname="L. Masinter">
577      <organization>Xerox Corporation</organization>
578      <address><email>masinter@parc.xerox.com</email></address>
579    </author>
580    <author initials="P." surname="Leach" fullname="P. Leach">
581      <organization>Microsoft Corporation</organization>
582      <address><email>paulle@microsoft.com</email></address>
583    </author>
584    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
585      <organization>W3C</organization>
586      <address><email>timbl@w3.org</email></address>
587    </author>
588    <date month="June" year="1999"/>
589  </front>
590  <seriesInfo name="RFC" value="2616"/>
591</reference>
592
593</references>
594
595
596<section title="Compatibility with Previous Versions" anchor="compatibility">
597
598<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
599</section>
600
601</section>
602
603<section title="Change Log (to be removed by RFC Editor before publication)">
604
605<section title="Since RFC2616">
606<t>
607  Extracted relevant partitions from <xref target="RFC2616"/>.
608</t>
609</section>
610
611<section title="Since draft-ietf-httpbis-p7-auth-00">
612<t>
613  Other changes:
614  <list style="symbols">
615    <t>
616      Start work on categorizing references as "Normative" or "Informative".
617    </t>
618  </list>
619</t>
620</section>
621
622</section>
623
624</back>
625</rfc>
Note: See TracBrowser for help on using the repository browser.