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

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

bump up document dates

  • Property svn:eol-style set to native
File size: 47.0 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 "April">
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.13"/>.
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<t>
470   The "Authorization" header field allows a user agent to authenticate
471   itself with a server &mdash; usually, but not necessarily, after receiving a 401
472   (Unauthorized) response. Its value consists of credentials containing
473   information of the user agent for the realm of the resource being
474   requested.
475</t>
476<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
477  <x:ref>Authorization</x:ref> = <x:ref>credentials</x:ref>
478</artwork></figure>
479<t>
480   If a request is
481   authenticated and a realm specified, the same credentials &SHOULD;
482   be valid for all other requests within this realm (assuming that
483   the authentication scheme itself does not require otherwise, such
484   as credentials that vary according to a challenge value or using
485   synchronized clocks).
486</t>
487<t>
488      When a shared cache (see &shared-and-non-shared-caches;) receives a request
489      containing an Authorization field, it &MUST-NOT; return the
490      corresponding response as a reply to any other request, unless one
491      of the following specific exceptions holds:
492</t>
493<t>
494  <list style="numbers">
495      <t>If the response includes the "s-maxage" cache-control
496         directive, the cache &MAY; use that response in replying to a
497         subsequent request. But (if the specified maximum age has
498         passed) a proxy cache &MUST; first revalidate it with the origin
499         server, using the header fields from the new request to allow
500         the origin server to authenticate the new request. (This is the
501         defined behavior for s-maxage.) If the response includes "s-maxage=0",
502         the proxy &MUST; always revalidate it before re-using
503         it.</t>
504
505      <t>If the response includes the "must-revalidate" cache-control
506         directive, the cache &MAY; use that response in replying to a
507         subsequent request. But if the response is stale, all caches
508         &MUST; first revalidate it with the origin server, using the
509         header fields from the new request to allow the origin server
510         to authenticate the new request.</t>
511
512      <t>If the response includes the "public" cache-control directive,
513         it &MAY; be returned in reply to any subsequent request.</t>
514  </list>
515</t>
516</section>
517
518<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
519  <iref primary="true" item="Proxy-Authenticate header field" x:for-anchor=""/>
520  <iref primary="true" item="Header Fields" subitem="Proxy-Authenticate" x:for-anchor=""/>
521  <x:anchor-alias value="Proxy-Authenticate"/>
522<t>
523   The "Proxy-Authenticate" header field consists of a challenge that
524   indicates the authentication scheme and parameters applicable to the proxy
525   for this effective request URI (&effective-request-uri;). It &MUST; be included as part
526   of a 407 (Proxy Authentication Required) response.
527</t>
528<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
529  <x:ref>Proxy-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
530</artwork></figure>
531<t>
532   Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to
533   the current connection and &SHOULD-NOT;  be passed on to downstream
534   clients. However, an intermediate proxy might need to obtain its own
535   credentials by requesting them from the downstream client, which in
536   some circumstances will appear as if the proxy is forwarding the
537   Proxy-Authenticate header field.
538</t>
539</section>
540
541<section title="Proxy-Authorization" anchor="header.proxy-authorization">
542  <iref primary="true" item="Proxy-Authorization header field" x:for-anchor=""/>
543  <iref primary="true" item="Header Fields" subitem="Proxy-Authorization" x:for-anchor=""/>
544  <x:anchor-alias value="Proxy-Authorization"/>
545<t>
546   The "Proxy-Authorization" header field allows the client to
547   identify itself (or its user) to a proxy which requires
548   authentication. Its value consists of
549   credentials containing the authentication information of the user
550   agent for the proxy and/or realm of the resource being requested.
551</t>
552<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
553  <x:ref>Proxy-Authorization</x:ref> = <x:ref>credentials</x:ref>
554</artwork></figure>
555<t>
556   Unlike Authorization, the Proxy-Authorization header field applies only to
557   the next outbound proxy that demanded authentication using the Proxy-Authenticate
558   field. When multiple proxies are used in a chain, the
559   Proxy-Authorization header field is consumed by the first outbound
560   proxy that was expecting to receive credentials. A proxy &MAY; relay
561   the credentials from the client request to the next proxy if that is
562   the mechanism by which the proxies cooperatively authenticate a given
563   request.
564</t>
565</section>
566
567<section title="WWW-Authenticate" anchor="header.www-authenticate">
568  <iref primary="true" item="WWW-Authenticate header field" x:for-anchor=""/>
569  <iref primary="true" item="Header Fields" subitem="WWW-Authenticate" x:for-anchor=""/>
570  <x:anchor-alias value="WWW-Authenticate"/>
571<t>
572   The "WWW-Authenticate" header field consists of at least one
573   challenge that indicates the authentication scheme(s) and parameters
574   applicable to the effective request URI (&effective-request-uri;). It &MUST; be included in 401
575   (Unauthorized) response messages.
576</t>
577<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
578  <x:ref>WWW-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
579</artwork></figure>
580<t>
581   User agents are advised to take special care in parsing the WWW-Authenticate
582   field value as it might contain more than one challenge,
583   or if more than one WWW-Authenticate header field is provided, the
584   contents of a challenge itself can contain a comma-separated list of
585   authentication parameters.
586</t>
587</section>
588
589</section>
590
591<section title="IANA Considerations" anchor="IANA.considerations">
592
593<section title="Authenticaton Scheme Registry" anchor="authentication.scheme.registration">
594<t>
595  The registration procedure for HTTP Authentication Schemes is defined by
596  <xref target="authentication.scheme.registry"/> of this document.
597</t>
598<t>
599   The HTTP Method Authentication Scheme shall be created at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
600</t>
601</section>
602
603<section title="Status Code Registration" anchor="status.code.registration">
604<t>
605   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
606   shall be updated with the registrations below:
607</t>
608<?BEGININC p7-auth.iana-status-codes ?>
609<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
610<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
611   <ttcol>Value</ttcol>
612   <ttcol>Description</ttcol>
613   <ttcol>Reference</ttcol>
614   <c>401</c>
615   <c>Unauthorized</c>
616   <c>
617      <xref target="status.401"/>
618   </c>
619   <c>407</c>
620   <c>Proxy Authentication Required</c>
621   <c>
622      <xref target="status.407"/>
623   </c>
624</texttable>
625<!--(END)-->
626<?ENDINC p7-auth.iana-status-codes ?>
627</section>
628
629<section title="Header Field Registration" anchor="header.field.registration">
630<t>
631   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
632   with the permanent registrations below (see <xref target="RFC3864"/>):
633</t>
634<?BEGININC p7-auth.iana-headers ?>
635<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
636<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
637   <ttcol>Header Field Name</ttcol>
638   <ttcol>Protocol</ttcol>
639   <ttcol>Status</ttcol>
640   <ttcol>Reference</ttcol>
641
642   <c>Authorization</c>
643   <c>http</c>
644   <c>standard</c>
645   <c>
646      <xref target="header.authorization"/>
647   </c>
648   <c>Proxy-Authenticate</c>
649   <c>http</c>
650   <c>standard</c>
651   <c>
652      <xref target="header.proxy-authenticate"/>
653   </c>
654   <c>Proxy-Authorization</c>
655   <c>http</c>
656   <c>standard</c>
657   <c>
658      <xref target="header.proxy-authorization"/>
659   </c>
660   <c>WWW-Authenticate</c>
661   <c>http</c>
662   <c>standard</c>
663   <c>
664      <xref target="header.www-authenticate"/>
665   </c>
666</texttable>
667<!--(END)-->
668<?ENDINC p7-auth.iana-headers ?>
669<t>
670   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
671</t>
672</section>
673</section>
674
675<section title="Security Considerations" anchor="security.considerations">
676<t>
677   This section is meant to inform application developers, information
678   providers, and users of the security limitations in HTTP/1.1 as
679   described by this document. The discussion does not include
680   definitive solutions to the problems revealed, though it does make
681   some suggestions for reducing security risks.
682</t>
683
684<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
685<t>
686   Existing HTTP clients and user agents typically retain authentication
687   information indefinitely. HTTP/1.1 does not provide a method for a
688   server to direct clients to discard these cached credentials. This is
689   a significant defect that requires further extensions to HTTP.
690   Circumstances under which credential caching can interfere with the
691   application's security model include but are not limited to:
692  <list style="symbols">
693     <t>Clients which have been idle for an extended period following
694        which the server might wish to cause the client to reprompt the
695        user for credentials.</t>
696
697     <t>Applications which include a session termination indication
698        (such as a "logout" or "commit" button on a page) after which
699        the server side of the application "knows" that there is no
700        further reason for the client to retain the credentials.</t>
701  </list>
702</t>
703<t>
704   This is currently under separate study. There are a number of work-arounds
705   to parts of this problem, and we encourage the use of
706   password protection in screen savers, idle time-outs, and other
707   methods which mitigate the security problems inherent in this
708   problem. In particular, user agents which cache credentials are
709   encouraged to provide a readily accessible mechanism for discarding
710   cached credentials under user control.
711</t>
712</section>
713</section>
714
715<section title="Acknowledgments" anchor="ack">
716<t>
717  This specification takes over the definition of the HTTP Authentication
718  Framework, previously defined in <xref target="RFC2616" x:fmt="none">RFC 2617</xref>. We thank to John Franks,
719  Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence,
720  Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for their work
721  on that specification.
722</t>
723<t>
724  <cref anchor="acks">HTTPbis acknowledgements.</cref>
725</t>
726</section>
727</middle>
728
729<back>
730
731<references title="Normative References">
732
733<reference anchor="Part1">
734  <front>
735    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
736    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
737      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
738      <address><email>fielding@gbiv.com</email></address>
739    </author>
740    <author initials="J." surname="Gettys" fullname="Jim Gettys">
741      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
742      <address><email>jg@freedesktop.org</email></address>
743    </author>
744    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
745      <organization abbrev="HP">Hewlett-Packard Company</organization>
746      <address><email>JeffMogul@acm.org</email></address>
747    </author>
748    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
749      <organization abbrev="Microsoft">Microsoft Corporation</organization>
750      <address><email>henrikn@microsoft.com</email></address>
751    </author>
752    <author initials="L." surname="Masinter" fullname="Larry Masinter">
753      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
754      <address><email>LMM@acm.org</email></address>
755    </author>
756    <author initials="P." surname="Leach" fullname="Paul J. Leach">
757      <organization abbrev="Microsoft">Microsoft Corporation</organization>
758      <address><email>paulle@microsoft.com</email></address>
759    </author>
760    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
761      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
762      <address><email>timbl@w3.org</email></address>
763    </author>
764    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
765      <organization abbrev="W3C">World Wide Web Consortium</organization>
766      <address><email>ylafon@w3.org</email></address>
767    </author>
768    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
769      <organization abbrev="greenbytes">greenbytes GmbH</organization>
770      <address><email>julian.reschke@greenbytes.de</email></address>
771    </author>
772    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
773  </front>
774  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
775  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
776</reference>
777
778<reference anchor="Part6">
779  <front>
780    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
781    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
782      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
783      <address><email>fielding@gbiv.com</email></address>
784    </author>
785    <author initials="J." surname="Gettys" fullname="Jim Gettys">
786      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
787      <address><email>jg@freedesktop.org</email></address>
788    </author>
789    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
790      <organization abbrev="HP">Hewlett-Packard Company</organization>
791      <address><email>JeffMogul@acm.org</email></address>
792    </author>
793    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
794      <organization abbrev="Microsoft">Microsoft Corporation</organization>
795      <address><email>henrikn@microsoft.com</email></address>
796    </author>
797    <author initials="L." surname="Masinter" fullname="Larry Masinter">
798      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
799      <address><email>LMM@acm.org</email></address>
800    </author>
801    <author initials="P." surname="Leach" fullname="Paul J. Leach">
802      <organization abbrev="Microsoft">Microsoft Corporation</organization>
803      <address><email>paulle@microsoft.com</email></address>
804    </author>
805    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
806      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
807      <address><email>timbl@w3.org</email></address>
808    </author>
809    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
810      <organization abbrev="W3C">World Wide Web Consortium</organization>
811      <address><email>ylafon@w3.org</email></address>
812    </author>
813    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
814      <address><email>mnot@mnot.net</email></address>
815    </author>
816    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
817      <organization abbrev="greenbytes">greenbytes GmbH</organization>
818      <address><email>julian.reschke@greenbytes.de</email></address>
819    </author>
820    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
821  </front>
822  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
823  <x:source href="p6-cache.xml" basename="p6-cache"/>
824</reference>
825
826<reference anchor="RFC2119">
827  <front>
828    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
829    <author initials="S." surname="Bradner" fullname="Scott Bradner">
830      <organization>Harvard University</organization>
831      <address><email>sob@harvard.edu</email></address>
832    </author>
833    <date month="March" year="1997"/>
834  </front>
835  <seriesInfo name="BCP" value="14"/>
836  <seriesInfo name="RFC" value="2119"/>
837</reference>
838
839<reference anchor="RFC5234">
840  <front>
841    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
842    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
843      <organization>Brandenburg InternetWorking</organization>
844      <address>
845        <email>dcrocker@bbiw.net</email>
846      </address> 
847    </author>
848    <author initials="P." surname="Overell" fullname="Paul Overell">
849      <organization>THUS plc.</organization>
850      <address>
851        <email>paul.overell@thus.net</email>
852      </address>
853    </author>
854    <date month="January" year="2008"/>
855  </front>
856  <seriesInfo name="STD" value="68"/>
857  <seriesInfo name="RFC" value="5234"/>
858</reference>
859
860</references>
861
862<references title="Informative References">
863
864<reference anchor="RFC2616">
865  <front>
866    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
867    <author initials="R." surname="Fielding" fullname="R. Fielding">
868      <organization>University of California, Irvine</organization>
869      <address><email>fielding@ics.uci.edu</email></address>
870    </author>
871    <author initials="J." surname="Gettys" fullname="J. Gettys">
872      <organization>W3C</organization>
873      <address><email>jg@w3.org</email></address>
874    </author>
875    <author initials="J." surname="Mogul" fullname="J. Mogul">
876      <organization>Compaq Computer Corporation</organization>
877      <address><email>mogul@wrl.dec.com</email></address>
878    </author>
879    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
880      <organization>MIT Laboratory for Computer Science</organization>
881      <address><email>frystyk@w3.org</email></address>
882    </author>
883    <author initials="L." surname="Masinter" fullname="L. Masinter">
884      <organization>Xerox Corporation</organization>
885      <address><email>masinter@parc.xerox.com</email></address>
886    </author>
887    <author initials="P." surname="Leach" fullname="P. Leach">
888      <organization>Microsoft Corporation</organization>
889      <address><email>paulle@microsoft.com</email></address>
890    </author>
891    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
892      <organization>W3C</organization>
893      <address><email>timbl@w3.org</email></address>
894    </author>
895    <date month="June" year="1999"/>
896  </front>
897  <seriesInfo name="RFC" value="2616"/>
898</reference>
899
900<reference anchor="RFC2617">
901  <front>
902    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
903    <author initials="J." surname="Franks" fullname="John Franks">
904      <organization>Northwestern University, Department of Mathematics</organization>
905      <address><email>john@math.nwu.edu</email></address>
906    </author>
907    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
908      <organization>Verisign Inc.</organization>
909      <address><email>pbaker@verisign.com</email></address>
910    </author>
911    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
912      <organization>AbiSource, Inc.</organization>
913      <address><email>jeff@AbiSource.com</email></address>
914    </author>
915    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
916      <organization>Agranat Systems, Inc.</organization>
917      <address><email>lawrence@agranat.com</email></address>
918    </author>
919    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
920      <organization>Microsoft Corporation</organization>
921      <address><email>paulle@microsoft.com</email></address>
922    </author>
923    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
924      <organization>Netscape Communications Corporation</organization>
925    </author>
926    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
927      <organization>Open Market, Inc.</organization>
928      <address><email>stewart@OpenMarket.com</email></address>
929    </author>
930    <date month="June" year="1999"/>
931  </front>
932  <seriesInfo name="RFC" value="2617"/>
933</reference>
934
935<reference anchor='RFC3864'>
936  <front>
937    <title>Registration Procedures for Message Header Fields</title>
938    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
939      <organization>Nine by Nine</organization>
940      <address><email>GK-IETF@ninebynine.org</email></address>
941    </author>
942    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
943      <organization>BEA Systems</organization>
944      <address><email>mnot@pobox.com</email></address>
945    </author>
946    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
947      <organization>HP Labs</organization>
948      <address><email>JeffMogul@acm.org</email></address>
949    </author>
950    <date year='2004' month='September' />
951  </front>
952  <seriesInfo name='BCP' value='90' />
953  <seriesInfo name='RFC' value='3864' />
954</reference>
955
956<reference anchor='RFC5226'>
957  <front>
958    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
959    <author initials='T.' surname='Narten' fullname='T. Narten'>
960      <organization>IBM</organization>
961      <address><email>narten@us.ibm.com</email></address>
962    </author>
963    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
964      <organization>Google</organization>
965      <address><email>Harald@Alvestrand.no</email></address>
966    </author>
967    <date year='2008' month='May' />
968  </front>
969  <seriesInfo name='BCP' value='26' />
970  <seriesInfo name='RFC' value='5226' />
971</reference>
972
973</references>
974
975<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
976<t>
977  Change ABNF productions for header fields to only define the field value.
978  (<xref target="header.fields"/>)
979</t>
980</section>
981 
982<?BEGININC p7-auth.abnf-appendix ?>
983<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
984<figure>
985<artwork type="abnf" name="p7-auth.parsed-abnf">
986<x:ref>Authorization</x:ref> = credentials
987
988<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
989
990<x:ref>Proxy-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS
991 challenge ] )
992<x:ref>Proxy-Authorization</x:ref> = credentials
993
994<x:ref>WWW-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
995 ] )
996
997<x:ref>auth-param</x:ref> = token "=" ( token / quoted-string )
998<x:ref>auth-scheme</x:ref> = token
999
1000<x:ref>challenge</x:ref> = auth-scheme 1*SP *( "," OWS ) auth-param *( OWS "," [ OWS
1001 auth-param ] )
1002<x:ref>credentials</x:ref> = auth-scheme ( token / quoted-string / [ ( "," /
1003 auth-param ) *( OWS "," [ OWS auth-param ] ) ] )
1004
1005<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1006
1007realm = "realm=" realm-value
1008realm-value = quoted-string
1009
1010<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1011</artwork>
1012</figure>
1013<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
1014; Authorization defined but not used
1015; Proxy-Authenticate defined but not used
1016; Proxy-Authorization defined but not used
1017; WWW-Authenticate defined but not used
1018; realm defined but not used
1019</artwork></figure></section>
1020<?ENDINC p7-auth.abnf-appendix ?>
1021
1022<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
1023
1024<section title="Since RFC 2616">
1025<t>
1026  Extracted relevant partitions from <xref target="RFC2616"/>.
1027</t>
1028</section>
1029
1030<section title="Since draft-ietf-httpbis-p7-auth-00">
1031<t>
1032  Closed issues:
1033  <list style="symbols"> 
1034    <t>
1035      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
1036      "Normative and Informative references"
1037    </t>
1038  </list>
1039</t>
1040</section>
1041
1042<section title="Since draft-ietf-httpbis-p7-auth-01">
1043<t>
1044  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1045  <list style="symbols"> 
1046    <t>
1047      Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.
1048    </t>
1049    <t>
1050      Add explicit references to BNF syntax and rules imported from other parts of the specification.
1051    </t>
1052  </list>
1053</t>
1054</section>
1055
1056<section title="Since draft-ietf-httpbis-p7-auth-02" anchor="changes.since.02">
1057<t>
1058  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
1059  <list style="symbols"> 
1060    <t>
1061      Reference RFC 3984, and update header field registrations for header fields defined
1062      in this document.
1063    </t>
1064  </list>
1065</t>
1066</section>
1067
1068<section title="Since draft-ietf-httpbis-p7-auth-03" anchor="changes.since.03">
1069<t>
1070</t>
1071</section>
1072
1073<section title="Since draft-ietf-httpbis-p7-auth-04" anchor="changes.since.04">
1074<t>
1075  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1076  <list style="symbols"> 
1077    <t>
1078      Use "/" instead of "|" for alternatives.
1079    </t>
1080    <t>
1081      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
1082      whitespace ("OWS") and required whitespace ("RWS").
1083    </t>
1084    <t>
1085      Rewrite ABNFs to spell out whitespace rules, factor out
1086      header field value format definitions.
1087    </t>
1088  </list>
1089</t>
1090</section>
1091
1092<section title="Since draft-ietf-httpbis-p7-auth-05" anchor="changes.since.05">
1093<t>
1094  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1095  <list style="symbols"> 
1096    <t>
1097      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
1098    </t>
1099  </list>
1100</t>
1101</section>
1102
1103<section title="Since draft-ietf-httpbis-p7-auth-06" anchor="changes.since.06">
1104<t>
1105  None.
1106</t>
1107</section>
1108
1109<section title="Since draft-ietf-httpbis-p7-auth-07" anchor="changes.since.07">
1110<t>
1111  Closed issues:
1112  <list style="symbols"> 
1113    <t>
1114      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/198"/>:
1115      "move IANA registrations for optional status codes"
1116    </t>
1117  </list>
1118</t>
1119</section>
1120
1121<section title="Since draft-ietf-httpbis-p7-auth-08" anchor="changes.since.08">
1122<t>
1123  No significant changes.
1124</t>
1125</section>
1126
1127<section title="Since draft-ietf-httpbis-p7-auth-09" anchor="changes.since.09">
1128<t>
1129  Partly resolved issues:
1130  <list style="symbols"> 
1131    <t>
1132      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
1133      "Term for the requested resource's URI"
1134    </t>
1135  </list>
1136</t>
1137</section>
1138
1139<section title="Since draft-ietf-httpbis-p7-auth-10" anchor="changes.since.10">
1140<t>
1141  None yet.
1142</t>
1143</section>
1144
1145<section title="Since draft-ietf-httpbis-p7-auth-11" anchor="changes.since.11">
1146<t>
1147  Closed issues:
1148  <list style="symbols"> 
1149    <t>
1150      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/130"/>:
1151      "introduction to part 7 is work-in-progress"
1152    </t>
1153    <t>
1154      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/195"/>:
1155      "auth-param syntax"
1156    </t>
1157    <t>
1158      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
1159      "Header Classification"
1160    </t>
1161    <t>
1162      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/237"/>:
1163      "absorbing the auth framework from 2617"
1164    </t>
1165  </list>
1166</t>
1167<t>
1168  Partly resolved issues:
1169  <list style="symbols"> 
1170    <t>
1171      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/141"/>:
1172      "should we have an auth scheme registry"
1173    </t>
1174  </list>
1175</t>
1176</section>
1177
1178<section title="Since draft-ietf-httpbis-p7-auth-12" anchor="changes.since.12">
1179<t>
1180  None.
1181</t>
1182</section>
1183
1184<section title="Since draft-ietf-httpbis-p7-auth-13" anchor="changes.since.13">
1185<t>
1186  Closed issues:
1187  <list style="symbols">
1188    <t>
1189      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
1190      "untangle ABNFs for header fields"
1191    </t>
1192  </list>
1193</t>
1194</section>
1195
1196</section>
1197
1198</back>
1199</rfc>
Note: See TracBrowser for help on using the repository browser.