source: draft-ietf-httpbis/02/draft-ietf-httpbis-p7-auth-02.xml @ 872

Last change on this file since 872 was 559, checked in by fielding@…, 11 years ago

remove executable and set eol-style for earlier drafts

  • Property svn:eol-style set to native
File size: 28.5 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3    This XML document is the output of clean-for-DTD.xslt; a tool that strips
4    extensions to RFC2629(bis) from documents for processing with xml2rfc.
5-->
6<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
7<?rfc toc="yes" ?>
8<?rfc symrefs="yes" ?>
9<?rfc sortrefs="yes" ?>
10<?rfc compact="yes"?>
11<?rfc subcompact="no" ?>
12<?rfc linkmailto="no" ?>
13<?rfc editing="no" ?>
14<?rfc comments="yes"?>
15<?rfc inline="yes"?>
16<!DOCTYPE rfc
17  PUBLIC "" "rfc2629.dtd">
18<rfc obsoletes="2616" updates="2617" category="std" ipr="full3978" docName="draft-ietf-httpbis-p7-auth-02">
19<front>
20
21  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
22
23  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
24    <organization abbrev="Day Software">Day Software</organization>
25    <address>
26      <postal>
27        <street>23 Corporate Plaza DR, Suite 280</street>
28        <city>Newport Beach</city>
29        <region>CA</region>
30        <code>92660</code>
31        <country>USA</country>
32      </postal>
33      <phone>+1-949-706-5300</phone>
34      <facsimile>+1-949-706-5305</facsimile>
35      <email>fielding@gbiv.com</email>
36      <uri>http://roy.gbiv.com/</uri>
37    </address>
38  </author>
39
40  <author initials="J." surname="Gettys" fullname="Jim Gettys">
41    <organization>One Laptop per Child</organization>
42    <address>
43      <postal>
44        <street>21 Oak Knoll Road</street>
45        <city>Carlisle</city>
46        <region>MA</region>
47        <code>01741</code>
48        <country>USA</country>
49      </postal>
50      <email>jg@laptop.org</email>
51      <uri>http://www.laptop.org/</uri>
52    </address>
53  </author>
54 
55  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
56    <organization abbrev="HP">Hewlett-Packard Company</organization>
57    <address>
58      <postal>
59        <street>HP Labs, Large Scale Systems Group</street>
60        <street>1501 Page Mill Road, MS 1177</street>
61        <city>Palo Alto</city>
62        <region>CA</region>
63        <code>94304</code>
64        <country>USA</country>
65      </postal>
66      <email>JeffMogul@acm.org</email>
67    </address>
68  </author>
69
70  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
71    <organization abbrev="Microsoft">Microsoft Corporation</organization>
72    <address>
73      <postal>
74        <street>1 Microsoft Way</street>
75        <city>Redmond</city>
76        <region>WA</region>
77        <code>98052</code>
78        <country>USA</country>
79      </postal>
80      <email>henrikn@microsoft.com</email>
81    </address>
82  </author>
83
84  <author initials="L." surname="Masinter" fullname="Larry Masinter">
85    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
86    <address>
87      <postal>
88        <street>345 Park Ave</street>
89        <city>San Jose</city>
90        <region>CA</region>
91        <code>95110</code>
92        <country>USA</country>
93      </postal>
94      <email>LMM@acm.org</email>
95      <uri>http://larry.masinter.net/</uri>
96    </address>
97  </author>
98 
99  <author initials="P." surname="Leach" fullname="Paul J. Leach">
100    <organization abbrev="Microsoft">Microsoft Corporation</organization>
101    <address>
102      <postal>
103        <street>1 Microsoft Way</street>
104        <city>Redmond</city>
105        <region>WA</region>
106        <code>98052</code>
107      </postal>
108      <email>paulle@microsoft.com</email>
109    </address>
110  </author>
111   
112  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
113    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
114    <address>
115      <postal>
116        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
117        <street>The Stata Center, Building 32</street>
118        <street>32 Vassar Street</street>
119        <city>Cambridge</city>
120        <region>MA</region>
121        <code>02139</code>
122        <country>USA</country>
123      </postal>
124      <email>timbl@w3.org</email>
125      <uri>http://www.w3.org/People/Berners-Lee/</uri>
126    </address>
127  </author>
128
129  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
130    <organization abbrev="W3C">World Wide Web Consortium</organization>
131    <address>
132      <postal>
133        <street>W3C / ERCIM</street>
134        <street>2004, rte des Lucioles</street>
135        <city>Sophia-Antipolis</city>
136        <region>AM</region>
137        <code>06902</code>
138        <country>France</country>
139      </postal>
140      <email>ylafon@w3.org</email>
141      <uri>http://www.raubacapeu.net/people/yves/</uri>
142    </address>
143  </author>
144
145  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
146    <organization abbrev="greenbytes">greenbytes GmbH</organization>
147    <address>
148      <postal>
149        <street>Hafenweg 16</street>
150        <city>Muenster</city><region>NW</region><code>48155</code>
151        <country>Germany</country>
152      </postal>
153      <phone>+49 251 2807760</phone>   
154      <facsimile>+49 251 2807761</facsimile>   
155      <email>julian.reschke@greenbytes.de</email>       
156      <uri>http://greenbytes.de/tech/webdav/</uri>     
157    </address>
158  </author>
159
160  <date month="February" year="2008" day="24"/>
161
162<abstract>
163<t>
164   The Hypertext Transfer Protocol (HTTP) is an application-level
165   protocol for distributed, collaborative, hypermedia information
166   systems. HTTP has been in use by the World Wide Web global information
167   initiative since 1990. This document is Part 7 of the seven-part specification
168   that defines the protocol referred to as "HTTP/1.1" and, taken together,
169   obsoletes RFC 2616.  Part 7 defines HTTP Authentication.
170</t>
171</abstract>
172
173<note title="Editorial Note (To be removed by RFC Editor)">
174  <t>
175    Discussion of this draft should take place on the HTTPBIS working group
176    mailing list (ietf-http-wg@w3.org). The current issues list is
177    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
178    and related documents (including fancy diffs) can be found at
179    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
180  </t>
181  <t>
182    This draft incorporates those issue resolutions that were either
183    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
184    or which were agreed upon on the mailing list between October 2006 and
185    November 2007 (as published in "draft-lafon-rfc2616bis-03").
186  </t>
187</note>
188</front>
189<middle>
190<section title="Introduction" anchor="introduction">
191<t>
192   This document defines HTTP/1.1 access control and authentication. Right now it
193   includes the extracted relevant sections of
194   RFC 2616 with only minor changes.
195   The intention is to move the general framework for HTTP authentication here,
196   as currently specified in <xref target="RFC2617"/>, and allow the individual
197   authentication mechanisms to be defined elsewhere.  This introduction will
198   be rewritten when that occurs.
199</t>
200<t>
201   HTTP provides several OPTIONAL challenge-response authentication
202   mechanisms which can be used by a server to challenge a client
203   request and by a client to provide authentication information. The
204   general framework for access authentication, and the specification of
205   "basic" and "digest" authentication, are specified in "HTTP
206   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. This
207   specification adopts the definitions of "challenge" and "credentials"
208   from that specification.
209</t>
210
211<section title="Requirements" anchor="intro.requirements">
212<t>
213   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
214   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
215   document are to be interpreted as described in <xref target="RFC2119"/>.
216</t>
217<t>
218   An implementation is not compliant if it fails to satisfy one or more
219   of the MUST or REQUIRED level requirements for the protocols it
220   implements. An implementation that satisfies all the MUST or REQUIRED
221   level and all the SHOULD level requirements for its protocols is said
222   to be "unconditionally compliant"; one that satisfies all the MUST
223   level requirements but not all the SHOULD level requirements for its
224   protocols is said to be "conditionally compliant."
225</t>
226</section>
227</section>
228
229<section title="Notational Conventions and Generic Grammar" anchor="notation">
230<t>
231  This specification uses the ABNF syntax defined in Section 2.1 of <xref target="Part1"/>.
232  <cref anchor="abnf.dep">ABNF syntax and basic rules will be adopted from RFC 5234, see
233  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/36&gt;.</cref>
234</t>
235<t anchor="abnf.dependencies">
236  The ABNF rules below are defined in other specifications:
237</t>
238<figure><iref primary="true" item="Grammar" subitem="challenge"/><iref primary="true" item="Grammar" subitem="credentials"/><artwork type="abnf2616"><![CDATA[
239  challenge   = <challenge, defined in [RFC2617], Section 1.2>
240  credentials = <credentials, defined in [RFC2617], Section 1.2>
241]]></artwork></figure>
242</section>
243
244
245<section title="Status Code Definitions">
246<section title="401 Unauthorized" anchor="status.401">
247  <iref primary="true" item="401 Unauthorized (status code)"/>
248  <iref primary="true" item="Status Codes" subitem="401 Unauthorized"/>
249<t>
250   The request requires user authentication. The response MUST include a
251   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
252   applicable to the requested resource. The client MAY repeat the
253   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
254   the request already included Authorization credentials, then the 401
255   response indicates that authorization has been refused for those
256   credentials. If the 401 response contains the same challenge as the
257   prior response, and the user agent has already attempted
258   authentication at least once, then the user SHOULD be presented the
259   entity that was given in the response, since that entity might
260   include relevant diagnostic information. HTTP access authentication
261   is explained in "HTTP Authentication: Basic and Digest Access
262   Authentication" <xref target="RFC2617"/>.
263</t>
264</section>
265<section title="407 Proxy Authentication Required" anchor="status.407">
266  <iref primary="true" item="407 Proxy Authentication Required (status code)"/>
267  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required"/>
268<t>
269   This code is similar to 401 (Unauthorized), but indicates that the
270   client must first authenticate itself with the proxy. The proxy MUST
271   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
272   challenge applicable to the proxy for the requested resource. The
273   client MAY repeat the request with a suitable Proxy-Authorization
274   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
275   in "HTTP Authentication: Basic and Digest Access Authentication"
276   <xref target="RFC2617"/>.
277</t>
278</section>
279</section>
280
281<section title="Header Field Definitions" anchor="header.fields">
282<t>
283   This section defines the syntax and semantics of HTTP/1.1 header fields
284   related to authentication.
285</t>
286
287<section title="Authorization" anchor="header.authorization">
288  <iref primary="true" item="Authorization header"/>
289  <iref primary="true" item="Headers" subitem="Authorization"/>
290<t>
291      A user agent that wishes to authenticate itself with a server--
292      usually, but not necessarily, after receiving a 401 response--does
293      so by including an Authorization request-header field with the
294      request.  The Authorization field value consists of credentials
295      containing the authentication information of the user agent for
296      the realm of the resource being requested.
297</t>
298<figure><iref primary="true" item="Grammar" subitem="Authorization"/><artwork type="abnf2616"><![CDATA[
299  Authorization  = "Authorization" ":" credentials
300]]></artwork></figure>
301<t>
302      HTTP access authentication is described in "HTTP Authentication:
303      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
304      authenticated and a realm specified, the same credentials SHOULD
305      be valid for all other requests within this realm (assuming that
306      the authentication scheme itself does not require otherwise, such
307      as credentials that vary according to a challenge value or using
308      synchronized clocks).
309</t>
310<t>
311      When a shared cache (see Section 9 of <xref target="Part6"/>) receives a request
312      containing an Authorization field, it MUST NOT return the
313      corresponding response as a reply to any other request, unless one
314      of the following specific exceptions holds:
315</t>
316<t>
317  <list style="numbers">
318      <t>If the response includes the "s-maxage" cache-control
319         directive, the cache MAY use that response in replying to a
320         subsequent request. But (if the specified maximum age has
321         passed) a proxy cache MUST first revalidate it with the origin
322         server, using the request-headers from the new request to allow
323         the origin server to authenticate the new request. (This is the
324         defined behavior for s-maxage.) If the response includes "s-maxage=0",
325         the proxy MUST always revalidate it before re-using
326         it.</t>
327
328      <t>If the response includes the "must-revalidate" cache-control
329         directive, the cache MAY use that response in replying to a
330         subsequent request. But if the response is stale, all caches
331         MUST first revalidate it with the origin server, using the
332         request-headers from the new request to allow the origin server
333         to authenticate the new request.</t>
334
335      <t>If the response includes the "public" cache-control directive,
336         it MAY be returned in reply to any subsequent request.</t>
337  </list>
338</t>
339</section>
340
341<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
342  <iref primary="true" item="Proxy-Authenticate header"/>
343  <iref primary="true" item="Headers" subitem="Proxy-Authenticate"/>
344<t>
345   The Proxy-Authenticate response-header field MUST be included as part
346   of a 407 (Proxy Authentication Required) response. The field value
347   consists of a challenge that indicates the authentication scheme and
348   parameters applicable to the proxy for this Request-URI.
349</t>
350<figure><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/><artwork type="abnf2616"><![CDATA[
351  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
352]]></artwork></figure>
353<t>
354   The HTTP access authentication process is described in "HTTP
355   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
356   WWW-Authenticate, the Proxy-Authenticate header field applies only to
357   the current connection and SHOULD NOT  be passed on to downstream
358   clients. However, an intermediate proxy might need to obtain its own
359   credentials by requesting them from the downstream client, which in
360   some circumstances will appear as if the proxy is forwarding the
361   Proxy-Authenticate header field.
362</t>
363</section>
364
365<section title="Proxy-Authorization" anchor="header.proxy-authorization">
366  <iref primary="true" item="Proxy-Authorization header"/>
367  <iref primary="true" item="Headers" subitem="Proxy-Authorization"/>
368<t>
369   The Proxy-Authorization request-header field allows the client to
370   identify itself (or its user) to a proxy which requires
371   authentication. The Proxy-Authorization field value consists of
372   credentials containing the authentication information of the user
373   agent for the proxy and/or realm of the resource being requested.
374</t>
375<figure><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/><artwork type="abnf2616"><![CDATA[
376  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
377]]></artwork></figure>
378<t>
379   The HTTP access authentication process is described in "HTTP
380   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
381   Authorization, the Proxy-Authorization header field applies only to
382   the next outbound proxy that demanded authentication using the Proxy-Authenticate
383   field. When multiple proxies are used in a chain, the
384   Proxy-Authorization header field is consumed by the first outbound
385   proxy that was expecting to receive credentials. A proxy MAY relay
386   the credentials from the client request to the next proxy if that is
387   the mechanism by which the proxies cooperatively authenticate a given
388   request.
389</t>
390</section>
391
392<section title="WWW-Authenticate" anchor="header.www-authenticate">
393  <iref primary="true" item="WWW-Authenticate header"/>
394  <iref primary="true" item="Headers" subitem="WWW-Authenticate"/>
395<t>
396   The WWW-Authenticate response-header field MUST be included in 401
397   (Unauthorized) response messages. The field value consists of at
398   least one challenge that indicates the authentication scheme(s) and
399   parameters applicable to the Request-URI.
400</t>
401<figure><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/><artwork type="abnf2616"><![CDATA[
402  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
403]]></artwork></figure>
404<t>
405   The HTTP access authentication process is described in "HTTP
406   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
407   agents are advised to take special care in parsing the WWW-Authenticate
408   field value as it might contain more than one challenge,
409   or if more than one WWW-Authenticate header field is provided, the
410   contents of a challenge itself can contain a comma-separated list of
411   authentication parameters.
412</t>
413</section>
414
415</section>
416
417<section title="IANA Considerations" anchor="IANA.considerations">
418<t>
419   <cref>TBD.</cref>
420</t>
421</section>
422
423<section title="Security Considerations" anchor="security.considerations">
424<t>
425   This section is meant to inform application developers, information
426   providers, and users of the security limitations in HTTP/1.1 as
427   described by this document. The discussion does not include
428   definitive solutions to the problems revealed, though it does make
429   some suggestions for reducing security risks.
430</t>
431
432<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
433<t>
434   Existing HTTP clients and user agents typically retain authentication
435   information indefinitely. HTTP/1.1 does not provide a method for a
436   server to direct clients to discard these cached credentials. This is
437   a significant defect that requires further extensions to HTTP.
438   Circumstances under which credential caching can interfere with the
439   application's security model include but are not limited to:
440  <list style="symbols">
441     <t>Clients which have been idle for an extended period following
442        which the server might wish to cause the client to reprompt the
443        user for credentials.</t>
444
445     <t>Applications which include a session termination indication
446        (such as a `logout' or `commit' button on a page) after which
447        the server side of the application `knows' that there is no
448        further reason for the client to retain the credentials.</t>
449  </list>
450</t>
451<t>
452   This is currently under separate study. There are a number of work-arounds
453   to parts of this problem, and we encourage the use of
454   password protection in screen savers, idle time-outs, and other
455   methods which mitigate the security problems inherent in this
456   problem. In particular, user agents which cache credentials are
457   encouraged to provide a readily accessible mechanism for discarding
458   cached credentials under user control.
459</t>
460</section>
461</section>
462
463<section title="Acknowledgments" anchor="ack">
464<t>
465  TBD.
466</t>
467</section>
468</middle>
469
470<back>
471
472<references title="Normative References">
473
474<reference anchor="Part1">
475  <front>
476    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
477    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
478      <organization abbrev="Day Software">Day Software</organization>
479      <address><email>fielding@gbiv.com</email></address>
480    </author>
481    <author initials="J." surname="Gettys" fullname="Jim Gettys">
482      <organization>One Laptop per Child</organization>
483      <address><email>jg@laptop.org</email></address>
484    </author>
485    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
486      <organization abbrev="HP">Hewlett-Packard Company</organization>
487      <address><email>JeffMogul@acm.org</email></address>
488    </author>
489    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
490      <organization abbrev="Microsoft">Microsoft Corporation</organization>
491      <address><email>henrikn@microsoft.com</email></address>
492    </author>
493    <author initials="L." surname="Masinter" fullname="Larry Masinter">
494      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
495      <address><email>LMM@acm.org</email></address>
496    </author>
497    <author initials="P." surname="Leach" fullname="Paul J. Leach">
498      <organization abbrev="Microsoft">Microsoft Corporation</organization>
499      <address><email>paulle@microsoft.com</email></address>
500    </author>
501    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
502      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
503      <address><email>timbl@w3.org</email></address>
504    </author>
505    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
506      <organization abbrev="W3C">World Wide Web Consortium</organization>
507      <address><email>ylafon@w3.org</email></address>
508    </author>
509    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
510      <organization abbrev="greenbytes">greenbytes GmbH</organization>
511      <address><email>julian.reschke@greenbytes.de</email></address>
512    </author>
513    <date month="February" year="2008"/>
514  </front>
515  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-02"/>
516 
517</reference>
518
519<reference anchor="Part6">
520  <front>
521    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
522    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
523      <organization abbrev="Day Software">Day Software</organization>
524      <address><email>fielding@gbiv.com</email></address>
525    </author>
526    <author initials="J." surname="Gettys" fullname="Jim Gettys">
527      <organization>One Laptop per Child</organization>
528      <address><email>jg@laptop.org</email></address>
529    </author>
530    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
531      <organization abbrev="HP">Hewlett-Packard Company</organization>
532      <address><email>JeffMogul@acm.org</email></address>
533    </author>
534    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
535      <organization abbrev="Microsoft">Microsoft Corporation</organization>
536      <address><email>henrikn@microsoft.com</email></address>
537    </author>
538    <author initials="L." surname="Masinter" fullname="Larry Masinter">
539      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
540      <address><email>LMM@acm.org</email></address>
541    </author>
542    <author initials="P." surname="Leach" fullname="Paul J. Leach">
543      <organization abbrev="Microsoft">Microsoft Corporation</organization>
544      <address><email>paulle@microsoft.com</email></address>
545    </author>
546    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
547      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
548      <address><email>timbl@w3.org</email></address>
549    </author>
550    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
551      <organization abbrev="W3C">World Wide Web Consortium</organization>
552      <address><email>ylafon@w3.org</email></address>
553    </author>
554    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
555      <organization abbrev="greenbytes">greenbytes GmbH</organization>
556      <address><email>julian.reschke@greenbytes.de</email></address>
557    </author>
558    <date month="February" year="2008"/>
559  </front>
560  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-02"/>
561 
562</reference>
563
564<reference anchor="RFC2119">
565  <front>
566    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
567    <author initials="S." surname="Bradner" fullname="Scott Bradner">
568      <organization>Harvard University</organization>
569      <address><email>sob@harvard.edu</email></address>
570    </author>
571    <date month="March" year="1997"/>
572  </front>
573  <seriesInfo name="BCP" value="14"/>
574  <seriesInfo name="RFC" value="2119"/>
575</reference>
576
577<reference anchor="RFC2617">
578  <front>
579    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
580    <author initials="J." surname="Franks" fullname="John Franks">
581      <organization>Northwestern University, Department of Mathematics</organization>
582      <address><email>john@math.nwu.edu</email></address>
583    </author>
584    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
585      <organization>Verisign Inc.</organization>
586      <address><email>pbaker@verisign.com</email></address>
587    </author>
588    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
589      <organization>AbiSource, Inc.</organization>
590      <address><email>jeff@AbiSource.com</email></address>
591    </author>
592    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
593      <organization>Agranat Systems, Inc.</organization>
594      <address><email>lawrence@agranat.com</email></address>
595    </author>
596    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
597      <organization>Microsoft Corporation</organization>
598      <address><email>paulle@microsoft.com</email></address>
599    </author>
600    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
601      <organization>Netscape Communications Corporation</organization>
602    </author>
603    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
604      <organization>Open Market, Inc.</organization>
605      <address><email>stewart@OpenMarket.com</email></address>
606    </author>
607    <date month="June" year="1999"/>
608  </front>
609  <seriesInfo name="RFC" value="2617"/>
610</reference>
611
612</references>
613
614<references title="Informative References">
615
616<reference anchor="RFC2616">
617  <front>
618    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
619    <author initials="R." surname="Fielding" fullname="R. Fielding">
620      <organization>University of California, Irvine</organization>
621      <address><email>fielding@ics.uci.edu</email></address>
622    </author>
623    <author initials="J." surname="Gettys" fullname="J. Gettys">
624      <organization>W3C</organization>
625      <address><email>jg@w3.org</email></address>
626    </author>
627    <author initials="J." surname="Mogul" fullname="J. Mogul">
628      <organization>Compaq Computer Corporation</organization>
629      <address><email>mogul@wrl.dec.com</email></address>
630    </author>
631    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
632      <organization>MIT Laboratory for Computer Science</organization>
633      <address><email>frystyk@w3.org</email></address>
634    </author>
635    <author initials="L." surname="Masinter" fullname="L. Masinter">
636      <organization>Xerox Corporation</organization>
637      <address><email>masinter@parc.xerox.com</email></address>
638    </author>
639    <author initials="P." surname="Leach" fullname="P. Leach">
640      <organization>Microsoft Corporation</organization>
641      <address><email>paulle@microsoft.com</email></address>
642    </author>
643    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
644      <organization>W3C</organization>
645      <address><email>timbl@w3.org</email></address>
646    </author>
647    <date month="June" year="1999"/>
648  </front>
649  <seriesInfo name="RFC" value="2616"/>
650</reference>
651
652</references>
653
654
655<section title="Compatibility with Previous Versions" anchor="compatibility">
656
657<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
658</section>
659
660</section>
661
662<section title="Change Log (to be removed by RFC Editor before publication)">
663
664<section title="Since RFC2616">
665<t>
666  Extracted relevant partitions from <xref target="RFC2616"/>.
667</t>
668</section>
669
670<section title="Since draft-ietf-httpbis-p7-auth-00">
671<t>
672  Closed issues:
673  <list style="symbols"> 
674    <t>
675      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
676      "Normative and Informative references"
677    </t>
678  </list>
679</t>
680</section>
681
682<section title="Since draft-ietf-httpbis-p7-auth-01">
683<t>
684  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
685  <list style="symbols"> 
686    <t>
687      Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.
688    </t>
689    <t>
690      Add explicit references to BNF syntax and rules imported from other parts of the specification.
691    </t>
692  </list>
693</t>
694</section>
695
696</section>
697
698</back>
699</rfc>
Note: See TracBrowser for help on using the repository browser.