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

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

Add subsections for "Changes from draft 01" (empty for now)

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