source: draft-ietf-httpbis/diffs/draft-ietf-httpbis-p3-payload-19-from-18.diff.html @ 1697

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

regen -19 draft (see #338)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html; charset=iso-8859-1
File size: 244.3 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-p3-payload-18.txt - draft-ietf-httpbis-p3-payload-19.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-p3-payload-18.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-httpbis-p3-payload-19.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><a name="diff0001" /></td></tr>
43      <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: 2616 (if approved)                                  <span class="delete">J. Gettys</span></td><td> </td><td class="rblock">Obsoletes: 2616 (if approved)                              <span class="insert">Y. Lafon, Ed.</span></td><td class="lineno" valign="top"></td></tr>
44      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Standards Track                          <span class="delete">Alcatel-Lucent</span></td><td> </td><td class="rblock">Intended status: Standards Track                                     <span class="insert">W3C</span></td><td class="lineno" valign="top"></td></tr>
45      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">July 7,</span> 2012                                           <span class="delete">J. Mogul</span></td><td> </td><td class="rblock">Expires: <span class="insert">September 13,</span> 2012                              J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
46      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                      HP</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
47      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                              H. Frystyk</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
48      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                               Microsoft</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
49      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                             L. Masinter</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
50      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                   Adobe</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
51      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                P. Leach</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
52      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                               Microsoft</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
53      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                          T. Berners-Lee</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
54      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                 W3C/MIT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
55      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                           Y. Lafon, Ed.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
56      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                     W3C</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
57      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                         J. Reschke, Ed.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
58      <tr><td class="lineno" valign="top"></td><td class="left">                                                              greenbytes</td><td> </td><td class="right">                                                              greenbytes</td><td class="lineno" valign="top"></td></tr>
59      <tr><td><a name="diff0002" /></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                         <span class="delete">January 4</span>, 2012</td><td> </td><td class="rblock">                                                         <span class="insert"> March 12</span>, 2012</td><td class="lineno" valign="top"></td></tr>
61      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
62      <tr><td class="lineno" valign="top"></td><td class="left">       HTTP/1.1, part 3: Message Payload and Content Negotiation</td><td> </td><td class="right">       HTTP/1.1, part 3: Message Payload and Content Negotiation</td><td class="lineno" valign="top"></td></tr>
63      <tr><td><a name="diff0003" /></td></tr>
64      <tr><td class="lineno" valign="top"></td><td class="lblock">                    draft-ietf-httpbis-p3-payload-1<span class="delete">8</span></td><td> </td><td class="rblock">                    draft-ietf-httpbis-p3-payload-1<span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
65      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
66      <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>
67      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
68      <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>
69      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for distributed, collaborative, hypertext information</td><td> </td><td class="right">   protocol for distributed, collaborative, hypertext information</td><td class="lineno" valign="top"></td></tr>
70      <tr><td class="lineno" valign="top"></td><td class="left">   systems.  HTTP has been in use by the World Wide Web global</td><td> </td><td class="right">   systems.  HTTP has been in use by the World Wide Web global</td><td class="lineno" valign="top"></td></tr>
71      <tr><td class="lineno" valign="top"></td><td class="left">   information initiative since 1990.  This document is Part 3 of the</td><td> </td><td class="right">   information initiative since 1990.  This document is Part 3 of the</td><td class="lineno" valign="top"></td></tr>
72      <tr><td class="lineno" valign="top"></td><td class="left">   seven-part specification that defines the protocol referred to as</td><td> </td><td class="right">   seven-part specification that defines the protocol referred to as</td><td class="lineno" valign="top"></td></tr>
73      <tr><td class="lineno" valign="top"></td><td class="left">   "HTTP/1.1" and, taken together, obsoletes RFC 2616.</td><td> </td><td class="right">   "HTTP/1.1" and, taken together, obsoletes RFC 2616.</td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
75      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
76      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 49</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 37</em></th><td></td></tr>
77      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
78      <tr><td class="lineno" valign="top"></td><td class="left">   Discussion of this draft should take place on the HTTPBIS working</td><td> </td><td class="right">   Discussion of this draft should take place on the HTTPBIS working</td><td class="lineno" valign="top"></td></tr>
79      <tr><td class="lineno" valign="top"></td><td class="left">   group mailing list (ietf-http-wg@w3.org), which is archived at</td><td> </td><td class="right">   group mailing list (ietf-http-wg@w3.org), which is archived at</td><td class="lineno" valign="top"></td></tr>
80      <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>
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">   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>
83      <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>
84      <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>
85      <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>
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">   The changes in this draft are summarized in Appendix E.<span class="delete">19</span>.</td><td> </td><td class="rblock">   The changes in this draft are summarized in Appendix E.<span class="insert">20</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">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno" valign="top"></td></tr>
91      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
92      <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>
93      <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>
94      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
95      <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>
96      <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>
97      <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>
98      <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>
99      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
100      <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>
101      <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>
102      <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>
103      <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>
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><a name="diff0005" /></td></tr>
106      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">July 7</span>, 2012.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">September 13</span>, 2012.</td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
108      <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>
109      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
110      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
111      <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>
112      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
113      <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>
114      <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>
115      <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>
116      <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>
117      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
118      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 3, line 9</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 2, line 46</em></th><td></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
120      <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>
121      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
122      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
123      <tr><td class="lineno" valign="top"></td><td class="left">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="left">     1.2.  Conformance and Error Handling . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     1.2.  Conformance and Error Handling . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="left">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">       1.3.1.  Core Rules . . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
127      <tr><td class="lineno" valign="top"></td><td class="left">       1.3.2.  ABNF Rules defined in other Parts of the</td><td> </td><td class="right">       1.3.2.  ABNF Rules defined in other Parts of the</td><td class="lineno" valign="top"></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="left">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">               Specification  . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
129      <tr><td><a name="diff0006" /></td></tr>
130      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">6</span></td><td> </td><td class="rblock">   2.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.1.  Character Encodings (charset)  . . . . . . . . . . . . . .  <span class="delete">6</span></td><td> </td><td class="rblock">     2.1.  Character Encodings (charset)  . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="left">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  7</td><td> </td><td class="right">     2.2.  Content Codings  . . . . . . . . . . . . . . . . . . . . .  7</td><td class="lineno" valign="top"></td></tr>
133      <tr><td class="lineno" valign="top"></td><td class="left">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">       2.2.1.  Content Coding Registry  . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
134      <tr><td class="lineno" valign="top"></td><td class="left">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">     2.3.  Media Types  . . . . . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="left">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . .  9</td><td> </td><td class="right">       2.3.1.  Canonicalization and Text Defaults . . . . . . . . . .  9</td><td class="lineno" valign="top"></td></tr>
136      <tr><td><a name="diff0007" /></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="lblock">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . . <span class="delete"> 9</span></td><td> </td><td class="rblock">       2.3.2.  Multipart Types  . . . . . . . . . . . . . . . . . . . <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="left">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . 10</td><td> </td><td class="right">     2.4.  Language Tags  . . . . . . . . . . . . . . . . . . . . . . 10</td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">   3.  Payload  . . . . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno" valign="top"></td><td class="left">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     3.1.  Payload Header Fields  . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
141      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     3.2.  Payload Body . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">   4.  Representation . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="left">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     4.1.  Representation Header Fields . . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
144      <tr><td><a name="diff0008" /></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 1<span class="delete">2</span></td><td> </td><td class="rblock">     4.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 1<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">   5.  Content Negotiation  . . . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 14</td><td> </td><td class="right">     5.1.  Server-driven Negotiation  . . . . . . . . . . . . . . . . 14</td><td class="lineno" valign="top"></td></tr>
148      <tr><td><a name="diff0009" /></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 1<span class="delete">5</span></td><td> </td><td class="rblock">     5.2.  Agent-driven Negotiation . . . . . . . . . . . . . . . . . 1<span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">   6.  Header Field Definitions . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">     6.1.  Accept . . . . . . . . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
152      <tr><td><a name="diff0010" /></td></tr>
153      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 1<span class="delete">8</span></td><td> </td><td class="rblock">     6.2.  Accept-Charset . . . . . . . . . . . . . . . . . . . . . . 1<span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="left">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . 19</td><td> </td><td class="right">     6.3.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . . 19</td><td class="lineno" valign="top"></td></tr>
155      <tr><td><a name="diff0011" /></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . <span class="delete">20</span></td><td> </td><td class="rblock">     6.4.  Accept-Language  . . . . . . . . . . . . . . . . . . . . . <span class="insert">21</span></td><td class="lineno" valign="top"></td></tr>
157      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . <span class="delete">21</span></td><td> </td><td class="rblock">     6.5.  Content-Encoding . . . . . . . . . . . . . . . . . . . . . <span class="insert">22</span></td><td class="lineno" valign="top"></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . <span class="delete">22</span></td><td> </td><td class="rblock">     6.6.  Content-Language . . . . . . . . . . . . . . . . . . . . . <span class="insert">23</span></td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="left">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 23</td><td> </td><td class="right">     6.7.  Content-Location . . . . . . . . . . . . . . . . . . . . . 23</td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left">     6.8.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">     6.8.  Content-Type . . . . . . . . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="left">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="left">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 25</td><td> </td><td class="right">     7.1.  Header Field Registration  . . . . . . . . . . . . . . . . 25</td><td class="lineno" valign="top"></td></tr>
163      <tr><td><a name="diff0012" /></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="lblock">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 2<span class="delete">5</span></td><td> </td><td class="rblock">     7.2.  Content Coding Registry  . . . . . . . . . . . . . . . . . 2<span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
165      <tr><td class="lineno" valign="top"></td><td class="left">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26</td><td> </td><td class="right">   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26</td><td class="lineno" valign="top"></td></tr>
166      <tr><td><a name="diff0013" /></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 2<span class="delete">6</span></td><td> </td><td class="rblock">     8.1.  Privacy Issues Connected to Accept Header Fields . . . . . 2<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
168      <tr><td class="lineno" valign="top"></td><td class="left">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
169      <tr><td class="lineno" valign="top"></td><td class="left">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
170      <tr><td class="lineno" valign="top"></td><td class="left">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     10.1. Normative References . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
171      <tr><td><a name="diff0014" /></td></tr>
172      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="delete">28</span></td><td> </td><td class="rblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="insert">29</span></td><td class="lineno" valign="top"></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . <span class="delete">29</span></td><td> </td><td class="rblock">   Appendix A.  Differences between HTTP and MIME . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30</td><td> </td><td class="right">     A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 30</td><td class="lineno" valign="top"></td></tr>
175      <tr><td><a name="diff0015" /></td></tr>
176      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 3<span class="delete">0</span></td><td> </td><td class="rblock">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 3<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="left">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 31</td><td> </td><td class="right">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 31</td><td> </td><td class="right">     A.4.  Introduction of Content-Encoding . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
179      <tr><td><a name="diff0016" /></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 3<span class="delete">1</span></td><td> </td><td class="rblock">     A.5.  No Content-Transfer-Encoding . . . . . . . . . . . . . . . 3<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
181      <tr><td class="lineno" valign="top"></td><td class="left">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 32</td><td> </td><td class="right">     A.6.  Introduction of Transfer-Encoding  . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="left">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 32</td><td> </td><td class="right">     A.7.  MHTML and Line Length Limitations  . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
183      <tr><td><a name="diff0017" /></td></tr>
184      <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>
185      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">   Appendix B.  Additional Features . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
186      <tr><td><a name="diff0018" /></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 3<span class="delete">2</span></td><td> </td><td class="rblock">   Appendix C.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 3<span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">   Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix E.  Change Log (to be removed by RFC Editor before</td><td> </td><td class="right">   Appendix E.  Change Log (to be removed by RFC Editor before</td><td class="lineno" valign="top"></td></tr>
190      <tr><td><a name="diff0019" /></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="lblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">                publication)  . . . . . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
192      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">     E.1.  Since RFC 2616 . . . . . . . . . . . . . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="delete">34</span></td><td> </td><td class="rblock">     E.2.  Since draft-ietf-httpbis-p3-payload-00 . . . . . . . . . . <span class="insert">35</span></td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="delete">35</span></td><td> </td><td class="rblock">     E.3.  Since draft-ietf-httpbis-p3-payload-01 . . . . . . . . . . <span class="insert">36</span></td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="delete">35</span></td><td> </td><td class="rblock">     E.4.  Since draft-ietf-httpbis-p3-payload-02 . . . . . . . . . . <span class="insert">36</span></td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36</td><td> </td><td class="right">     E.5.  Since draft-ietf-httpbis-p3-payload-03 . . . . . . . . . . 36</td><td class="lineno" valign="top"></td></tr>
197      <tr><td><a name="diff0020" /></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock">     E.6.  Since draft-ietf-httpbis-p3-payload-04 . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="delete">36</span></td><td> </td><td class="rblock">     E.7.  Since draft-ietf-httpbis-p3-payload-05 . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37</td><td> </td><td class="right">     E.8.  Since draft-ietf-httpbis-p3-payload-06 . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
201      <tr><td><a name="diff0021" /></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 3<span class="delete">7</span></td><td> </td><td class="rblock">     E.9.  Since draft-ietf-httpbis-p3-payload-07 . . . . . . . . . . 3<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38</td><td> </td><td class="right">     E.10. Since draft-ietf-httpbis-p3-payload-08 . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
204      <tr><td><a name="diff0022" /></td></tr>
205      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">     E.11. Since draft-ietf-httpbis-p3-payload-09 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . <span class="delete">38</span></td><td> </td><td class="rblock">     E.12. Since draft-ietf-httpbis-p3-payload-10 . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.13. Since draft-ietf-httpbis-p3-payload-11 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
208      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.14. Since draft-ietf-httpbis-p3-payload-12 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
209      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">     E.15. Since draft-ietf-httpbis-p3-payload-13 . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="left">     E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40</td><td> </td><td class="right">     E.16. Since draft-ietf-httpbis-p3-payload-14 . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
211      <tr><td><a name="diff0023" /></td></tr>
212      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.17. Since draft-ietf-httpbis-p3-payload-15 . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
213      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.18. Since draft-ietf-httpbis-p3-payload-16 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.18. Since draft-ietf-httpbis-p3-payload-16 . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="lblock">     E.19. Since draft-ietf-httpbis-p3-payload-17 . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock">     E.19. Since draft-ietf-httpbis-p3-payload-17 . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
215      <tr><td class="lineno" valign="top"></td><td class="lblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">40</span></td><td> </td><td class="rblock"><span class="insert">     E.20. Since draft-ietf-httpbis-p3-payload-18 . . . . . . . . . . 41</span></td><td class="lineno" valign="top"></td></tr>
216      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">41</span></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">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
219      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines HTTP/1.1 message payloads (a.k.a., content),</td><td> </td><td class="right">   This document defines HTTP/1.1 message payloads (a.k.a., content),</td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno" valign="top"></td><td class="left">   the associated metadata header fields that define how the payload is</td><td> </td><td class="right">   the associated metadata header fields that define how the payload is</td><td class="lineno" valign="top"></td></tr>
222      <tr><td class="lineno" valign="top"></td><td class="left">   intended to be interpreted by a recipient, the request header fields</td><td> </td><td class="right">   intended to be interpreted by a recipient, the request header fields</td><td class="lineno" valign="top"></td></tr>
223      <tr><td class="lineno" valign="top"></td><td class="left">   that might influence content selection, and the various selection</td><td> </td><td class="right">   that might influence content selection, and the various selection</td><td class="lineno" valign="top"></td></tr>
224      <tr><td class="lineno" valign="top"></td><td class="left">   algorithms that are collectively referred to as HTTP content</td><td> </td><td class="right">   algorithms that are collectively referred to as HTTP content</td><td class="lineno" valign="top"></td></tr>
225      <tr><td class="lineno" valign="top"></td><td class="left">   negotiation.</td><td> </td><td class="right">   negotiation.</td><td class="lineno" valign="top"></td></tr>
226      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
227      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
228      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 5, line 35</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 35</em></th><td></td></tr>
229      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
230      <tr><td class="lineno" valign="top"></td><td class="left">   This specification uses a number of terms to refer to the roles</td><td> </td><td class="right">   This specification uses a number of terms to refer to the roles</td><td class="lineno" valign="top"></td></tr>
231      <tr><td class="lineno" valign="top"></td><td class="left">   played by participants in, and objects of, the HTTP communication.</td><td> </td><td class="right">   played by participants in, and objects of, the HTTP communication.</td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
233      <tr><td class="lineno" valign="top"></td><td class="left">   content negotiation</td><td> </td><td class="right">   content negotiation</td><td class="lineno" valign="top"></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">      The mechanism for selecting the appropriate representation when</td><td> </td><td class="right">      The mechanism for selecting the appropriate representation when</td><td class="lineno" valign="top"></td></tr>
236      <tr><td class="lineno" valign="top"></td><td class="left">      servicing a request.  The representation in any response can be</td><td> </td><td class="right">      servicing a request.  The representation in any response can be</td><td class="lineno" valign="top"></td></tr>
237      <tr><td class="lineno" valign="top"></td><td class="left">      negotiated (including error responses).</td><td> </td><td class="right">      negotiated (including error responses).</td><td class="lineno" valign="top"></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
239      <tr><td><a name="diff0024" /></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">selected representation</span></td><td class="lineno" valign="top"></td></tr>
241      <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>
242      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      The current representation of the target resource that would have</span></td><td class="lineno" valign="top"></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      been selected in a successful response if the same request had</span></td><td class="lineno" valign="top"></td></tr>
244      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      used the method GET and excluded any conditional request header</span></td><td class="lineno" valign="top"></td></tr>
245      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      fields.</span></td><td class="lineno" valign="top"></td></tr>
246      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="left">1.2.  Conformance and Error Handling</td><td> </td><td class="right">1.2.  Conformance and Error Handling</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">   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>
250      <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>
251      <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>
252      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines conformance criteria for several roles in HTTP</td><td> </td><td class="right">   This document defines conformance criteria for several roles in HTTP</td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="left">   communication, including Senders, Recipients, Clients, Servers, User-</td><td> </td><td class="right">   communication, including Senders, Recipients, Clients, Servers, User-</td><td class="lineno" valign="top"></td></tr>
255      <tr><td class="lineno" valign="top"></td><td class="left">   Agents, Origin Servers, Intermediaries, Proxies and Gateways.  See</td><td> </td><td class="right">   Agents, Origin Servers, Intermediaries, Proxies and Gateways.  See</td><td class="lineno" valign="top"></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="left">   Section 2 of [Part1] for definitions of these terms.</td><td> </td><td class="right">   Section 2 of [Part1] for definitions of these terms.</td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
258      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 6, line 18</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 6, line 26</em></th><td></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="left">   define specific error handling mechanisms, except in cases where it</td><td> </td><td class="right">   define specific error handling mechanisms, except in cases where it</td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="left">   has direct impact on security.  This is because different uses of the</td><td> </td><td class="right">   has direct impact on security.  This is because different uses of the</td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="left">   protocol require different error handling strategies; for example, a</td><td> </td><td class="right">   protocol require different error handling strategies; for example, a</td><td class="lineno" valign="top"></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="left">   Web browser may wish to transparently recover from a response where</td><td> </td><td class="right">   Web browser may wish to transparently recover from a response where</td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="left">   the Location header field doesn't parse according to the ABNF,</td><td> </td><td class="right">   the Location header field doesn't parse according to the ABNF,</td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="left">   whereby in a systems control protocol using HTTP, this type of error</td><td> </td><td class="right">   whereby in a systems control protocol using HTTP, this type of error</td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="left">   recovery could lead to dangerous consequences.</td><td> </td><td class="right">   recovery could lead to dangerous consequences.</td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
267      <tr><td class="lineno" valign="top"></td><td class="left">1.3.  Syntax Notation</td><td> </td><td class="right">1.3.  Syntax Notation</td><td class="lineno" valign="top"></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
269      <tr><td><a name="diff0025" /></td></tr>
270      <tr><td class="lineno" valign="top"></td><td class="lblock">   This specification uses the <span class="delete">ABNF syntax</span> defined in Section 1.2 of</td><td> </td><td class="rblock">   This specification uses the <span class="insert">Augmented Backus-Naur Form (ABNF)</span></td><td class="lineno" valign="top"></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">[Part1] (which extends the syntax defined in [RFC5234] with a list</span></td><td> </td><td class="rblock"><span class="insert">   notation of [RFC5234] with the list rule extension</span> defined in Section</td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   rule).</span>  Appendix D shows the collected <span class="delete">ABNF,</span> with the list rule</td><td> </td><td class="rblock">   1.2 of <span class="insert">[Part1].</span>  Appendix D shows the collected <span class="insert">ABNF</span> with the list</td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="lblock">   expanded.</td><td> </td><td class="rblock">   rule expanded.</td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
275      <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>
276      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5234], Appendix B.1: ALPHA (letters), CR (carriage return), CRLF</td><td> </td><td class="right">   [RFC5234], Appendix B.1: ALPHA (letters), CR (carriage return), CRLF</td><td class="lineno" valign="top"></td></tr>
277      <tr><td class="lineno" valign="top"></td><td class="left">   (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote),</td><td> </td><td class="right">   (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote),</td><td class="lineno" valign="top"></td></tr>
278      <tr><td class="lineno" valign="top"></td><td class="left">   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit</td><td> </td><td class="right">   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit</td><td class="lineno" valign="top"></td></tr>
279      <tr><td class="lineno" valign="top"></td><td class="left">   sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td> </td><td class="right">   sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td class="lineno" valign="top"></td></tr>
280      <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>
281      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="left">1.3.1.  Core Rules</td><td> </td><td class="right">1.3.1.  Core Rules</td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="left">   The core rules below are defined in [Part1]:</td><td> </td><td class="right">   The core rules below are defined in [Part1]:</td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
286      <tr><td><a name="diff0026" /></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="lblock">     OWS            = &lt;OWS, defined in [Part1], Section <span class="delete">1.2.2&gt;</span></td><td> </td><td class="rblock">     OWS            = &lt;OWS, defined in [Part1], Section <span class="insert">3.2.1&gt;</span></td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="lblock">     token          = &lt;token, defined in [Part1], Section <span class="delete">3.2.3&gt;</span></td><td> </td><td class="rblock">     token          = &lt;token, defined in [Part1], Section <span class="insert">3.2.4&gt;</span></td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="lblock">     word           = &lt;word, defined in [Part1], Section <span class="delete">3.2.3&gt;</span></td><td> </td><td class="rblock">     word           = &lt;word, defined in [Part1], Section <span class="insert">3.2.4&gt;</span></td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno" valign="top"></td><td class="left">1.3.2.  ABNF Rules defined in other Parts of the Specification</td><td> </td><td class="right">1.3.2.  ABNF Rules defined in other Parts of the Specification</td><td class="lineno" valign="top"></td></tr>
292      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
293      <tr><td class="lineno" valign="top"></td><td class="left">   The ABNF rules below are defined in other parts:</td><td> </td><td class="right">   The ABNF rules below are defined in other parts:</td><td class="lineno" valign="top"></td></tr>
294      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
295      <tr><td class="lineno" valign="top"></td><td class="left">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;</td><td> </td><td class="right">     absolute-URI   = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;</td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="left">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.7&gt;</td><td> </td><td class="right">     partial-URI    = &lt;partial-URI, defined in [Part1], Section 2.7&gt;</td><td class="lineno" valign="top"></td></tr>
297      <tr><td><a name="diff0027" /></td></tr>
298      <tr><td class="lineno" valign="top"></td><td class="lblock">     qvalue         = &lt;qvalue, defined in [Part1], Section <span class="delete">5.3</span>&gt;</td><td> </td><td class="rblock">     qvalue         = &lt;qvalue, defined in [Part1], Section <span class="insert">4.3.1</span>&gt;</td><td class="lineno" valign="top"></td></tr>
299      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="left">2.  Protocol Parameters</td><td> </td><td class="right">2.  Protocol Parameters</td><td class="lineno" valign="top"></td></tr>
301      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="left">2.1.  Character Encodings (charset)</td><td> </td><td class="right">2.1.  Character Encodings (charset)</td><td class="lineno" valign="top"></td></tr>
303      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses charset names to indicate the character encoding of a</td><td> </td><td class="right">   HTTP uses charset names to indicate the character encoding of a</td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="left">   textual representation.</td><td> </td><td class="right">   textual representation.</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="left">   A character encoding is identified by a case-insensitive token.  The</td><td> </td><td class="right">   A character encoding is identified by a case-insensitive token.  The</td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left">   complete set of tokens is defined by the IANA Character Set registry</td><td> </td><td class="right">   complete set of tokens is defined by the IANA Character Set registry</td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
310      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 7, line 46</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 8, line 4</em></th><td></td></tr>
311      <tr><td class="lineno" valign="top"></td><td class="left">     content-coding   = token</td><td> </td><td class="right">     content-coding   = token</td><td class="lineno" valign="top"></td></tr>
312      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
313      <tr><td class="lineno" valign="top"></td><td class="left">   All content-coding values are case-insensitive.  HTTP/1.1 uses</td><td> </td><td class="right">   All content-coding values are case-insensitive.  HTTP/1.1 uses</td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="left">   content-coding values in the Accept-Encoding (Section 6.3) and</td><td> </td><td class="right">   content-coding values in the Accept-Encoding (Section 6.3) and</td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="left">   Content-Encoding (Section 6.5) header fields.  Although the value</td><td> </td><td class="right">   Content-Encoding (Section 6.5) header fields.  Although the value</td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno" valign="top"></td><td class="left">   describes the content-coding, what is more important is that it</td><td> </td><td class="right">   describes the content-coding, what is more important is that it</td><td class="lineno" valign="top"></td></tr>
317      <tr><td class="lineno" valign="top"></td><td class="left">   indicates what decoding mechanism will be required to remove the</td><td> </td><td class="right">   indicates what decoding mechanism will be required to remove the</td><td class="lineno" valign="top"></td></tr>
318      <tr><td class="lineno" valign="top"></td><td class="left">   encoding.</td><td> </td><td class="right">   encoding.</td><td class="lineno" valign="top"></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="left">   compress</td><td> </td><td class="right">   compress</td><td class="lineno" valign="top"></td></tr>
321      <tr><td><a name="diff0028" /></td></tr>
322      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock">      See Section <span class="insert">4.2.1</span> of [Part1].</td><td class="lineno" valign="top"></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">5.1.2.1</span> of [Part1].</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
324      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="left">   deflate</td><td> </td><td class="right">   deflate</td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
327      <tr><td><a name="diff0029" /></td></tr>
328      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">5.1</span>.2.2 of [Part1].</td><td> </td><td class="rblock">      See Section <span class="insert">4</span>.2.2 of [Part1].</td><td class="lineno" valign="top"></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
330      <tr><td class="lineno" valign="top"></td><td class="left">   gzip</td><td> </td><td class="right">   gzip</td><td class="lineno" valign="top"></td></tr>
331      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
332      <tr><td><a name="diff0030" /></td></tr>
333      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Section <span class="delete">5.1</span>.2.3 of [Part1].</td><td> </td><td class="rblock">      See Section <span class="insert">4</span>.2.3 of [Part1].</td><td class="lineno" valign="top"></td></tr>
334      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
335      <tr><td class="lineno" valign="top"></td><td class="left">2.2.1.  Content Coding Registry</td><td> </td><td class="right">2.2.1.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
336      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
337      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP Content Coding Registry defines the name space for the</td><td> </td><td class="right">   The HTTP Content Coding Registry defines the name space for the</td><td class="lineno" valign="top"></td></tr>
338      <tr><td class="lineno" valign="top"></td><td class="left">   content coding names.</td><td> </td><td class="right">   content coding names.</td><td class="lineno" valign="top"></td></tr>
339      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
340      <tr><td class="lineno" valign="top"></td><td class="left">   Registrations MUST include the following fields:</td><td> </td><td class="right">   Registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
341      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
342      <tr><td class="lineno" valign="top"></td><td class="left">   o  Name</td><td> </td><td class="right">   o  Name</td><td class="lineno" valign="top"></td></tr>
343      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
344      <tr><td class="lineno" valign="top"></td><td class="left">   o  Description</td><td> </td><td class="right">   o  Description</td><td class="lineno" valign="top"></td></tr>
345      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
346      <tr><td class="lineno" valign="top"></td><td class="left">   o  Pointer to specification text</td><td> </td><td class="right">   o  Pointer to specification text</td><td class="lineno" valign="top"></td></tr>
347      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
348      <tr><td class="lineno" valign="top"></td><td class="left">   Names of content codings MUST NOT overlap with names of transfer</td><td> </td><td class="right">   Names of content codings MUST NOT overlap with names of transfer</td><td class="lineno" valign="top"></td></tr>
349      <tr><td><a name="diff0031" /></td></tr>
350      <tr><td class="lineno" valign="top"></td><td class="lblock">   codings (Section <span class="delete">5.1</span> of [Part1]), unless the encoding transformation</td><td> </td><td class="rblock">   codings (Section <span class="insert">4</span> of [Part1]), unless the encoding transformation is</td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="lblock">   is identical (as <span class="delete">it</span> is the case for the compression codings defined</td><td> </td><td class="rblock">   identical (as is the case for the compression codings defined in</td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="lblock">   in Section <span class="delete">5.1.2</span> of [Part1]).</td><td> </td><td class="rblock">   Section <span class="insert">4.2</span> of [Part1]).</td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
354      <tr><td><a name="diff0032" /></td></tr>
355      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this name space require <span class="delete">a specification</span> (see</td><td> </td><td class="rblock">   Values to be added to this name space require <span class="insert">IETF Review</span> (see</td><td class="lineno" valign="top"></td></tr>
356      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">"Specification Required" in</span> Section 4.1 of [RFC5226]), and MUST</td><td> </td><td class="rblock">   Section 4.1 of [RFC5226]), and MUST conform to the purpose of content</td><td class="lineno" valign="top"></td></tr>
357      <tr><td class="lineno" valign="top"></td><td class="lblock">   conform to the purpose of content coding defined in this section.</td><td> </td><td class="rblock">   coding defined in this section.</td><td class="lineno" valign="top"></td></tr>
358      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
359      <tr><td class="lineno" valign="top"></td><td class="left">   The registry itself is maintained at</td><td> </td><td class="right">   The registry itself is maintained at</td><td class="lineno" valign="top"></td></tr>
360      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td class="lineno" valign="top"></td></tr>
361      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
362      <tr><td class="lineno" valign="top"></td><td class="left">2.3.  Media Types</td><td> </td><td class="right">2.3.  Media Types</td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses Internet Media Types [RFC2046] in the Content-Type</td><td> </td><td class="right">   HTTP uses Internet Media Types [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.8) and Accept (Section 6.1) header fields in order to</td><td> </td><td class="right">   (Section 6.8) and Accept (Section 6.1) header fields in order to</td><td class="lineno" valign="top"></td></tr>
366      <tr><td class="lineno" valign="top"></td><td class="left">   provide open and extensible data typing and type negotiation.</td><td> </td><td class="right">   provide open and extensible data typing and type negotiation.</td><td class="lineno" valign="top"></td></tr>
367      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
368      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
369      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 9, line 50</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 10, line 8</em></th><td></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="left">   line breaks applies only to text media in the payload body; a bare CR</td><td> </td><td class="right">   line breaks applies only to text media in the payload body; a bare CR</td><td class="lineno" valign="top"></td></tr>
371      <tr><td class="lineno" valign="top"></td><td class="left">   or LF MUST NOT be substituted for CRLF within any of the HTTP control</td><td> </td><td class="right">   or LF MUST NOT be substituted for CRLF within any of the HTTP control</td><td class="lineno" valign="top"></td></tr>
372      <tr><td class="lineno" valign="top"></td><td class="left">   structures (such as header fields and multipart boundaries).</td><td> </td><td class="right">   structures (such as header fields and multipart boundaries).</td><td class="lineno" valign="top"></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
374      <tr><td class="lineno" valign="top"></td><td class="left">   If a representation is encoded with a content-coding, the underlying</td><td> </td><td class="right">   If a representation is encoded with a content-coding, the underlying</td><td class="lineno" valign="top"></td></tr>
375      <tr><td class="lineno" valign="top"></td><td class="left">   data MUST be in a form defined above prior to being encoded.</td><td> </td><td class="right">   data MUST be in a form defined above prior to being encoded.</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">2.3.2.  Multipart Types</td><td> </td><td class="right">2.3.2.  Multipart Types</td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno" valign="top"></td><td class="left">   MIME provides for a number of "multipart" types -- encapsulations of</td><td> </td><td class="right">   MIME provides for a number of "multipart" types -- encapsulations of</td><td class="lineno" valign="top"></td></tr>
380      <tr><td><a name="diff0033" /></td></tr>
381      <tr><td class="lineno" valign="top"></td><td class="lblock">   one or more representations within a single message<span class="delete">-</span>body.  All</td><td> </td><td class="rblock">   one or more representations within a single message<span class="insert"> </span>body.  All</td><td class="lineno" valign="top"></td></tr>
382      <tr><td class="lineno" valign="top"></td><td class="left">   multipart types share a common syntax, as defined in Section 5.1.1 of</td><td> </td><td class="right">   multipart types share a common syntax, as defined in Section 5.1.1 of</td><td class="lineno" valign="top"></td></tr>
383      <tr><td><a name="diff0034" /></td></tr>
384      <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>
385      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2046], and MUST include a boundary parameter as part of the media</td><td> </td><td class="right">   [RFC2046], and MUST include a boundary parameter as part of the media</td><td class="lineno" valign="top"></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="left">   type value.  The message body is itself a protocol element and MUST</td><td> </td><td class="right">   type value.  The message body is itself a protocol element and MUST</td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="left">   therefore use only CRLF to represent line breaks between body-parts.</td><td> </td><td class="right">   therefore use only CRLF to represent line breaks between body-parts.</td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
389      <tr><td><a name="diff0035" /></td></tr>
390      <tr><td class="lineno" valign="top"></td><td class="lblock">   In general, HTTP treats a multipart message<span class="delete">-</span>body no differently than</td><td> </td><td class="rblock">   In general, HTTP treats a multipart message<span class="insert"> </span>body no differently than</td><td class="lineno" valign="top"></td></tr>
391      <tr><td class="lineno" valign="top"></td><td class="left">   any other media type: strictly as payload.  HTTP does not use the</td><td> </td><td class="right">   any other media type: strictly as payload.  HTTP does not use the</td><td class="lineno" valign="top"></td></tr>
392      <tr><td><a name="diff0036" /></td></tr>
393      <tr><td class="lineno" valign="top"></td><td class="lblock">   multipart boundary as an indicator of message<span class="delete">-</span>body length.  In all</td><td> </td><td class="rblock">   multipart boundary as an indicator of message<span class="insert"> </span>body length.  In all</td><td class="lineno" valign="top"></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="left">   other respects, an HTTP user agent SHOULD follow the same or similar</td><td> </td><td class="right">   other respects, an HTTP user agent SHOULD follow the same or similar</td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno" valign="top"></td><td class="left">   behavior as a MIME user agent would upon receipt of a multipart type.</td><td> </td><td class="right">   behavior as a MIME user agent would upon receipt of a multipart type.</td><td class="lineno" valign="top"></td></tr>
396      <tr><td><a name="diff0037" /></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="lblock">   The MIME header fields within each body-part of a multipart message<span class="delete">-</span></td><td> </td><td class="rblock">   The MIME header fields within each body-part of a multipart message</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno" valign="top"></td><td class="left">   body do not have any significance to HTTP beyond that defined by</td><td> </td><td class="right">   body do not have any significance to HTTP beyond that defined by</td><td class="lineno" valign="top"></td></tr>
399      <tr><td class="lineno" valign="top"></td><td class="left">   their MIME semantics.</td><td> </td><td class="right">   their MIME semantics.</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 an application receives an unrecognized multipart subtype, the</td><td> </td><td class="right">   If an application receives an unrecognized multipart subtype, the</td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">   application MUST treat it as being equivalent to "multipart/mixed".</td><td> </td><td class="right">   application MUST treat it as being equivalent to "multipart/mixed".</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left">      Note: The "multipart/form-data" type has been specifically defined</td><td> </td><td class="right">      Note: The "multipart/form-data" type has been specifically defined</td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left">      for carrying form data suitable for processing via the POST</td><td> </td><td class="right">      for carrying form data suitable for processing via the POST</td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left">      request method, as described in [RFC2388].</td><td> </td><td class="right">      request method, as described in [RFC2388].</td><td class="lineno" valign="top"></td></tr>
407      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></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 11, line 10</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 11, line 12</em></th><td></td></tr>
410      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
411      <tr><td class="lineno" valign="top"></td><td class="left">     en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN</td><td> </td><td class="right">     en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN</td><td class="lineno" valign="top"></td></tr>
412      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
413      <tr><td class="lineno" valign="top"></td><td class="left">   See [RFC5646] for further information.</td><td> </td><td class="right">   See [RFC5646] for further information.</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">3.  Payload</td><td> </td><td class="right">3.  Payload</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">   HTTP messages MAY transfer a payload if not otherwise restricted by</td><td> </td><td class="right">   HTTP messages MAY transfer a payload if not otherwise restricted by</td><td class="lineno" valign="top"></td></tr>
418      <tr><td class="lineno" valign="top"></td><td class="left">   the request method or response status code.  The payload consists of</td><td> </td><td class="right">   the request method or response status code.  The payload consists of</td><td class="lineno" valign="top"></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="left">   metadata, in the form of header fields, and data, in the form of the</td><td> </td><td class="right">   metadata, in the form of header fields, and data, in the form of the</td><td class="lineno" valign="top"></td></tr>
420      <tr><td><a name="diff0038" /></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="lblock">   sequence of octets in the message<span class="delete">-</span>body after any transfer-coding has</td><td> </td><td class="rblock">   sequence of octets in the message<span class="insert"> </span>body after any transfer-coding has</td><td class="lineno" valign="top"></td></tr>
422      <tr><td class="lineno" valign="top"></td><td class="left">   been decoded.</td><td> </td><td class="right">   been decoded.</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">   A "payload" in HTTP is always a partial or complete representation of</td><td> </td><td class="right">   A "payload" in HTTP is always a partial or complete representation of</td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="left">   some resource.  We use separate terms for payload and representation</td><td> </td><td class="right">   some resource.  We use separate terms for payload and representation</td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="left">   because some messages contain only the associated representation's</td><td> </td><td class="right">   because some messages contain only the associated representation's</td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno" valign="top"></td><td class="left">   header fields (e.g., responses to HEAD) or only some part(s) of the</td><td> </td><td class="right">   header fields (e.g., responses to HEAD) or only some part(s) of the</td><td class="lineno" valign="top"></td></tr>
428      <tr><td class="lineno" valign="top"></td><td class="left">   representation (e.g., the 206 status code).</td><td> </td><td class="right">   representation (e.g., the 206 status code).</td><td class="lineno" valign="top"></td></tr>
429      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
430      <tr><td class="lineno" valign="top"></td><td class="left">3.1.  Payload Header Fields</td><td> </td><td class="right">3.1.  Payload Header Fields</td><td class="lineno" valign="top"></td></tr>
431      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
432      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields that specifically define the payload, rather than</td><td> </td><td class="right">   HTTP header fields that specifically define the payload, rather than</td><td class="lineno" valign="top"></td></tr>
433      <tr><td class="lineno" valign="top"></td><td class="left">   the associated representation, are referred to as "payload header</td><td> </td><td class="right">   the associated representation, are referred to as "payload header</td><td class="lineno" valign="top"></td></tr>
434      <tr><td class="lineno" valign="top"></td><td class="left">   fields".  The following payload header fields are defined by</td><td> </td><td class="right">   fields".  The following payload header fields are defined by</td><td class="lineno" valign="top"></td></tr>
435      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1:</td><td> </td><td class="right">   HTTP/1.1:</td><td class="lineno" valign="top"></td></tr>
436      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
437      <tr><td><a name="diff0039" /></td></tr>
438      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-------------------+------------------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+--------------------------+</span></td><td class="lineno" valign="top"></td></tr>
439      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Header Field Name | Defined in...          |</td><td> </td><td class="rblock">   | Header Field Name | Defined in...            |</td><td class="lineno" valign="top"></td></tr>
440      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-------------------+------------------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+--------------------------+</span></td><td class="lineno" valign="top"></td></tr>
441      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Length    | Section <span class="delete">8.2</span> of [Part1] |</td><td> </td><td class="rblock">   | Content-Length    | Section <span class="insert">3.3.2</span> of [Part1] |</td><td class="lineno" valign="top"></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Content-Range     | Section 5.2 of [Part5] |</td><td> </td><td class="rblock">   | Content-Range     | Section 5.2 of [Part5]   |</td><td class="lineno" valign="top"></td></tr>
443      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-------------------+------------------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+--------------------------+</span></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 class="lineno" valign="top"></td><td class="left">3.2.  Payload Body</td><td> </td><td class="right">3.2.  Payload Body</td><td class="lineno" valign="top"></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
447      <tr><td><a name="diff0040" /></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="lblock">   A payload body is only present in a message when a message<span class="delete">-</span>body is</td><td> </td><td class="rblock">   A payload body is only present in a message when a message<span class="insert"> </span>body is</td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="left">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td> </td><td class="right">   present, as described in Section 3.3 of [Part1].  The payload body is</td><td class="lineno" valign="top"></td></tr>
450      <tr><td><a name="diff0041" /></td></tr>
451      <tr><td class="lineno" valign="top"></td><td class="lblock">   obtained from the message<span class="delete">-</span>body by decoding any Transfer-Encoding that</td><td> </td><td class="rblock">   obtained from the message<span class="insert"> </span>body by decoding any Transfer-Encoding that</td><td class="lineno" valign="top"></td></tr>
452      <tr><td class="lineno" valign="top"></td><td class="left">   might have been applied to ensure safe and proper transfer of the</td><td> </td><td class="right">   might have been applied to ensure safe and proper transfer of the</td><td class="lineno" valign="top"></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="left">   message.</td><td> </td><td class="right">   message.</td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="left">4.  Representation</td><td> </td><td class="right">4.  Representation</td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno" valign="top"></td><td class="left">   A "representation" is information in a format that can be readily</td><td> </td><td class="right">   A "representation" is information in a format that can be readily</td><td class="lineno" valign="top"></td></tr>
458      <tr><td class="lineno" valign="top"></td><td class="left">   communicated from one party to another.  A resource representation is</td><td> </td><td class="right">   communicated from one party to another.  A resource representation is</td><td class="lineno" valign="top"></td></tr>
459      <tr><td class="lineno" valign="top"></td><td class="left">   information that reflects the state of that resource, as observed at</td><td> </td><td class="right">   information that reflects the state of that resource, as observed at</td><td class="lineno" valign="top"></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="left">   some point in the past (e.g., in a response to GET) or to be desired</td><td> </td><td class="right">   some point in the past (e.g., in a response to GET) or to be desired</td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="left">   at some point in the future (e.g., in a PUT request).</td><td> </td><td class="right">   at some point in the future (e.g., in a PUT request).</td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
463      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 12, line 18</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 12, line 20</em></th><td></td></tr>
464      <tr><td class="lineno" valign="top"></td><td class="left">   contrast, contains either a representation that describes the</td><td> </td><td class="right">   contrast, contains either a representation that describes the</td><td class="lineno" valign="top"></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="left">   successful action or a representation of the target resource, with</td><td> </td><td class="right">   successful action or a representation of the target resource, with</td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="left">   the latter indicated by a Content-Location header field with the same</td><td> </td><td class="right">   the latter indicated by a Content-Location header field with the same</td><td class="lineno" valign="top"></td></tr>
467      <tr><td class="lineno" valign="top"></td><td class="left">   value as the effective request URI.  Likewise, response messages with</td><td> </td><td class="right">   value as the effective request URI.  Likewise, response messages with</td><td class="lineno" valign="top"></td></tr>
468      <tr><td class="lineno" valign="top"></td><td class="left">   an error status code usually contain a representation that describes</td><td> </td><td class="right">   an error status code usually contain a representation that describes</td><td class="lineno" valign="top"></td></tr>
469      <tr><td class="lineno" valign="top"></td><td class="left">   the error and what next steps are suggested for resolving it.</td><td> </td><td class="right">   the error and what next steps are suggested for resolving it.</td><td class="lineno" valign="top"></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
471      <tr><td class="lineno" valign="top"></td><td class="left">4.1.  Representation Header Fields</td><td> </td><td class="right">4.1.  Representation Header Fields</td><td class="lineno" valign="top"></td></tr>
472      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
473      <tr><td class="lineno" valign="top"></td><td class="left">   Representation header fields define metadata about the representation</td><td> </td><td class="right">   Representation header fields define metadata about the representation</td><td class="lineno" valign="top"></td></tr>
474      <tr><td><a name="diff0042" /></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="lblock">   data enclosed in the message<span class="delete">-body or, if no message-</span>body is present,</td><td> </td><td class="rblock">   data enclosed in the message<span class="insert"> body or, if no message </span>body is present,</td><td class="lineno" valign="top"></td></tr>
476      <tr><td class="lineno" valign="top"></td><td class="left">   about the representation that would have been transferred in a 200</td><td> </td><td class="right">   about the representation that would have been transferred in a 200</td><td class="lineno" valign="top"></td></tr>
477      <tr><td class="lineno" valign="top"></td><td class="left">   response to a simultaneous GET request with the same effective</td><td> </td><td class="right">   response to a simultaneous GET request with the same effective</td><td class="lineno" valign="top"></td></tr>
478      <tr><td class="lineno" valign="top"></td><td class="left">   request URI.</td><td> </td><td class="right">   request URI.</td><td class="lineno" valign="top"></td></tr>
479      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
480      <tr><td class="lineno" valign="top"></td><td class="left">   The following header fields are defined as representation metadata:</td><td> </td><td class="right">   The following header fields are defined as representation metadata:</td><td class="lineno" valign="top"></td></tr>
481      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
482      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
483      <tr><td class="lineno" valign="top"></td><td class="left">   | Header Field Name | Defined in...          |</td><td> </td><td class="right">   | Header Field Name | Defined in...          |</td><td class="lineno" valign="top"></td></tr>
484      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
485      <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Encoding  | Section 6.5            |</td><td> </td><td class="right">   | Content-Encoding  | Section 6.5            |</td><td class="lineno" valign="top"></td></tr>
486      <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Language  | Section 6.6            |</td><td> </td><td class="right">   | Content-Language  | Section 6.6            |</td><td class="lineno" valign="top"></td></tr>
487      <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Location  | Section 6.7            |</td><td> </td><td class="right">   | Content-Location  | Section 6.7            |</td><td class="lineno" valign="top"></td></tr>
488      <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Type      | Section 6.8            |</td><td> </td><td class="right">   | Content-Type      | Section 6.8            |</td><td class="lineno" valign="top"></td></tr>
489      <tr><td class="lineno" valign="top"></td><td class="left">   | Expires           | Section 3.3 of [Part6] |</td><td> </td><td class="right">   | Expires           | Section 3.3 of [Part6] |</td><td class="lineno" valign="top"></td></tr>
490      <tr><td><a name="diff0043" /></td></tr>
491      <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>
492      <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>
493      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Additional header fields define metadata about the selected</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">   representation, which might differ from the representation included</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">   in the message for responses to some state-changing methods.  The</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">   following header fields are defined as selected representation</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">   metadata:</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">   +-------------------+------------------------+</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">   | Header Field Name | Defined in...          |</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">   +-------------------+------------------------+</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">   | ETag              | Section 2.3 of [Part4] |</span></td><td class="lineno" valign="top"></td></tr>
503      <tr><td class="lineno" valign="top"></td><td class="left">   | Last-Modified     | Section 2.2 of [Part4] |</td><td> </td><td class="right">   | Last-Modified     | Section 2.2 of [Part4] |</td><td class="lineno" valign="top"></td></tr>
504      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+------------------------+</td><td> </td><td class="right">   +-------------------+------------------------+</td><td class="lineno" valign="top"></td></tr>
505      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
506      <tr><td class="lineno" valign="top"></td><td class="left">4.2.  Representation Data</td><td> </td><td class="right">4.2.  Representation Data</td><td class="lineno" valign="top"></td></tr>
507      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
508      <tr><td class="lineno" valign="top"></td><td class="left">   The representation body associated with an HTTP message is either</td><td> </td><td class="right">   The representation body associated with an HTTP message is either</td><td class="lineno" valign="top"></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="left">   provided as the payload body of the message or referred to by the</td><td> </td><td class="right">   provided as the payload body of the message or referred to by the</td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="left">   message semantics and the effective request URI.  The representation</td><td> </td><td class="right">   message semantics and the effective request URI.  The representation</td><td class="lineno" valign="top"></td></tr>
511      <tr><td class="lineno" valign="top"></td><td class="left">   data is in a format and encoding defined by the representation</td><td> </td><td class="right">   data is in a format and encoding defined by the representation</td><td class="lineno" valign="top"></td></tr>
512      <tr><td class="lineno" valign="top"></td><td class="left">   metadata header fields.</td><td> </td><td class="right">   metadata header fields.</td><td class="lineno" valign="top"></td></tr>
513      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
514      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 15, line 17</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 15, line 32</em></th><td></td></tr>
515      <tr><td class="lineno" valign="top"></td><td class="left">       of responses have multiple representations) and a potential</td><td> </td><td class="right">       of responses have multiple representations) and a potential</td><td class="lineno" valign="top"></td></tr>
516      <tr><td class="lineno" valign="top"></td><td class="left">       violation of the user's privacy.</td><td> </td><td class="right">       violation of the user's privacy.</td><td class="lineno" valign="top"></td></tr>
517      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
518      <tr><td class="lineno" valign="top"></td><td class="left">   3.  It complicates the implementation of an origin server and the</td><td> </td><td class="right">   3.  It complicates the implementation of an origin server and the</td><td class="lineno" valign="top"></td></tr>
519      <tr><td class="lineno" valign="top"></td><td class="left">       algorithms for generating responses to a request.</td><td> </td><td class="right">       algorithms for generating responses to a request.</td><td class="lineno" valign="top"></td></tr>
520      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
521      <tr><td class="lineno" valign="top"></td><td class="left">   4.  It might limit a public cache's ability to use the same response</td><td> </td><td class="right">   4.  It might limit a public cache's ability to use the same response</td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="left">       for multiple user's requests.</td><td> </td><td class="right">       for multiple user's requests.</td><td class="lineno" valign="top"></td></tr>
523      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
524      <tr><td class="lineno" valign="top"></td><td class="left">   Server-driven negotiation allows the user agent to specify its</td><td> </td><td class="right">   Server-driven negotiation allows the user agent to specify its</td><td class="lineno" valign="top"></td></tr>
525      <tr><td><a name="diff0044" /></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="lblock">   preferences, but it cannot expect responses to always hono<span class="delete">u</span>r them.</td><td> </td><td class="rblock">   preferences, but it cannot expect responses to always honor them.</td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="left">   For example, the origin server might not implement server-driven</td><td> </td><td class="right">   For example, the origin server might not implement server-driven</td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="left">   negotiation, or it might decide that sending a response that doesn't</td><td> </td><td class="right">   negotiation, or it might decide that sending a response that doesn't</td><td class="lineno" valign="top"></td></tr>
529      <tr><td class="lineno" valign="top"></td><td class="left">   conform to them is better than sending a 406 (Not Acceptable)</td><td> </td><td class="right">   conform to them is better than sending a 406 (Not Acceptable)</td><td class="lineno" valign="top"></td></tr>
530      <tr><td class="lineno" valign="top"></td><td class="left">   response.</td><td> </td><td class="right">   response.</td><td class="lineno" valign="top"></td></tr>
531      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
532      <tr><td class="lineno" valign="top"></td><td class="left">   Many of the mechanisms for expressing preferences use quality values</td><td> </td><td class="right">   Many of the mechanisms for expressing preferences use quality values</td><td class="lineno" valign="top"></td></tr>
533      <tr><td><a name="diff0045" /></td></tr>
534      <tr><td class="lineno" valign="top"></td><td class="lblock">   to declare relative preference.  See Section <span class="delete">5.3</span> of [Part1] for more</td><td> </td><td class="rblock">   to declare relative preference.  See Section <span class="insert">4.3.1</span> of [Part1] for</td><td class="lineno" valign="top"></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="lblock">   information.</td><td> </td><td class="rblock">   more information.</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">   HTTP/1.1 includes the following header fields for enabling server-</td><td> </td><td class="right">   HTTP/1.1 includes the following header fields for enabling server-</td><td class="lineno" valign="top"></td></tr>
538      <tr><td class="lineno" valign="top"></td><td class="left">   driven negotiation through description of user agent capabilities and</td><td> </td><td class="right">   driven negotiation through description of user agent capabilities and</td><td class="lineno" valign="top"></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="left">   user preferences: Accept (Section 6.1), Accept-Charset (Section 6.2),</td><td> </td><td class="right">   user preferences: Accept (Section 6.1), Accept-Charset (Section 6.2),</td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="left">   Accept-Encoding (Section 6.3), Accept-Language (Section 6.4), and</td><td> </td><td class="right">   Accept-Encoding (Section 6.3), Accept-Language (Section 6.4), and</td><td class="lineno" valign="top"></td></tr>
541      <tr><td><a name="diff0046" /></td></tr>
542      <tr><td class="lineno" valign="top"></td><td class="lblock">   User-Agent (Section <span class="delete">9</span>.10 of [Part2]).  However, an origin server is</td><td> </td><td class="rblock">   User-Agent (Section <span class="insert">10</span>.10 of [Part2]).  However, an origin server is</td><td class="lineno" valign="top"></td></tr>
543      <tr><td class="lineno" valign="top"></td><td class="left">   not limited to these dimensions and MAY vary the response based on</td><td> </td><td class="right">   not limited to these dimensions and MAY vary the response based on</td><td class="lineno" valign="top"></td></tr>
544      <tr><td class="lineno" valign="top"></td><td class="left">   any aspect of the request, including aspects of the connection (e.g.,</td><td> </td><td class="right">   any aspect of the request, including aspects of the connection (e.g.,</td><td class="lineno" valign="top"></td></tr>
545      <tr><td class="lineno" valign="top"></td><td class="left">   IP address) or information within extension header fields not defined</td><td> </td><td class="right">   IP address) or information within extension header fields not defined</td><td class="lineno" valign="top"></td></tr>
546      <tr><td class="lineno" valign="top"></td><td class="left">   by this specification.</td><td> </td><td class="right">   by this specification.</td><td class="lineno" valign="top"></td></tr>
547      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
548      <tr><td class="lineno" valign="top"></td><td class="left">      Note: In practice, User-Agent based negotiation is fragile,</td><td> </td><td class="right">      Note: In practice, User-Agent based negotiation is fragile,</td><td class="lineno" valign="top"></td></tr>
549      <tr><td class="lineno" valign="top"></td><td class="left">      because new clients might not be recognized.</td><td> </td><td class="right">      because new clients might not be recognized.</td><td class="lineno" valign="top"></td></tr>
550      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
551      <tr><td class="lineno" valign="top"></td><td class="left">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td> </td><td class="right">   The Vary header field (Section 3.5 of [Part6]) can be used to express</td><td class="lineno" valign="top"></td></tr>
552      <tr><td class="lineno" valign="top"></td><td class="left">   the parameters the server uses to select a representation that is</td><td> </td><td class="right">   the parameters the server uses to select a representation that is</td><td class="lineno" valign="top"></td></tr>
553      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
554      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 17, line 10</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 17, line 26</em></th><td></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="left">   The asterisk "*" character is used to group media types into ranges,</td><td> </td><td class="right">   The asterisk "*" character is used to group media types into ranges,</td><td class="lineno" valign="top"></td></tr>
556      <tr><td class="lineno" valign="top"></td><td class="left">   with "*/*" indicating all media types and "type/*" indicating all</td><td> </td><td class="right">   with "*/*" indicating all media types and "type/*" indicating all</td><td class="lineno" valign="top"></td></tr>
557      <tr><td class="lineno" valign="top"></td><td class="left">   subtypes of that type.  The media-range MAY include media type</td><td> </td><td class="right">   subtypes of that type.  The media-range MAY include media type</td><td class="lineno" valign="top"></td></tr>
558      <tr><td class="lineno" valign="top"></td><td class="left">   parameters that are applicable to that range.</td><td> </td><td class="right">   parameters that are applicable to that range.</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">   Each media-range MAY be followed by one or more accept-params,</td><td> </td><td class="right">   Each media-range MAY be followed by one or more accept-params,</td><td class="lineno" valign="top"></td></tr>
561      <tr><td class="lineno" valign="top"></td><td class="left">   beginning with the "q" parameter for indicating a relative quality</td><td> </td><td class="right">   beginning with the "q" parameter for indicating a relative quality</td><td class="lineno" valign="top"></td></tr>
562      <tr><td class="lineno" valign="top"></td><td class="left">   factor.  The first "q" parameter (if any) separates the media-range</td><td> </td><td class="right">   factor.  The first "q" parameter (if any) separates the media-range</td><td class="lineno" valign="top"></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="left">   parameter(s) from the accept-params.  Quality factors allow the user</td><td> </td><td class="right">   parameter(s) from the accept-params.  Quality factors allow the user</td><td class="lineno" valign="top"></td></tr>
564      <tr><td class="lineno" valign="top"></td><td class="left">   or user agent to indicate the relative degree of preference for that</td><td> </td><td class="right">   or user agent to indicate the relative degree of preference for that</td><td class="lineno" valign="top"></td></tr>
565      <tr><td><a name="diff0047" /></td></tr>
566      <tr><td class="lineno" valign="top"></td><td class="lblock">   media-range, using the qvalue scale from 0 to 1 (Section <span class="delete">5.3</span> of</td><td> </td><td class="rblock">   media-range, using the qvalue scale from 0 to 1 (Section <span class="insert">4.3.1</span> of</td><td class="lineno" valign="top"></td></tr>
567      <tr><td class="lineno" valign="top"></td><td class="left">   [Part1]).  The default value is q=1.</td><td> </td><td class="right">   [Part1]).  The default value is q=1.</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">      Note: Use of the "q" parameter name to separate media type</td><td> </td><td class="right">      Note: Use of the "q" parameter name to separate media type</td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="left">      parameters from Accept extension parameters is due to historical</td><td> </td><td class="right">      parameters from Accept extension parameters is due to historical</td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="left">      practice.  Although this prevents any media type parameter named</td><td> </td><td class="right">      practice.  Although this prevents any media type parameter named</td><td class="lineno" valign="top"></td></tr>
572      <tr><td class="lineno" valign="top"></td><td class="left">      "q" from being used with a media range, such an event is believed</td><td> </td><td class="right">      "q" from being used with a media range, such an event is believed</td><td class="lineno" valign="top"></td></tr>
573      <tr><td class="lineno" valign="top"></td><td class="left">      to be unlikely given the lack of any "q" parameters in the IANA</td><td> </td><td class="right">      to be unlikely given the lack of any "q" parameters in the IANA</td><td class="lineno" valign="top"></td></tr>
574      <tr><td class="lineno" valign="top"></td><td class="left">      media type registry and the rare usage of any media type</td><td> </td><td class="right">      media type registry and the rare usage of any media type</td><td class="lineno" valign="top"></td></tr>
575      <tr><td class="lineno" valign="top"></td><td class="left">      parameters in Accept.  Future media types are discouraged from</td><td> </td><td class="right">      parameters in Accept.  Future media types are discouraged from</td><td class="lineno" valign="top"></td></tr>
576      <tr><td class="lineno" valign="top"></td><td class="left">      registering any parameter named "q".</td><td> </td><td class="right">      registering any parameter named "q".</td><td class="lineno" valign="top"></td></tr>
577      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
578      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 20, line 14</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 20, line 30</em></th><td></td></tr>
579      <tr><td class="lineno" valign="top"></td><td class="left">       field.</td><td> </td><td class="right">       field.</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 class="lineno" valign="top"></td><td class="left">   2.  If the representation has no content-coding, then it is</td><td> </td><td class="right">   2.  If the representation has no content-coding, then it is</td><td class="lineno" valign="top"></td></tr>
582      <tr><td class="lineno" valign="top"></td><td class="left">       acceptable by default unless specifically excluded by the Accept-</td><td> </td><td class="right">       acceptable by default unless specifically excluded by the Accept-</td><td class="lineno" valign="top"></td></tr>
583      <tr><td class="lineno" valign="top"></td><td class="left">       Encoding field stating either "identity;q=0" or "*;q=0" without a</td><td> </td><td class="right">       Encoding field stating either "identity;q=0" or "*;q=0" without a</td><td class="lineno" valign="top"></td></tr>
584      <tr><td class="lineno" valign="top"></td><td class="left">       more specific entry for "identity".</td><td> </td><td class="right">       more specific entry for "identity".</td><td class="lineno" valign="top"></td></tr>
585      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
586      <tr><td class="lineno" valign="top"></td><td class="left">   3.  If the representation's content-coding is one of the content-</td><td> </td><td class="right">   3.  If the representation's content-coding is one of the content-</td><td class="lineno" valign="top"></td></tr>
587      <tr><td class="lineno" valign="top"></td><td class="left">       codings listed in the Accept-Encoding field, then it is</td><td> </td><td class="right">       codings listed in the Accept-Encoding field, then it is</td><td class="lineno" valign="top"></td></tr>
588      <tr><td class="lineno" valign="top"></td><td class="left">       acceptable unless it is accompanied by a qvalue of 0.  (As</td><td> </td><td class="right">       acceptable unless it is accompanied by a qvalue of 0.  (As</td><td class="lineno" valign="top"></td></tr>
589      <tr><td><a name="diff0048" /></td></tr>
590      <tr><td class="lineno" valign="top"></td><td class="lblock">       defined in Section <span class="delete">5.3</span> of [Part1], a qvalue of 0 means "not</td><td> </td><td class="rblock">       defined in Section <span class="insert">4.3.1</span> of [Part1], a qvalue of 0 means "not</td><td class="lineno" valign="top"></td></tr>
591      <tr><td class="lineno" valign="top"></td><td class="left">       acceptable".)</td><td> </td><td class="right">       acceptable".)</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">   4.  If multiple content-codings are acceptable, then the acceptable</td><td> </td><td class="right">   4.  If multiple content-codings are acceptable, then the acceptable</td><td class="lineno" valign="top"></td></tr>
594      <tr><td class="lineno" valign="top"></td><td class="left">       content-coding with the highest non-zero qvalue is preferred.</td><td> </td><td class="right">       content-coding with the highest non-zero qvalue is preferred.</td><td class="lineno" valign="top"></td></tr>
595      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
596      <tr><td class="lineno" valign="top"></td><td class="left">   An Accept-Encoding header field with a combined field-value that is</td><td> </td><td class="right">   An Accept-Encoding header field with a combined field-value that is</td><td class="lineno" valign="top"></td></tr>
597      <tr><td class="lineno" valign="top"></td><td class="left">   empty implies that the user agent does not want any content-coding in</td><td> </td><td class="right">   empty implies that the user agent does not want any content-coding in</td><td class="lineno" valign="top"></td></tr>
598      <tr><td class="lineno" valign="top"></td><td class="left">   response.  If an Accept-Encoding header field is present in a request</td><td> </td><td class="right">   response.  If an Accept-Encoding header field is present in a request</td><td class="lineno" valign="top"></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="left">   and none of the available representations for the response have a</td><td> </td><td class="right">   and none of the available representations for the response have a</td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno" valign="top"></td><td class="left">   content-coding that is listed as acceptable, the origin server SHOULD</td><td> </td><td class="right">   content-coding that is listed as acceptable, the origin server SHOULD</td><td class="lineno" valign="top"></td></tr>
601      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
602      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 23, line 39</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 24, line 6</em></th><td></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left">   The "Content-Location" header field supplies a URI that can be used</td><td> </td><td class="right">   The "Content-Location" header field supplies a URI that can be used</td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left">   as a specific identifier for the representation in this message.  In</td><td> </td><td class="right">   as a specific identifier for the representation in this message.  In</td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left">   other words, if one were to perform a GET on this URI at the time of</td><td> </td><td class="right">   other words, if one were to perform a GET on this URI at the time of</td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left">   this message's generation, then a 200 response would contain the same</td><td> </td><td class="right">   this message's generation, then a 200 response would contain the same</td><td class="lineno" valign="top"></td></tr>
608      <tr><td class="lineno" valign="top"></td><td class="left">   representation that is enclosed as payload in this message.</td><td> </td><td class="right">   representation that is enclosed as payload in this message.</td><td class="lineno" valign="top"></td></tr>
609      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
610      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Location = absolute-URI / partial-URI</td><td> </td><td class="right">     Content-Location = absolute-URI / partial-URI</td><td class="lineno" valign="top"></td></tr>
611      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
612      <tr><td class="lineno" valign="top"></td><td class="left">   The Content-Location value is not a replacement for the effective</td><td> </td><td class="right">   The Content-Location value is not a replacement for the effective</td><td class="lineno" valign="top"></td></tr>
613      <tr><td><a name="diff0049" /></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="lblock">   Request URI (Section <span class="delete">4.3</span> of [Part1]).  It is representation metadata.</td><td> </td><td class="rblock">   Request URI (Section <span class="insert">5.5</span> of [Part1]).  It is representation metadata.</td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="left">   It has the same syntax and semantics as the header field of the same</td><td> </td><td class="right">   It has the same syntax and semantics as the header field of the same</td><td class="lineno" valign="top"></td></tr>
616      <tr><td class="lineno" valign="top"></td><td class="left">   name defined for MIME body parts in Section 4 of [RFC2557].  However,</td><td> </td><td class="right">   name defined for MIME body parts in Section 4 of [RFC2557].  However,</td><td class="lineno" valign="top"></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="left">   its appearance in an HTTP message has some special implications for</td><td> </td><td class="right">   its appearance in an HTTP message has some special implications for</td><td class="lineno" valign="top"></td></tr>
618      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP recipients.</td><td> </td><td class="right">   HTTP recipients.</td><td class="lineno" valign="top"></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="left">   If Content-Location is included in a response message and its value</td><td> </td><td class="right">   If Content-Location is included in a response message and its value</td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="left">   is the same as the effective request URI, then the response payload</td><td> </td><td class="right">   is the same as the effective request URI, then the response payload</td><td class="lineno" valign="top"></td></tr>
622      <tr><td><a name="diff0050" /></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="lblock">   SHOULD be considered <span class="delete">the</span> current representation of that resource.</td><td> </td><td class="rblock">   SHOULD be considered <span class="insert">a</span> current representation of that resource.  For</td><td class="lineno" valign="top"></td></tr>
624      <tr><td class="lineno" valign="top"></td><td class="lblock">   For a GET or HEAD request, this is the same as the default semantics</td><td> </td><td class="rblock">   a GET or HEAD request, this is the same as the default semantics when</td><td class="lineno" valign="top"></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="lblock">   when no Content-Location is provided by the server.  For a <span class="delete">state-</span></td><td> </td><td class="rblock">   no Content-Location is provided by the server.  For a <span class="insert">state-changing</span></td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   changing</span> request like PUT or POST, it implies that the server's</td><td> </td><td class="rblock">   request like PUT or POST, it implies that the server's response</td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="lblock">   response contains the new representation of that resource, thereby</td><td> </td><td class="rblock">   contains the new representation of that resource, thereby</td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno" valign="top"></td><td class="left">   distinguishing it from representations that might only report about</td><td> </td><td class="right">   distinguishing it from representations that might only report about</td><td class="lineno" valign="top"></td></tr>
629      <tr><td class="lineno" valign="top"></td><td class="left">   the action (e.g., "It worked!").  This allows authoring applications</td><td> </td><td class="right">   the action (e.g., "It worked!").  This allows authoring applications</td><td class="lineno" valign="top"></td></tr>
630      <tr><td class="lineno" valign="top"></td><td class="left">   to update their local copies without the need for a subsequent GET</td><td> </td><td class="right">   to update their local copies without the need for a subsequent GET</td><td class="lineno" valign="top"></td></tr>
631      <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>
632      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
633      <tr><td class="lineno" valign="top"></td><td class="left">   If Content-Location is included in a response message and its value</td><td> </td><td class="right">   If Content-Location is included in a response message and its value</td><td class="lineno" valign="top"></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="left">   differs from the effective request URI, then the origin server is</td><td> </td><td class="right">   differs from the effective request URI, then the origin server is</td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left">   informing recipients that this representation has its own, presumably</td><td> </td><td class="right">   informing recipients that this representation has its own, presumably</td><td class="lineno" valign="top"></td></tr>
636      <tr><td class="lineno" valign="top"></td><td class="left">   more specific, identifier.  For a GET or HEAD request, this is an</td><td> </td><td class="right">   more specific, identifier.  For a GET or HEAD request, this is an</td><td class="lineno" valign="top"></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="left">   indication that the effective request URI identifies a resource that</td><td> </td><td class="right">   indication that the effective request URI identifies a resource that</td><td class="lineno" valign="top"></td></tr>
638      <tr><td><a name="diff0051" /></td></tr>
639      <tr><td class="lineno" valign="top"></td><td class="lblock">   is subject to content negotiation and the <span class="delete">representation selected</span> for</td><td> </td><td class="rblock">   is subject to content negotiation and the <span class="insert">selected representation</span> for</td><td class="lineno" valign="top"></td></tr>
640      <tr><td class="lineno" valign="top"></td><td class="left">   this response can also be found at the identified URI.  For other</td><td> </td><td class="right">   this response can also be found at the identified URI.  For other</td><td class="lineno" valign="top"></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="left">   methods, such a Content-Location indicates that this representation</td><td> </td><td class="right">   methods, such a Content-Location indicates that this representation</td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="left">   contains a report on the action's status and the same report is</td><td> </td><td class="right">   contains a report on the action's status and the same report is</td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno" valign="top"></td><td class="left">   available (for future access with GET) at the given URI.  For</td><td> </td><td class="right">   available (for future access with GET) at the given URI.  For</td><td class="lineno" valign="top"></td></tr>
644      <tr><td class="lineno" valign="top"></td><td class="left">   example, a purchase transaction made via a POST request might include</td><td> </td><td class="right">   example, a purchase transaction made via a POST request might include</td><td class="lineno" valign="top"></td></tr>
645      <tr><td class="lineno" valign="top"></td><td class="left">   a receipt document as the payload of the 200 response; the Content-</td><td> </td><td class="right">   a receipt document as the payload of the 200 response; the Content-</td><td class="lineno" valign="top"></td></tr>
646      <tr><td class="lineno" valign="top"></td><td class="left">   Location value provides an identifier for retrieving a copy of that</td><td> </td><td class="right">   Location value provides an identifier for retrieving a copy of that</td><td class="lineno" valign="top"></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left">   same receipt in the future.</td><td> </td><td class="right">   same receipt in the future.</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">   If Content-Location is included in a request message, then it MAY be</td><td> </td><td class="right">   If Content-Location is included in a request message, then it MAY be</td><td class="lineno" valign="top"></td></tr>
650      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
651      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 26, line 7</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 26, line 31</em></th><td></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">7.2.  Content Coding Registry</td><td> </td><td class="right">7.2.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
655      <tr><td class="lineno" valign="top"></td><td class="left">   The registration procedure for HTTP Content Codings is now defined by</td><td> </td><td class="right">   The registration procedure for HTTP Content Codings is now defined by</td><td class="lineno" valign="top"></td></tr>
656      <tr><td class="lineno" valign="top"></td><td class="left">   Section 2.2.1 of this document.</td><td> </td><td class="right">   Section 2.2.1 of this document.</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">   The HTTP Content Codings Registry located at</td><td> </td><td class="right">   The HTTP Content Codings Registry located at</td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt; shall be updated</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt; shall be updated</td><td class="lineno" valign="top"></td></tr>
660      <tr><td class="lineno" valign="top"></td><td class="left">   with the registration below:</td><td> </td><td class="right">   with the registration below:</td><td class="lineno" valign="top"></td></tr>
661      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
662      <tr><td><a name="diff0052" /></td></tr>
663      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+----------+-----------------------------------------+--------------+</span></td><td> </td><td class="rblock">   <span class="insert">+----------+------------------------------------------+-------------+</span></td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Name     | Description                             | Reference    |</td><td> </td><td class="rblock">   | Name     | Description                              | Reference   |</td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+----------+-----------------------------------------+--------------+</span></td><td> </td><td class="rblock">   <span class="insert">+----------+------------------------------------------+-------------+</span></td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="lblock">   | compress | UNIX "compress" program method          | Section      |</td><td> </td><td class="rblock">   | compress | UNIX "compress" program method           | Section     |</td><td class="lineno" valign="top"></td></tr>
667      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | <span class="delete">5.1.2.1</span> of   |</td><td> </td><td class="rblock">   |          |                                          | <span class="insert">4.2.1</span> of    |</td><td class="lineno" valign="top"></td></tr>
668      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | [Part1]      |</td><td> </td><td class="rblock">   |          |                                          | [Part1]     |</td><td class="lineno" valign="top"></td></tr>
669      <tr><td class="lineno" valign="top"></td><td class="lblock">   | deflate  | "deflate" compression mechanism         | Section      |</td><td> </td><td class="rblock">   | deflate  | "deflate" compression mechanism          | Section     |</td><td class="lineno" valign="top"></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          | ([RFC1951]) used inside the "zlib" data | <span class="delete">5.1.2.2</span> of   |</td><td> </td><td class="rblock">   |          | ([RFC1951]) used inside the "zlib" data  | <span class="insert">4.2.2</span> of    |</td><td class="lineno" valign="top"></td></tr>
671      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          | format ([RFC1950])                      | [Part1]      |</td><td> </td><td class="rblock">   |          | format ([RFC1950])                       | [Part1]     |</td><td class="lineno" valign="top"></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="lblock">   | gzip     | Same as GNU zip [RFC1952]               | Section      |</td><td> </td><td class="rblock">   | gzip     | Same as GNU zip [RFC1952]                | Section     |</td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | <span class="delete">5.1.2.3</span> of   |</td><td> </td><td class="rblock">   |          |                                          | <span class="insert">4.2.3</span> of    |</td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          |                                         | [Part1]      |</td><td> </td><td class="rblock">   |          |                                          | [Part1]     |</td><td class="lineno" valign="top"></td></tr>
675      <tr><td class="lineno" valign="top"></td><td class="lblock">   | identity | reserved (synonym for "no encoding" in  | Section 6.3  |</td><td> </td><td class="rblock">   | identity | reserved (synonym for "no encoding" in   | Section 6.3 |</td><td class="lineno" valign="top"></td></tr>
676      <tr><td class="lineno" valign="top"></td><td class="lblock">   |          | Accept-Encoding header field)           |              |</td><td> </td><td class="rblock">   |          | Accept-Encoding header field)            |             |</td><td class="lineno" valign="top"></td></tr>
677      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+----------+-----------------------------------------+--------------+</span></td><td> </td><td class="rblock">   <span class="insert">+----------+------------------------------------------+-------------+</span></td><td class="lineno" valign="top"></td></tr>
678      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
679      <tr><td class="lineno" valign="top"></td><td class="left">8.  Security Considerations</td><td> </td><td class="right">8.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
680      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
681      <tr><td class="lineno" valign="top"></td><td class="left">   This section is meant to inform application developers, information</td><td> </td><td class="right">   This section is meant to inform application developers, information</td><td class="lineno" valign="top"></td></tr>
682      <tr><td class="lineno" valign="top"></td><td class="left">   providers, and users of the security limitations in HTTP/1.1 as</td><td> </td><td class="right">   providers, and users of the security limitations in HTTP/1.1 as</td><td class="lineno" valign="top"></td></tr>
683      <tr><td class="lineno" valign="top"></td><td class="left">   described by this document.  The discussion does not include</td><td> </td><td class="right">   described by this document.  The discussion does not include</td><td class="lineno" valign="top"></td></tr>
684      <tr><td class="lineno" valign="top"></td><td class="left">   definitive solutions to the problems revealed, though it does make</td><td> </td><td class="right">   definitive solutions to the problems revealed, though it does make</td><td class="lineno" valign="top"></td></tr>
685      <tr><td class="lineno" valign="top"></td><td class="left">   some suggestions for reducing security risks.</td><td> </td><td class="right">   some suggestions for reducing security risks.</td><td class="lineno" valign="top"></td></tr>
686      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
687      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Privacy Issues Connected to Accept Header Fields</td><td> </td><td class="right">8.1.  Privacy Issues Connected to Accept Header Fields</td><td class="lineno" valign="top"></td></tr>
688      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
689      <tr><td><a name="diff0053" /></td></tr>
690      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept header<span class="delete">s</span> fields can reveal information about the user to all</td><td> </td><td class="rblock">   Accept header fields can reveal information about the user to all</td><td class="lineno" valign="top"></td></tr>
691      <tr><td class="lineno" valign="top"></td><td class="left">   servers which are accessed.  The Accept-Language header field in</td><td> </td><td class="right">   servers which are accessed.  The Accept-Language header field in</td><td class="lineno" valign="top"></td></tr>
692      <tr><td class="lineno" valign="top"></td><td class="left">   particular can reveal information the user would consider to be of a</td><td> </td><td class="right">   particular can reveal information the user would consider to be of a</td><td class="lineno" valign="top"></td></tr>
693      <tr><td class="lineno" valign="top"></td><td class="left">   private nature, because the understanding of particular languages is</td><td> </td><td class="right">   private nature, because the understanding of particular languages is</td><td class="lineno" valign="top"></td></tr>
694      <tr><td class="lineno" valign="top"></td><td class="left">   often strongly correlated to the membership of a particular ethnic</td><td> </td><td class="right">   often strongly correlated to the membership of a particular ethnic</td><td class="lineno" valign="top"></td></tr>
695      <tr><td class="lineno" valign="top"></td><td class="left">   group.  User agents which offer the option to configure the contents</td><td> </td><td class="right">   group.  User agents which offer the option to configure the contents</td><td class="lineno" valign="top"></td></tr>
696      <tr><td class="lineno" valign="top"></td><td class="left">   of an Accept-Language header field to be sent in every request are</td><td> </td><td class="right">   of an Accept-Language header field to be sent in every request are</td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="left">   strongly encouraged to let the configuration process include a</td><td> </td><td class="right">   strongly encouraged to let the configuration process include a</td><td class="lineno" valign="top"></td></tr>
698      <tr><td class="lineno" valign="top"></td><td class="left">   message which makes the user aware of the loss of privacy involved.</td><td> </td><td class="right">   message which makes the user aware of the loss of privacy involved.</td><td class="lineno" valign="top"></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
700      <tr><td class="lineno" valign="top"></td><td class="left">   An approach that limits the loss of privacy would be for a user agent</td><td> </td><td class="right">   An approach that limits the loss of privacy would be for a user agent</td><td class="lineno" valign="top"></td></tr>
701      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
702      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 27, line 20</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 27, line 43</em></th><td></td></tr>
703      <tr><td class="lineno" valign="top"></td><td class="left">   identifier.  In environments where proxies are used to enhance</td><td> </td><td class="right">   identifier.  In environments where proxies are used to enhance</td><td class="lineno" valign="top"></td></tr>
704      <tr><td class="lineno" valign="top"></td><td class="left">   privacy, user agents ought to be conservative in offering accept</td><td> </td><td class="right">   privacy, user agents ought to be conservative in offering accept</td><td class="lineno" valign="top"></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="left">   header configuration options to end users.  As an extreme privacy</td><td> </td><td class="right">   header configuration options to end users.  As an extreme privacy</td><td class="lineno" valign="top"></td></tr>
706      <tr><td class="lineno" valign="top"></td><td class="left">   measure, proxies could filter the accept header fields in relayed</td><td> </td><td class="right">   measure, proxies could filter the accept header fields in relayed</td><td class="lineno" valign="top"></td></tr>
707      <tr><td class="lineno" valign="top"></td><td class="left">   requests.  General purpose user agents which provide a high degree of</td><td> </td><td class="right">   requests.  General purpose user agents which provide a high degree of</td><td class="lineno" valign="top"></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="left">   header configurability SHOULD warn users about the loss of privacy</td><td> </td><td class="right">   header configurability SHOULD warn users about the loss of privacy</td><td class="lineno" valign="top"></td></tr>
709      <tr><td class="lineno" valign="top"></td><td class="left">   which can be involved.</td><td> </td><td class="right">   which can be involved.</td><td class="lineno" valign="top"></td></tr>
710      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
711      <tr><td class="lineno" valign="top"></td><td class="left">9.  Acknowledgments</td><td> </td><td class="right">9.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
712      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
713      <tr><td><a name="diff0054" /></td></tr>
714      <tr><td class="lineno" valign="top"></td><td class="lblock">   See Section <span class="delete">11</span> of [Part1].</td><td> </td><td class="rblock">   See Section <span class="insert">9</span> of [Part1].</td><td class="lineno" valign="top"></td></tr>
715      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
716      <tr><td class="lineno" valign="top"></td><td class="left">10.  References</td><td> </td><td class="right">10.  References</td><td class="lineno" valign="top"></td></tr>
717      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
718      <tr><td class="lineno" valign="top"></td><td class="left">10.1.  Normative References</td><td> </td><td class="right">10.1.  Normative References</td><td class="lineno" valign="top"></td></tr>
719      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
720      <tr><td><a name="diff0055" /></td></tr>
721      <tr><td class="lineno" valign="top"></td><td class="lblock">   [Part1]    Fielding, R., Ed., <span class="delete">Gettys, J., Mogul, J., Frystyk, H.,</span></td><td> </td><td class="rblock">   [Part1]    Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
722      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              Masinter, L., Leach, P., Berners-Lee, T.,</span> Lafon, Y., Ed.,</td><td> </td><td class="rblock">              "HTTP/1.1, part 1: URIs, Connections, and Message</td><td class="lineno" valign="top"></td></tr>
723      <tr><td class="lineno" valign="top"></td><td class="lblock">              and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections,</td><td> </td><td class="rblock">              Parsing", <span class="insert">draft-ietf-httpbis-p1-messaging-19</span> (work in</td><td class="lineno" valign="top"></td></tr>
724      <tr><td class="lineno" valign="top"></td><td class="lblock">              and Message Parsing", <span class="delete">draft-ietf-httpbis-p1-messaging-18</span></td><td> </td><td class="rblock">              progress), <span class="insert">March</span> 2012.</td><td class="lineno" valign="top"></td></tr>
725      <tr><td class="lineno" valign="top"></td><td class="lblock">              (work in progress), <span class="delete">January</span> 2012.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
726      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
727      <tr><td><a name="diff0056" /></td></tr>
728      <tr><td class="lineno" valign="top"></td><td class="lblock">   [Part2]    Fielding, R., Ed., <span class="delete">Gettys, J., Mogul, J., Frystyk, H.,</span></td><td> </td><td class="rblock">   [Part2]    Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
729      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              Masinter, L., Leach, P., Berners-Lee, T.,</span> Lafon, Y., Ed.,</td><td> </td><td class="rblock">              "HTTP/1.1, part 2: Message Semantics",</td><td class="lineno" valign="top"></td></tr>
730      <tr><td class="lineno" valign="top"></td><td class="lblock">              and J. Reschke, Ed., "HTTP/1.1, part 2: Message</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p2-semantics-19</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
731      <tr><td class="lineno" valign="top"></td><td class="lblock">              Semantics", <span class="delete">draft-ietf-httpbis-p2-semantics-18</span> (work in</td><td> </td><td class="rblock">              <span class="insert">March</span> 2012.</td><td class="lineno" valign="top"></td></tr>
732      <tr><td class="lineno" valign="top"></td><td class="lblock">              progress), <span class="delete">January</span> 2012.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
733      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
734      <tr><td><a name="diff0057" /></td></tr>
735      <tr><td class="lineno" valign="top"></td><td class="lblock">   [Part4]    Fielding, R., Ed., <span class="delete">Gettys, J., Mogul, J., Frystyk, H.,</span></td><td> </td><td class="rblock">   [Part4]    Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
736      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              Masinter, L., Leach, P., Berners-Lee, T.,</span> Lafon, Y., Ed.,</td><td> </td><td class="rblock">              "HTTP/1.1, part 4: Conditional Requests",</td><td class="lineno" valign="top"></td></tr>
737      <tr><td class="lineno" valign="top"></td><td class="lblock">              and J. Reschke, Ed., "HTTP/1.1, part 4: Conditional</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p4-conditional-19</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
738      <tr><td class="lineno" valign="top"></td><td class="lblock">              Requests", <span class="delete">draft-ietf-httpbis-p4-conditional-18</span> (work in</td><td> </td><td class="rblock">              <span class="insert">March</span> 2012.</td><td class="lineno" valign="top"></td></tr>
739      <tr><td class="lineno" valign="top"></td><td class="lblock">              progress), <span class="delete">January</span> 2012.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
740      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
741      <tr><td><a name="diff0058" /></td></tr>
742      <tr><td class="lineno" valign="top"></td><td class="lblock">   [Part5]    Fielding, R., Ed., <span class="delete">Gettys, J., Mogul, J., Frystyk, H.,</span></td><td> </td><td class="rblock">   [Part5]    Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
743      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              Masinter, L., Leach, P., Berners-Lee, T.,</span> Lafon, Y., Ed.,</td><td> </td><td class="rblock">              "HTTP/1.1, part 5: Range Requests and Partial Responses",</td><td class="lineno" valign="top"></td></tr>
744      <tr><td class="lineno" valign="top"></td><td class="lblock">              and J. Reschke, Ed., "HTTP/1.1, part 5: Range Requests and</td><td> </td><td class="rblock">              <span class="insert">draft-ietf-httpbis-p5-range-19</span> (work in progress),</td><td class="lineno" valign="top"></td></tr>
745      <tr><td class="lineno" valign="top"></td><td class="lblock">              Partial Responses", <span class="delete">draft-ietf-httpbis-p5-range-18</span> (work</td><td> </td><td class="rblock">              <span class="insert">March</span> 2012.</td><td class="lineno" valign="top"></td></tr>
746      <tr><td class="lineno" valign="top"></td><td class="lblock">              in progress), <span class="delete">January</span> 2012.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
747      <tr><td class="lineno" valign=