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

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

remove historical Acks (see #219)

  • Property svn:eol-style set to native
File size: 50.4 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "July">
16  <!ENTITY ID-YEAR "2011">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY notation-abnf                "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY basic-rules                  "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY effective-request-uri        "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY msg-orient-and-buffering     "<xref target='Part1' x:rel='#message-orientation-and-buffering' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY end-to-end.and-hop-by-hop    "<xref target='Part1' x:rel='#end-to-end.and.hop-by-hop.header-fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26]>
27<?rfc toc="yes" ?>
28<?rfc symrefs="yes" ?>
29<?rfc sortrefs="yes" ?>
30<?rfc compact="yes"?>
31<?rfc subcompact="no" ?>
32<?rfc linkmailto="no" ?>
33<?rfc editing="no" ?>
34<?rfc comments="yes"?>
35<?rfc inline="yes"?>
36<?rfc rfcedstyle="yes"?>
37<?rfc-ext allow-markup-in-artwork="yes" ?>
38<?rfc-ext include-references-in-index="yes" ?>
39<rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="draft"
40     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
41     xmlns:x='http://purl.org/net/xml2rfc/ext'>
42<front>
43
44  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
45
46  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
47    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
48    <address>
49      <postal>
50        <street>345 Park Ave</street>
51        <city>San Jose</city>
52        <region>CA</region>
53        <code>95110</code>
54        <country>USA</country>
55      </postal>
56      <email>fielding@gbiv.com</email>
57      <uri>http://roy.gbiv.com/</uri>
58    </address>
59  </author>
60
61  <author initials="J." surname="Gettys" fullname="Jim Gettys">
62    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
63    <address>
64      <postal>
65        <street>21 Oak Knoll Road</street>
66        <city>Carlisle</city>
67        <region>MA</region>
68        <code>01741</code>
69        <country>USA</country>
70      </postal>
71      <email>jg@freedesktop.org</email>
72      <uri>http://gettys.wordpress.com/</uri>
73    </address>
74  </author>
75 
76  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
77    <organization abbrev="HP">Hewlett-Packard Company</organization>
78    <address>
79      <postal>
80        <street>HP Labs, Large Scale Systems Group</street>
81        <street>1501 Page Mill Road, MS 1177</street>
82        <city>Palo Alto</city>
83        <region>CA</region>
84        <code>94304</code>
85        <country>USA</country>
86      </postal>
87      <email>JeffMogul@acm.org</email>
88    </address>
89  </author>
90
91  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
92    <organization abbrev="Microsoft">Microsoft Corporation</organization>
93    <address>
94      <postal>
95        <street>1 Microsoft Way</street>
96        <city>Redmond</city>
97        <region>WA</region>
98        <code>98052</code>
99        <country>USA</country>
100      </postal>
101      <email>henrikn@microsoft.com</email>
102    </address>
103  </author>
104
105  <author initials="L." surname="Masinter" fullname="Larry Masinter">
106    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
107    <address>
108      <postal>
109        <street>345 Park Ave</street>
110        <city>San Jose</city>
111        <region>CA</region>
112        <code>95110</code>
113        <country>USA</country>
114      </postal>
115      <email>LMM@acm.org</email>
116      <uri>http://larry.masinter.net/</uri>
117    </address>
118  </author>
119 
120  <author initials="P." surname="Leach" fullname="Paul J. Leach">
121    <organization abbrev="Microsoft">Microsoft Corporation</organization>
122    <address>
123      <postal>
124        <street>1 Microsoft Way</street>
125        <city>Redmond</city>
126        <region>WA</region>
127        <code>98052</code>
128      </postal>
129      <email>paulle@microsoft.com</email>
130    </address>
131  </author>
132   
133  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
134    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
135    <address>
136      <postal>
137        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
138        <street>The Stata Center, Building 32</street>
139        <street>32 Vassar Street</street>
140        <city>Cambridge</city>
141        <region>MA</region>
142        <code>02139</code>
143        <country>USA</country>
144      </postal>
145      <email>timbl@w3.org</email>
146      <uri>http://www.w3.org/People/Berners-Lee/</uri>
147    </address>
148  </author>
149
150  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
151    <organization abbrev="W3C">World Wide Web Consortium</organization>
152    <address>
153      <postal>
154        <street>W3C / ERCIM</street>
155        <street>2004, rte des Lucioles</street>
156        <city>Sophia-Antipolis</city>
157        <region>AM</region>
158        <code>06902</code>
159        <country>France</country>
160      </postal>
161      <email>ylafon@w3.org</email>
162      <uri>http://www.raubacapeu.net/people/yves/</uri>
163    </address>
164  </author>
165
166  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
167    <organization abbrev="greenbytes">greenbytes GmbH</organization>
168    <address>
169      <postal>
170        <street>Hafenweg 16</street>
171        <city>Muenster</city><region>NW</region><code>48155</code>
172        <country>Germany</country>
173      </postal>
174      <phone>+49 251 2807760</phone>
175      <facsimile>+49 251 2807761</facsimile>
176      <email>julian.reschke@greenbytes.de</email>
177      <uri>http://greenbytes.de/tech/webdav/</uri>
178    </address>
179  </author>
180
181  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
182  <workgroup>HTTPbis Working Group</workgroup>
183
184<abstract>
185<t>
186   The Hypertext Transfer Protocol (HTTP) is an application-level
187   protocol for distributed, collaborative, hypermedia information
188   systems. HTTP has been in use by the World Wide Web global information
189   initiative since 1990. This document is Part 7 of the seven-part specification
190   that defines the protocol referred to as "HTTP/1.1" and, taken together,
191   obsoletes RFC 2616.  Part 7 defines HTTP Authentication.
192</t>
193</abstract>
194
195<note title="Editorial Note (To be removed by RFC Editor)">
196  <t>
197    Discussion of this draft should take place on the HTTPBIS working group
198    mailing list (ietf-http-wg@w3.org), which is archived at
199    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
200  </t>
201  <t>
202    The current issues list is at
203    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
204    documents (including fancy diffs) can be found at
205    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
206  </t>
207  <t>
208    The changes in this draft are summarized in <xref target="changes.since.15"/>.
209  </t>
210</note>
211</front>
212<middle>
213<section title="Introduction" anchor="introduction">
214<t>
215   This document defines HTTP/1.1 access control and authentication. It
216   includes the relevant parts of <xref target="RFC2616" x:fmt="none">RFC 2616</xref>
217   with only minor changes, plus the general framework for HTTP authentication,
218   as previously defined in "HTTP Authentication: Basic and Digest Access
219   Authentication" (<xref target="RFC2617"/>).
220</t>
221<t>
222   HTTP provides several &OPTIONAL; challenge-response authentication
223   mechanisms which can be used by a server to challenge a client request and
224   by a client to provide authentication information. The "basic" and "digest"
225   authentication schemes continue to be specified in
226   <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
227</t>
228
229<section title="Requirements" anchor="intro.requirements">
230<t>
231   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
232   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
233   document are to be interpreted as described in <xref target="RFC2119"/>.
234</t>
235<t>
236   An implementation is not compliant if it fails to satisfy one or more
237   of the "MUST" or "REQUIRED" level requirements for the protocols it
238   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
239   level and all the "SHOULD" level requirements for its protocols is said
240   to be "unconditionally compliant"; one that satisfies all the "MUST"
241   level requirements but not all the "SHOULD" level requirements for its
242   protocols is said to be "conditionally compliant".
243</t>
244</section>
245
246<section title="Syntax Notation" anchor="notation">
247  <x:anchor-alias value="ALPHA"/>
248  <x:anchor-alias value="CR"/>
249  <x:anchor-alias value="DIGIT"/>
250  <x:anchor-alias value="LF"/>
251  <x:anchor-alias value="OCTET"/>
252  <x:anchor-alias value="VCHAR"/>
253  <x:anchor-alias value="SP"/>
254  <x:anchor-alias value="WSP"/>
255<t>
256  This specification uses the ABNF syntax defined in &notation; (which
257  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
258  <xref target="collected.abnf"/> shows the collected ABNF, with the list
259  rule expanded.
260</t>
261<t>
262  The following core rules are included by
263  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
264  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
265  DIGIT (decimal 0-9), DQUOTE (double quote),
266  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
267  OCTET (any 8-bit sequence of data), SP (space),
268  VCHAR (any visible USASCII character),
269  and WSP (whitespace).
270</t>
271
272<section title="Core Rules" anchor="core.rules">
273   <x:anchor-alias value="quoted-string"/>
274   <x:anchor-alias value="token"/>
275   <x:anchor-alias value="OWS"/>
276<t>
277   The core rules below are defined in &basic-rules;:
278</t>
279<figure><artwork type="abnf2616">
280  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &basic-rules;&gt;
281  <x:ref>token</x:ref>         = &lt;token, defined in &basic-rules;&gt;
282  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &basic-rules;&gt;
283</artwork></figure>
284</section>
285</section>
286</section>
287
288<section title="Access Authentication Framework" anchor="access.authentication.framework">
289
290<section title="Challenge and Response" anchor="challenge.and.response">
291  <x:anchor-alias value="auth-scheme"/>
292  <x:anchor-alias value="auth-param"/>
293  <x:anchor-alias value="challenge"/>
294  <x:anchor-alias value="credentials"/>
295<t>
296   HTTP provides a simple challenge-response authentication mechanism
297   that can be used by a server to challenge a client request and by a
298   client to provide authentication information. It uses an extensible,
299   case-insensitive token to identify the authentication scheme,
300   followed by a comma-separated list of attribute-value pairs which
301   carry the parameters necessary for achieving authentication via that
302   scheme.
303</t>
304<figure><artwork type="abnf2616"><iref item="auth-scheme" primary="true"/><iref item="auth-param" primary="true"/>
305  auth-scheme    = token
306  auth-param     = token "=" ( token / quoted-string )
307</artwork></figure>
308<t>
309   The 401 (Unauthorized) response message is used by an origin server
310   to challenge the authorization of a user agent. This response &MUST;
311   include a WWW-Authenticate header field containing at least one
312   challenge applicable to the requested resource.
313</t>
314<t>   
315   The 407 (Proxy Authentication Required) response message is used by a proxy to
316   challenge the authorization of a client and &MUST; include a Proxy-Authenticate
317   header field containing at least one challenge
318   applicable to the proxy for the requested resource.
319</t>
320<figure><artwork type="abnf2616"><iref item="challenge" primary="true"/>
321  <x:ref>challenge</x:ref>   = <x:ref>auth-scheme</x:ref> 1*<x:ref>SP</x:ref> 1#<x:ref>auth-param</x:ref>
322</artwork></figure>
323<x:note>
324  <t>
325     <x:h>Note:</x:h> User agents will need to take special care in parsing the
326     WWW-Authenticate and Proxy-Authenticate header field values because they
327     can contain more than one challenge, or if more than one of each is
328     provided, since the contents of a challenge can itself contain a
329     comma-separated list of authentication parameters.
330  </t>
331</x:note>
332<x:note>
333  <t>
334     <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
335     schemes. A workaround for this problem is to list well-supported schemes
336     (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 -->
337  </t>
338</x:note>
339<t>
340   A user agent that wishes to authenticate itself with an origin server
341   &mdash; usually, but not necessarily, after receiving a 401 (Unauthorized)
342   &mdash; &MAY; do so by including an Authorization header field with the
343   request.
344</t>
345<t>   
346   A client that wishes to authenticate itself with a proxy &mdash; usually,
347   but not necessarily, after receiving a 407 (Proxy Authentication Required)
348   &mdash; &MAY; do so by including a Proxy-Authorization header field with the
349   request.
350</t>
351<t>   
352   Both the Authorization field value and the Proxy-Authorization field value
353   consist of credentials containing the authentication information of the
354   client for the realm of the resource being requested. The user agent &MUST;
355   choose to use one of the challenges with the strongest auth-scheme it
356   understands and request credentials from the user based upon that challenge.
357</t>
358<figure><artwork type="abnf2616"><iref item="credentials" primary="true"/>
359  <x:ref>credentials</x:ref> = <x:ref>auth-scheme</x:ref> ( <x:ref>token</x:ref>
360                            / <x:ref>quoted-string</x:ref>
361                            / #<x:ref>auth-param</x:ref> )
362</artwork></figure>
363<t>
364   If the origin server does not wish to accept the credentials sent
365   with a request, it &SHOULD; return a 401 (Unauthorized) response. The
366   response &MUST; include a WWW-Authenticate header field containing at
367   least one (possibly new) challenge applicable to the requested
368   resource.
369</t>
370<t>
371   If a proxy does not accept the credentials sent with a
372   request, it &SHOULD; return a 407 (Proxy Authentication Required). The
373   response &MUST; include a Proxy-Authenticate header field containing a
374   (possibly new) challenge applicable to the proxy for the requested
375   resource.
376</t>
377<t>
378   The HTTP protocol does not restrict applications to this simple
379   challenge-response mechanism for access authentication. Additional
380   mechanisms &MAY; be used, such as encryption at the transport level or
381   via message encapsulation, and with additional header fields
382   specifying authentication information. However, such additional
383   mechanisms are not defined by this specification.
384</t>
385<t>
386   Proxies &MUST; forward the WWW-Authenticate and Authorization headers
387   unmodified and follow the rules found in <xref target="header.authorization"/>.
388</t>
389</section>
390
391<section title="Protection Space (Realm)" anchor="protection.space">
392  <iref item="Protection Space"/>
393  <iref item="Realm"/>
394<t>
395   The authentication parameter realm is reserved for use by authentication
396   schemes that wish to indicate the scope of protection:
397</t>
398<figure><artwork type="abnf2616"><iref item="realm" primary="true"/><iref item="realm-value" primary="true"/>
399  realm       = "realm" "=" realm-value
400  realm-value = quoted-string
401</artwork></figure>
402<t>
403   A <x:dfn>protection space</x:dfn> is defined by the canonical root URI (the
404   scheme and authority components of the effective request URI; see
405   <xref target="Part1" x:fmt="of" x:rel="#effective.request.uri"/>) of the
406   server being accessed, in combination with the realm value if present.
407   These realms allow the protected resources on a server to be
408   partitioned into a set of protection spaces, each with its own
409   authentication scheme and/or authorization database. The realm value
410   is a string, generally assigned by the origin server, which can have
411   additional semantics specific to the authentication scheme. Note that
412   there can be multiple challenges with the same auth-scheme but
413   different realms.
414</t>
415<t>
416   The protection space determines the domain over which credentials can
417   be automatically applied. If a prior request has been authorized, the
418   same credentials &MAY; be reused for all other requests within that
419   protection space for a period of time determined by the
420   authentication scheme, parameters, and/or user preference. Unless
421   otherwise defined by the authentication scheme, a single protection
422   space cannot extend outside the scope of its server.
423</t>
424</section>
425
426<section title="Authentication Scheme Registry" anchor="authentication.scheme.registry">
427<t>
428  The HTTP Authentication Scheme Registry defines the name space for the
429  authentication schemes in challenges and credentials.
430</t>
431<t>
432  Registrations &MUST; include the following fields:
433  <list style="symbols">
434    <t>Authentication Scheme Name</t>
435    <t>Pointer to specification text</t>
436  </list>
437</t>
438<t>
439  Values to be added to this name space are subject to IETF review
440  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
441</t>
442<t>
443  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
444</t>
445
446<section title="Considerations for New Authentication Schemes" anchor="considerations.for.new.authentication.schemes">
447<t>
448  There are certain aspects of the HTTP Authentication Framework that put
449  constraints on how new authentication schemes can work:
450</t>
451<t>
452  <list style="symbols">
453    <x:lt>
454    <t>
455      Authentication schemes need to be compatible with the inherent
456      constraints of HTTP; for instance, that messages need to keep their
457      semantics when inspected in isolation, thus an authentication scheme
458      can not bind information to the TCP session over which the message
459      was received (see &msg-orient-and-buffering;).
460    </t>
461    </x:lt>
462    <x:lt>
463    <t>
464      The authentication parameter "realm" is reserved for defining Protection
465      Spaces as defined in <xref target="protection.space"/>. New schemes
466      &MUST-NOT; use it in a way incompatible with that definition.
467    </t>
468    </x:lt>
469    <x:lt>
470    <t>
471      Authentication schemes need to document whether they are usable in
472      origin-server authentication (i.e., using WWW-Authenticate), and/or
473      proxy authentication (i.e., using Proxy-Authenticate).
474    </t>
475    </x:lt>
476    <x:lt>
477    <t>
478      The credentials carried in an Authorization header field are specific to
479      the User Agent, and therefore have the same effect on HTTP caches as the
480      "private" Cache-Control response directive, within the scope of the
481      request they appear in.
482    </t>
483    <t>
484      Therefore, new authentication schemes which choose not to carry
485      credentials in the Authorization header (e.g., using a newly defined
486      header) will need to explicitly disallow caching, by mandating the use of
487      either Cache-Control request directives (e.g., "no-store") or response
488      directives (e.g., "private").
489    </t>
490    </x:lt>
491  </list>
492</t>
493</section>
494
495</section>
496
497</section>
498
499<section title="Status Code Definitions" anchor="status.code.definitions">
500<section title="401 Unauthorized" anchor="status.401">
501  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
502  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
503<t>
504   The request requires user authentication. The response &MUST; include a
505   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
506   applicable to the target resource. The client &MAY; repeat the
507   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
508   the request already included Authorization credentials, then the 401
509   response indicates that authorization has been refused for those
510   credentials. If the 401 response contains the same challenge as the
511   prior response, and the user agent has already attempted
512   authentication at least once, then the user &SHOULD; be presented the
513   representation that was given in the response, since that representation might
514   include relevant diagnostic information.
515</t>
516</section>
517<section title="407 Proxy Authentication Required" anchor="status.407">
518  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
519  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
520<t>
521   This code is similar to 401 (Unauthorized), but indicates that the
522   client ought to first authenticate itself with the proxy. The proxy &MUST;
523   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
524   challenge applicable to the proxy for the target resource. The
525   client &MAY; repeat the request with a suitable Proxy-Authorization
526   header field (<xref target="header.proxy-authorization"/>).
527</t>
528</section>
529</section>
530
531<section title="Header Field Definitions" anchor="header.fields">
532<t>
533   This section defines the syntax and semantics of HTTP/1.1 header fields
534   related to authentication.
535</t>
536
537<section title="Authorization" anchor="header.authorization">
538  <iref primary="true" item="Authorization header field" x:for-anchor=""/>
539  <iref primary="true" item="Header Fields" subitem="Authorization" x:for-anchor=""/>
540  <x:anchor-alias value="Authorization"/>
541<t>
542   The "Authorization" header field allows a user agent to authenticate
543   itself with a server &mdash; usually, but not necessarily, after receiving a 401
544   (Unauthorized) response. Its value consists of credentials containing
545   information of the user agent for the realm of the resource being
546   requested.
547</t>
548<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
549  <x:ref>Authorization</x:ref> = <x:ref>credentials</x:ref>
550</artwork></figure>
551<t>
552   If a request is
553   authenticated and a realm specified, the same credentials &SHOULD;
554   be valid for all other requests within this realm (assuming that
555   the authentication scheme itself does not require otherwise, such
556   as credentials that vary according to a challenge value or using
557   synchronized clocks).
558</t>
559<t>
560      When a shared cache (see &shared-and-non-shared-caches;) receives a request
561      containing an Authorization field, it &MUST-NOT; return the
562      corresponding response as a reply to any other request, unless one
563      of the following specific exceptions holds:
564</t>
565<t>
566  <list style="numbers">
567      <t>If the response includes the "s-maxage" cache-control
568         directive, the cache &MAY; use that response in replying to a
569         subsequent request. But (if the specified maximum age has
570         passed) a proxy cache &MUST; first revalidate it with the origin
571         server, using the header fields from the new request to allow
572         the origin server to authenticate the new request. (This is the
573         defined behavior for s-maxage.) If the response includes "s-maxage=0",
574         the proxy &MUST; always revalidate it before re-using
575         it.</t>
576
577      <t>If the response includes the "must-revalidate" cache-control
578         directive, the cache &MAY; use that response in replying to a
579         subsequent request. But if the response is stale, all caches
580         &MUST; first revalidate it with the origin server, using the
581         header fields from the new request to allow the origin server
582         to authenticate the new request.</t>
583
584      <t>If the response includes the "public" cache-control directive,
585         it &MAY; be returned in reply to any subsequent request.</t>
586  </list>
587</t>
588</section>
589
590<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
591  <iref primary="true" item="Proxy-Authenticate header field" x:for-anchor=""/>
592  <iref primary="true" item="Header Fields" subitem="Proxy-Authenticate" x:for-anchor=""/>
593  <x:anchor-alias value="Proxy-Authenticate"/>
594<t>
595   The "Proxy-Authenticate" header field consists of a challenge that
596   indicates the authentication scheme and parameters applicable to the proxy
597   for this effective request URI (&effective-request-uri;). It &MUST; be included as part
598   of a 407 (Proxy Authentication Required) response.
599</t>
600<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
601  <x:ref>Proxy-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
602</artwork></figure>
603<t>
604   Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to
605   the current connection and &SHOULD-NOT;  be passed on to downstream
606   clients. However, an intermediate proxy might need to obtain its own
607   credentials by requesting them from the downstream client, which in
608   some circumstances will appear as if the proxy is forwarding the
609   Proxy-Authenticate header field.
610</t>
611</section>
612
613<section title="Proxy-Authorization" anchor="header.proxy-authorization">
614  <iref primary="true" item="Proxy-Authorization header field" x:for-anchor=""/>
615  <iref primary="true" item="Header Fields" subitem="Proxy-Authorization" x:for-anchor=""/>
616  <x:anchor-alias value="Proxy-Authorization"/>
617<t>
618   The "Proxy-Authorization" header field allows the client to
619   identify itself (or its user) to a proxy which requires
620   authentication. Its value consists of
621   credentials containing the authentication information of the user
622   agent for the proxy and/or realm of the resource being requested.
623</t>
624<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
625  <x:ref>Proxy-Authorization</x:ref> = <x:ref>credentials</x:ref>
626</artwork></figure>
627<t>
628   Unlike Authorization, the Proxy-Authorization header field applies only to
629   the next outbound proxy that demanded authentication using the Proxy-Authenticate
630   field. When multiple proxies are used in a chain, the
631   Proxy-Authorization header field is consumed by the first outbound
632   proxy that was expecting to receive credentials. A proxy &MAY; relay
633   the credentials from the client request to the next proxy if that is
634   the mechanism by which the proxies cooperatively authenticate a given
635   request.
636</t>
637</section>
638
639<section title="WWW-Authenticate" anchor="header.www-authenticate">
640  <iref primary="true" item="WWW-Authenticate header field" x:for-anchor=""/>
641  <iref primary="true" item="Header Fields" subitem="WWW-Authenticate" x:for-anchor=""/>
642  <x:anchor-alias value="WWW-Authenticate"/>
643<t>
644   The "WWW-Authenticate" header field consists of at least one
645   challenge that indicates the authentication scheme(s) and parameters
646   applicable to the effective request URI (&effective-request-uri;).
647</t>
648<t>   
649   It &MUST; be included in 401 (Unauthorized) response messages and &MAY; be
650   included in other response messages to indicate that supplying credentials
651   (or different credentials) might affect the response.
652</t>
653<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
654  <x:ref>WWW-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
655</artwork></figure>
656<t>
657   User agents are advised to take special care in parsing the WWW-Authenticate
658   field value as it might contain more than one challenge,
659   or if more than one WWW-Authenticate header field is provided, the
660   contents of a challenge itself can contain a comma-separated list of
661   authentication parameters.
662</t>
663</section>
664
665</section>
666
667<section title="IANA Considerations" anchor="IANA.considerations">
668
669<section title="Authenticaton Scheme Registry" anchor="authentication.scheme.registration">
670<t>
671  The registration procedure for HTTP Authentication Schemes is defined by
672  <xref target="authentication.scheme.registry"/> of this document.
673</t>
674<t>
675   The HTTP Method Authentication Scheme shall be created at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
676</t>
677</section>
678
679<section title="Status Code Registration" anchor="status.code.registration">
680<t>
681   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
682   shall be updated with the registrations below:
683</t>
684<?BEGININC p7-auth.iana-status-codes ?>
685<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
686<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
687   <ttcol>Value</ttcol>
688   <ttcol>Description</ttcol>
689   <ttcol>Reference</ttcol>
690   <c>401</c>
691   <c>Unauthorized</c>
692   <c>
693      <xref target="status.401"/>
694   </c>
695   <c>407</c>
696   <c>Proxy Authentication Required</c>
697   <c>
698      <xref target="status.407"/>
699   </c>
700</texttable>
701<!--(END)-->
702<?ENDINC p7-auth.iana-status-codes ?>
703</section>
704
705<section title="Header Field Registration" anchor="header.field.registration">
706<t>
707   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
708   with the permanent registrations below (see <xref target="RFC3864"/>):
709</t>
710<?BEGININC p7-auth.iana-headers ?>
711<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
712<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
713   <ttcol>Header Field Name</ttcol>
714   <ttcol>Protocol</ttcol>
715   <ttcol>Status</ttcol>
716   <ttcol>Reference</ttcol>
717
718   <c>Authorization</c>
719   <c>http</c>
720   <c>standard</c>
721   <c>
722      <xref target="header.authorization"/>
723   </c>
724   <c>Proxy-Authenticate</c>
725   <c>http</c>
726   <c>standard</c>
727   <c>
728      <xref target="header.proxy-authenticate"/>
729   </c>
730   <c>Proxy-Authorization</c>
731   <c>http</c>
732   <c>standard</c>
733   <c>
734      <xref target="header.proxy-authorization"/>
735   </c>
736   <c>WWW-Authenticate</c>
737   <c>http</c>
738   <c>standard</c>
739   <c>
740      <xref target="header.www-authenticate"/>
741   </c>
742</texttable>
743<!--(END)-->
744<?ENDINC p7-auth.iana-headers ?>
745<t>
746   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
747</t>
748</section>
749</section>
750
751<section title="Security Considerations" anchor="security.considerations">
752<t>
753   This section is meant to inform application developers, information
754   providers, and users of the security limitations in HTTP/1.1 as
755   described by this document. The discussion does not include
756   definitive solutions to the problems revealed, though it does make
757   some suggestions for reducing security risks.
758</t>
759
760<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
761<t>
762   Existing HTTP clients and user agents typically retain authentication
763   information indefinitely. HTTP/1.1 does not provide a method for a
764   server to direct clients to discard these cached credentials. This is
765   a significant defect that requires further extensions to HTTP.
766   Circumstances under which credential caching can interfere with the
767   application's security model include but are not limited to:
768  <list style="symbols">
769     <t>Clients which have been idle for an extended period following
770        which the server might wish to cause the client to reprompt the
771        user for credentials.</t>
772
773     <t>Applications which include a session termination indication
774        (such as a "logout" or "commit" button on a page) after which
775        the server side of the application "knows" that there is no
776        further reason for the client to retain the credentials.</t>
777  </list>
778</t>
779<t>
780   This is currently under separate study. There are a number of work-arounds
781   to parts of this problem, and we encourage the use of
782   password protection in screen savers, idle time-outs, and other
783   methods which mitigate the security problems inherent in this
784   problem. In particular, user agents which cache credentials are
785   encouraged to provide a readily accessible mechanism for discarding
786   cached credentials under user control.
787</t>
788</section>
789</section>
790
791<section title="Acknowledgments" anchor="acks">
792<t>
793  This specification takes over the definition of the HTTP Authentication
794  Framework, previously defined in <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
795  We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence,
796  Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for their work
797  on that specification. See <xref target="RFC2617" x:format="of" x:sec="6"/>
798  for further acknowledgements. 
799</t>
800<t>
801  See &acks; for the Acknowledgments related to this document revision.
802</t>
803</section>
804</middle>
805
806<back>
807
808<references title="Normative References">
809
810<reference anchor="Part1">
811  <front>
812    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
813    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
814      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
815      <address><email>fielding@gbiv.com</email></address>
816    </author>
817    <author initials="J." surname="Gettys" fullname="Jim Gettys">
818      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
819      <address><email>jg@freedesktop.org</email></address>
820    </author>
821    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
822      <organization abbrev="HP">Hewlett-Packard Company</organization>
823      <address><email>JeffMogul@acm.org</email></address>
824    </author>
825    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
826      <organization abbrev="Microsoft">Microsoft Corporation</organization>
827      <address><email>henrikn@microsoft.com</email></address>
828    </author>
829    <author initials="L." surname="Masinter" fullname="Larry Masinter">
830      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
831      <address><email>LMM@acm.org</email></address>
832    </author>
833    <author initials="P." surname="Leach" fullname="Paul J. Leach">
834      <organization abbrev="Microsoft">Microsoft Corporation</organization>
835      <address><email>paulle@microsoft.com</email></address>
836    </author>
837    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
838      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
839      <address><email>timbl@w3.org</email></address>
840    </author>
841    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
842      <organization abbrev="W3C">World Wide Web Consortium</organization>
843      <address><email>ylafon@w3.org</email></address>
844    </author>
845    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
846      <organization abbrev="greenbytes">greenbytes GmbH</organization>
847      <address><email>julian.reschke@greenbytes.de</email></address>
848    </author>
849    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
850  </front>
851  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
852  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
853</reference>
854
855<reference anchor="Part6">
856  <front>
857    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
858    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
859      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
860      <address><email>fielding@gbiv.com</email></address>
861    </author>
862    <author initials="J." surname="Gettys" fullname="Jim Gettys">
863      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
864      <address><email>jg@freedesktop.org</email></address>
865    </author>
866    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
867      <organization abbrev="HP">Hewlett-Packard Company</organization>
868      <address><email>JeffMogul@acm.org</email></address>
869    </author>
870    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
871      <organization abbrev="Microsoft">Microsoft Corporation</organization>
872      <address><email>henrikn@microsoft.com</email></address>
873    </author>
874    <author initials="L." surname="Masinter" fullname="Larry Masinter">
875      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
876      <address><email>LMM@acm.org</email></address>
877    </author>
878    <author initials="P." surname="Leach" fullname="Paul J. Leach">
879      <organization abbrev="Microsoft">Microsoft Corporation</organization>
880      <address><email>paulle@microsoft.com</email></address>
881    </author>
882    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
883      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
884      <address><email>timbl@w3.org</email></address>
885    </author>
886    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
887      <organization abbrev="W3C">World Wide Web Consortium</organization>
888      <address><email>ylafon@w3.org</email></address>
889    </author>
890    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
891      <address><email>mnot@mnot.net</email></address>
892    </author>
893    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
894      <organization abbrev="greenbytes">greenbytes GmbH</organization>
895      <address><email>julian.reschke@greenbytes.de</email></address>
896    </author>
897    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
898  </front>
899  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
900  <x:source href="p6-cache.xml" basename="p6-cache"/>
901</reference>
902
903<reference anchor="RFC2119">
904  <front>
905    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
906    <author initials="S." surname="Bradner" fullname="Scott Bradner">
907      <organization>Harvard University</organization>
908      <address><email>sob@harvard.edu</email></address>
909    </author>
910    <date month="March" year="1997"/>
911  </front>
912  <seriesInfo name="BCP" value="14"/>
913  <seriesInfo name="RFC" value="2119"/>
914</reference>
915
916<reference anchor="RFC5234">
917  <front>
918    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
919    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
920      <organization>Brandenburg InternetWorking</organization>
921      <address>
922        <email>dcrocker@bbiw.net</email>
923      </address> 
924    </author>
925    <author initials="P." surname="Overell" fullname="Paul Overell">
926      <organization>THUS plc.</organization>
927      <address>
928        <email>paul.overell@thus.net</email>
929      </address>
930    </author>
931    <date month="January" year="2008"/>
932  </front>
933  <seriesInfo name="STD" value="68"/>
934  <seriesInfo name="RFC" value="5234"/>
935</reference>
936
937</references>
938
939<references title="Informative References">
940
941<reference anchor="RFC2616">
942  <front>
943    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
944    <author initials="R." surname="Fielding" fullname="R. Fielding">
945      <organization>University of California, Irvine</organization>
946      <address><email>fielding@ics.uci.edu</email></address>
947    </author>
948    <author initials="J." surname="Gettys" fullname="J. Gettys">
949      <organization>W3C</organization>
950      <address><email>jg@w3.org</email></address>
951    </author>
952    <author initials="J." surname="Mogul" fullname="J. Mogul">
953      <organization>Compaq Computer Corporation</organization>
954      <address><email>mogul@wrl.dec.com</email></address>
955    </author>
956    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
957      <organization>MIT Laboratory for Computer Science</organization>
958      <address><email>frystyk@w3.org</email></address>
959    </author>
960    <author initials="L." surname="Masinter" fullname="L. Masinter">
961      <organization>Xerox Corporation</organization>
962      <address><email>masinter@parc.xerox.com</email></address>
963    </author>
964    <author initials="P." surname="Leach" fullname="P. Leach">
965      <organization>Microsoft Corporation</organization>
966      <address><email>paulle@microsoft.com</email></address>
967    </author>
968    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
969      <organization>W3C</organization>
970      <address><email>timbl@w3.org</email></address>
971    </author>
972    <date month="June" year="1999"/>
973  </front>
974  <seriesInfo name="RFC" value="2616"/>
975</reference>
976
977<reference anchor="RFC2617">
978  <front>
979    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
980    <author initials="J." surname="Franks" fullname="John Franks">
981      <organization>Northwestern University, Department of Mathematics</organization>
982      <address><email>john@math.nwu.edu</email></address>
983    </author>
984    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
985      <organization>Verisign Inc.</organization>
986      <address><email>pbaker@verisign.com</email></address>
987    </author>
988    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
989      <organization>AbiSource, Inc.</organization>
990      <address><email>jeff@AbiSource.com</email></address>
991    </author>
992    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
993      <organization>Agranat Systems, Inc.</organization>
994      <address><email>lawrence@agranat.com</email></address>
995    </author>
996    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
997      <organization>Microsoft Corporation</organization>
998      <address><email>paulle@microsoft.com</email></address>
999    </author>
1000    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
1001      <organization>Netscape Communications Corporation</organization>
1002    </author>
1003    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
1004      <organization>Open Market, Inc.</organization>
1005      <address><email>stewart@OpenMarket.com</email></address>
1006    </author>
1007    <date month="June" year="1999"/>
1008  </front>
1009  <seriesInfo name="RFC" value="2617"/>
1010</reference>
1011
1012<reference anchor='RFC3864'>
1013  <front>
1014    <title>Registration Procedures for Message Header Fields</title>
1015    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
1016      <organization>Nine by Nine</organization>
1017      <address><email>GK-IETF@ninebynine.org</email></address>
1018    </author>
1019    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
1020      <organization>BEA Systems</organization>
1021      <address><email>mnot@pobox.com</email></address>
1022    </author>
1023    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
1024      <organization>HP Labs</organization>
1025      <address><email>JeffMogul@acm.org</email></address>
1026    </author>
1027    <date year='2004' month='September' />
1028  </front>
1029  <seriesInfo name='BCP' value='90' />
1030  <seriesInfo name='RFC' value='3864' />
1031</reference>
1032
1033<reference anchor='RFC5226'>
1034  <front>
1035    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
1036    <author initials='T.' surname='Narten' fullname='T. Narten'>
1037      <organization>IBM</organization>
1038      <address><email>narten@us.ibm.com</email></address>
1039    </author>
1040    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
1041      <organization>Google</organization>
1042      <address><email>Harald@Alvestrand.no</email></address>
1043    </author>
1044    <date year='2008' month='May' />
1045  </front>
1046  <seriesInfo name='BCP' value='26' />
1047  <seriesInfo name='RFC' value='5226' />
1048</reference>
1049
1050</references>
1051
1052<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1053<t>
1054  Change ABNF productions for header fields to only define the field value.
1055  (<xref target="header.fields"/>)
1056</t>
1057</section>
1058 
1059<?BEGININC p7-auth.abnf-appendix ?>
1060<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1061<figure>
1062<artwork type="abnf" name="p7-auth.parsed-abnf">
1063<x:ref>Authorization</x:ref> = credentials
1064
1065<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1066
1067<x:ref>Proxy-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS
1068 challenge ] )
1069<x:ref>Proxy-Authorization</x:ref> = credentials
1070
1071<x:ref>WWW-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
1072 ] )
1073
1074<x:ref>auth-param</x:ref> = token "=" ( token / quoted-string )
1075<x:ref>auth-scheme</x:ref> = token
1076
1077<x:ref>challenge</x:ref> = auth-scheme 1*SP *( "," OWS ) auth-param *( OWS "," [ OWS
1078 auth-param ] )
1079<x:ref>credentials</x:ref> = auth-scheme ( token / quoted-string / [ ( "," /
1080 auth-param ) *( OWS "," [ OWS auth-param ] ) ] )
1081
1082<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1083
1084realm = "realm=" realm-value
1085realm-value = quoted-string
1086
1087<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1088</artwork>
1089</figure>
1090<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
1091; Authorization defined but not used
1092; Proxy-Authenticate defined but not used
1093; Proxy-Authorization defined but not used
1094; WWW-Authenticate defined but not used
1095; realm defined but not used
1096</artwork></figure></section>
1097<?ENDINC p7-auth.abnf-appendix ?>
1098
1099<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
1100
1101<section title="Since RFC 2616">
1102<t>
1103  Extracted relevant partitions from <xref target="RFC2616"/>.
1104</t>
1105</section>
1106
1107<section title="Since draft-ietf-httpbis-p7-auth-00">
1108<t>
1109  Closed issues:
1110  <list style="symbols"> 
1111    <t>
1112      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
1113      "Normative and Informative references"
1114    </t>
1115  </list>
1116</t>
1117</section>
1118
1119<section title="Since draft-ietf-httpbis-p7-auth-01">
1120<t>
1121  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1122  <list style="symbols"> 
1123    <t>
1124      Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.
1125    </t>
1126    <t>
1127      Add explicit references to BNF syntax and rules imported from other parts of the specification.
1128    </t>
1129  </list>
1130</t>
1131</section>
1132
1133<section title="Since draft-ietf-httpbis-p7-auth-02" anchor="changes.since.02">
1134<t>
1135  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
1136  <list style="symbols"> 
1137    <t>
1138      Reference RFC 3984, and update header field registrations for header fields defined
1139      in this document.
1140    </t>
1141  </list>
1142</t>
1143</section>
1144
1145<section title="Since draft-ietf-httpbis-p7-auth-03" anchor="changes.since.03">
1146<t>
1147</t>
1148</section>
1149
1150<section title="Since draft-ietf-httpbis-p7-auth-04" anchor="changes.since.04">
1151<t>
1152  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1153  <list style="symbols"> 
1154    <t>
1155      Use "/" instead of "|" for alternatives.
1156    </t>
1157    <t>
1158      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
1159      whitespace ("OWS") and required whitespace ("RWS").
1160    </t>
1161    <t>
1162      Rewrite ABNFs to spell out whitespace rules, factor out
1163      header field value format definitions.
1164    </t>
1165  </list>
1166</t>
1167</section>
1168
1169<section title="Since draft-ietf-httpbis-p7-auth-05" anchor="changes.since.05">
1170<t>
1171  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1172  <list style="symbols"> 
1173    <t>
1174      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
1175    </t>
1176  </list>
1177</t>
1178</section>
1179
1180<section title="Since draft-ietf-httpbis-p7-auth-06" anchor="changes.since.06">
1181<t>
1182  None.
1183</t>
1184</section>
1185
1186<section title="Since draft-ietf-httpbis-p7-auth-07" anchor="changes.since.07">
1187<t>
1188  Closed issues:
1189  <list style="symbols"> 
1190    <t>
1191      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/198"/>:
1192      "move IANA registrations for optional status codes"
1193    </t>
1194  </list>
1195</t>
1196</section>
1197
1198<section title="Since draft-ietf-httpbis-p7-auth-08" anchor="changes.since.08">
1199<t>
1200  No significant changes.
1201</t>
1202</section>
1203
1204<section title="Since draft-ietf-httpbis-p7-auth-09" anchor="changes.since.09">
1205<t>
1206  Partly resolved issues:
1207  <list style="symbols"> 
1208    <t>
1209      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
1210      "Term for the requested resource's URI"
1211    </t>
1212  </list>
1213</t>
1214</section>
1215
1216<section title="Since draft-ietf-httpbis-p7-auth-10" anchor="changes.since.10">
1217<t>
1218  None.
1219</t>
1220</section>
1221
1222<section title="Since draft-ietf-httpbis-p7-auth-11" anchor="changes.since.11">
1223<t>
1224  Closed issues:
1225  <list style="symbols"> 
1226    <t>
1227      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/130"/>:
1228      "introduction to part 7 is work-in-progress"
1229    </t>
1230    <t>
1231      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/195"/>:
1232      "auth-param syntax"
1233    </t>
1234    <t>
1235      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
1236      "Header Classification"
1237    </t>
1238    <t>
1239      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/237"/>:
1240      "absorbing the auth framework from 2617"
1241    </t>
1242  </list>
1243</t>
1244<t>
1245  Partly resolved issues:
1246  <list style="symbols"> 
1247    <t>
1248      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/141"/>:
1249      "should we have an auth scheme registry"
1250    </t>
1251  </list>
1252</t>
1253</section>
1254
1255<section title="Since draft-ietf-httpbis-p7-auth-12" anchor="changes.since.12">
1256<t>
1257  None.
1258</t>
1259</section>
1260
1261<section title="Since draft-ietf-httpbis-p7-auth-13" anchor="changes.since.13">
1262<t>
1263  Closed issues:
1264  <list style="symbols">
1265    <t>
1266      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
1267      "untangle ABNFs for header fields"
1268    </t>
1269  </list>
1270</t>
1271</section>
1272
1273<section title="Since draft-ietf-httpbis-p7-auth-14" anchor="changes.since.14">
1274<t>
1275  None.
1276</t>
1277</section>
1278
1279<section title="Since draft-ietf-httpbis-p7-auth-15" anchor="changes.since.15">
1280<t>
1281  Closed issues:
1282  <list style="symbols">
1283    <t>
1284      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/78"/>:
1285      "Relationship between 401, Authorization and WWW-Authenticate"
1286    </t>
1287    <t>
1288      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/177"/>:
1289      "Realm required on challenges"
1290    </t>
1291    <t>
1292      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/257"/>:
1293      "Considerations for new authentications schemes"
1294    </t>
1295  </list>
1296</t>
1297</section>
1298
1299</section>
1300
1301</back>
1302</rfc>
Note: See TracBrowser for help on using the repository browser.