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

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

Add information about changes since -00.

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