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

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

Realm is optional in new schemes (see #177)

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