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

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

s/canonical root URL/canonical root URI/ and fix whitespace (related to #237)

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