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

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

fix width problems in ABNF (related to #36)

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