source: draft-ietf-httpbis/04/p7-auth.xml @ 2082

Last change on this file since 2082 was 1500, checked in by julian.reschke@…, 8 years ago

fix mime types

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 32.9 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 "04">
15  <!ENTITY ID-MONTH "August">
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;" day="29"/>
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    The changes in this draft are summarized in <xref target="changes.since.02"/>.
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  The ABNF rules below are defined in other specifications:
252</t>
253<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="challenge"/><iref primary="true" item="Grammar" subitem="credentials"/>
254  <x:ref>challenge</x:ref>   = &lt;challenge, defined in <xref target="RFC2617" x:fmt="," x:sec="1.2"/>&gt;
255  <x:ref>credentials</x:ref> = &lt;credentials, defined in <xref target="RFC2617" x:fmt="," x:sec="1.2"/>&gt;
256</artwork></figure>
257</section>
258
259
260<section title="Status Code Definitions">
261<section title="401 Unauthorized" anchor="status.401">
262  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
263  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
264<t>
265   The request requires user authentication. The response &MUST; include a
266   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
267   applicable to the requested resource. The client &MAY; repeat the
268   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
269   the request already included Authorization credentials, then the 401
270   response indicates that authorization has been refused for those
271   credentials. If the 401 response contains the same challenge as the
272   prior response, and the user agent has already attempted
273   authentication at least once, then the user &SHOULD; be presented the
274   entity that was given in the response, since that entity might
275   include relevant diagnostic information. HTTP access authentication
276   is explained in "HTTP Authentication: Basic and Digest Access
277   Authentication" <xref target="RFC2617"/>.
278</t>
279</section>
280<section title="407 Proxy Authentication Required" anchor="status.407">
281  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
282  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
283<t>
284   This code is similar to 401 (Unauthorized), but indicates that the
285   client must first authenticate itself with the proxy. The proxy &MUST;
286   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
287   challenge applicable to the proxy for the requested resource. The
288   client &MAY; repeat the request with a suitable Proxy-Authorization
289   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
290   in "HTTP Authentication: Basic and Digest Access Authentication"
291   <xref target="RFC2617"/>.
292</t>
293</section>
294</section>
295
296<section title="Header Field Definitions" anchor="header.fields">
297<t>
298   This section defines the syntax and semantics of HTTP/1.1 header fields
299   related to authentication.
300</t>
301
302<section title="Authorization" anchor="header.authorization">
303  <iref primary="true" item="Authorization header" x:for-anchor=""/>
304  <iref primary="true" item="Headers" subitem="Authorization" x:for-anchor=""/>
305  <x:anchor-alias value="Authorization"/>
306<t>
307      A user agent that wishes to authenticate itself with a server--
308      usually, but not necessarily, after receiving a 401 response--does
309      so by including an Authorization request-header field with the
310      request.  The Authorization field value consists of credentials
311      containing the authentication information of the user agent for
312      the realm of the resource being requested.
313</t>
314<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
315  <x:ref>Authorization</x:ref>  = "Authorization" ":" <x:ref>credentials</x:ref>
316</artwork></figure>
317<t>
318      HTTP access authentication is described in "HTTP Authentication:
319      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
320      authenticated and a realm specified, the same credentials &SHOULD;
321      be valid for all other requests within this realm (assuming that
322      the authentication scheme itself does not require otherwise, such
323      as credentials that vary according to a challenge value or using
324      synchronized clocks).
325</t>
326<t>
327      When a shared cache (see &shared-and-non-shared-caches;) receives a request
328      containing an Authorization field, it &MUST-NOT; return the
329      corresponding response as a reply to any other request, unless one
330      of the following specific exceptions holds:
331</t>
332<t>
333  <list style="numbers">
334      <t>If the response includes the "s-maxage" cache-control
335         directive, the cache &MAY; use that response in replying to a
336         subsequent request. But (if the specified maximum age has
337         passed) a proxy cache &MUST; first revalidate it with the origin
338         server, using the request-headers from the new request to allow
339         the origin server to authenticate the new request. (This is the
340         defined behavior for s-maxage.) If the response includes "s-maxage=0",
341         the proxy &MUST; always revalidate it before re-using
342         it.</t>
343
344      <t>If the response includes the "must-revalidate" cache-control
345         directive, the cache &MAY; use that response in replying to a
346         subsequent request. But if the response is stale, all caches
347         &MUST; first revalidate it with the origin server, using the
348         request-headers from the new request to allow the origin server
349         to authenticate the new request.</t>
350
351      <t>If the response includes the "public" cache-control directive,
352         it &MAY; be returned in reply to any subsequent request.</t>
353  </list>
354</t>
355</section>
356
357<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
358  <iref primary="true" item="Proxy-Authenticate header" x:for-anchor=""/>
359  <iref primary="true" item="Headers" subitem="Proxy-Authenticate" x:for-anchor=""/>
360  <x:anchor-alias value="Proxy-Authenticate"/>
361<t>
362   The Proxy-Authenticate response-header field &MUST; be included as part
363   of a 407 (Proxy Authentication Required) response. The field value
364   consists of a challenge that indicates the authentication scheme and
365   parameters applicable to the proxy for this Request-URI.
366</t>
367<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
368  <x:ref>Proxy-Authenticate</x:ref>  = "Proxy-Authenticate" ":" 1#<x:ref>challenge</x:ref>
369</artwork></figure>
370<t>
371   The HTTP access authentication process is described in "HTTP
372   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
373   WWW-Authenticate, the Proxy-Authenticate header field applies only to
374   the current connection and &SHOULD-NOT;  be passed on to downstream
375   clients. However, an intermediate proxy might need to obtain its own
376   credentials by requesting them from the downstream client, which in
377   some circumstances will appear as if the proxy is forwarding the
378   Proxy-Authenticate header field.
379</t>
380</section>
381
382<section title="Proxy-Authorization" anchor="header.proxy-authorization">
383  <iref primary="true" item="Proxy-Authorization header" x:for-anchor=""/>
384  <iref primary="true" item="Headers" subitem="Proxy-Authorization" x:for-anchor=""/>
385  <x:anchor-alias value="Proxy-Authorization"/>
386<t>
387   The Proxy-Authorization request-header field allows the client to
388   identify itself (or its user) to a proxy which requires
389   authentication. The Proxy-Authorization field value consists of
390   credentials containing the authentication information of the user
391   agent for the proxy and/or realm of the resource being requested.
392</t>
393<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
394  <x:ref>Proxy-Authorization</x:ref>     = "Proxy-Authorization" ":" <x:ref>credentials</x:ref>
395</artwork></figure>
396<t>
397   The HTTP access authentication process is described in "HTTP
398   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
399   Authorization, the Proxy-Authorization header field applies only to
400   the next outbound proxy that demanded authentication using the Proxy-Authenticate
401   field. When multiple proxies are used in a chain, the
402   Proxy-Authorization header field is consumed by the first outbound
403   proxy that was expecting to receive credentials. A proxy &MAY; relay
404   the credentials from the client request to the next proxy if that is
405   the mechanism by which the proxies cooperatively authenticate a given
406   request.
407</t>
408</section>
409
410<section title="WWW-Authenticate" anchor="header.www-authenticate">
411  <iref primary="true" item="WWW-Authenticate header" x:for-anchor=""/>
412  <iref primary="true" item="Headers" subitem="WWW-Authenticate" x:for-anchor=""/>
413  <x:anchor-alias value="WWW-Authenticate"/>
414<t>
415   The WWW-Authenticate response-header field &MUST; be included in 401
416   (Unauthorized) response messages. The field value consists of at
417   least one challenge that indicates the authentication scheme(s) and
418   parameters applicable to the Request-URI.
419</t>
420<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
421  <x:ref>WWW-Authenticate</x:ref>  = "WWW-Authenticate" ":" 1#<x:ref>challenge</x:ref>
422</artwork></figure>
423<t>
424   The HTTP access authentication process is described in "HTTP
425   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
426   agents are advised to take special care in parsing the WWW-Authenticate
427   field value as it might contain more than one challenge,
428   or if more than one WWW-Authenticate header field is provided, the
429   contents of a challenge itself can contain a comma-separated list of
430   authentication parameters.
431</t>
432</section>
433
434</section>
435
436<section title="IANA Considerations" anchor="IANA.considerations">
437<section title="Message Header Registration" anchor="message.header.registration">
438<t>
439   The Message Header Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
440   with the permanent registrations below (see <xref target="RFC3864"/>):
441</t>
442<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
443<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
444   <ttcol>Header Field Name</ttcol>
445   <ttcol>Protocol</ttcol>
446   <ttcol>Status</ttcol>
447   <ttcol>Reference</ttcol>
448
449   <c>Authorization</c>
450   <c>http</c>
451   <c>standard</c>
452   <c>
453      <xref target="header.authorization"/>
454   </c>
455   <c>Proxy-Authenticate</c>
456   <c>http</c>
457   <c>standard</c>
458   <c>
459      <xref target="header.proxy-authenticate"/>
460   </c>
461   <c>Proxy-Authorization</c>
462   <c>http</c>
463   <c>standard</c>
464   <c>
465      <xref target="header.proxy-authorization"/>
466   </c>
467   <c>WWW-Authenticate</c>
468   <c>http</c>
469   <c>standard</c>
470   <c>
471      <xref target="header.www-authenticate"/>
472   </c>
473</texttable>
474<!--(END)-->
475<t>
476   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
477</t>
478</section>
479</section>
480
481<section title="Security Considerations" anchor="security.considerations">
482<t>
483   This section is meant to inform application developers, information
484   providers, and users of the security limitations in HTTP/1.1 as
485   described by this document. The discussion does not include
486   definitive solutions to the problems revealed, though it does make
487   some suggestions for reducing security risks.
488</t>
489
490<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
491<t>
492   Existing HTTP clients and user agents typically retain authentication
493   information indefinitely. HTTP/1.1 does not provide a method for a
494   server to direct clients to discard these cached credentials. This is
495   a significant defect that requires further extensions to HTTP.
496   Circumstances under which credential caching can interfere with the
497   application's security model include but are not limited to:
498  <list style="symbols">
499     <t>Clients which have been idle for an extended period following
500        which the server might wish to cause the client to reprompt the
501        user for credentials.</t>
502
503     <t>Applications which include a session termination indication
504        (such as a `logout' or `commit' button on a page) after which
505        the server side of the application `knows' that there is no
506        further reason for the client to retain the credentials.</t>
507  </list>
508</t>
509<t>
510   This is currently under separate study. There are a number of work-arounds
511   to parts of this problem, and we encourage the use of
512   password protection in screen savers, idle time-outs, and other
513   methods which mitigate the security problems inherent in this
514   problem. In particular, user agents which cache credentials are
515   encouraged to provide a readily accessible mechanism for discarding
516   cached credentials under user control.
517</t>
518</section>
519</section>
520
521<section title="Acknowledgments" anchor="ack">
522<t>
523  <cref>TBD.</cref>
524</t>
525</section>
526</middle>
527
528<back>
529
530<references title="Normative References">
531
532<reference anchor="Part1">
533  <front>
534    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
535    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
536      <organization abbrev="Day Software">Day Software</organization>
537      <address><email>fielding@gbiv.com</email></address>
538    </author>
539    <author initials="J." surname="Gettys" fullname="Jim Gettys">
540      <organization>One Laptop per Child</organization>
541      <address><email>jg@laptop.org</email></address>
542    </author>
543    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
544      <organization abbrev="HP">Hewlett-Packard Company</organization>
545      <address><email>JeffMogul@acm.org</email></address>
546    </author>
547    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
548      <organization abbrev="Microsoft">Microsoft Corporation</organization>
549      <address><email>henrikn@microsoft.com</email></address>
550    </author>
551    <author initials="L." surname="Masinter" fullname="Larry Masinter">
552      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
553      <address><email>LMM@acm.org</email></address>
554    </author>
555    <author initials="P." surname="Leach" fullname="Paul J. Leach">
556      <organization abbrev="Microsoft">Microsoft Corporation</organization>
557      <address><email>paulle@microsoft.com</email></address>
558    </author>
559    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
560      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
561      <address><email>timbl@w3.org</email></address>
562    </author>
563    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
564      <organization abbrev="W3C">World Wide Web Consortium</organization>
565      <address><email>ylafon@w3.org</email></address>
566    </author>
567    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
568      <organization abbrev="greenbytes">greenbytes GmbH</organization>
569      <address><email>julian.reschke@greenbytes.de</email></address>
570    </author>
571    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
572  </front>
573  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
574  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
575</reference>
576
577<reference anchor="Part6">
578  <front>
579    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
580    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
581      <organization abbrev="Day Software">Day Software</organization>
582      <address><email>fielding@gbiv.com</email></address>
583    </author>
584    <author initials="J." surname="Gettys" fullname="Jim Gettys">
585      <organization>One Laptop per Child</organization>
586      <address><email>jg@laptop.org</email></address>
587    </author>
588    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
589      <organization abbrev="HP">Hewlett-Packard Company</organization>
590      <address><email>JeffMogul@acm.org</email></address>
591    </author>
592    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
593      <organization abbrev="Microsoft">Microsoft Corporation</organization>
594      <address><email>henrikn@microsoft.com</email></address>
595    </author>
596    <author initials="L." surname="Masinter" fullname="Larry Masinter">
597      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
598      <address><email>LMM@acm.org</email></address>
599    </author>
600    <author initials="P." surname="Leach" fullname="Paul J. Leach">
601      <organization abbrev="Microsoft">Microsoft Corporation</organization>
602      <address><email>paulle@microsoft.com</email></address>
603    </author>
604    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
605      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
606      <address><email>timbl@w3.org</email></address>
607    </author>
608    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
609      <organization abbrev="W3C">World Wide Web Consortium</organization>
610      <address><email>ylafon@w3.org</email></address>
611    </author>
612    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
613      <organization abbrev="greenbytes">greenbytes GmbH</organization>
614      <address><email>julian.reschke@greenbytes.de</email></address>
615    </author>
616    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
617  </front>
618  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
619  <x:source href="p6-cache.xml" basename="p6-cache"/>
620</reference>
621
622<reference anchor="RFC2119">
623  <front>
624    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
625    <author initials="S." surname="Bradner" fullname="Scott Bradner">
626      <organization>Harvard University</organization>
627      <address><email>sob@harvard.edu</email></address>
628    </author>
629    <date month="March" year="1997"/>
630  </front>
631  <seriesInfo name="BCP" value="14"/>
632  <seriesInfo name="RFC" value="2119"/>
633</reference>
634
635<reference anchor="RFC2617">
636  <front>
637    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
638    <author initials="J." surname="Franks" fullname="John Franks">
639      <organization>Northwestern University, Department of Mathematics</organization>
640      <address><email>john@math.nwu.edu</email></address>
641    </author>
642    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
643      <organization>Verisign Inc.</organization>
644      <address><email>pbaker@verisign.com</email></address>
645    </author>
646    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
647      <organization>AbiSource, Inc.</organization>
648      <address><email>jeff@AbiSource.com</email></address>
649    </author>
650    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
651      <organization>Agranat Systems, Inc.</organization>
652      <address><email>lawrence@agranat.com</email></address>
653    </author>
654    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
655      <organization>Microsoft Corporation</organization>
656      <address><email>paulle@microsoft.com</email></address>
657    </author>
658    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
659      <organization>Netscape Communications Corporation</organization>
660    </author>
661    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
662      <organization>Open Market, Inc.</organization>
663      <address><email>stewart@OpenMarket.com</email></address>
664    </author>
665    <date month="June" year="1999"/>
666  </front>
667  <seriesInfo name="RFC" value="2617"/>
668</reference>
669
670</references>
671
672<references title="Informative References">
673
674<reference anchor="RFC2616">
675  <front>
676    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
677    <author initials="R." surname="Fielding" fullname="R. Fielding">
678      <organization>University of California, Irvine</organization>
679      <address><email>fielding@ics.uci.edu</email></address>
680    </author>
681    <author initials="J." surname="Gettys" fullname="J. Gettys">
682      <organization>W3C</organization>
683      <address><email>jg@w3.org</email></address>
684    </author>
685    <author initials="J." surname="Mogul" fullname="J. Mogul">
686      <organization>Compaq Computer Corporation</organization>
687      <address><email>mogul@wrl.dec.com</email></address>
688    </author>
689    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
690      <organization>MIT Laboratory for Computer Science</organization>
691      <address><email>frystyk@w3.org</email></address>
692    </author>
693    <author initials="L." surname="Masinter" fullname="L. Masinter">
694      <organization>Xerox Corporation</organization>
695      <address><email>masinter@parc.xerox.com</email></address>
696    </author>
697    <author initials="P." surname="Leach" fullname="P. Leach">
698      <organization>Microsoft Corporation</organization>
699      <address><email>paulle@microsoft.com</email></address>
700    </author>
701    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
702      <organization>W3C</organization>
703      <address><email>timbl@w3.org</email></address>
704    </author>
705    <date month="June" year="1999"/>
706  </front>
707  <seriesInfo name="RFC" value="2616"/>
708</reference>
709
710<reference anchor='RFC3864'>
711  <front>
712    <title>Registration Procedures for Message Header Fields</title>
713    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
714      <organization>Nine by Nine</organization>
715      <address><email>GK-IETF@ninebynine.org</email></address>
716    </author>
717    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
718      <organization>BEA Systems</organization>
719      <address><email>mnot@pobox.com</email></address>
720    </author>
721    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
722      <organization>HP Labs</organization>
723      <address><email>JeffMogul@acm.org</email></address>
724    </author>
725    <date year='2004' month='September' />
726  </front>
727  <seriesInfo name='BCP' value='90' />
728  <seriesInfo name='RFC' value='3864' />
729</reference>
730
731</references>
732
733
734<section title="Compatibility with Previous Versions" anchor="compatibility">
735
736<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
737</section>
738
739</section>
740
741<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
742
743<section title="Since RFC2616">
744<t>
745  Extracted relevant partitions from <xref target="RFC2616"/>.
746</t>
747</section>
748
749<section title="Since draft-ietf-httpbis-p7-auth-00">
750<t>
751  Closed issues:
752  <list style="symbols"> 
753    <t>
754      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
755      "Normative and Informative references"
756    </t>
757  </list>
758</t>
759</section>
760
761<section title="Since draft-ietf-httpbis-p7-auth-01">
762<t>
763  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
764  <list style="symbols"> 
765    <t>
766      Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.
767    </t>
768    <t>
769      Add explicit references to BNF syntax and rules imported from other parts of the specification.
770    </t>
771  </list>
772</t>
773</section>
774
775<section title="Since draft-ietf-httpbis-p7-auth-02" anchor="changes.since.02">
776<t>
777  Ongoing work on IANA Message Header Registration (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
778  <list style="symbols"> 
779    <t>
780      Reference RFC 3984, and update header registrations for headers defined
781      in this document.
782    </t>
783  </list>
784</t>
785</section>
786
787<section title="Since draft-ietf-httpbis-p7-auth-03" anchor="changes.since.03">
788<t>
789</t>
790</section>
791
792</section>
793
794</back>
795</rfc>
Note: See TracBrowser for help on using the repository browser.