source: draft-ietf-httpbis/05/draft-ietf-httpbis-p7-auth-05.xml @ 559

Last change on this file since 559 was 559, checked in by fielding@…, 10 years ago

remove executable and set eol-style for earlier drafts

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