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

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

Restructure section 2 (auth framework) in order to decouple Realm

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