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

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

Remove header field classifications.

Addresses #224 and #104

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