source: draft-ietf-httpbis/diffs/draft-ietf-httpbis-p7-auth-23-from-22.diff.html @ 2323

Last change on this file since 2323 was 2304, checked in by julian.reschke@…, 7 years ago

prepare release of -23

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html; charset=iso-8859-1
File size: 160.4 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<!-- Generated by rfcdiff 1.38: rfcdiff  -->
3<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
4<html> 
5<head> 
6  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7  <meta http-equiv="Content-Style-Type" content="text/css" />
8  <title>Diff: draft-ietf-httpbis-p7-auth-22.txt - draft-ietf-httpbis-p7-auth-23.txt</title>
9  <style type="text/css">
10    body    { margin: 0.4ex; margin-right: auto; }
11    tr      { }
12    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;}
13    th      { font-size: 0.86em; }
14    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; }
15    .left   { background-color: #EEE; }
16    .right  { background-color: #FFF; }
17    .diff   { background-color: #CCF; }
18    .lblock { background-color: #BFB; }
19    .rblock { background-color: #FF8; }
20    .insert { background-color: #8FF; }
21    .delete { background-color: #ACF; }
22    .void   { background-color: #FFB; }
23    .cont   { background-color: #EEE; }
24    .linebr { background-color: #AAA; }
25    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; }
26    .elipsis{ background-color: #AAA; }
27    .left .cont { background-color: #DDD; }
28    .right .cont { background-color: #EEE; }
29    .lblock .cont { background-color: #9D9; }
30    .rblock .cont { background-color: #DD6; }
31    .insert .cont { background-color: #0DD; }
32    .delete .cont { background-color: #8AD; }
33    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; }
34  </style>
35</head>
36<body > 
37  <table border="0" cellpadding="0" cellspacing="0">
38  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-httpbis-p7-auth-22.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-httpbis-p7-auth-23.txt&nbsp;</th><th></th></tr>
39      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
40      <tr><td class="lineno" valign="top"></td><td class="left">HTTPbis Working Group                                   R. Fielding, Ed.</td><td> </td><td class="right">HTTPbis Working Group                                   R. Fielding, Ed.</td><td class="lineno" valign="top"></td></tr>
41      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                     Adobe</td><td> </td><td class="right">Internet-Draft                                                     Adobe</td><td class="lineno" valign="top"></td></tr>
42      <tr><td class="lineno" valign="top"></td><td class="left">Obsoletes: 2616 (if approved)                            J. Reschke, Ed.</td><td> </td><td class="right">Obsoletes: 2616 (if approved)                            J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
43      <tr><td class="lineno" valign="top"></td><td class="left">Updates: 2617 (if approved)                                   greenbytes</td><td> </td><td class="right">Updates: 2617 (if approved)                                   greenbytes</td><td class="lineno" valign="top"></td></tr>
44      <tr><td><a name="diff0001" /></td></tr>
45      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Standards Track                       <span class="delete">February 23,</span> 2013</td><td> </td><td class="rblock">Intended status: Standards Track                           <span class="insert">July 15,</span> 2013</td><td class="lineno" valign="top"></td></tr>
46      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">August 27, 2013</span></td><td> </td><td class="rblock">Expires: <span class="insert">January 16, 2014</span></td><td class="lineno" valign="top"></td></tr>
47      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
48      <tr><td class="lineno" valign="top"></td><td class="left">         Hypertext Transfer Protocol (HTTP/1.1): Authentication</td><td> </td><td class="right">         Hypertext Transfer Protocol (HTTP/1.1): Authentication</td><td class="lineno" valign="top"></td></tr>
49      <tr><td><a name="diff0002" /></td></tr>
50      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-httpbis-p7-auth-2<span class="delete">2</span></td><td> </td><td class="rblock">                     draft-ietf-httpbis-p7-auth-2<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
51      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
52      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
53      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
54      <tr><td class="lineno" valign="top"></td><td class="left">   The Hypertext Transfer Protocol (HTTP) is an application-level</td><td> </td><td class="right">   The Hypertext Transfer Protocol (HTTP) is an application-level</td><td class="lineno" valign="top"></td></tr>
55      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for distributed, collaborative, hypermedia information</td><td> </td><td class="right">   protocol for distributed, collaborative, hypermedia information</td><td class="lineno" valign="top"></td></tr>
56      <tr><td class="lineno" valign="top"></td><td class="left">   systems.  This document defines the HTTP Authentication framework.</td><td> </td><td class="right">   systems.  This document defines the HTTP Authentication framework.</td><td class="lineno" valign="top"></td></tr>
57      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
58      <tr><td class="lineno" valign="top"></td><td class="left">Editorial Note (To be removed by RFC Editor)</td><td> </td><td class="right">Editorial Note (To be removed by RFC Editor)</td><td class="lineno" valign="top"></td></tr>
59      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="left">   Discussion of this draft takes place on the HTTPBIS working group</td><td> </td><td class="right">   Discussion of this draft takes place on the HTTPBIS working group</td><td class="lineno" valign="top"></td></tr>
61      <tr><td class="lineno" valign="top"></td><td class="left">   mailing list (ietf-http-wg@w3.org), which is archived at</td><td> </td><td class="right">   mailing list (ietf-http-wg@w3.org), which is archived at</td><td class="lineno" valign="top"></td></tr>
62      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://lists.w3.org/Archives/Public/ietf-http-wg/&gt;.</td><td> </td><td class="right">   &lt;http://lists.w3.org/Archives/Public/ietf-http-wg/&gt;.</td><td class="lineno" valign="top"></td></tr>
63      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
64      <tr><td class="lineno" valign="top"></td><td class="left">   The current issues list is at</td><td> </td><td class="right">   The current issues list is at</td><td class="lineno" valign="top"></td></tr>
65      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td> </td><td class="right">   &lt;http://tools.ietf.org/wg/httpbis/trac/report/3&gt; and related</td><td class="lineno" valign="top"></td></tr>
66      <tr><td class="lineno" valign="top"></td><td class="left">   documents (including fancy diffs) can be found at</td><td> </td><td class="right">   documents (including fancy diffs) can be found at</td><td class="lineno" valign="top"></td></tr>
67      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://tools.ietf.org/wg/httpbis/&gt;.</td><td> </td><td class="right">   &lt;http://tools.ietf.org/wg/httpbis/&gt;.</td><td class="lineno" valign="top"></td></tr>
68      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
69      <tr><td><a name="diff0003" /></td></tr>
70      <tr><td class="lineno" valign="top"></td><td class="lblock">   The changes in this draft are summarized in Appendix D.<span class="delete">3</span>.</td><td> </td><td class="rblock">   The changes in this draft are summarized in Appendix D.<span class="insert">4</span>.</td><td class="lineno" valign="top"></td></tr>
71      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
72      <tr><td class="lineno" valign="top"></td><td class="left">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno" valign="top"></td></tr>
73      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="left">   This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right">   This Internet-Draft is submitted in full conformance with the</td><td class="lineno" valign="top"></td></tr>
75      <tr><td class="lineno" valign="top"></td><td class="left">   provisions of BCP 78 and BCP 79.</td><td> </td><td class="right">   provisions of BCP 78 and BCP 79.</td><td class="lineno" valign="top"></td></tr>
76      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
77      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
78      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
79      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
80      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
81      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
82      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
83      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
84      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
85      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
86      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
87      <tr><td><a name="diff0004" /></td></tr>
88      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">August 27, 2013</span>.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">January 16, 2014</span>.</td><td class="lineno" valign="top"></td></tr>
89      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
90      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
91      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2013 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2013 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
92      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
93      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
94      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
95      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
96      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
97      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
98      <tr><td class="lineno" valign="top"></td><td class="left">   carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right">   carefully, as they describe your rights and restrictions with respect</td><td class="lineno" valign="top"></td></tr>
99      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
100      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 3, line 13</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 3, line 13</em></th><td></td></tr>
101      <tr><td class="lineno" valign="top"></td><td class="left">   than English.</td><td> </td><td class="right">   than English.</td><td class="lineno" valign="top"></td></tr>
102      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
103      <tr><td class="lineno" valign="top"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno" valign="top"></td></tr>
104      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
105      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
106      <tr><td class="lineno" valign="top"></td><td class="left">     1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  4</td><td> </td><td class="right">     1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left">     1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">     1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
108      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Access Authentication Framework  . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">   2.  Access Authentication Framework  . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
109      <tr><td class="lineno" valign="top"></td><td class="left">     2.1.  Challenge and Response . . . . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">     2.1.  Challenge and Response . . . . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
110      <tr><td class="lineno" valign="top"></td><td class="left">     2.2.  Protection Space (Realm) . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     2.2.  Protection Space (Realm) . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
111      <tr><td><a name="diff0005" /></td></tr>
112      <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">2.3.  Authentication Scheme Registry . . . . . . . . . . . . . .  7</span></td><td> </td><td class="rblock">   3.  Status Code Definitions  . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
113      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       2.3.1.  Considerations for New Authentication Schemes  . . . .  7</span></td><td> </td><td class="rblock">     3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
114      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Status Code Definitions  . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
115      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
116      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.1.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
117      <tr><td class="lineno" valign="top"></td><td class="lblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.2.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
118      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.1.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.3.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.2.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">     4.4.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
120      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.3.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
121      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.4.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">     5.1.  Authentication Scheme Registry . . . . . . . . . . . . . . <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
122      <tr><td class="lineno" valign="top"></td><td class="lblock">   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">11</span></td><td> </td><td class="rblock"><span class="insert">       5.1.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 10</span></td><td class="lineno" valign="top"></td></tr>
123      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.1.  Authentication Scheme Registry . . . . . . . . . . . . . . <span class="delete">11</span></td><td> </td><td class="rblock"><span class="insert">       5.1.2.  Considerations for New Authentication Schemes  . . . . 10</span></td><td class="lineno" valign="top"></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="left">     5.2.  Status Code Registration . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     5.2.  Status Code Registration . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="left">     5.3.  Header Field Registration  . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     5.3.  Header Field Registration  . . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="left">     6.1.  Authentication Credentials and Idle Clients  . . . . . . . 12</td><td> </td><td class="right">     6.1.  Authentication Credentials and Idle Clients  . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="left">     6.2.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">     6.2.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
129      <tr><td class="lineno" valign="top"></td><td class="left">   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
130      <tr><td><a name="diff0006" /></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">13</span></td><td> </td><td class="rblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">14</span></td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="delete">13</span></td><td> </td><td class="rblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="insert">14</span></td><td class="lineno" valign="top"></td></tr>
133      <tr><td class="lineno" valign="top"></td><td class="left">     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14</td><td> </td><td class="right">     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14</td><td class="lineno" valign="top"></td></tr>
134      <tr><td><a name="diff0007" /></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . 1<span class="delete">4</span></td><td> </td><td class="rblock">   Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . 1<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
136      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 15</td><td> </td><td class="right">   Appendix B.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 15</td><td class="lineno" valign="top"></td></tr>
137      <tr><td><a name="diff0008" /></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix C.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 1<span class="delete">6</span></td><td> </td><td class="rblock">   Appendix C.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 1<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix D.  Change Log (to be removed by RFC Editor before</td><td> </td><td class="right">   Appendix D.  Change Log (to be removed by RFC Editor before</td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno" valign="top"></td><td class="left">                publication)  . . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">                publication)  . . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
141      <tr><td class="lineno" valign="top"></td><td class="left">     D.1.  Since draft-ietf-httpbis-p7-auth-19  . . . . . . . . . . . 16</td><td> </td><td class="right">     D.1.  Since draft-ietf-httpbis-p7-auth-19  . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="left">     D.2.  Since draft-ietf-httpbis-p7-auth-20  . . . . . . . . . . . 17</td><td> </td><td class="right">     D.2.  Since draft-ietf-httpbis-p7-auth-20  . . . . . . . . . . . 17</td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="left">     D.3.  Since draft-ietf-httpbis-p7-auth-21  . . . . . . . . . . . 17</td><td> </td><td class="right">     D.3.  Since draft-ietf-httpbis-p7-auth-21  . . . . . . . . . . . 17</td><td class="lineno" valign="top"></td></tr>
144      <tr><td><a name="diff0009" /></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     D.4.  Since draft-ietf-httpbis-p7-auth-22  . . . . . . . . . . . 17</span></td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17</td><td> </td><td class="right">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17</td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines HTTP/1.1 access control and authentication.  It</td><td> </td><td class="right">   This document defines HTTP/1.1 access control and authentication.  It</td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">   includes the relevant parts of RFC 2616 with only minor changes</td><td> </td><td class="right">   includes the relevant parts of RFC 2616 with only minor changes</td><td class="lineno" valign="top"></td></tr>
152      <tr><td class="lineno" valign="top"></td><td class="left">   ([RFC2616]), plus the general framework for HTTP authentication, as</td><td> </td><td class="right">   ([RFC2616]), plus the general framework for HTTP authentication, as</td><td class="lineno" valign="top"></td></tr>
153      <tr><td class="lineno" valign="top"></td><td class="left">   previously defined in "HTTP Authentication: Basic and Digest Access</td><td> </td><td class="right">   previously defined in "HTTP Authentication: Basic and Digest Access</td><td class="lineno" valign="top"></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="left">   Authentication" ([RFC2617]).</td><td> </td><td class="right">   Authentication" ([RFC2617]).</td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP provides several OPTIONAL challenge-response authentication</td><td> </td><td class="right">   HTTP provides several OPTIONAL challenge-response authentication</td><td class="lineno" valign="top"></td></tr>
157      <tr><td><a name="diff0010" /></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">mechanism</span>s that can be used by a server to challenge a client request</td><td> </td><td class="rblock">   <span class="insert">scheme</span>s that can be used by a server to challenge a client request</td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="left">   and by a client to provide authentication information.  The "basic"</td><td> </td><td class="right">   and by a client to provide authentication information.  The "basic"</td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left">   and "digest" authentication schemes continue to be specified in RFC</td><td> </td><td class="right">   and "digest" authentication schemes continue to be specified in RFC</td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="left">   2617.</td><td> </td><td class="right">   2617.</td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="left">1.1.  Conformance and Error Handling</td><td> </td><td class="right">1.1.  Conformance and Error Handling</td><td class="lineno" valign="top"></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="left">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno" valign="top"></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="left">   document are to be interpreted as described in [RFC2119].</td><td> </td><td class="right">   document are to be interpreted as described in [RFC2119].</td><td class="lineno" valign="top"></td></tr>
168      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
169      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
170      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 4, line 40</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 4, line 40</em></th><td></td></tr>
171      <tr><td class="lineno" valign="top"></td><td class="left">   This specification uses the Augmented Backus-Naur Form (ABNF)</td><td> </td><td class="right">   This specification uses the Augmented Backus-Naur Form (ABNF)</td><td class="lineno" valign="top"></td></tr>
172      <tr><td class="lineno" valign="top"></td><td class="left">   notation of [RFC5234] with the list rule extension defined in Section</td><td> </td><td class="right">   notation of [RFC5234] with the list rule extension defined in Section</td><td class="lineno" valign="top"></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="left">   1.2 of [Part1].  Appendix B describes rules imported from other</td><td> </td><td class="right">   1.2 of [Part1].  Appendix B describes rules imported from other</td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">   documents.  Appendix C shows the collected ABNF with the list rule</td><td> </td><td class="right">   documents.  Appendix C shows the collected ABNF with the list rule</td><td class="lineno" valign="top"></td></tr>
175      <tr><td class="lineno" valign="top"></td><td class="left">   expanded.</td><td> </td><td class="right">   expanded.</td><td class="lineno" valign="top"></td></tr>
176      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="left">2.  Access Authentication Framework</td><td> </td><td class="right">2.  Access Authentication Framework</td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="left">2.1.  Challenge and Response</td><td> </td><td class="right">2.1.  Challenge and Response</td><td class="lineno" valign="top"></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
181      <tr><td><a name="diff0011" /></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP provides a simple challenge-response authentication <span class="delete">mechanism</span></td><td> </td><td class="rblock">   HTTP provides a simple challenge-response authentication <span class="insert">framework</span></td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="left">   that can be used by a server to challenge a client request and by a</td><td> </td><td class="right">   that can be used by a server to challenge a client request and by a</td><td class="lineno" valign="top"></td></tr>
184      <tr><td><a name="diff0012" /></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="lblock">   client to provide authentication information.  It uses <span class="delete">an extensible,</span></td><td> </td><td class="rblock">   client to provide authentication information.  It uses <span class="insert">a case-</span></td><td class="lineno" valign="top"></td></tr>
186      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   case-insensitive</span> token to identify the authentication scheme,</td><td> </td><td class="rblock"><span class="insert">   insensitive</span> token <span class="insert">as a means</span> to identify the authentication scheme,</td><td class="lineno" valign="top"></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="left">   followed by additional information necessary for achieving</td><td> </td><td class="right">   followed by additional information necessary for achieving</td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">   authentication via that scheme.  The latter can either be a comma-</td><td> </td><td class="right">   authentication via that scheme.  The latter can either be a comma-</td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">   separated list of parameters or a single sequence of characters</td><td> </td><td class="right">   separated list of parameters or a single sequence of characters</td><td class="lineno" valign="top"></td></tr>
190      <tr><td class="lineno" valign="top"></td><td class="left">   capable of holding base64-encoded information.</td><td> </td><td class="right">   capable of holding base64-encoded information.</td><td class="lineno" valign="top"></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="left">   Parameters are name-value pairs where the name is matched case-</td><td> </td><td class="right">   Parameters are name-value pairs where the name is matched case-</td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="left">   insensitively, and each parameter name MUST only occur once per</td><td> </td><td class="right">   insensitively, and each parameter name MUST only occur once per</td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="left">   challenge.</td><td> </td><td class="right">   challenge.</td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">     auth-scheme    = token</td><td> </td><td class="right">     auth-scheme    = token</td><td class="lineno" valign="top"></td></tr>
197      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
198      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 6, line 4</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 6, line 4</em></th><td></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="left">   -- can do so by including an Authorization header field with the</td><td> </td><td class="right">   -- can do so by including an Authorization header field with the</td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">   request.</td><td> </td><td class="right">   request.</td><td class="lineno" valign="top"></td></tr>
201      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="left">   A client that wishes to authenticate itself with a proxy -- usually,</td><td> </td><td class="right">   A client that wishes to authenticate itself with a proxy -- usually,</td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left">   but not necessarily, after receiving a 407 (Proxy Authentication</td><td> </td><td class="right">   but not necessarily, after receiving a 407 (Proxy Authentication</td><td class="lineno" valign="top"></td></tr>
204      <tr><td class="lineno" valign="top"></td><td class="left">   Required) -- can do so by including a Proxy-Authorization header</td><td> </td><td class="right">   Required) -- can do so by including a Proxy-Authorization header</td><td class="lineno" valign="top"></td></tr>
205      <tr><td class="lineno" valign="top"></td><td class="left">   field with the request.</td><td> </td><td class="right">   field with the request.</td><td class="lineno" valign="top"></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="left">   Both the Authorization field value and the Proxy-Authorization field</td><td> </td><td class="right">   Both the Authorization field value and the Proxy-Authorization field</td><td class="lineno" valign="top"></td></tr>
208      <tr><td class="lineno" valign="top"></td><td class="left">   value contain the client's credentials for the realm of the resource</td><td> </td><td class="right">   value contain the client's credentials for the realm of the resource</td><td class="lineno" valign="top"></td></tr>
209      <tr><td><a name="diff0013" /></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="lblock">   being requested, based upon a challenge received <span class="delete">from the server</span></td><td> </td><td class="rblock">   being requested, based upon a challenge received <span class="insert">in a response</span></td><td class="lineno" valign="top"></td></tr>
211      <tr><td class="lineno" valign="top"></td><td class="left">   (possibly at some point in the past).  When creating their values,</td><td> </td><td class="right">   (possibly at some point in the past).  When creating their values,</td><td class="lineno" valign="top"></td></tr>
212      <tr><td class="lineno" valign="top"></td><td class="left">   the user agent ought to do so by selecting the challenge with what it</td><td> </td><td class="right">   the user agent ought to do so by selecting the challenge with what it</td><td class="lineno" valign="top"></td></tr>
213      <tr><td class="lineno" valign="top"></td><td class="left">   considers to be the most secure auth-scheme that it understands,</td><td> </td><td class="right">   considers to be the most secure auth-scheme that it understands,</td><td class="lineno" valign="top"></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="left">   obtaining credentials from the user as appropriate.</td><td> </td><td class="right">   obtaining credentials from the user as appropriate.</td><td class="lineno" valign="top"></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
216      <tr><td class="lineno" valign="top"></td><td class="left">     credentials = auth-scheme [ 1*SP ( token68 / #auth-param ) ]</td><td> </td><td class="right">     credentials = auth-scheme [ 1*SP ( token68 / #auth-param ) ]</td><td class="lineno" valign="top"></td></tr>
217      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
218      <tr><td class="lineno" valign="top"></td><td class="left">   Upon a request for a protected resource that omits credentials,</td><td> </td><td class="right">   Upon a request for a protected resource that omits credentials,</td><td class="lineno" valign="top"></td></tr>
219      <tr><td class="lineno" valign="top"></td><td class="left">   contains invalid credentials (e.g., a bad password) or partial</td><td> </td><td class="right">   contains invalid credentials (e.g., a bad password) or partial</td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left">   credentials (e.g., when the authentication scheme requires more than</td><td> </td><td class="right">   credentials (e.g., when the authentication scheme requires more than</td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
222      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 6, line 30</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 6, line 30</em></th><td></td></tr>
223      <tr><td class="lineno" valign="top"></td><td class="left">   omit credentials or contain invalid or partial credentials, a proxy</td><td> </td><td class="right">   omit credentials or contain invalid or partial credentials, a proxy</td><td class="lineno" valign="top"></td></tr>
224      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD send a 407 (Proxy Authentication Required) response that</td><td> </td><td class="right">   SHOULD send a 407 (Proxy Authentication Required) response that</td><td class="lineno" valign="top"></td></tr>
225      <tr><td class="lineno" valign="top"></td><td class="left">   contains a Proxy-Authenticate header field with a (possibly new)</td><td> </td><td class="right">   contains a Proxy-Authenticate header field with a (possibly new)</td><td class="lineno" valign="top"></td></tr>
226      <tr><td class="lineno" valign="top"></td><td class="left">   challenge applicable to the proxy.</td><td> </td><td class="right">   challenge applicable to the proxy.</td><td class="lineno" valign="top"></td></tr>
227      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
228      <tr><td class="lineno" valign="top"></td><td class="left">   A server receiving credentials that are valid, but not adequate to</td><td> </td><td class="right">   A server receiving credentials that are valid, but not adequate to</td><td class="lineno" valign="top"></td></tr>
229      <tr><td class="lineno" valign="top"></td><td class="left">   gain access, ought to respond with the 403 (Forbidden) status code</td><td> </td><td class="right">   gain access, ought to respond with the 403 (Forbidden) status code</td><td class="lineno" valign="top"></td></tr>
230      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.5.3 of [Part2]).</td><td> </td><td class="right">   (Section 6.5.3 of [Part2]).</td><td class="lineno" valign="top"></td></tr>
231      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP protocol does not restrict applications to this simple</td><td> </td><td class="right">   The HTTP protocol does not restrict applications to this simple</td><td class="lineno" valign="top"></td></tr>
233      <tr><td><a name="diff0014" /></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="lblock">   challenge-response <span class="delete">mechanism</span> for access authentication.  Additional</td><td> </td><td class="rblock">   challenge-response <span class="insert">framework</span> for access authentication.  Additional</td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">   mechanisms MAY be used, such as encryption at the transport level or</td><td> </td><td class="right">   mechanisms MAY be used, such as encryption at the transport level or</td><td class="lineno" valign="top"></td></tr>
236      <tr><td class="lineno" valign="top"></td><td class="left">   via message encapsulation, and with additional header fields</td><td> </td><td class="right">   via message encapsulation, and with additional header fields</td><td class="lineno" valign="top"></td></tr>
237      <tr><td class="lineno" valign="top"></td><td class="left">   specifying authentication information.  However, such additional</td><td> </td><td class="right">   specifying authentication information.  However, such additional</td><td class="lineno" valign="top"></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="left">   mechanisms are not defined by this specification.</td><td> </td><td class="right">   mechanisms are not defined by this specification.</td><td class="lineno" valign="top"></td></tr>
239      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="left">   Proxies MUST forward the WWW-Authenticate and Authorization header</td><td> </td><td class="right">   Proxies MUST forward the WWW-Authenticate and Authorization header</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="left">   fields unmodified and follow the rules found in Section 4.1.</td><td> </td><td class="right">   fields unmodified and follow the rules found in Section 4.1.</td><td class="lineno" valign="top"></td></tr>
242      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="left">2.2.  Protection Space (Realm)</td><td> </td><td class="right">2.2.  Protection Space (Realm)</td><td class="lineno" valign="top"></td></tr>
244      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
245      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
246      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 7, line 4</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 7, line 4</em></th><td></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="left">   authentication schemes that wish to indicate the scope of protection.</td><td> </td><td class="right">   authentication schemes that wish to indicate the scope of protection.</td><td class="lineno" valign="top"></td></tr>
248      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
249      <tr><td class="lineno" valign="top"></td><td class="left">   A protection space is defined by the canonical root URI (the scheme</td><td> </td><td class="right">   A protection space is defined by the canonical root URI (the scheme</td><td class="lineno" valign="top"></td></tr>
250      <tr><td class="lineno" valign="top"></td><td class="left">   and authority components of the effective request URI; see Section</td><td> </td><td class="right">   and authority components of the effective request URI; see Section</td><td class="lineno" valign="top"></td></tr>
251      <tr><td class="lineno" valign="top"></td><td class="left">   5.5 of [Part1]) of the server being accessed, in combination with the</td><td> </td><td class="right">   5.5 of [Part1]) of the server being accessed, in combination with the</td><td class="lineno" valign="top"></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="left">   realm value if present.  These realms allow the protected resources</td><td> </td><td class="right">   realm value if present.  These realms allow the protected resources</td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="left">   on a server to be partitioned into a set of protection spaces, each</td><td> </td><td class="right">   on a server to be partitioned into a set of protection spaces, each</td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="left">   with its own authentication scheme and/or authorization database.</td><td> </td><td class="right">   with its own authentication scheme and/or authorization database.</td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="left">   The realm value is a string, generally assigned by the origin server,</td><td> </td><td class="right">   The realm value is a string, generally assigned by the origin server,</td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="left">   that can have additional semantics specific to the authentication</td><td> </td><td class="right">   that can have additional semantics specific to the authentication</td><td class="lineno" valign="top"></td></tr>
257      <tr><td><a name="diff0015" /></td></tr>
258      <tr><td class="lineno" valign="top"></td><td class="lblock">   scheme.  Note that <span class="delete">there</span> can <span class="delete">be</span> multiple challenges with the same</td><td> </td><td class="rblock">   scheme.  Note that <span class="insert">a response</span> can <span class="insert">have</span> multiple challenges with the</td><td class="lineno" valign="top"></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="lblock">   auth-scheme but different realms.</td><td> </td><td class="rblock">   same auth-scheme but different realms.</td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="left">   The protection space determines the domain over which credentials can</td><td> </td><td class="right">   The protection space determines the domain over which credentials can</td><td class="lineno" valign="top"></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="left">   be automatically applied.  If a prior request has been authorized,</td><td> </td><td class="right">   be automatically applied.  If a prior request has been authorized,</td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="left">   the same credentials MAY be reused for all other requests within that</td><td> </td><td class="right">   the same credentials MAY be reused for all other requests within that</td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="left">   protection space for a period of time determined by the</td><td> </td><td class="right">   protection space for a period of time determined by the</td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="left">   authentication scheme, parameters, and/or user preference.  Unless</td><td> </td><td class="right">   authentication scheme, parameters, and/or user preference.  Unless</td><td class="lineno" valign="top"></td></tr>
266      <tr><td><a name="diff0016" /></td></tr>
267      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">otherwise defined</span> by the authentication scheme, a single protection</td><td> </td><td class="rblock">   <span class="insert">specifically allowed</span> by the authentication scheme, a single</td><td class="lineno" valign="top"></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="lblock">   space cannot extend outside the scope of its server.</td><td> </td><td class="rblock">   protection space cannot extend outside the scope of its server.</td><td class="lineno" valign="top"></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
270      <tr><td><a name="diff0017" /></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="lblock">   For historical reasons, senders MUST only <span class="delete">us</span>e the quoted-string</td><td> </td><td class="rblock">   For historical reasons, senders MUST only <span class="insert">generat</span>e the quoted-string</td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="left">   syntax.  Recipients might have to support both token and quoted-</td><td> </td><td class="right">   syntax.  Recipients might have to support both token and quoted-</td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="left">   string syntax for maximum interoperability with existing clients that</td><td> </td><td class="right">   string syntax for maximum interoperability with existing clients that</td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left">   have been accepting both notations for a long time.</td><td> </td><td class="right">   have been accepting both notations for a long time.</td><td class="lineno" valign="top"></td></tr>
275      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
276      <tr><td><a name="diff0018" /></td></tr>
277      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">2.3.  Authentication Scheme Registry</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
278      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
279      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The HTTP Authentication Scheme Registry defines the name space for</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
280      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the authentication schemes in challenges and credentials.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
281      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registrations MUST include the following fields:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Authentication Scheme Name</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Pointer to specification text</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Notes (optional)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Values to be added to this name space require IETF Review (see</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   [RFC5226], Section 4.1).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
292      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
293      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The registry itself is maintained at</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
294      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   &lt;http://www.iana.org/assignments/http-authschemes&gt;.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
295      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">2.3.1.  Considerations for New Authentication Schemes</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
297      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
298      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   There are certain aspects of the HTTP Authentication Framework that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
299      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   put constraints on how new authentication schemes can work:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
301      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  HTTP authentication is presumed to be stateless: all of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      information necessary to authenticate a request MUST be provided</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
303      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      in the request, rather than be dependent on the server remembering</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      prior requests.  Authentication based on, or bound to, the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      underlying connection is outside the scope of this specification</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      and inherently flawed unless steps are taken to ensure that the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      connection cannot be used by any party other than the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      authenticated user (see Section 2.3 of [Part1]).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
310      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  The authentication parameter "realm" is reserved for defining</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
311      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Protection Spaces as defined in Section 2.2.  New schemes MUST NOT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
312      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      use it in a way incompatible with that definition.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
313      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  The "token68" notation was introduced for compatibility with</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      existing authentication schemes and can only be used once per</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      challenge/credentials.  New schemes thus ought to use the "auth-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
317      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      param" syntax instead, because otherwise future extensions will be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      impossible.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  The parsing of challenges and credentials is defined by this</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
321      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      specification, and cannot be modified by new authentication</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
322      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      schemes.  When the auth-param syntax is used, all parameters ought</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      to support both token and quoted-string syntax, and syntactical</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
324      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      constraints ought to be defined on the field value after parsing</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      (i.e., quoted-string processing).  This is necessary so that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      recipients can use a generic parser that applies to all</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
327      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      authentication schemes.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
328      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: The fact that the value syntax for the "realm" parameter is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
330      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      restricted to quoted-string was a bad design choice not to be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
331      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      repeated for new parameters.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
332      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
333      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Definitions of new schemes ought to define the treatment of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
334      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      unknown extension parameters.  In general, a "must-ignore" rule is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
335      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      preferable over "must-understand", because otherwise it will be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
336      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      hard to introduce new parameters in the presence of legacy</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
337      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      recipients.  Furthermore, it's good to describe the policy for</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
338      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      defining new parameters (such as "update the specification", or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
339      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      "use this registry").</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
340      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
341      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Authentication schemes need to document whether they are usable in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
342      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      origin-server authentication (i.e., using WWW-Authenticate),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
343      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      and/or proxy authentication (i.e., using Proxy-Authenticate).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
344      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
345      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  The credentials carried in an Authorization header field are</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
346      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      specific to the User Agent, and therefore have the same effect on</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
347      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      HTTP caches as the "private" Cache-Control response directive,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
348      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      within the scope of the request they appear in.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
349      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
350      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Therefore, new authentication schemes that choose not to carry</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      credentials in the Authorization header field (e.g., using a newly</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      defined header field) will need to explicitly disallow caching, by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      mandating the use of either Cache-Control request directives</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
354      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      (e.g., "no-store") or response directives (e.g., "private").</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
355      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
356      <tr><td class="lineno" valign="top"></td><td class="left">3.  Status Code Definitions</td><td> </td><td class="right">3.  Status Code Definitions</td><td class="lineno" valign="top"></td></tr>
357      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
358      <tr><td class="lineno" valign="top"></td><td class="left">3.1.  401 Unauthorized</td><td> </td><td class="right">3.1.  401 Unauthorized</td><td class="lineno" valign="top"></td></tr>
359      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
360      <tr><td class="lineno" valign="top"></td><td class="left">   The 401 (Unauthorized) status code indicates that the request has not</td><td> </td><td class="right">   The 401 (Unauthorized) status code indicates that the request has not</td><td class="lineno" valign="top"></td></tr>
361      <tr><td class="lineno" valign="top"></td><td class="left">   been applied because it lacks valid authentication credentials for</td><td> </td><td class="right">   been applied because it lacks valid authentication credentials for</td><td class="lineno" valign="top"></td></tr>
362      <tr><td class="lineno" valign="top"></td><td class="left">   the target resource.  The origin server MUST send a WWW-Authenticate</td><td> </td><td class="right">   the target resource.  The origin server MUST send a WWW-Authenticate</td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="left">   header field (Section 4.4) containing at least one challenge</td><td> </td><td class="right">   header field (Section 4.4) containing at least one challenge</td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="left">   applicable to the target resource.  If the request included</td><td> </td><td class="right">   applicable to the target resource.  If the request included</td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="left">   authentication credentials, then the 401 response indicates that</td><td> </td><td class="right">   authentication credentials, then the 401 response indicates that</td><td class="lineno" valign="top"></td></tr>
366      <tr><td><a name="diff0019" /></td></tr>
367      <tr><td class="lineno" valign="top"></td><td class="lblock">   authorization has been refused for those credentials.  The <span class="delete">client</span> MAY</td><td> </td><td class="rblock">   authorization has been refused for those credentials.  The <span class="insert">user agent</span></td><td class="lineno" valign="top"></td></tr>
368      <tr><td class="lineno" valign="top"></td><td class="lblock">   repeat the request with a new or replaced Authorization header field</td><td> </td><td class="rblock">   MAY repeat the request with a new or replaced Authorization header</td><td class="lineno" valign="top"></td></tr>
369      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 4.1).  If the 401 response contains the same challenge as</td><td> </td><td class="rblock">   field (Section 4.1).  If the 401 response contains the same challenge</td><td class="lineno" valign="top"></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="lblock">   the prior response, and the user agent has already attempted</td><td> </td><td class="rblock">   as the prior response, and the user agent has already attempted</td><td class="lineno" valign="top"></td></tr>
371      <tr><td class="lineno" valign="top"></td><td class="left">   authentication at least once, then the user agent SHOULD present the</td><td> </td><td class="right">   authentication at least once, then the user agent SHOULD present the</td><td class="lineno" valign="top"></td></tr>
372      <tr><td class="lineno" valign="top"></td><td class="left">   enclosed representation to the user, since it usually contains</td><td> </td><td class="right">   enclosed representation to the user, since it usually contains</td><td class="lineno" valign="top"></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="left">   relevant diagnostic information.</td><td> </td><td class="right">   relevant diagnostic information.</td><td class="lineno" valign="top"></td></tr>
374      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
375      <tr><td class="lineno" valign="top"></td><td class="left">3.2.  407 Proxy Authentication Required</td><td> </td><td class="right">3.2.  407 Proxy Authentication Required</td><td class="lineno" valign="top"></td></tr>
376      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
377      <tr><td class="lineno" valign="top"></td><td class="left">   The 407 (Proxy Authentication Required) status code is similar to 401</td><td> </td><td class="right">   The 407 (Proxy Authentication Required) status code is similar to 401</td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left">   (Unauthorized), but indicates that the client needs to authenticate</td><td> </td><td class="right">   (Unauthorized), but indicates that the client needs to authenticate</td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno" valign="top"></td><td class="left">   itself in order to use a proxy.  The proxy MUST send a Proxy-</td><td> </td><td class="right">   itself in order to use a proxy.  The proxy MUST send a Proxy-</td><td class="lineno" valign="top"></td></tr>
380      <tr><td class="lineno" valign="top"></td><td class="left">   Authenticate header field (Section 4.2) containing a challenge</td><td> </td><td class="right">   Authenticate header field (Section 4.2) containing a challenge</td><td class="lineno" valign="top"></td></tr>
381      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
382      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 9, line 41</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 8, line 8</em></th><td></td></tr>
383      <tr><td class="lineno" valign="top"></td><td class="left">   field (Section 4.3).</td><td> </td><td class="right">   field (Section 4.3).</td><td class="lineno" valign="top"></td></tr>
384      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
385      <tr><td class="lineno" valign="top"></td><td class="left">4.  Header Field Definitions</td><td> </td><td class="right">4.  Header Field Definitions</td><td class="lineno" valign="top"></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="left">   This section defines the syntax and semantics of HTTP/1.1 header</td><td> </td><td class="right">   This section defines the syntax and semantics of HTTP/1.1 header</td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left">   fields related to authentication.</td><td> </td><td class="right">   fields related to authentication.</td><td class="lineno" valign="top"></td></tr>
389      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
390      <tr><td class="lineno" valign="top"></td><td class="left">4.1.  Authorization</td><td> </td><td class="right">4.1.  Authorization</td><td class="lineno" valign="top"></td></tr>
391      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
392      <tr><td class="lineno" valign="top"></td><td class="left">   The "Authorization" header field allows a user agent to authenticate</td><td> </td><td class="right">   The "Authorization" header field allows a user agent to authenticate</td><td class="lineno" valign="top"></td></tr>
393      <tr><td><a name="diff0020" /></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="lblock">   itself with <span class="delete">a</span> server -- usually, but not necessarily, after receiving</td><td> </td><td class="rblock">   itself with <span class="insert">an origin</span> server -- usually, but not necessarily, after</td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno" valign="top"></td><td class="lblock">   a 401 (Unauthorized) response.  Its value consists of credentials</td><td> </td><td class="rblock">   receiving a 401 (Unauthorized) response.  Its value consists of</td><td class="lineno" valign="top"></td></tr>
396      <tr><td class="lineno" valign="top"></td><td class="lblock">   containing information of the user agent for the realm of the</td><td> </td><td class="rblock">   credentials containing information of the user agent for the realm of</td><td class="lineno" valign="top"></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="lblock">   resource being requested.</td><td> </td><td class="rblock">   the resource being requested.</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
399      <tr><td class="lineno" valign="top"></td><td class="left">     Authorization = credentials</td><td> </td><td class="right">     Authorization = credentials</td><td class="lineno" valign="top"></td></tr>
400      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
401      <tr><td class="lineno" valign="top"></td><td class="left">   If a request is authenticated and a realm specified, the same</td><td> </td><td class="right">   If a request is authenticated and a realm specified, the same</td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">   credentials SHOULD be valid for all other requests within this realm</td><td> </td><td class="right">   credentials SHOULD be valid for all other requests within this realm</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left">   (assuming that the authentication scheme itself does not require</td><td> </td><td class="right">   (assuming that the authentication scheme itself does not require</td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left">   otherwise, such as credentials that vary according to a challenge</td><td> </td><td class="right">   otherwise, such as credentials that vary according to a challenge</td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left">   value or using synchronized clocks).</td><td> </td><td class="right">   value or using synchronized clocks).</td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
407      <tr><td class="lineno" valign="top"></td><td class="left">   See Section 3.2 of [Part6] for details of and requirements pertaining</td><td> </td><td class="right">   See Section 3.2 of [Part6] for details of and requirements pertaining</td><td class="lineno" valign="top"></td></tr>
408      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
409      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 10, line 33</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 8, line 49</em></th><td></td></tr>
410      <tr><td class="lineno" valign="top"></td><td class="left">   forwarding the Proxy-Authenticate header field.</td><td> </td><td class="right">   forwarding the Proxy-Authenticate header field.</td><td class="lineno" valign="top"></td></tr>
411      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
412      <tr><td class="lineno" valign="top"></td><td class="left">   Note that the parsing considerations for WWW-Authenticate apply to</td><td> </td><td class="right">   Note that the parsing considerations for WWW-Authenticate apply to</td><td class="lineno" valign="top"></td></tr>
413      <tr><td class="lineno" valign="top"></td><td class="left">   this header field as well; see Section 4.4 for details.</td><td> </td><td class="right">   this header field as well; see Section 4.4 for details.</td><td class="lineno" valign="top"></td></tr>
414      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
415      <tr><td class="lineno" valign="top"></td><td class="left">4.3.  Proxy-Authorization</td><td> </td><td class="right">4.3.  Proxy-Authorization</td><td class="lineno" valign="top"></td></tr>
416      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
417      <tr><td class="lineno" valign="top"></td><td class="left">   The "Proxy-Authorization" header field allows the client to identify</td><td> </td><td class="right">   The "Proxy-Authorization" header field allows the client to identify</td><td class="lineno" valign="top"></td></tr>
418      <tr><td class="lineno" valign="top"></td><td class="left">   itself (or its user) to a proxy that requires authentication.  Its</td><td> </td><td class="right">   itself (or its user) to a proxy that requires authentication.  Its</td><td class="lineno" valign="top"></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="left">   value consists of credentials containing the authentication</td><td> </td><td class="right">   value consists of credentials containing the authentication</td><td class="lineno" valign="top"></td></tr>
420      <tr><td><a name="diff0021" /></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="lblock">   information of the <span class="delete">user agent</span> for the proxy and/or realm of the</td><td> </td><td class="rblock">   information of the <span class="insert">client</span> for the proxy and/or realm of the resource</td><td class="lineno" valign="top"></td></tr>
422      <tr><td class="lineno" valign="top"></td><td class="lblock">   resource being requested.</td><td> </td><td class="rblock">   being requested.</td><td class="lineno" valign="top"></td></tr>
423      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
424      <tr><td class="lineno" valign="top"></td><td class="left">     Proxy-Authorization = credentials</td><td> </td><td class="right">     Proxy-Authorization = credentials</td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="left">   Unlike Authorization, the Proxy-Authorization header field applies</td><td> </td><td class="right">   Unlike Authorization, the Proxy-Authorization header field applies</td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno" valign="top"></td><td class="left">   only to the next outbound proxy that demanded authentication using</td><td> </td><td class="right">   only to the next outbound proxy that demanded authentication using</td><td class="lineno" valign="top"></td></tr>
428      <tr><td class="lineno" valign="top"></td><td class="left">   the Proxy-Authenticate field.  When multiple proxies are used in a</td><td> </td><td class="right">   the Proxy-Authenticate field.  When multiple proxies are used in a</td><td class="lineno" valign="top"></td></tr>
429      <tr><td class="lineno" valign="top"></td><td class="left">   chain, the Proxy-Authorization header field is consumed by the first</td><td> </td><td class="right">   chain, the Proxy-Authorization header field is consumed by the first</td><td class="lineno" valign="top"></td></tr>
430      <tr><td class="lineno" valign="top"></td><td class="left">   outbound proxy that was expecting to receive credentials.  A proxy</td><td> </td><td class="right">   outbound proxy that was expecting to receive credentials.  A proxy</td><td class="lineno" valign="top"></td></tr>
431      <tr><td class="lineno" valign="top"></td><td class="left">   MAY relay the credentials from the client request to the next proxy</td><td> </td><td class="right">   MAY relay the credentials from the client request to the next proxy</td><td class="lineno" valign="top"></td></tr>
432      <tr><td class="lineno" valign="top"></td><td class="left">   if that is the mechanism by which the proxies cooperatively</td><td> </td><td class="right">   if that is the mechanism by which the proxies cooperatively</td><td class="lineno" valign="top"></td></tr>
433      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
434      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 11, line 38</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 10, line 9</em></th><td></td></tr>
435      <tr><td class="lineno" valign="top"></td><td class="left">      well.  Therefore, a sequence of comma, whitespace, and comma can</td><td> </td><td class="right">      well.  Therefore, a sequence of comma, whitespace, and comma can</td><td class="lineno" valign="top"></td></tr>
436      <tr><td class="lineno" valign="top"></td><td class="left">      be considered both as applying to the preceding challenge, or to</td><td> </td><td class="right">      be considered both as applying to the preceding challenge, or to</td><td class="lineno" valign="top"></td></tr>
437      <tr><td class="lineno" valign="top"></td><td class="left">      be an empty entry in the list of challenges.  In practice, this</td><td> </td><td class="right">      be an empty entry in the list of challenges.  In practice, this</td><td class="lineno" valign="top"></td></tr>
438      <tr><td class="lineno" valign="top"></td><td class="left">      ambiguity does not affect the semantics of the header field value</td><td> </td><td class="right">      ambiguity does not affect the semantics of the header field value</td><td class="lineno" valign="top"></td></tr>
439      <tr><td class="lineno" valign="top"></td><td class="left">      and thus is harmless.</td><td> </td><td class="right">      and thus is harmless.</td><td class="lineno" valign="top"></td></tr>
440      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
441      <tr><td class="lineno" valign="top"></td><td class="left">5.  IANA Considerations</td><td> </td><td class="right">5.  IANA Considerations</td><td class="lineno" valign="top"></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
443      <tr><td class="lineno" valign="top"></td><td class="left">5.1.  Authentication Scheme Registry</td><td> </td><td class="right">5.1.  Authentication Scheme Registry</td><td class="lineno" valign="top"></td></tr>
444      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
445      <tr><td><a name="diff0022" /></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">registration procedure for HTTP Authentication Schemes is defined</span></td><td> </td><td class="rblock">   The HTTP Authentication Scheme <span class="insert">Registry defines the name space for</span></td><td class="lineno" valign="top"></td></tr>
447      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   by Section 2.3 of this document.</span></td><td> </td><td class="rblock"><span class="insert">   the authentication schemes in challenges and credentials.  It will</span> be</td><td class="lineno" valign="top"></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock">   created <span class="insert">and maintained</span> at</td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The</span> HTTP <span class="delete">Method</span> Authentication Scheme <span class="delete">shall</span> be created at</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
450      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-authschemes&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-authschemes&gt;.</td><td class="lineno" valign="top"></td></tr>
451      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
452      <tr><td><a name="diff0023" /></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">5.1.1.  Procedure</span></td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Registrations MUST include the following fields:</span></td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  Authentication Scheme Name</span></td><td class="lineno" valign="top"></td></tr>
458      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
459      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  Pointer to specification text</span></td><td class="lineno" valign="top"></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  Notes (optional)</span></td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
463      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Values to be added to this name space require IETF Review (see</span></td><td class="lineno" valign="top"></td></tr>
464      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   [RFC5226], Section 4.1).</span></td><td class="lineno" valign="top"></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">5.1.2.  Considerations for New Authentication Schemes</span></td><td class="lineno" valign="top"></td></tr>
467      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
468      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   There are certain aspects of the HTTP Authentication Framework that</span></td><td class="lineno" valign="top"></td></tr>
469      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   put constraints on how new authentication schemes can work:</span></td><td class="lineno" valign="top"></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
471      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  HTTP authentication is presumed to be stateless: all of the</span></td><td class="lineno" valign="top"></td></tr>
472      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      information necessary to authenticate a request MUST be provided</span></td><td class="lineno" valign="top"></td></tr>
473      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      in the request, rather than be dependent on the server remembering</span></td><td class="lineno" valign="top"></td></tr>
474      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      prior requests.  Authentication based on, or bound to, the</span></td><td class="lineno" valign="top"></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      underlying connection is outside the scope of this specification</span></td><td class="lineno" valign="top"></td></tr>
476      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      and inherently flawed unless steps are taken to ensure that the</span></td><td class="lineno" valign="top"></td></tr>
477      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      connection cannot be used by any party other than the</span></td><td class="lineno" valign="top"></td></tr>
478      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      authenticated user (see Section 2.3 of [Part1]).</span></td><td class="lineno" valign="top"></td></tr>
479      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
480      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  The authentication parameter "realm" is reserved for defining</span></td><td class="lineno" valign="top"></td></tr>
481      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      Protection Spaces as defined in Section 2.2.  New schemes MUST NOT</span></td><td class="lineno" valign="top"></td></tr>
482      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      use it in a way incompatible with that definition.</span></td><td class="lineno" valign="top"></td></tr>
483      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
484      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  The "token68" notation was introduced for compatibility with</span></td><td class="lineno" valign="top"></td></tr>
485      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      existing authentication schemes and can only be used once per</span></td><td class="lineno" valign="top"></td></tr>
486      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      challenge or credential.  New schemes thus ought to use the "auth-</span></td><td class="lineno" valign="top"></td></tr>
487      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      param" syntax instead, because otherwise future extensions will be</span></td><td class="lineno" valign="top"></td></tr>
488      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      impossible.</span></td><td class="lineno" valign="top"></td></tr>
489      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
490      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  The parsing of challenges and credentials is defined by this</span></td><td class="lineno" valign="top"></td></tr>
491      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      specification, and cannot be modified by new authentication</span></td><td class="lineno" valign="top"></td></tr>
492      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      schemes.  When the auth-param syntax is used, all parameters ought</span></td><td class="lineno" valign="top"></td></tr>
493      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      to support both token and quoted-string syntax, and syntactical</span></td><td class="lineno" valign="top"></td></tr>
494      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      constraints ought to be defined on the field value after parsing</span></td><td class="lineno" valign="top"></td></tr>
495      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      (i.e., quoted-string processing).  This is necessary so that</span></td><td class="lineno" valign="top"></td></tr>
496      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      recipients can use a generic parser that applies to all</span></td><td class="lineno" valign="top"></td></tr>
497      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      authentication schemes.</span></td><td class="lineno" valign="top"></td></tr>
498      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
499      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      Note: The fact that the value syntax for the "realm" parameter is</span></td><td class="lineno" valign="top"></td></tr>
500      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      restricted to quoted-string was a bad design choice not to be</span></td><td class="lineno" valign="top"></td></tr>
501      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      repeated for new parameters.</span></td><td class="lineno" valign="top"></td></tr>
502      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
503      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  Definitions of new schemes ought to define the treatment of</span></td><td class="lineno" valign="top"></td></tr>
504      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      unknown extension parameters.  In general, a "must-ignore" rule is</span></td><td class="lineno" valign="top"></td></tr>
505      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      preferable over "must-understand", because otherwise it will be</span></td><td class="lineno" valign="top"></td></tr>
506      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      hard to introduce new parameters in the presence of legacy</span></td><td class="lineno" valign="top"></td></tr>
507      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      recipients.  Furthermore, it's good to describe the policy for</span></td><td class="lineno" valign="top"></td></tr>
508      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      defining new parameters (such as "update the specification", or</span></td><td class="lineno" valign="top"></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      "use this registry").</span></td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
511      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  Authentication schemes need to document whether they are usable in</span></td><td class="lineno" valign="top"></td></tr>
512      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      origin-server authentication (i.e., using WWW-Authenticate),</span></td><td class="lineno" valign="top"></td></tr>
513      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      and/or proxy authentication (i.e., using Proxy-Authenticate).</span></td><td class="lineno" valign="top"></td></tr>
514      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
515      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  The credentials carried in an Authorization header field are</span></td><td class="lineno" valign="top"></td></tr>
516      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      specific to the User Agent, and therefore have the same effect on</span></td><td class="lineno" valign="top"></td></tr>
517      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      HTTP caches as the "private" Cache-Control response directive</span></td><td class="lineno" valign="top"></td></tr>
518      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      (Section 7.2.2.6 of [Part6]), within the scope of the request they</span></td><td class="lineno" valign="top"></td></tr>
519      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      appear in.</span></td><td class="lineno" valign="top"></td></tr>
520      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
521      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      Therefore, new authentication schemes that choose not to carry</span></td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      credentials in the Authorization header field (e.g., using a newly</span></td><td class="lineno" valign="top"></td></tr>
523      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      defined header field) will need to explicitly disallow caching, by</span></td><td class="lineno" valign="top"></td></tr>
524      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      mandating the use of either Cache-Control request directives</span></td><td class="lineno" valign="top"></td></tr>
525      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      (e.g., "no-store", Section 7.2.1.5 of [Part6]) or response</span></td><td class="lineno" valign="top"></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      directives (e.g., "private").</span></td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="left">5.2.  Status Code Registration</td><td> </td><td class="right">5.2.  Status Code Registration</td><td class="lineno" valign="top"></td></tr>
529      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
530      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP Status Code Registry located at</td><td> </td><td class="right">   The HTTP Status Code Registry located at</td><td class="lineno" valign="top"></td></tr>
531      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-status-codes&gt; shall be updated</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-status-codes&gt; shall be updated</td><td class="lineno" valign="top"></td></tr>
532      <tr><td class="lineno" valign="top"></td><td class="left">   with the registrations below:</td><td> </td><td class="right">   with the registrations below:</td><td class="lineno" valign="top"></td></tr>
533      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
534      <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+-------------+</td><td> </td><td class="right">   +-------+-------------------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="left">   | Value | Description                   | Reference   |</td><td> </td><td class="right">   | Value | Description                   | Reference   |</td><td class="lineno" valign="top"></td></tr>
536      <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+-------------+</td><td> </td><td class="right">   +-------+-------------------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
537      <tr><td class="lineno" valign="top"></td><td class="left">   | 401   | Unauthorized                  | Section 3.1 |</td><td> </td><td class="right">   | 401   | Unauthorized                  | Section 3.1 |</td><td class="lineno" valign="top"></td></tr>
538      <tr><td class="lineno" valign="top"></td><td class="left">   | 407   | Proxy Authentication Required | Section 3.2 |</td><td> </td><td class="right">   | 407   | Proxy Authentication Required | Section 3.2 |</td><td class="lineno" valign="top"></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+-------------+</td><td> </td><td class="right">   +-------+-------------------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
541      <tr><td class="lineno" valign="top"></td><td class="left">5.3.  Header Field Registration</td><td> </td><td class="right">5.3.  Header Field Registration</td><td class="lineno" valign="top"></td></tr>
542      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
543      <tr><td><a name="diff0024" /></td></tr>
544      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">The</span> Message Header Field Registry <span class="delete">located</span> at <span class="delete">&lt;http://www.iana.org/</span></td><td> </td><td class="rblock">   <span class="insert">HTTP header fields are registered within the</span> Message Header Field</td><td class="lineno" valign="top"></td></tr>
545      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   assignments/message-headers/message-header-index.html&gt;</span> shall be</td><td> </td><td class="rblock">   Registry <span class="insert">maintained</span> at <span class="insert">&lt;http://www.iana.org/assignments/</span></td><td class="lineno" valign="top"></td></tr>
546      <tr><td class="lineno" valign="top"></td><td class="lblock">   updated <span class="delete">with</span> the permanent registrations below (see [BCP90]):</td><td> </td><td class="rblock"><span class="insert">   message-headers/message-header-index.html&gt;.</span></td><td class="lineno" valign="top"></td></tr>
547      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
548      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This document defines the following HTTP header fields, so their</span></td><td class="lineno" valign="top"></td></tr>
549      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   associated registry entries</span> shall be updated <span class="insert">according to</span> the</td><td class="lineno" valign="top"></td></tr>
550      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   permanent registrations below (see [BCP90]):</td><td class="lineno" valign="top"></td></tr>
551      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
552      <tr><td class="lineno" valign="top"></td><td class="left">   +---------------------+----------+----------+-------------+</td><td> </td><td class="right">   +---------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
553      <tr><td class="lineno" valign="top"></td><td class="left">   | Header Field Name   | Protocol | Status   | Reference   |</td><td> </td><td class="right">   | Header Field Name   | Protocol | Status   | Reference   |</td><td class="lineno" valign="top"></td></tr>
554      <tr><td class="lineno" valign="top"></td><td class="left">   +---------------------+----------+----------+-------------+</td><td> </td><td class="right">   +---------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="left">   | Authorization       | http     | standard | Section 4.1 |</td><td> </td><td class="right">   | Authorization       | http     | standard | Section 4.1 |</td><td class="lineno" valign="top"></td></tr>
556      <tr><td class="lineno" valign="top"></td><td class="left">   | Proxy-Authenticate  | http     | standard | Section 4.2 |</td><td> </td><td class="right">   | Proxy-Authenticate  | http     | standard | Section 4.2 |</td><td class="lineno" valign="top"></td></tr>
557      <tr><td class="lineno" valign="top"></td><td class="left">   | Proxy-Authorization | http     | standard | Section 4.3 |</td><td> </td><td class="right">   | Proxy-Authorization | http     | standard | Section 4.3 |</td><td class="lineno" valign="top"></td></tr>
558      <tr><td class="lineno" valign="top"></td><td class="left">   | WWW-Authenticate    | http     | standard | Section 4.4 |</td><td> </td><td class="right">   | WWW-Authenticate    | http     | standard | Section 4.4 |</td><td class="lineno" valign="top"></td></tr>
559      <tr><td class="lineno" valign="top"></td><td class="left">   +---------------------+----------+----------+-------------+</td><td> </td><td class="right">   +---------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
560      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
561      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
562      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 13, line 18</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 13, line 22</em></th><td></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="left">   password protection in screen savers, idle time-outs, and other</td><td> </td><td class="right">   password protection in screen savers, idle time-outs, and other</td><td class="lineno" valign="top"></td></tr>
564      <tr><td class="lineno" valign="top"></td><td class="left">   methods that mitigate the security problems inherent in this problem.</td><td> </td><td class="right">   methods that mitigate the security problems inherent in this problem.</td><td class="lineno" valign="top"></td></tr>
565      <tr><td class="lineno" valign="top"></td><td class="left">   In particular, user agents that cache credentials are encouraged to</td><td> </td><td class="right">   In particular, user agents that cache credentials are encouraged to</td><td class="lineno" valign="top"></td></tr>
566      <tr><td class="lineno" valign="top"></td><td class="left">   provide a readily accessible mechanism for discarding cached</td><td> </td><td class="right">   provide a readily accessible mechanism for discarding cached</td><td class="lineno" valign="top"></td></tr>
567      <tr><td class="lineno" valign="top"></td><td class="left">   credentials under user control.</td><td> </td><td class="right">   credentials under user control.</td><td class="lineno" valign="top"></td></tr>
568      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
569      <tr><td class="lineno" valign="top"></td><td class="left">6.2.  Protection Spaces</td><td> </td><td class="right">6.2.  Protection Spaces</td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="left">   Authentication schemes that solely rely on the "realm" mechanism for</td><td> </td><td class="right">   Authentication schemes that solely rely on the "realm" mechanism for</td><td class="lineno" valign="top"></td></tr>
572      <tr><td class="lineno" valign="top"></td><td class="left">   establishing a protection space will expose credentials to all</td><td> </td><td class="right">   establishing a protection space will expose credentials to all</td><td class="lineno" valign="top"></td></tr>
573      <tr><td><a name="diff0025" /></td></tr>
574      <tr><td class="lineno" valign="top"></td><td class="lblock">   resources on a server.  Clients that have successfully made</td><td> </td><td class="rblock">   resources on a<span class="insert">n origin</span> server.  Clients that have successfully made</td><td class="lineno" valign="top"></td></tr>
575      <tr><td class="lineno" valign="top"></td><td class="left">   authenticated requests with a resource can use the same</td><td> </td><td class="right">   authenticated requests with a resource can use the same</td><td class="lineno" valign="top"></td></tr>
576      <tr><td><a name="diff0026" /></td></tr>
577      <tr><td class="lineno" valign="top"></td><td class="lblock">   authentication credentials for other resources on the same server.</td><td> </td><td class="rblock">   authentication credentials for other resources on the same <span class="insert">origin</span></td><td class="lineno" valign="top"></td></tr>
578      <tr><td class="lineno" valign="top"></td><td class="lblock">   This makes it possible for a different resource to harvest</td><td> </td><td class="rblock">   server.  This makes it possible for a different resource to harvest</td><td class="lineno" valign="top"></td></tr>
579      <tr><td class="lineno" valign="top"></td><td class="left">   authentication credentials for other resources.</td><td> </td><td class="right">   authentication credentials for other resources.</td><td class="lineno" valign="top"></td></tr>
580      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
581      <tr><td><a name="diff0027" /></td></tr>
582      <tr><td class="lineno" valign="top"></td><td class="lblock">   This is of particular concern when <span class="delete">a</span> server hosts resources for</td><td> </td><td class="rblock">   This is of particular concern when <span class="insert">an origin</span> server hosts resources</td><td class="lineno" valign="top"></td></tr>
583      <tr><td class="lineno" valign="top"></td><td class="lblock">   multiple parties under the same canonical root URI (Section 2.2).</td><td> </td><td class="rblock">   for multiple parties under the same canonical root URI (Section 2.2).</td><td class="lineno" valign="top"></td></tr>
584      <tr><td class="lineno" valign="top"></td><td class="left">   Possible mitigation strategies include restricting direct access to</td><td> </td><td class="right">   Possible mitigation strategies include restricting direct access to</td><td class="lineno" valign="top"></td></tr>
585      <tr><td class="lineno" valign="top"></td><td class="left">   authentication credentials (i.e., not making the content of the</td><td> </td><td class="right">   authentication credentials (i.e., not making the content of the</td><td class="lineno" valign="top"></td></tr>
586      <tr><td class="lineno" valign="top"></td><td class="left">   Authorization request header field available), and separating</td><td> </td><td class="right">   Authorization request header field available), and separating</td><td class="lineno" valign="top"></td></tr>
587      <tr><td><a name="diff0028" /></td></tr>
588      <tr><td class="lineno" valign="top"></td><td class="lblock">   protection spaces by using a different host name for each party.</td><td> </td><td class="rblock">   protection spaces by using a different host name <span class="insert">(or port number)</span> for</td><td class="lineno" valign="top"></td></tr>
589      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   each party.</td><td class="lineno" valign="top"></td></tr>
590      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
591      <tr><td class="lineno" valign="top"></td><td class="left">7.  Acknowledgments</td><td> </td><td class="right">7.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
592      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
593      <tr><td class="lineno" valign="top"></td><td class="left">   This specification takes over the definition of the HTTP</td><td> </td><td class="right">   This specification takes over the definition of the HTTP</td><td class="lineno" valign="top"></td></tr>
594      <tr><td class="lineno" valign="top"></td><td class="left">   Authentication Framework, previously defined in RFC 2617.  We thank</td><td> </td><td class="right">   Authentication Framework, previously defined in RFC 2617.  We thank</td><td class="lineno" valign="top"></td></tr>
595      <tr><td class="lineno" valign="top"></td><td class="left">   John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D.</td><td> </td><td class="right">   John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D.</td><td class="lineno" valign="top"></td></tr>
596      <tr><td class="lineno" valign="top"></td><td class="left">   Lawrence, Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for</td><td> </td><td class="right">   Lawrence, Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for</td><td class="lineno" valign="top"></td></tr>
597      <tr><td class="lineno" valign="top"></td><td class="left">   their work on that specification.  See Section 6 of [RFC2617] for</td><td> </td><td class="right">   their work on that specification.  See Section 6 of [RFC2617] for</td><td class="lineno" valign="top"></td></tr>
598      <tr><td class="lineno" valign="top"></td><td class="left">   further acknowledgements.</td><td> </td><td class="right">   further acknowledgements.</td><td class="lineno" valign="top"></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
601      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 13, line 44</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr>
602      <tr><td class="lineno" valign="top"></td><td class="left">   Authentication Framework, previously defined in RFC 2617.  We thank</td><td> </td><td class="right">   Authentication Framework, previously defined in RFC 2617.  We thank</td><td class="lineno" valign="top"></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left">   John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D.</td><td> </td><td class="right">   John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D.</td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left">   Lawrence, Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for</td><td> </td><td class="right">   Lawrence, Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for</td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left">   their work on that specification.  See Section 6 of [RFC2617] for</td><td> </td><td class="right">   their work on that specification.  See Section 6 of [RFC2617] for</td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left">   further acknowledgements.</td><td> </td><td class="right">   further acknowledgements.</td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
608      <tr><td class="lineno" valign="top"></td><td class="left">   See Section 9 of [Part1] for the Acknowledgments related to this</td><td> </td><td class="right">   See Section 9 of [Part1] for the Acknowledgments related to this</td><td class="lineno" valign="top"></td></tr>
609      <tr><td class="lineno" valign="top"></td><td class="left">   document revision.</td><td> </td><td class="right">   document revision.</td><td class="lineno" valign="top"></td></tr>
610      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
611      <tr><td class="lineno" valign="top"></td><td class="left">8.  References</td><td> </td><td class="right">8.  References</td><td class="lineno" valign="top"></td></tr>
612      <tr><td><a name="diff0029" /></td></tr>
613      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Normative References</td><td> </td><td class="right">8.1.  Normative References</td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
616      <tr><td class="lineno" valign="top"></td><td class="left">   [Part1]    Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [Part1]    Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
618      <tr><td><a name="diff0030" /></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-22</span> (work in progress),</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p1-messaging-23</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">February</span> 2013.</td><td> </td><td class="rblock">              <span class="insert">July</span> 2013.</td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
622      <tr><td class="lineno" valign="top"></td><td class="left">   [Part2]    Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [Part2]    Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Semantics and Content",</td><td class="lineno" valign="top"></td></tr>
624      <tr><td><a name="diff0031" /></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p2-semantics-22</span> (work in progress),</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p2-semantics-23</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">February</span> 2013.</td><td> </td><td class="rblock">              <span class="insert">July</span> 2013.</td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno" valign="top"></td><td class="left">   [Part6]    Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right">   [Part6]    Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
629      <tr><td class="lineno" valign="top"></td><td class="left">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
630      <tr><td><a name="diff0032" /></td></tr>
631      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p6-cache-22</span> (work in progress),</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p6-cache-23</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
632      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">February</span> 2013.</td><td> </td><td class="rblock">              <span class="insert">July</span> 2013.</td><td class="lineno" valign="top"></td></tr>
633      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate</td><td> </td><td class="right">   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate</td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left">              Requirement Levels", BCP 14, RFC 2119, March 1997.</td><td> </td><td class="right">              Requirement Levels", BCP 14, RFC 2119, March 1997.</td><td class="lineno" valign="top"></td></tr>
636      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax</td><td> </td><td class="right">   [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax</td><td class="lineno" valign="top"></td></tr>
638      <tr><td class="lineno" valign="top"></td><td class="left">              Specifications: ABNF", STD 68, RFC 5234, January 2008.</td><td> </td><td class="right">              Specifications: ABNF", STD 68, RFC 5234, January 2008.</td><td class="lineno" valign="top"></td></tr>
639      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
640      <tr><td class="lineno" valign="top"></td><td class="left">8.2.  Informative References</td><td> </td><td class="right">8.2.  Informative References</td><td class="lineno" valign="top"></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="left">   [BCP90]    Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td> </td><td class="right">   [BCP90]    Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
644      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 15, line 13</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 15, line 20</em></th><td></td></tr>
645      <tr><td class="lineno" valign="top"></td><td class="left">   The "realm" parameter is no longer always required on challenges;</td><td> </td><td class="right">   The "realm" parameter is no longer always required on challenges;</td><td class="lineno" valign="top"></td></tr>
646      <tr><td class="lineno" valign="top"></td><td class="left">   consequently, the ABNF allows challenges without any auth parameters.</td><td> </td><td class="right">   consequently, the ABNF allows challenges without any auth parameters.</td><td class="lineno" valign="top"></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 2)</td><td> </td><td class="right">   (Section 2)</td><td class="lineno" valign="top"></td></tr>
648      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
649      <tr><td class="lineno" valign="top"></td><td class="left">   The "token68" alternative to auth-param lists has been added for</td><td> </td><td class="right">   The "token68" alternative to auth-param lists has been added for</td><td class="lineno" valign="top"></td></tr>
650      <tr><td class="lineno" valign="top"></td><td class="left">   consistency with legacy authentication schemes such as "Basic".</td><td> </td><td class="right">   consistency with legacy authentication schemes such as "Basic".</td><td class="lineno" valign="top"></td></tr>
651      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 2)</td><td> </td><td class="right">   (Section 2)</td><td class="lineno" valign="top"></td></tr>
652      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
653      <tr><td class="lineno" valign="top"></td><td class="left">   This specification introduces the Authentication Scheme Registry,</td><td> </td><td class="right">   This specification introduces the Authentication Scheme Registry,</td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left">   along with considerations for new authentication schemes.</td><td> </td><td class="right">   along with considerations for new authentication schemes.</td><td class="lineno" valign="top"></td></tr>
655      <tr><td><a name="diff0033" /></td></tr>
656      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">2.3</span>)</td><td> </td><td class="rblock">   (Section <span class="insert">5.1</span>)</td><td class="lineno" valign="top"></td></tr>
657      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
658      <tr><td class="lineno" valign="top"></td><td class="left">Appendix B.  Imported ABNF</td><td> </td><td class="right">Appendix B.  Imported ABNF</td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
660      <tr><td class="lineno" valign="top"></td><td class="left">   The following core rules are included by reference, as defined in</td><td> </td><td class="right">   The following core rules are included by reference, as defined in</td><td class="lineno" valign="top"></td></tr>
661      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.1 of [RFC5234]: ALPHA (letters), CR (carriage return),</td><td> </td><td class="right">   Appendix B.1 of [RFC5234]: ALPHA (letters), CR (carriage return),</td><td class="lineno" valign="top"></td></tr>
662      <tr><td class="lineno" valign="top"></td><td class="left">   CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double</td><td> </td><td class="right">   CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double</td><td class="lineno" valign="top"></td></tr>
663      <tr><td class="lineno" valign="top"></td><td class="left">   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any</td><td> </td><td class="right">   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any</td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="left">   8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td> </td><td class="right">   8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="left">   character).</td><td> </td><td class="right">   character).</td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
667      <tr><td class="lineno" valign="top"></td><td class="left">   The rules below are defined in [Part1]:</td><td> </td><td class="right">   The rules below are defined in [Part1]:</td><td class="lineno" valign="top"></td></tr>
668      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
669      <tr><td class="lineno" valign="top"></td><td class="left">     BWS           = &lt;BWS, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">     BWS           = &lt;BWS, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="left">     OWS           = &lt;OWS, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">     OWS           = &lt;OWS, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
671      <tr><td class="lineno" valign="top"></td><td class="left">     quoted-string = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;</td><td> </td><td class="right">     quoted-string = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;</td><td class="lineno" valign="top"></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="left">     token         = &lt;token, defined in [Part1], Section 3.2.6&gt;</td><td> </td><td class="right">     token         = &lt;token, defined in [Part1], Section 3.2.6&gt;</td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="left">Appendix C.  Collected ABNF</td><td> </td><td class="right">Appendix C.  Collected ABNF</td><td class="lineno" valign="top"></td></tr>
675      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
676      <tr><td><a name="diff0034" /></td></tr>
677      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">In the collected ABNF below, list rules are expanded as per Section</span></td><td class="lineno" valign="top"></td></tr>
678      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   1.2 of [Part1].</span></td><td class="lineno" valign="top"></td></tr>
679      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
680      <tr><td class="lineno" valign="top"></td><td class="left">   Authorization = credentials</td><td> </td><td class="right">   Authorization = credentials</td><td class="lineno" valign="top"></td></tr>
681      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
682      <tr><td class="lineno" valign="top"></td><td class="left">   BWS = &lt;BWS, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">   BWS = &lt;BWS, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
683      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
684      <tr><td class="lineno" valign="top"></td><td class="left">   OWS = &lt;OWS, defined in [Part1], Section 3.2.3&gt;</td><td> </td><td class="right">   OWS = &lt;OWS, defined in [Part1], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
685      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
686      <tr><td class="lineno" valign="top"></td><td class="left">   Proxy-Authenticate = *( "," OWS ) challenge *( OWS "," [ OWS</td><td> </td><td class="right">   Proxy-Authenticate = *( "," OWS ) challenge *( OWS "," [ OWS</td><td class="lineno" valign="top"></td></tr>
687      <tr><td class="lineno" valign="top"></td><td class="left">    challenge ] )</td><td> </td><td class="right">    challenge ] )</td><td class="lineno" valign="top"></td></tr>
688      <tr><td class="lineno" valign="top"></td><td class="left">   Proxy-Authorization = credentials</td><td> </td><td class="right">   Proxy-Authorization = credentials</td><td class="lineno" valign="top"></td></tr>
689      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
690      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
691      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 17, line 30</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 17, line 27</em></th><td></td></tr>
692      <tr><td class="lineno" valign="top"></td><td class="left">   o  Conformance criteria and considerations regarding error handling</td><td> </td><td class="right">   o  Conformance criteria and considerations regarding error handling</td><td class="lineno" valign="top"></td></tr>
693      <tr><td class="lineno" valign="top"></td><td class="left">      are now defined in Part 1.</td><td> </td><td class="right">      are now defined in Part 1.</td><td class="lineno" valign="top"></td></tr>
694      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
695      <tr><td class="lineno" valign="top"></td><td class="left">D.3.  Since draft-ietf-httpbis-p7-auth-21</td><td> </td><td class="right">D.3.  Since draft-ietf-httpbis-p7-auth-21</td><td class="lineno" valign="top"></td></tr>
696      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="left">   Closed issues:</td><td> </td><td class="right">   Closed issues:</td><td class="lineno" valign="top"></td></tr>
698      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="left">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/403&gt;:</td><td> </td><td class="right">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/403&gt;:</td><td class="lineno" valign="top"></td></tr>
700      <tr><td class="lineno" valign="top"></td><td class="left">      "Authentication and caching - max-age"</td><td> </td><td class="right">      "Authentication and caching - max-age"</td><td class="lineno" valign="top"></td></tr>
701      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
702      <tr><td><a name="diff0035" /></td></tr>
703      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">D.4.  Since draft-ietf-httpbis-p7-auth-22</span></td><td class="lineno" valign="top"></td></tr>
704      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Closed issues:</span></td><td class="lineno" valign="top"></td></tr>
706      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
707      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/436&gt;: "explain list</span></td><td class="lineno" valign="top"></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      expansion in ABNF appendices"</span></td><td class="lineno" valign="top"></td></tr>
709      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
710      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/439&gt;: "terminology:</span></td><td class="lineno" valign="top"></td></tr>
711      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      mechanism vs framework vs scheme"</span></td><td class="lineno" valign="top"></td></tr>
712      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
713      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/463&gt;: "Editorial</span></td><td class="lineno" valign="top"></td></tr>
714      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      suggestions"</span></td><td class="lineno" valign="top"></td></tr>
715      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
716      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   o  &lt;http://tools.ietf.org/wg/httpbis/trac/ticket/464&gt;: "placement of</span></td><td class="lineno" valign="top"></td></tr>
717      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      extension point considerations"</span></td><td class="lineno" valign="top"></td></tr>
718      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
719      <tr><td class="lineno" valign="top"></td><td class="left">Index</td><td> </td><td class="right">Index</td><td class="lineno" valign="top"></td></tr>
720      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
721      <tr><td class="lineno" valign="top"></td><td class="left">   4</td><td> </td><td class="right">   4</td><td class="lineno" valign="top"></td></tr>
722      <tr><td><a name="diff0036" /></td></tr>
723      <tr><td class="lineno" valign="top"></td><td class="lblock">      401 Unauthorized (status code)  <span class="delete">9</span></td><td> </td><td class="rblock">      401 Unauthorized (status code)  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
724      <tr><td class="lineno" valign="top"></td><td class="lblock">      407 Proxy Authentication Required (status code)  <span class="delete">9</span></td><td> </td><td class="rblock">      407 Proxy Authentication Required (status code)  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
725      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
726      <tr><td class="lineno" valign="top"></td><td class="left">   A</td><td> </td><td class="right">   A</td><td class="lineno" valign="top"></td></tr>
727      <tr><td><a name="diff0037" /></td></tr>
728      <tr><td class="lineno" valign="top"></td><td class="lblock">      Authorization header field  <span class="delete">9</span></td><td> </td><td class="rblock">      Authorization header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
729      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
730      <tr><td class="lineno" valign="top"></td><td class="left">   C</td><td> </td><td class="right">   C</td><td class="lineno" valign="top"></td></tr>
731      <tr><td class="lineno" valign="top"></td><td class="left">      Canonical Root URI  6</td><td> </td><td class="right">      Canonical Root URI  6</td><td class="lineno" valign="top"></td></tr>
732      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
733      <tr><td class="lineno" valign="top"></td><td class="left">   G</td><td> </td><td class="right">   G</td><td class="lineno" valign="top"></td></tr>
734      <tr><td class="lineno" valign="top"></td><td class="left">      Grammar</td><td> </td><td class="right">      Grammar</td><td class="lineno" valign="top"></td></tr>
735      <tr><td class="lineno" valign="top"></td><td class="left">         auth-param  5</td><td> </td><td class="right">         auth-param  5</td><td class="lineno" valign="top"></td></tr>
736      <tr><td class="lineno" valign="top"></td><td class="left">         auth-scheme  5</td><td> </td><td class="right">         auth-scheme  5</td><td class="lineno" valign="top"></td></tr>
737      <tr><td><a name="diff0038" /></td></tr>
738      <tr><td class="lineno" valign="top"></td><td class="lblock">         Authorization  <span class="delete">9</span></td><td> </td><td class="rblock">         Authorization  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
739      <tr><td class="lineno" valign="top"></td><td class="left">         challenge  5</td><td> </td><td class="right">         challenge  5</td><td class="lineno" valign="top"></td></tr>
740      <tr><td class="lineno" valign="top"></td><td class="left">         credentials  6</td><td> </td><td class="right">         credentials  6</td><td class="lineno" valign="top"></td></tr>
741      <tr><td><a name="diff0039" /></td></tr>
742      <tr><td class="lineno" valign="top"></td><td class="lblock">         Proxy-Authenticate  <span class="delete">10</span></td><td> </td><td class="rblock">         Proxy-Authenticate  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
743      <tr><td class="lineno" valign="top"></td><td class="lblock">         Proxy-Authorization  <span class="delete">10</span></td><td> </td><td class="rblock">         Proxy-Authorization  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
744      <tr><td class="lineno" valign="top"></td><td class="left">         token68  5</td><td> </td><td class="right">         token68  5</td><td class="lineno" valign="top"></td></tr>
745      <tr><td><a name="diff0040" /></td></tr>
746      <tr><td class="lineno" valign="top"></td><td class="lblock">         WWW-Authenticate  <span class="delete">11</span></td><td> </td><td class="rblock">         WWW-Authenticate  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
747      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
748      <tr><td class="lineno" valign="top"></td><td class="left">   P</td><td> </td><td class="right">   P</td><td class="lineno" valign="top"></td></tr>
749      <tr><td class="lineno" valign="top"></td><td class="left">      Protection Space  6</td><td> </td><td class="right">      Protection Space  6</td><td class="lineno" valign="top"></td></tr>
750      <tr><td><a name="diff0041" /></td></tr>
751      <tr><td class="lineno" valign="top"></td><td class="lblock">      Proxy-Authenticate header field  <span class="delete">10</span></td><td> </td><td class="rblock">      Proxy-Authenticate header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
752      <tr><td class="lineno" valign="top"></td><td class="lblock">      Proxy-Authorization header field  <span class="delete">10</span></td><td> </td><td class="rblock">      Proxy-Authorization header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
753      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
754      <tr><td class="lineno" valign="top"></td><td class="left">   R</td><td> </td><td class="right">   R</td><td class="lineno" valign="top"></td></tr>
755      <tr><td class="lineno" valign="top"></td><td class="left">      Realm  6</td><td> </td><td class="right">      Realm  6</td><td class="lineno" valign="top"></td></tr>
756      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
757      <tr><td class="lineno" valign="top"></td><td class="left">   W</td><td> </td><td class="right">   W</td><td class="lineno" valign="top"></td></tr>
758      <tr><td><a name="diff0042" /></td></tr>
759      <tr><td class="lineno" valign="top"></td><td class="lblock">      WWW-Authenticate header field  <span class="delete">10</span></td><td> </td><td class="rblock">      WWW-Authenticate header field  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
760      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
761      <tr><td class="lineno" valign="top"></td><td class="left">Authors' Addresses</td><td> </td><td class="right">Authors' Addresses</td><td class="lineno" valign="top"></td></tr>
762      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
763      <tr><td class="lineno" valign="top"></td><td class="left">   Roy T. Fielding (editor)</td><td> </td><td class="right">   Roy T. Fielding (editor)</td><td class="lineno" valign="top"></td></tr>
764      <tr><td class="lineno" valign="top"></td><td class="left">   Adobe Systems Incorporated</td><td> </td><td class="right">   Adobe Systems Incorporated</td><td class="lineno" valign="top"></td></tr>
765      <tr><td class="lineno" valign="top"></td><td class="left">   345 Park Ave</td><td> </td><td class="right">   345 Park Ave</td><td class="lineno" valign="top"></td></tr>
766      <tr><td class="lineno" valign="top"></td><td class="left">   San Jose, CA  95110</td><td> </td><td class="right">   San Jose, CA  95110</td><td class="lineno" valign="top"></td></tr>
767      <tr><td class="lineno" valign="top"></td><td class="left">   USA</td><td> </td><td class="right">   USA</td><td class="lineno" valign="top"></td></tr>
768      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
769      <tr><td class="lineno" valign="top"></td><td class="left">   EMail: fielding@gbiv.com</td><td> </td><td class="right">   EMail: fielding@gbiv.com</td><td class="lineno" valign="top"></td></tr>
770
771     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
772     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 42 change blocks.&nbsp;</a></th></tr>
773     <tr class="stats"><td></td><th><i>152 lines changed or deleted</i></th><th><i> </i></th><th><i>171 lines changed or added</i></th><td></td></tr>
774     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
775   </table>
776   </body>
777   </html>
Note: See TracBrowser for help on using the repository browser.