Ignore:
Timestamp:
Jun 14, 2014, 4:20:37 AM (6 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/01/p7-auth.html

    r1099 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>HTTP/1.1, part 7: Authentication</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
    3031  font-style: normal;
    3132}
    32 dd {
    33   margin-right: 2em;
    34 }
    3533dl {
    3634  margin-left: 2em;
    3735}
    38 
    3936ul.empty {
    4037  list-style-type: none;
     
    5047}
    5148h1 {
    52   font-size: 14pt;
     49  font-size: 130%;
    5350  line-height: 21pt;
    5451  page-break-after: avoid;
     
    5754  page-break-before: always;
    5855}
    59 h1 a {
    60   color: #333333;
    61 }
    6256h2 {
    63   font-size: 12pt;
     57  font-size: 120%;
    6458  line-height: 15pt;
    6559  page-break-after: avoid;
    6660}
    67 h3, h4, h5, h6 {
    68   font-size: 10pt;
     61h3 {
     62  font-size: 110%;
    6963  page-break-after: avoid;
    7064}
    71 h2 a, h3 a, h4 a, h5 a, h6 a {
     65h4, h5, h6 {
     66  page-break-after: avoid;
     67}
     68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7269  color: black;
    7370}
     
    7774li {
    7875  margin-left: 2em;
    79   margin-right: 2em;
    8076}
    8177ol {
    8278  margin-left: 2em;
    83   margin-right: 2em;
     79}
     80ol.la {
     81  list-style-type: lower-alpha;
     82}
     83ol.ua {
     84  list-style-type: upper-alpha;
    8485}
    8586ol p {
     
    8889p {
    8990  margin-left: 2em;
    90   margin-right: 2em;
    9191}
    9292pre {
     
    9494  background-color: lightyellow;
    9595  padding: .25em;
     96  page-break-inside: avoid;
    9697}
    9798pre.text2 {
     
    123124  border-spacing: 1px;
    124125  width: 95%;
    125   font-size: 10pt;
     126  font-size: 11pt;
    126127  color: white;
    127128}
     
    131132td.topnowrap {
    132133  vertical-align: top;
    133   white-space: nowrap; 
     134  white-space: nowrap;
    134135}
    135136table.header td {
     
    151152  list-style: none;
    152153  margin-left: 1.5em;
    153   margin-right: 0em;
    154154  padding-left: 0em;
    155155}
     
    157157  line-height: 150%;
    158158  font-weight: bold;
    159   font-size: 10pt;
    160159  margin-left: 0em;
    161   margin-right: 0em;
    162160}
    163161ul.toc li li {
    164162  line-height: normal;
    165163  font-weight: normal;
    166   font-size: 9pt;
     164  font-size: 10pt;
    167165  margin-left: 0em;
    168   margin-right: 0em;
    169166}
    170167li.excluded {
     
    173170ul p {
    174171  margin-left: 0em;
     172}
     173.title, .filename, h1, h2, h3, h4 {
     174  font-family: candara, helvetica, arial, sans-serif;
     175}
     176samp, tt, code, pre {
     177  font: consolas, monospace;
    175178}
    176179ul.ind, ul.ind ul {
    177180  list-style: none;
    178181  margin-left: 1.5em;
    179   margin-right: 0em;
    180182  padding-left: 0em;
    181183  page-break-before: avoid;
     
    185187  line-height: 200%;
    186188  margin-left: 0em;
    187   margin-right: 0em;
    188189}
    189190ul.ind li li {
     
    191192  line-height: 150%;
    192193  margin-left: 0em;
    193   margin-right: 0em;
    194194}
    195195.avoidbreak {
     
    215215  font-weight: bold;
    216216  text-align: center;
    217   font-size: 9pt;
     217  font-size: 10pt;
    218218}
    219219.filename {
    220220  color: #333333;
     221  font-size: 75%;
    221222  font-weight: bold;
    222   font-size: 12pt;
    223223  line-height: 21pt;
    224224  text-align: center;
     
    227227  font-weight: bold;
    228228}
    229 .hidden {
    230   display: none;
    231 }
    232229.left {
    233230  text-align: left;
     
    237234}
    238235.title {
    239   color: #990000;
    240   font-size: 18pt;
     236  color: green;
     237  font-size: 150%;
    241238  line-height: 18pt;
    242239  font-weight: bold;
     
    244241  margin-top: 36pt;
    245242}
    246 .vcardline {
    247   display: block;
    248 }
    249243.warning {
    250   font-size: 14pt;
     244  font-size: 130%;
    251245  background-color: yellow;
    252246}
     
    257251    display: none;
    258252  }
    259  
     253
    260254  a {
    261255    color: black;
     
    272266    background-color: white;
    273267    vertical-align: top;
    274     font-size: 12pt;
    275   }
    276 
    277   ul.toc a::after {
     268    font-size: 110%;
     269  }
     270
     271  ul.toc a:nth-child(2)::after {
    278272    content: leader('.') target-counter(attr(href), page);
    279273  }
    280  
     274
    281275  ul.ind li li a {
    282276    content: target-counter(attr(href), page);
    283277  }
    284  
     278
    285279  .print2col {
    286280    column-count: 2;
     
    292286@page {
    293287  @top-left {
    294        content: "Internet-Draft"; 
    295   } 
     288       content: "Internet-Draft";
     289  }
    296290  @top-right {
    297        content: "January 2008"; 
    298   } 
     291       content: "January 2008";
     292  }
    299293  @top-center {
    300        content: "HTTP/1.1, Part 7"; 
    301   } 
     294       content: "HTTP/1.1, Part 7";
     295  }
    302296  @bottom-left {
    303        content: "Fielding, et al."; 
    304   } 
     297       content: "Fielding, et al.";
     298  }
    305299  @bottom-center {
    306        content: "Standards Track";
    307   } 
     300       content: "Expires July 15, 2008";
     301  }
    308302  @bottom-right {
    309        content: "[Page " counter(page) "]"; 
    310   } 
    311 }
    312 
    313 @page:first { 
     303       content: "[Page " counter(page) "]";
     304  }
     305}
     306
     307@page:first {
    314308    @top-left {
    315309      content: normal;
     
    335329      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
    336330      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    337       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     331      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    338332      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    339333      <meta name="dct.creator" content="Fielding, R.">
     
    364358            </tr>
    365359            <tr>
    366                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     360               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    367361               </td>
    368362               <td class="right">J. Gettys</td>
    369363            </tr>
    370364            <tr>
    371                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
     365               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
    372366               </td>
    373367               <td class="right">One Laptop per Child</td>
     
    436430      </table>
    437431      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-01</span></p>
    438       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    439       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    440          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    441          6 of BCP 79.
    442       </p>
    443       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    444          that other groups may also distribute working documents as Internet-Drafts.
    445       </p>
    446       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    447          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    448          in progress”.
    449       </p>
    450       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    451       </p>
    452       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
    453       </p>
    454       <p>This Internet-Draft will expire on July 15, 2008.</p>
    455       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     432      <div id="rfc.status">
     433         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     434         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
     435            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
     436            6 of BCP 79.
     437         </p>
     438         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     439            that other groups may also distribute working documents as Internet-Drafts.
     440         </p>
     441         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     442            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     443            in progress”.
     444         </p>
     445         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     446         </p>
     447         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     448         </p>
     449         <p>This Internet-Draft will expire on July 15, 2008.</p>
     450      </div>
     451      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    456452      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    457453         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
    458454         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    459455         7 defines HTTP Authentication.
    460       </p> 
    461       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     456      </p>
     457      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    462458      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    463459         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    464       </p> 
     460      </p>
    465461      <p>This draft incorporates those issue resolutions that were either collected in the original RFC2616 errata list (&lt;<a href="http://purl.org/NET/http-errata">http://purl.org/NET/http-errata</a>&gt;), or which were agreed upon on the mailing list between October 2006 and November 2007 (as published in "draft-lafon-rfc2616bis-03").
    466       </p> 
     462      </p>
    467463      <hr class="noprint">
    468464      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    469465      <ul class="toc">
    470          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    471                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     466         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     467               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    472468            </ul>
    473469         </li>
    474          <li>2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
    475                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    476                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
     470         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
     471               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     472               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    477473            </ul>
    478474         </li>
    479          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    480                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
    481                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
    482                <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
    483                <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
     475         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     476               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
     477               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
     478               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
     479               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
    484480            </ul>
    485481         </li>
    486          <li>4.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
    487          <li>5.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    488                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
     482         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
     483         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     484               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
    489485            </ul>
    490486         </li>
    491          <li>6.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    492          <li>7.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    493                <li>7.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    494                <li>7.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     487         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     488         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     489               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     490               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    495491            </ul>
    496492         </li>
    497          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    498          <li>A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    499                <li>A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     493         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     494               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    500495            </ul>
    501496         </li>
    502          <li>B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul>
    503                <li>B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
    504                <li>B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
     497         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul>
     498               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
     499               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
    505500            </ul>
    506501         </li>
    507502         <li><a href="#rfc.index">Index</a></li>
     503         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    508504         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    509505      </ul>
    510       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    511       <p id="rfc.section.1.p.1">This document defines HTTP/1.1 access control and authentication. Right now it includes the extracted relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor changes. The intention is to move the general framework for HTTP authentication here, as currently specified
    512          in <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, and allow the individual authentication mechanisms to be defined elsewhere. This introduction will be rewritten when that
    513          occurs.
    514       </p>
    515       <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
    516          provide authentication information. The general framework for access authentication, and the specification of "basic" and
    517          "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
    518       </p>
    519       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    520       <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    521          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    522       </p>
    523       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    524       </p>
    525       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
    526       </h1>
    527       <div id="rfc.iref."></div>
    528       <div id="rfc.iref.s.1"></div>
    529       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h2>
    530       <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
    531          refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
    532          already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
    533          access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    534       </p>
    535       <div id="rfc.iref.1"></div>
    536       <div id="rfc.iref.s.2"></div>
    537       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h2>
    538       <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
    539          proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    540       </p>
    541       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    542       <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
    543       <div id="rfc.iref.a.1"></div>
    544       <div id="rfc.iref.h.1"></div>
    545       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
    546       <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
    547          so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
    548          containing the authentication information of the user agent for the realm of the resource being requested.
    549       </p>
    550       <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  Authorization  = "Authorization" ":" credentials
     506      <div id="introduction">
     507         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     508         <p id="rfc.section.1.p.1">This document defines HTTP/1.1 access control and authentication. Right now it includes the extracted relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor changes. The intention is to move the general framework for HTTP authentication here, as currently specified
     509            in <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, and allow the individual authentication mechanisms to be defined elsewhere. This introduction will be rewritten when that
     510            occurs.
     511         </p>
     512         <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
     513            provide authentication information. The general framework for access authentication, and the specification of "basic" and
     514            "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
     515         </p>
     516         <div id="intro.requirements">
     517            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     518            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     519               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
     520            </p>
     521            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     522            </p>
     523         </div>
     524      </div>
     525      <div>
     526         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
     527         </h1>
     528         <div id="status.401">
     529            <div id="rfc.iref.4.1"></div>
     530            <div id="rfc.iref.s.1"></div>
     531            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
     532            <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
     533               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
     534               already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
     535               access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
     536            </p>
     537         </div>
     538         <div id="status.407">
     539            <div id="rfc.iref.4.2"></div>
     540            <div id="rfc.iref.s.2"></div>
     541            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h2>
     542            <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
     543               proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
     544            </p>
     545         </div>
     546      </div>
     547      <div id="header.fields">
     548         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     549         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
     550         <div id="header.authorization">
     551            <div id="rfc.iref.a.1"></div>
     552            <div id="rfc.iref.h.1"></div>
     553            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
     554            <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
     555               so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
     556               containing the authentication information of the user agent for the realm of the resource being requested.
     557            </p>
     558            <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  Authorization  = "Authorization" ":" credentials
    551559</pre><p id="rfc.section.3.1.p.3">HTTP access authentication is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.5"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
    552          such as credentials that vary according to a challenge value or using synchronized clocks).
    553       </p>
    554       <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
    555       </p>
    556       <p id="rfc.section.3.1.p.5"> </p>
    557       <ol>
    558          <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
    559             the new request. (This is the defined behavior for s-maxage.) If the response includes "s-maxage=0", the proxy <em class="bcp14">MUST</em> always revalidate it before re-using it.
    560          </li>
    561          <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
    562             the new request.
    563          </li>
    564          <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
    565          </li>
    566       </ol>
    567       <div id="rfc.iref.p.1"></div>
    568       <div id="rfc.iref.h.2"></div>
    569       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
    570       <p id="rfc.section.3.2.p.1">The Proxy-Authenticate response-header field <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
    571          the authentication scheme and parameters applicable to the proxy for this Request-URI.
    572       </p>
    573       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
     560               such as credentials that vary according to a challenge value or using synchronized clocks).
     561            </p>
     562            <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
     563            </p>
     564            <p id="rfc.section.3.1.p.5"></p>
     565            <ol>
     566               <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
     567                  the new request. (This is the defined behavior for s-maxage.) If the response includes "s-maxage=0", the proxy <em class="bcp14">MUST</em> always revalidate it before re-using it.
     568               </li>
     569               <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
     570                  the new request.
     571               </li>
     572               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
     573               </li>
     574            </ol>
     575         </div>
     576         <div id="header.proxy-authenticate">
     577            <div id="rfc.iref.p.1"></div>
     578            <div id="rfc.iref.h.2"></div>
     579            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
     580            <p id="rfc.section.3.2.p.1">The Proxy-Authenticate response-header field <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
     581               the authentication scheme and parameters applicable to the proxy for this Request-URI.
     582            </p>
     583            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
    574584</pre><p id="rfc.section.3.2.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.6"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to the current connection and <em class="bcp14">SHOULD NOT</em> be passed on to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting
    575          them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
    576          header field.
    577       </p>
    578       <div id="rfc.iref.p.2"></div>
    579       <div id="rfc.iref.h.3"></div>
    580       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2>
    581       <p id="rfc.section.3.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
    582          authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
    583          user agent for the proxy and/or realm of the resource being requested.
    584       </p>
    585       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
     585               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
     586               header field.
     587            </p>
     588         </div>
     589         <div id="header.proxy-authorization">
     590            <div id="rfc.iref.p.2"></div>
     591            <div id="rfc.iref.h.3"></div>
     592            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></h2>
     593            <p id="rfc.section.3.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
     594               authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
     595               user agent for the proxy and/or realm of the resource being requested.
     596            </p>
     597            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
    586598</pre><p id="rfc.section.3.3.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.7"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication
    587          using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
    588          by the first outbound proxy that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
    589          authenticate a given request.
    590       </p>
    591       <div id="rfc.iref.w.1"></div>
    592       <div id="rfc.iref.h.4"></div>
    593       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
    594       <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
    595          authentication scheme(s) and parameters applicable to the Request-URI.
    596       </p>
    597       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
     599               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
     600               by the first outbound proxy that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
     601               authenticate a given request.
     602            </p>
     603         </div>
     604         <div id="header.www-authenticate">
     605            <div id="rfc.iref.w.1"></div>
     606            <div id="rfc.iref.h.4"></div>
     607            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></h2>
     608            <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
     609               authentication scheme(s) and parameters applicable to the Request-URI.
     610            </p>
     611            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
    598612</pre><p id="rfc.section.3.4.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.8"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
    599          challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
    600          comma-separated list of authentication parameters.
    601       </p>
    602       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    603       <p id="rfc.section.4.p.1">TBD.</p>
    604       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    605       <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    606          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    607          make some suggestions for reducing security risks.
    608       </p>
    609       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="auth.credentials.and.idle.clients" href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
    610       <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1 does not provide
    611          a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
    612          extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
    613          but are not limited to:
    614       </p>
    615       <ul>
    616          <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
    617             the user for credentials.
    618          </li>
    619          <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
    620             the server side of the application `knows' that there is no further reason for the client to retain the credentials.
    621          </li>
    622       </ul>
    623       <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
    624          use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
    625          in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
    626          for discarding cached credentials under user control.
    627       </p>
    628       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    629       <p id="rfc.section.6.p.1">TBD.</p>
     613               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
     614               comma-separated list of authentication parameters.
     615            </p>
     616         </div>
     617      </div>
     618      <div id="IANA.considerations">
     619         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     620         <p id="rfc.section.4.p.1">TBD.</p>
     621      </div>
     622      <div id="security.considerations">
     623         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     624         <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     625            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
     626            make some suggestions for reducing security risks.
     627         </p>
     628         <div id="auth.credentials.and.idle.clients">
     629            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
     630            <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1 does not provide
     631               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
     632               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
     633               but are not limited to:
     634            </p>
     635            <ul>
     636               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
     637                  the user for credentials.
     638               </li>
     639               <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
     640                  the server side of the application `knows' that there is no further reason for the client to retain the credentials.
     641               </li>
     642            </ul>
     643            <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
     644               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
     645               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
     646               for discarding cached credentials under user control.
     647            </p>
     648         </div>
     649      </div>
     650      <div id="ack">
     651         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     652         <p id="rfc.section.6.p.1">TBD.</p>
     653      </div>
    630654      <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References
    631655      </h1>
    632656      <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References
    633657      </h2>
    634       <table>     
     658      <table>
    635659         <tr>
    636660            <td class="reference"><b id="Part6">[Part6]</b></td>
    637             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-01 (work in progress), January&nbsp;2008.
     661            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-01 (work in progress), January&nbsp;2008.
    638662            </td>
    639663         </tr>
    640664         <tr>
    641665            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    642             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     666            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    643667            </td>
    644668         </tr>
    645669         <tr>
    646670            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
    647             <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
     671            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="https://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
    648672            </td>
    649673         </tr>
     
    651675      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References
    652676      </h2>
    653       <table> 
     677      <table>
    654678         <tr>
    655679            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    656             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     680            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    657681            </td>
    658682         </tr>
    659683      </table>
    660       <div class="avoidbreak">
    661          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    662          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    663                (editor)
    664                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    665          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:jg@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    666          <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
    667          <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
    668          <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
    669          <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
    670          <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
    671          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    672                (editor)
    673                <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
    674          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    675                (editor)
    676                <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
    677       </div>
    678       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    679       <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    680       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
    681       </h1>
    682       <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
    683       </h2>
    684       <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    685       </p>
    686       <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
    687       </h2>
    688       <p id="rfc.section.B.2.p.1">Closed issues: </p>
    689       <ul>
    690          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    691          </li>
    692       </ul>
     684      <div id="compatibility">
     685         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     686         <div id="changes.from.rfc.2616">
     687            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     688         </div>
     689      </div>
     690      <div>
     691         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     692         </h1>
     693         <div>
     694            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     695            </h2>
     696            <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     697            </p>
     698         </div>
     699         <div>
     700            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
     701            </h2>
     702            <p id="rfc.section.B.2.p.1">Closed issues: </p>
     703            <ul>
     704               <li>&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     705               </li>
     706            </ul>
     707         </div>
     708      </div>
    693709      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    694710      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a>
     
    697713         <ul class="ind">
    698714            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    699                   <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref."><b>2.1</b></a></li>
    700                   <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.1"><b>2.2</b></a></li>
     715                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>2.1</b></a></li>
     716                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>2.2</b></a></li>
    701717               </ul>
    702718            </li>
     
    757773         </ul>
    758774      </div>
    759       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    760       <p>Copyright © The IETF Trust (2008).</p>
    761       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    762          authors retain all their rights.
    763       </p>
    764       <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
    765          HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
    766          DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
    767          WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    768       </p>
    769       <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    770       <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    771          be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
    772          license under such rights might or might not be available; nor does it represent that it has made any independent effort to
    773          identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
    774          BCP 79.
    775       </p>
    776       <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    777          of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    778          of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    779       </p>
    780       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    781          rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
    782          at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    783       </p>
     775      <div class="avoidbreak">
     776         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     777         <p><b>Roy T. Fielding</b>
     778            (editor)
     779            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>EMail: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
     780         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
     781         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>EMail: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
     782         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>EMail: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
     783         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>EMail: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
     784         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>EMail: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
     785         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>EMail: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
     786         <p><b>Yves Lafon</b>
     787            (editor)
     788            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>EMail: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
     789         <p><b>Julian F. Reschke</b>
     790            (editor)
     791            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>EMail: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
     792      </div>
     793      <div id="rfc.copyright">
     794         <h1><a href="#rfc.copyright">Full Copyright Statement</a></h1>
     795         <p>Copyright © The IETF Trust (2008).</p>
     796         <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
     797            authors retain all their rights.
     798         </p>
     799         <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
     800            HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
     801            DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
     802            WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
     803         </p>
     804      </div>
     805      <div id="rfc.ipr">
     806         <h1><a href="#rfc.ipr">Intellectual Property</a></h1>
     807         <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
     808            be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
     809            license under such rights might or might not be available; nor does it represent that it has made any independent effort to
     810            identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
     811            BCP 79.
     812         </p>
     813         <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
     814            of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
     815            of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
     816         </p>
     817         <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
     818            rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
     819            at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
     820         </p>
     821      </div>
    784822   </body>
    785823</html>
Note: See TracChangeset for help on using the changeset viewer.