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

Last change on this file since 156 was 156, checked in by fielding@…, 12 years ago

editorial: minor update of p7 introduction to reflect status.

  • Property svn:eol-style set to native
File size: 26.2 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 "January">
16  <!ENTITY ID-YEAR "2008">
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="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'>
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  <t>
194    This draft incorporates those issue resolutions that were either
195    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
196    or which were agreed upon on the mailing list between October 2006 and
197    November 2007 (as published in "draft-lafon-rfc2616bis-03").
198  </t>
199</note>
200</front>
201<middle>
202<section title="Introduction" anchor="introduction">
203<t>
204   This document defines aspects of HTTP related to access control and
205   authentication. Right now it only includes the extracted relevant sections
206   of <xref target="RFC2616" x:fmt="none">RFC 2616</xref> with editorial changes.
207</t>
208<t>
209   HTTP provides several &OPTIONAL; challenge-response authentication
210   mechanisms which can be used by a server to challenge a client
211   request and by a client to provide authentication information. The
212   general framework for access authentication, and the specification of
213   "basic" and "digest" authentication, are specified in "HTTP
214   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. This
215   specification adopts the definitions of "challenge" and "credentials"
216   from that specification.
217</t>
218
219<section title="Requirements" anchor="intro.requirements">
220<t>
221   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
222   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
223   document are to be interpreted as described in <xref target="RFC2119"/>.
224</t>
225<t>
226   An implementation is not compliant if it fails to satisfy one or more
227   of the &MUST; or &REQUIRED; level requirements for the protocols it
228   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
229   level and all the &SHOULD; level requirements for its protocols is said
230   to be "unconditionally compliant"; one that satisfies all the &MUST;
231   level requirements but not all the &SHOULD; level requirements for its
232   protocols is said to be "conditionally compliant."
233</t>
234</section>
235</section>
236
237<section title="Status Code Definitions">
238<section title="401 Unauthorized" anchor="status.401">
239  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
240  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
241<t>
242   The request requires user authentication. The response &MUST; include a
243   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
244   applicable to the requested resource. The client &MAY; repeat the
245   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
246   the request already included Authorization credentials, then the 401
247   response indicates that authorization has been refused for those
248   credentials. If the 401 response contains the same challenge as the
249   prior response, and the user agent has already attempted
250   authentication at least once, then the user &SHOULD; be presented the
251   entity that was given in the response, since that entity might
252   include relevant diagnostic information. HTTP access authentication
253   is explained in "HTTP Authentication: Basic and Digest Access
254   Authentication" <xref target="RFC2617"/>.
255</t>
256</section>
257<section title="407 Proxy Authentication Required" anchor="status.407">
258  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
259  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
260<t>
261   This code is similar to 401 (Unauthorized), but indicates that the
262   client must first authenticate itself with the proxy. The proxy &MUST;
263   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
264   challenge applicable to the proxy for the requested resource. The
265   client &MAY; repeat the request with a suitable Proxy-Authorization
266   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
267   in "HTTP Authentication: Basic and Digest Access Authentication"
268   <xref target="RFC2617"/>.
269</t>
270</section>
271</section>
272
273<section title="Header Field Definitions" anchor="header.fields">
274<t>
275   This section defines the syntax and semantics of HTTP/1.1 header fields
276   related to authentication.
277</t>
278
279<section title="Authorization" anchor="header.authorization">
280  <iref primary="true" item="Authorization header" x:for-anchor=""/>
281  <iref primary="true" item="Headers" subitem="Authorization" x:for-anchor=""/>
282<t>
283      A user agent that wishes to authenticate itself with a server--
284      usually, but not necessarily, after receiving a 401 response--does
285      so by including an Authorization request-header field with the
286      request.  The Authorization field value consists of credentials
287      containing the authentication information of the user agent for
288      the realm of the resource being requested.
289</t>
290<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
291  Authorization  = "Authorization" ":" credentials
292</artwork></figure>
293<t>
294      HTTP access authentication is described in "HTTP Authentication:
295      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
296      authenticated and a realm specified, the same credentials &SHOULD;
297      be valid for all other requests within this realm (assuming that
298      the authentication scheme itself does not require otherwise, such
299      as credentials that vary according to a challenge value or using
300      synchronized clocks).
301</t>
302<t>
303      When a shared cache (see &shared-and-non-shared-caches;) receives a request
304      containing an Authorization field, it &MUST-NOT; return the
305      corresponding response as a reply to any other request, unless one
306      of the following specific exceptions holds:
307</t>
308<t>
309  <list style="numbers">
310      <t>If the response includes the "s-maxage" cache-control
311         directive, the cache &MAY; use that response in replying to a
312         subsequent request. But (if the specified maximum age has
313         passed) a proxy cache &MUST; first revalidate it with the origin
314         server, using the request-headers from the new request to allow
315         the origin server to authenticate the new request. (This is the
316         defined behavior for s-maxage.) If the response includes "s-maxage=0",
317         the proxy &MUST; always revalidate it before re-using
318         it.</t>
319
320      <t>If the response includes the "must-revalidate" cache-control
321         directive, the cache &MAY; use that response in replying to a
322         subsequent request. But if the response is stale, all caches
323         &MUST; first revalidate it with the origin server, using the
324         request-headers from the new request to allow the origin server
325         to authenticate the new request.</t>
326
327      <t>If the response includes the "public" cache-control directive,
328         it &MAY; be returned in reply to any subsequent request.</t>
329  </list>
330</t>
331</section>
332
333<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
334  <iref primary="true" item="Proxy-Authenticate header" x:for-anchor=""/>
335  <iref primary="true" item="Headers" subitem="Proxy-Authenticate" x:for-anchor=""/>
336<t>
337   The Proxy-Authenticate response-header field &MUST; be included as part
338   of a 407 (Proxy Authentication Required) response. The field value
339   consists of a challenge that indicates the authentication scheme and
340   parameters applicable to the proxy for this Request-URI.
341</t>
342<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
343  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
344</artwork></figure>
345<t>
346   The HTTP access authentication process is described in "HTTP
347   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
348   WWW-Authenticate, the Proxy-Authenticate header field applies only to
349   the current connection and &SHOULD-NOT;  be passed on to downstream
350   clients. However, an intermediate proxy might need to obtain its own
351   credentials by requesting them from the downstream client, which in
352   some circumstances will appear as if the proxy is forwarding the
353   Proxy-Authenticate header field.
354</t>
355</section>
356
357<section title="Proxy-Authorization" anchor="header.proxy-authorization">
358  <iref primary="true" item="Proxy-Authorization header" x:for-anchor=""/>
359  <iref primary="true" item="Headers" subitem="Proxy-Authorization" x:for-anchor=""/>
360<t>
361   The Proxy-Authorization request-header field allows the client to
362   identify itself (or its user) to a proxy which requires
363   authentication. The Proxy-Authorization field value consists of
364   credentials containing the authentication information of the user
365   agent for the proxy and/or realm of the resource being requested.
366</t>
367<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
368  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
369</artwork></figure>
370<t>
371   The HTTP access authentication process is described in "HTTP
372   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
373   Authorization, the Proxy-Authorization header field applies only to
374   the next outbound proxy that demanded authentication using the Proxy-Authenticate
375   field. When multiple proxies are used in a chain, the
376   Proxy-Authorization header field is consumed by the first outbound
377   proxy that was expecting to receive credentials. A proxy &MAY; relay
378   the credentials from the client request to the next proxy if that is
379   the mechanism by which the proxies cooperatively authenticate a given
380   request.
381</t>
382</section>
383
384<section title="WWW-Authenticate" anchor="header.www-authenticate">
385  <iref primary="true" item="WWW-Authenticate header" x:for-anchor=""/>
386  <iref primary="true" item="Headers" subitem="WWW-Authenticate" x:for-anchor=""/>
387<t>
388   The WWW-Authenticate response-header field &MUST; be included in 401
389   (Unauthorized) response messages. The field value consists of at
390   least one challenge that indicates the authentication scheme(s) and
391   parameters applicable to the Request-URI.
392</t>
393<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
394  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
395</artwork></figure>
396<t>
397   The HTTP access authentication process is described in "HTTP
398   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
399   agents are advised to take special care in parsing the WWW-Authenticate
400   field value as it might contain more than one challenge,
401   or if more than one WWW-Authenticate header field is provided, the
402   contents of a challenge itself can contain a comma-separated list of
403   authentication parameters.
404</t>
405</section>
406
407</section>
408
409<section title="IANA Considerations" anchor="IANA.considerations">
410<t>
411   TBD.
412</t>
413</section>
414
415<section title="Security Considerations" anchor="security.considerations">
416<t>
417   This section is meant to inform application developers, information
418   providers, and users of the security limitations in HTTP/1.1 as
419   described by this document. The discussion does not include
420   definitive solutions to the problems revealed, though it does make
421   some suggestions for reducing security risks.
422</t>
423
424<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
425<t>
426   Existing HTTP clients and user agents typically retain authentication
427   information indefinitely. HTTP/1.1 does not provide a method for a
428   server to direct clients to discard these cached credentials. This is
429   a significant defect that requires further extensions to HTTP.
430   Circumstances under which credential caching can interfere with the
431   application's security model include but are not limited to:
432  <list style="symbols">
433     <t>Clients which have been idle for an extended period following
434        which the server might wish to cause the client to reprompt the
435        user for credentials.</t>
436
437     <t>Applications which include a session termination indication
438        (such as a `logout' or `commit' button on a page) after which
439        the server side of the application `knows' that there is no
440        further reason for the client to retain the credentials.</t>
441  </list>
442</t>
443<t>
444   This is currently under separate study. There are a number of work-arounds
445   to parts of this problem, and we encourage the use of
446   password protection in screen savers, idle time-outs, and other
447   methods which mitigate the security problems inherent in this
448   problem. In particular, user agents which cache credentials are
449   encouraged to provide a readily accessible mechanism for discarding
450   cached credentials under user control.
451</t>
452</section>
453</section>
454
455<section title="Acknowledgments" anchor="ack">
456<t>
457  TBD.
458</t>
459</section>
460</middle>
461
462<back>
463
464<references title="Normative References">
465
466<reference anchor="Part6">
467  <front>
468    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
469    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
470      <organization abbrev="Day Software">Day Software</organization>
471      <address><email>fielding@gbiv.com</email></address>
472    </author>
473    <author initials="J." surname="Gettys" fullname="Jim Gettys">
474      <organization>One Laptop per Child</organization>
475      <address><email>jg@laptop.org</email></address>
476    </author>
477    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
478      <organization abbrev="HP">Hewlett-Packard Company</organization>
479      <address><email>JeffMogul@acm.org</email></address>
480    </author>
481    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
482      <organization abbrev="Microsoft">Microsoft Corporation</organization>
483      <address><email>henrikn@microsoft.com</email></address>
484    </author>
485    <author initials="L." surname="Masinter" fullname="Larry Masinter">
486      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
487      <address><email>LMM@acm.org</email></address>
488    </author>
489    <author initials="P." surname="Leach" fullname="Paul J. Leach">
490      <organization abbrev="Microsoft">Microsoft Corporation</organization>
491      <address><email>paulle@microsoft.com</email></address>
492    </author>
493    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
494      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
495      <address><email>timbl@w3.org</email></address>
496    </author>
497    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
498      <organization abbrev="W3C">World Wide Web Consortium</organization>
499      <address><email>ylafon@w3.org</email></address>
500    </author>
501    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
502      <organization abbrev="greenbytes">greenbytes GmbH</organization>
503      <address><email>julian.reschke@greenbytes.de</email></address>
504    </author>
505    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
506  </front>
507  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
508  <x:source href="p6-cache.xml" basename="p6-cache"/>
509</reference>
510
511<reference anchor="RFC2119">
512  <front>
513    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
514    <author initials="S." surname="Bradner" fullname="Scott Bradner">
515      <organization>Harvard University</organization>
516      <address><email>sob@harvard.edu</email></address>
517    </author>
518    <date month="March" year="1997"/>
519  </front>
520  <seriesInfo name="BCP" value="14"/>
521  <seriesInfo name="RFC" value="2119"/>
522</reference>
523
524<reference anchor="RFC2617">
525  <front>
526    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
527    <author initials="J." surname="Franks" fullname="John Franks">
528      <organization>Northwestern University, Department of Mathematics</organization>
529      <address><email>john@math.nwu.edu</email></address>
530    </author>
531    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
532      <organization>Verisign Inc.</organization>
533      <address><email>pbaker@verisign.com</email></address>
534    </author>
535    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
536      <organization>AbiSource, Inc.</organization>
537      <address><email>jeff@AbiSource.com</email></address>
538    </author>
539    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
540      <organization>Agranat Systems, Inc.</organization>
541      <address><email>lawrence@agranat.com</email></address>
542    </author>
543    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
544      <organization>Microsoft Corporation</organization>
545      <address><email>paulle@microsoft.com</email></address>
546    </author>
547    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
548      <organization>Netscape Communications Corporation</organization>
549    </author>
550    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
551      <organization>Open Market, Inc.</organization>
552      <address><email>stewart@OpenMarket.com</email></address>
553    </author>
554    <date month="June" year="1999"/>
555  </front>
556  <seriesInfo name="RFC" value="2617"/>
557</reference>
558
559</references>
560
561<references title="Informative References">
562
563<reference anchor="RFC2616">
564  <front>
565    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
566    <author initials="R." surname="Fielding" fullname="R. Fielding">
567      <organization>University of California, Irvine</organization>
568      <address><email>fielding@ics.uci.edu</email></address>
569    </author>
570    <author initials="J." surname="Gettys" fullname="J. Gettys">
571      <organization>W3C</organization>
572      <address><email>jg@w3.org</email></address>
573    </author>
574    <author initials="J." surname="Mogul" fullname="J. Mogul">
575      <organization>Compaq Computer Corporation</organization>
576      <address><email>mogul@wrl.dec.com</email></address>
577    </author>
578    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
579      <organization>MIT Laboratory for Computer Science</organization>
580      <address><email>frystyk@w3.org</email></address>
581    </author>
582    <author initials="L." surname="Masinter" fullname="L. Masinter">
583      <organization>Xerox Corporation</organization>
584      <address><email>masinter@parc.xerox.com</email></address>
585    </author>
586    <author initials="P." surname="Leach" fullname="P. Leach">
587      <organization>Microsoft Corporation</organization>
588      <address><email>paulle@microsoft.com</email></address>
589    </author>
590    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
591      <organization>W3C</organization>
592      <address><email>timbl@w3.org</email></address>
593    </author>
594    <date month="June" year="1999"/>
595  </front>
596  <seriesInfo name="RFC" value="2616"/>
597</reference>
598
599</references>
600
601
602<section title="Compatibility with Previous Versions" anchor="compatibility">
603
604<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
605</section>
606
607</section>
608
609<section title="Change Log (to be removed by RFC Editor before publication)">
610
611<section title="Since RFC2616">
612<t>
613  Extracted relevant partitions from <xref target="RFC2616"/>.
614</t>
615</section>
616
617<section title="Since draft-ietf-httpbis-p7-auth-00">
618<t>
619  Closed issues:
620  <list style="symbols"> 
621    <t>
622      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
623      "Normative and Informative references"
624    </t>
625  </list>
626</t>
627</section>
628
629</section>
630
631</back>
632</rfc>
Note: See TracBrowser for help on using the repository browser.