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

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

Bump up document dates.

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