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

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

Update my org after Adobe acquisition

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