Changeset 2698


Ignore:
Timestamp:
May 27, 2014, 7:27:54 AM (6 years ago)
Author:
julian.reschke@…
Message:

updated AUTH48 version of RFC7234 (#553)

Location:
draft-ietf-httpbis/latest/auth48
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/rfc7234-to-be.unpg.txt

    r2683 r2698  
    650650
    651651   o  If the Expires response header field (Section 5.3) is present, use
    652       its value minus the value of the Date response header field,
     652      its value minus the value of the Date response header field, or
    653653
    654654   o  Otherwise, no explicit expiration time is present in the response.
     
    812812   explicit in-protocol directive (e.g., by a "no-store" or "no-cache"
    813813   cache directive, a "must-revalidate" cache-response-directive, or an
    814    applicable "s-maxage" or "proxy-revalidate" cache response directive;
     814   applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
    815815   see Section 5.2.2).
    816816
     
    12321232   specified number of seconds.
    12331233
    1234    This directive uses the token form of the argument syntax; e.g.,
    1235    'min-fresh=20', not 'min-fresh="20"'.  A sender SHOULD NOT generate
     1234   This directive uses the token form of the argument syntax: e.g.,
     1235   'min-fresh=20' not 'min-fresh="20"'.  A sender SHOULD NOT generate
    12361236   the quoted-string form.
    12371237
     
    14131413   not to be needed for single-entry lists).
    14141414
    1415    Note: This use of the word "private" refers only to the control of
    1416    the location in which the response can be stored; the privacy of the
    1417    message content cannot be ensured.  Also, private response directives
    1418    with field-names are often handled by caches as if an unqualified
    1419    private directive was received; i.e., the special handling for the
     1415   Note: This usage of the word "private" only controls where the
     1416   response can be stored; it cannot ensure the privacy of the message
     1417   content.  Also, private response directives with field-names are
     1418   often handled by caches as if an unqualified private directive was
     1419   received; i.e., the special handling for the qualified form is not
    14201420
    14211421
     
    14271427
    14281428
    1429    qualified form is not widely implemented.
     1429   widely implemented.
    14301430
    143114315.2.2.7.  proxy-revalidate
     
    177617767.1.  Cache Directive Registry
    17771777
    1778    The "HTTP Cache Directive Registry" defines the name space for the
    1779    cache directives.  It has been created and is now maintained at
     1778   The "Hypertext Transfer Protocol (HTTP) Cache Directive Registry"
     1779   defines the namespace for the cache directives.  It has been created
     1780   and is now maintained at
    17801781   <http://www.iana.org/assignments/http-cache-directives>.
    17811782
     
    17881789   o  Pointer to specification text
    17891790
    1790    Values to be added to this name space require IETF Review (see
     1791   Values to be added to this namespace require IETF Review (see
    17911792   [RFC5226], Section 4.1).
    17921793
     
    181018117.1.3.  Registrations
    18111812
    1812    The "HTTP Cache Directive Registry" shall be populated with the
    1813    registrations below:
     1813   The registry has been populated with the registrations below:
    18141814
    18151815
     
    184718477.2.  Warn Code Registry
    18481848
    1849    The "HTTP Warn Codes" registry defines the name space for warn codes.
    1850    It has been created and is now maintained at
    1851    <http://www.iana.org/assignments/http-warn-codes>.
     1849   The "Hypertext Transfer Protocol (HTTP) Warn Codes" registry defines
     1850   the namespace for warn codes.  It has been created and is now
     1851   maintained at <http://www.iana.org/assignments/http-warn-codes>.
    18521852
    185318537.2.1.  Procedure
     
    18611861   o  Pointer to specification text
    18621862
    1863    Values to be added to this name pace require IETF Review (see
     1863   Values to be added to this namespace require IETF Review (see
    18641864   [RFC5226], Section 4.1).
    18651865
    186618667.2.2.  Registrations
    18671867
    1868    The "HTTP Warn Codes" registry has been populated with the
    1869    registrations below:
     1868   The registry has been populated with the registrations below:
     1869
    18701870
    18711871
     
    189718977.3.  Header Field Registration
    18981898
    1899    HTTP header fields are registered within the Message Header Field
    1900    Registry maintained at
    1901    <http://www.iana.org/assignments/message-headers>.
    1902 
    1903    This document defines the following HTTP header fields, so their
    1904    associated registry entries have been updated according to the
    1905    permanent registrations below (see [BCP90]):
     1899   HTTP header fields are registered within the "Message Headers"
     1900   registry maintained at
     1901   <http://www.iana.org/assignments/message-headers/>.
     1902
     1903   This document defines the following HTTP header fields, so the
     1904   "Permanent Message Header Field Names" registry has been updated
     1905   accordingly (see [BCP90]).
    19061906
    19071907   +-------------------+----------+----------+-------------+
     
    20662066   been clarified in several ways.  In particular, it now explicitly
    20672067   allows header-specific canonicalization when processing selecting
    2068    header fields.  (Section 4.1).
     2068   header fields.  (Section 4.1)
    20692069
    20702070   Requirements regarding denial-of-service attack avoidance when
     
    21142114
    21152115   This specification introduces the Cache Directive and Warn Code
    2116    Registries, and defines considerations for new cache directives
    2117    (Sections 7.1 and 7.2).
     2116   Registries, and defines considerations for new cache directives.
     2117   (Section 7.1 and Section 7.2)
    21182118
    21192119Appendix B.  Imported ABNF
  • draft-ietf-httpbis/latest/auth48/rfc7234-to-be.xml

    r2683 r2698  
    6767  <workgroup>HTTPbis Working Group</workgroup>
    6868
    69 
    70 
    71 <keyword>HTTP, caching</keyword>
     69  <keyword>Hypertext Transfer Protocol</keyword>
     70  <keyword>HTTP</keyword>
     71  <keyword>HTTP Caching</keyword>
    7272
    7373<abstract>
     
    345345
    346346<section anchor="constructing.responses.from.caches" title="Constructing Responses from Caches">
    347 
    348347<t>
    349348   When presented with a request, a cache MUST NOT reuse a stored response,
     
    563562      <t>If the <xref target="header.expires" format="none">Expires</xref> response header field
    564563      (<xref target="header.expires"/>) is present, use its value minus the
    565       value of the Date response header field,</t>
     564      value of the Date response header field, or</t>
    566565      <t>Otherwise, no explicit expiration time is present in the response. A
    567566      heuristic freshness lifetime might be applicable; see <xref target="heuristic.freshness"/>.</t>
     
    738737   explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
    739738   directive, a "must-revalidate" cache-response-directive, or an applicable
    740    "s-maxage" or "proxy-revalidate" cache response directive; see <xref
    741    target="cache-response-directive"/>).
     739   "s-maxage" or "proxy-revalidate" cache-response-directive; see <xref target="cache-response-directive"/>).
    742740</t>
    743741<t>
     
    11861184</t>
    11871185<t>
    1188    This directive uses the token form of the argument syntax;
    1189    e.g., 'min-fresh=20', not 'min-fresh="20"'. A sender SHOULD NOT generate
     1186   This directive uses the token form of the argument syntax:
     1187   e.g., 'min-fresh=20' not 'min-fresh="20"'. A sender SHOULD NOT generate
    11901188   the quoted-string form.
    11911189</t>
     
    13931391</t>
    13941392<t>
    1395    Note: This use of the word "private" refers only to the control
    1396    of the location in which the response can be stored; the privacy of the
    1397    message content cannot be ensured. Also, private response directives with field-names are
     1393   Note: This usage of the word "private" only controls
     1394   where the response can be stored; it cannot ensure the privacy of the
     1395   message content. Also, private response directives with field-names are
    13981396   often handled by caches as if an unqualified private directive
    13991397   was received; i.e., the special handling for the qualified form is not
     
    14861484   allow the UCI community to use an otherwise private response in their
    14871485   shared cache(s) could do so by including
    1488 
    14891486</t>
    14901487<figure><artwork type="example"><![CDATA[
     
    17901787<t>
    17911788   The freshness model (<xref target="expiration.model"/>) does not
    1792    necessarily apply to history mechanisms.  That is, a history mechanism can
     1789   necessarily apply to history mechanisms. That is, a history mechanism can
    17931790   display a previous representation even if it has expired.
    17941791</t>
     
    18051802<section title="Cache Directive Registry" anchor="cache.directive.registry">
    18061803<t>
    1807    The "HTTP Cache Directive Registry" defines the name space for the
     1804   The "Hypertext Transfer Protocol (HTTP) Cache Directive Registry" defines the namespace for the
    18081805   cache directives. It has been created and is now maintained at
    18091806   &lt;http://www.iana.org/assignments/http-cache-directives&gt;.
     
    18191816</t>
    18201817<t>
    1821    Values to be added to this name space require IETF Review (see <xref target="RFC5226"/>, Section 4.1).
     1818   Values to be added to this namespace require IETF Review (see <xref target="RFC5226"/>, Section 4.1).
    18221819</t>
    18231820</section>
     
    18451842<section title="Registrations" anchor="cache.directive.registration">
    18461843<t>
    1847   The "HTTP Cache Directive Registry" shall be populated with the registrations below:
     1844  The registry has been populated with the registrations below:
    18481845</t>
    18491846
     
    19161913<section title="Warn Code Registry" anchor="warn.code.registry">
    19171914<t>
    1918    The "HTTP Warn Codes" registry defines the name space for warn codes.
     1915   The "Hypertext Transfer Protocol (HTTP) Warn Codes" registry defines the namespace for warn codes.
    19191916   It has been created and is now maintained at
    19201917   &lt;http://www.iana.org/assignments/http-warn-codes&gt;.
     
    19311928</t>
    19321929<t>
    1933    Values to be added to this name pace require IETF Review (see <xref target="RFC5226"/>, Section 4.1).
     1930   Values to be added to this namespace require IETF Review (see <xref target="RFC5226"/>, Section 4.1).
    19341931</t>
    19351932</section>
     
    19371934<section title="Registrations" anchor="warn.code.registration">
    19381935<t>
    1939   The "HTTP Warn Codes" registry has been populated with the registrations below:
     1936  The registry has been populated with the registrations below:
    19401937</t>
    19411938
     
    19861983<section title="Header Field Registration" anchor="header.field.registration">
    19871984<t>
    1988    HTTP header fields are registered within the Message Header Field Registry
     1985   HTTP header fields are registered within the "Message Headers" registry
    19891986   maintained at
    1990    &lt;http://www.iana.org/assignments/message-headers&gt;.
    1991 </t>
    1992 <t>
    1993    This document defines the following HTTP header fields, so their
    1994    associated registry entries have been updated according to the permanent
    1995    registrations below (see <xref target="BCP90"/>):
     1987   &lt;http://www.iana.org/assignments/message-headers/&gt;.
     1988</t>
     1989<t>
     1990   This document defines the following HTTP header fields, so the
     1991   "Permanent Message Header Field Names" registry has been updated
     1992   accordingly (see <xref target="BCP90"/>).
    19961993</t>
    19971994
     
    20472044   More general security considerations are addressed in HTTP messaging
    20482045   <xref target="RFC7230"/> and semantics <xref target="RFC7231"/>.
    2049 
    20502046</t>
    20512047<t>
     
    23782374  clarified in several ways. In particular, it now explicitly allows
    23792375  header-specific canonicalization when processing selecting header fields.
    2380   (<xref target="caching.negotiated.responses"/>).
     2376  (<xref target="caching.negotiated.responses"/>)
    23812377</t>
    23822378<t>
     
    23982394  The "no-store" request directive doesn't apply to responses; i.e.,
    23992395  a cache can satisfy a request with no-store on it and does not invalidate
    2400   it. (<xref target="cache-request-directive.no-store"/>)
     2396  it.
     2397  (<xref target="cache-request-directive.no-store"/>)
    24012398</t>
    24022399<t>
     
    24302427<t>
    24312428  This specification introduces the Cache Directive and Warn Code Registries,
    2432   and defines considerations for new cache directives
    2433   (Sections <xref target="cache.directive.registry" format="counter"/> and <xref target="warn.code.registry" format="counter"/>).
     2429  and defines considerations for new cache directives.
     2430  (<xref target="cache.directive.registry"/> and <xref target="warn.code.registry"/>)
    24342431</t>
    24352432</section>
     
    25302527</section>
    25312528
    2532 
    2533   </back>
     2529</back>
    25342530</rfc>
  • draft-ietf-httpbis/latest/auth48/rfc7234.abdiff.txt

    r2691 r2698  
    101101
    102102
    103 Section 4.2.1., paragraph 4:
    104 OLD:
    105 
    106     o  If the Expires response header field (Section 5.3) is present, use
    107        its value minus the value of the Date response header field, or
    108 
    109 NEW:
    110 
    111     o  If the Expires response header field (Section 5.3) is present, use
    112        its value minus the value of the Date response header field,
    113 
    114 
    115 Section 4.2.4., paragraph 2:
    116 OLD:
    117 
    118     A cache MUST NOT generate a stale response if it is prohibited by an
    119     explicit in-protocol directive (e.g., by a "no-store" or "no-cache"
    120     cache directive, a "must-revalidate" cache-response-directive, or an
    121     applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
    122     see Section 5.2.2).
    123 
    124 NEW:
    125 
    126     A cache MUST NOT generate a stale response if it is prohibited by an
    127     explicit in-protocol directive (e.g., by a "no-store" or "no-cache"
    128     cache directive, a "must-revalidate" cache-response-directive, or an
    129     applicable "s-maxage" or "proxy-revalidate" cache response directive;
    130     see Section 5.2.2).
    131 
    132 
    133 Section 5.2.1.3., paragraph 4:
    134 OLD:
    135 
    136     This directive uses the token form of the argument syntax: e.g.,
    137     'min-fresh=20' not 'min-fresh="20"'.  A sender SHOULD NOT generate
    138     the quoted-string form.
    139 
    140 NEW:
    141 
    142     This directive uses the token form of the argument syntax; e.g.,
    143     'min-fresh=20', not 'min-fresh="20"'.  A sender SHOULD NOT generate
    144     the quoted-string form.
    145 
    146 
    147 Section 5.2.2.6., paragraph 7:
    148 OLD:
    149 
    150     Note: This usage of the word "private" only controls where the
    151     response can be stored; it cannot ensure the privacy of the message
    152     content.  Also, private response directives with field-names are
    153     often handled by caches as if an unqualified private directive was
    154     received; i.e., the special handling for the qualified form is not
    155     widely implemented.
    156 
    157 NEW:
    158 
    159     Note: This use of the word "private" refers only to the control of
    160     the location in which the response can be stored; the privacy of the
    161     message content cannot be ensured.  Also, private response directives
    162     with field-names are often handled by caches as if an unqualified
    163     private directive was received; i.e., the special handling for the
    164     qualified form is not widely implemented.
    165 
    166 
    167 Section 7.1., paragraph 1:
    168 OLD:
    169 
    170     The "Hypertext Transfer Protocol (HTTP) Cache Directive Registry"
    171     defines the namespace for the cache directives.  It has been created
    172     and is now maintained at
    173     <http://www.iana.org/assignments/http-cache-directives>.
    174 
    175 NEW:
    176 
    177     The "HTTP Cache Directive Registry" defines the name space for the
    178     cache directives.  It has been created and is now maintained at
    179     <http://www.iana.org/assignments/http-cache-directives>.
    180 
    181 
    182 Section 7.1.3., paragraph 1:
    183 OLD:
    184 
    185     The registry has been populated with the registrations below:
    186 
    187 NEW:
    188 
    189     The "HTTP Cache Directive Registry" shall be populated with the
    190     registrations below:
    191 
    192 
    193 Section 7.2., paragraph 1:
    194 OLD:
    195 
    196     The "Hypertext Transfer Protocol (HTTP) Warn Codes" registry defines
    197     the namespace for warn codes.  It has been created and is now
    198     maintained at <http://www.iana.org/assignments/http-warn-codes>.
    199 
    200 NEW:
    201 
    202     The "HTTP Warn Codes" registry defines the name space for warn codes.
    203     It has been created and is now maintained at
    204     <http://www.iana.org/assignments/http-warn-codes>.
    205 
    206 
    207 Section 7.2.1., paragraph 5:
    208 OLD:
    209 
    210     Values to be added to this namespace require IETF Review (see
    211     [RFC5226], Section 4.1).
    212 
    213 NEW:
    214 
    215     Values to be added to this name pace require IETF Review (see
    216     [RFC5226], Section 4.1).
    217 
    218 
    219 Section 7.2.2., paragraph 1:
    220 OLD:
    221 
    222     The registry has been populated with the registrations below:
    223 
    224 NEW:
    225 
    226     The "HTTP Warn Codes" registry has been populated with the
    227     registrations below:
    228 
    229 
    230 Section 7.3., paragraph 1:
    231 OLD:
    232 
    233     HTTP header fields are registered within the "Message Headers"
    234     registry maintained at
    235     <http://www.iana.org/assignments/message-headers/>.
    236 
    237 NEW:
    238 
    239     HTTP header fields are registered within the Message Header Field
    240     Registry maintained at
    241     <http://www.iana.org/assignments/message-headers>.
    242 
    243 
    244 Section 7.3., paragraph 2:
    245 OLD:
    246 
    247     This document defines the following HTTP header fields, so the
    248     "Permanent Message Header Field Names" registry has been updated
    249     accordingly (see [BCP90]).
    250 
    251 NEW:
    252 
    253     This document defines the following HTTP header fields, so their
    254     associated registry entries have been updated according to the
    255     permanent registrations below (see [BCP90]):
    256 
    257 
    258103Section 10.1., paragraph 3:
    259104OLD:
     
    352197    (Section 4.2.3)
    353198
    354 
    355 Appendix A., paragraph 5:
    356 OLD:
    357 
    358     The algorithm for selecting a cached negotiated response to use has
    359     been clarified in several ways.  In particular, it now explicitly
    360     allows header-specific canonicalization when processing selecting
    361     header fields.  (Section 4.1)
    362 
    363 NEW:
    364 
    365     The algorithm for selecting a cached negotiated response to use has
    366     been clarified in several ways.  In particular, it now explicitly
    367     allows header-specific canonicalization when processing selecting
    368     header fields.  (Section 4.1).
    369 
    370 
    371 Appendix A., paragraph 15:
    372 OLD:
    373 
    374     This specification introduces the Cache Directive and Warn Code
    375     Registries, and defines considerations for new cache directives.
    376     (Section 7.1 and Section 7.2)
    377 
    378 NEW:
    379 
    380     This specification introduces the Cache Directive and Warn Code
    381     Registries, and defines considerations for new cache directives
    382     (Sections 7.1 and 7.2).
    383 
  • draft-ietf-httpbis/latest/auth48/rfc7234.diff.html

    r2691 r2698  
    105105      <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>
    106106      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    107       <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 12, line 26</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 12, line 26</em></th><td></td></tr>
    108       <tr><td class="lineno" valign="top"></td><td class="left">   freshness_lifetime) of a response by using the first match of the</td><td> </td><td class="right">   freshness_lifetime) of a response by using the first match of the</td><td class="lineno" valign="top"></td></tr>
    109       <tr><td class="lineno" valign="top"></td><td class="left">   following:</td><td> </td><td class="right">   following:</td><td class="lineno" valign="top"></td></tr>
    110       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    111       <tr><td class="lineno" valign="top"></td><td class="left">   o  If the cache is shared and the s-maxage response directive</td><td> </td><td class="right">   o  If the cache is shared and the s-maxage response directive</td><td class="lineno" valign="top"></td></tr>
    112       <tr><td class="lineno" valign="top"></td><td class="left">      (Section 5.2.2.9) is present, use its value, or</td><td> </td><td class="right">      (Section 5.2.2.9) is present, use its value, or</td><td class="lineno" valign="top"></td></tr>
    113       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    114       <tr><td class="lineno" valign="top"></td><td class="left">   o  If the max-age response directive (Section 5.2.2.8) is present,</td><td> </td><td class="right">   o  If the max-age response directive (Section 5.2.2.8) is present,</td><td class="lineno" valign="top"></td></tr>
    115       <tr><td class="lineno" valign="top"></td><td class="left">      use its value, or</td><td> </td><td class="right">      use its value, or</td><td class="lineno" valign="top"></td></tr>
    116       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    117       <tr><td class="lineno" valign="top"></td><td class="left">   o  If the Expires response header field (Section 5.3) is present, use</td><td> </td><td class="right">   o  If the Expires response header field (Section 5.3) is present, use</td><td class="lineno" valign="top"></td></tr>
    118       <tr><td><a name="diff0008" /></td></tr>
    119       <tr><td class="lineno" valign="top"></td><td class="lblock">      its value minus the value of the Date response header field,<span class="delete"> or</span></td><td> </td><td class="rblock">      its value minus the value of the Date response header field,</td><td class="lineno" valign="top"></td></tr>
    120       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    121       <tr><td class="lineno" valign="top"></td><td class="left">   o  Otherwise, no explicit expiration time is present in the response.</td><td> </td><td class="right">   o  Otherwise, no explicit expiration time is present in the response.</td><td class="lineno" valign="top"></td></tr>
    122       <tr><td class="lineno" valign="top"></td><td class="left">      A heuristic freshness lifetime might be applicable; see</td><td> </td><td class="right">      A heuristic freshness lifetime might be applicable; see</td><td class="lineno" valign="top"></td></tr>
    123       <tr><td class="lineno" valign="top"></td><td class="left">      Section 4.2.2.</td><td> </td><td class="right">      Section 4.2.2.</td><td class="lineno" valign="top"></td></tr>
    124       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    125       <tr><td class="lineno" valign="top"></td><td class="left">   Note that this calculation is not vulnerable to clock skew, since all</td><td> </td><td class="right">   Note that this calculation is not vulnerable to clock skew, since all</td><td class="lineno" valign="top"></td></tr>
    126       <tr><td class="lineno" valign="top"></td><td class="left">   of the information comes from the origin server.</td><td> </td><td class="right">   of the information comes from the origin server.</td><td class="lineno" valign="top"></td></tr>
    127       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    128       <tr><td class="lineno" valign="top"></td><td class="left">   When there is more than one value present for a given directive</td><td> </td><td class="right">   When there is more than one value present for a given directive</td><td class="lineno" valign="top"></td></tr>
    129       <tr><td class="lineno" valign="top"></td><td class="left">   (e.g., two Expires header fields, multiple Cache-Control: max-age</td><td> </td><td class="right">   (e.g., two Expires header fields, multiple Cache-Control: max-age</td><td class="lineno" valign="top"></td></tr>
    130       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    131       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 15, line 17</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 15, line 17</em></th><td></td></tr>
    132       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    133       <tr><td class="lineno" valign="top"></td><td class="left">4.2.4.  Serving Stale Responses</td><td> </td><td class="right">4.2.4.  Serving Stale Responses</td><td class="lineno" valign="top"></td></tr>
    134       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    135       <tr><td class="lineno" valign="top"></td><td class="left">   A "stale" response is one that either has explicit expiry information</td><td> </td><td class="right">   A "stale" response is one that either has explicit expiry information</td><td class="lineno" valign="top"></td></tr>
    136       <tr><td class="lineno" valign="top"></td><td class="left">   or is allowed to have heuristic expiry calculated, but is not fresh</td><td> </td><td class="right">   or is allowed to have heuristic expiry calculated, but is not fresh</td><td class="lineno" valign="top"></td></tr>
    137       <tr><td class="lineno" valign="top"></td><td class="left">   according to the calculations in Section 4.2.</td><td> </td><td class="right">   according to the calculations in Section 4.2.</td><td class="lineno" valign="top"></td></tr>
    138       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    139       <tr><td class="lineno" valign="top"></td><td class="left">   A cache MUST NOT generate a stale response if it is prohibited by an</td><td> </td><td class="right">   A cache MUST NOT generate a stale response if it is prohibited by an</td><td class="lineno" valign="top"></td></tr>
    140       <tr><td class="lineno" valign="top"></td><td class="left">   explicit in-protocol directive (e.g., by a "no-store" or "no-cache"</td><td> </td><td class="right">   explicit in-protocol directive (e.g., by a "no-store" or "no-cache"</td><td class="lineno" valign="top"></td></tr>
    141       <tr><td class="lineno" valign="top"></td><td class="left">   cache directive, a "must-revalidate" cache-response-directive, or an</td><td> </td><td class="right">   cache directive, a "must-revalidate" cache-response-directive, or an</td><td class="lineno" valign="top"></td></tr>
    142       <tr><td><a name="diff0009" /></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="lblock">   applicable "s-maxage" or "proxy-revalidate" cache<span class="delete">-response-</span>directive;</td><td> </td><td class="rblock">   applicable "s-maxage" or "proxy-revalidate" cache<span class="insert"> response </span>directive;</td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="left">   see Section 5.2.2).</td><td> </td><td class="right">   see Section 5.2.2).</td><td class="lineno" valign="top"></td></tr>
    145       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    146       <tr><td class="lineno" valign="top"></td><td class="left">   A cache MUST NOT send stale responses unless it is disconnected</td><td> </td><td class="right">   A cache MUST NOT send stale responses unless it is disconnected</td><td class="lineno" valign="top"></td></tr>
    147       <tr><td class="lineno" valign="top"></td><td class="left">   (i.e., it cannot contact the origin server or otherwise find a</td><td> </td><td class="right">   (i.e., it cannot contact the origin server or otherwise find a</td><td class="lineno" valign="top"></td></tr>
    148       <tr><td class="lineno" valign="top"></td><td class="left">   forward path) or doing so is explicitly allowed (e.g., by the max-</td><td> </td><td class="right">   forward path) or doing so is explicitly allowed (e.g., by the max-</td><td class="lineno" valign="top"></td></tr>
    149       <tr><td class="lineno" valign="top"></td><td class="left">   stale request directive; see Section 5.2.1).</td><td> </td><td class="right">   stale request directive; see Section 5.2.1).</td><td class="lineno" valign="top"></td></tr>
    150       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    151       <tr><td class="lineno" valign="top"></td><td class="left">   A cache SHOULD generate a Warning header field with the 110 warn-code</td><td> </td><td class="right">   A cache SHOULD generate a Warning header field with the 110 warn-code</td><td class="lineno" valign="top"></td></tr>
    152       <tr><td class="lineno" valign="top"></td><td class="left">   (see Section 5.5.1) in stale responses.  Likewise, a cache SHOULD</td><td> </td><td class="right">   (see Section 5.5.1) in stale responses.  Likewise, a cache SHOULD</td><td class="lineno" valign="top"></td></tr>
    153       <tr><td class="lineno" valign="top"></td><td class="left">   generate a 112 warn-code (see Section 5.5.3) in stale responses if</td><td> </td><td class="right">   generate a 112 warn-code (see Section 5.5.3) in stale responses if</td><td class="lineno" valign="top"></td></tr>
    154       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    155       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 22, line 37</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 22, line 37</em></th><td></td></tr>
    156       <tr><td class="lineno" valign="top"></td><td class="left">   Argument syntax:</td><td> </td><td class="right">   Argument syntax:</td><td class="lineno" valign="top"></td></tr>
    157       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    158       <tr><td class="lineno" valign="top"></td><td class="left">      delta-seconds (see Section 1.2.1)</td><td> </td><td class="right">      delta-seconds (see Section 1.2.1)</td><td class="lineno" valign="top"></td></tr>
    159       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    160       <tr><td class="lineno" valign="top"></td><td class="left">   The "min-fresh" request directive indicates that the client is</td><td> </td><td class="right">   The "min-fresh" request directive indicates that the client is</td><td class="lineno" valign="top"></td></tr>
    161       <tr><td class="lineno" valign="top"></td><td class="left">   willing to accept a response whose freshness lifetime is no less than</td><td> </td><td class="right">   willing to accept a response whose freshness lifetime is no less than</td><td class="lineno" valign="top"></td></tr>
    162       <tr><td class="lineno" valign="top"></td><td class="left">   its current age plus the specified time in seconds.  That is, the</td><td> </td><td class="right">   its current age plus the specified time in seconds.  That is, the</td><td class="lineno" valign="top"></td></tr>
    163       <tr><td class="lineno" valign="top"></td><td class="left">   client wants a response that will still be fresh for at least the</td><td> </td><td class="right">   client wants a response that will still be fresh for at least the</td><td class="lineno" valign="top"></td></tr>
    164       <tr><td class="lineno" valign="top"></td><td class="left">   specified number of seconds.</td><td> </td><td class="right">   specified number of seconds.</td><td class="lineno" valign="top"></td></tr>
    165       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    166       <tr><td><a name="diff0010" /></td></tr>
    167       <tr><td class="lineno" valign="top"></td><td class="lblock">   This directive uses the token form of the argument <span class="delete">syntax:</span> e.g.,</td><td> </td><td class="rblock">   This directive uses the token form of the argument <span class="insert">syntax;</span> e.g.,</td><td class="lineno" valign="top"></td></tr>
    168       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">'min-fresh=20'</span> not 'min-fresh="20"'.  A sender SHOULD NOT generate</td><td> </td><td class="rblock">   <span class="insert">'min-fresh=20',</span> not 'min-fresh="20"'.  A sender SHOULD NOT generate</td><td class="lineno" valign="top"></td></tr>
    169       <tr><td class="lineno" valign="top"></td><td class="left">   the quoted-string form.</td><td> </td><td class="right">   the quoted-string form.</td><td class="lineno" valign="top"></td></tr>
    170       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    171       <tr><td class="lineno" valign="top"></td><td class="left">5.2.1.4.  no-cache</td><td> </td><td class="right">5.2.1.4.  no-cache</td><td class="lineno" valign="top"></td></tr>
    172       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    173       <tr><td class="lineno" valign="top"></td><td class="left">   The "no-cache" request directive indicates that a cache MUST NOT use</td><td> </td><td class="right">   The "no-cache" request directive indicates that a cache MUST NOT use</td><td class="lineno" valign="top"></td></tr>
    174       <tr><td class="lineno" valign="top"></td><td class="left">   a stored response to satisfy the request without successful</td><td> </td><td class="right">   a stored response to satisfy the request without successful</td><td class="lineno" valign="top"></td></tr>
    175       <tr><td class="lineno" valign="top"></td><td class="left">   validation on the origin server.</td><td> </td><td class="right">   validation on the origin server.</td><td class="lineno" valign="top"></td></tr>
    176       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    177       <tr><td class="lineno" valign="top"></td><td class="left">5.2.1.5.  no-store</td><td> </td><td class="right">5.2.1.5.  no-store</td><td class="lineno" valign="top"></td></tr>
    178       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    179       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    180       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 25, line 47</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 25, line 47</em></th><td></td></tr>
    181       <tr><td class="lineno" valign="top"></td><td class="left">   store the specified field-names(s), whereas it MAY store the</td><td> </td><td class="right">   store the specified field-names(s), whereas it MAY store the</td><td class="lineno" valign="top"></td></tr>
    182       <tr><td class="lineno" valign="top"></td><td class="left">   remainder of the response message.</td><td> </td><td class="right">   remainder of the response message.</td><td class="lineno" valign="top"></td></tr>
    183       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    184       <tr><td class="lineno" valign="top"></td><td class="left">   The field-names given are not limited to the set of header fields</td><td> </td><td class="right">   The field-names given are not limited to the set of header fields</td><td class="lineno" valign="top"></td></tr>
    185       <tr><td class="lineno" valign="top"></td><td class="left">   defined by this specification.  Field names are case-insensitive.</td><td> </td><td class="right">   defined by this specification.  Field names are case-insensitive.</td><td class="lineno" valign="top"></td></tr>
    186       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    187       <tr><td class="lineno" valign="top"></td><td class="left">   This directive uses the quoted-string form of the argument syntax.  A</td><td> </td><td class="right">   This directive uses the quoted-string form of the argument syntax.  A</td><td class="lineno" valign="top"></td></tr>
    188       <tr><td class="lineno" valign="top"></td><td class="left">   sender SHOULD NOT generate the token form (even if quoting appears</td><td> </td><td class="right">   sender SHOULD NOT generate the token form (even if quoting appears</td><td class="lineno" valign="top"></td></tr>
    189       <tr><td class="lineno" valign="top"></td><td class="left">   not to be needed for single-entry lists).</td><td> </td><td class="right">   not to be needed for single-entry lists).</td><td class="lineno" valign="top"></td></tr>
    190       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    191       <tr><td><a name="diff0011" /></td></tr>
    192       <tr><td class="lineno" valign="top"></td><td class="lblock">   Note: This <span class="delete">usage</span> of the word "private" only <span class="delete">controls where</span> the</td><td> </td><td class="rblock">   Note: This <span class="insert">use</span> of the word "private" <span class="insert">refers</span> only <span class="insert">to the control of</span></td><td class="lineno" valign="top"></td></tr>
    193       <tr><td class="lineno" valign="top"></td><td class="lblock">   response can be stored; <span class="delete">it cannot ensure</span> the privacy of the message</td><td> </td><td class="rblock"><span class="insert">   the location in which</span> the response can be stored; the privacy of the</td><td class="lineno" valign="top"></td></tr>
    194       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">content.</span>  Also, private response directives with field-names are</td><td> </td><td class="rblock">   message <span class="insert">content cannot be ensured.</span>  Also, private response directives</td><td class="lineno" valign="top"></td></tr>
    195       <tr><td class="lineno" valign="top"></td><td class="lblock">   often handled by caches as if an unqualified private directive was</td><td> </td><td class="rblock">   with field-names are often handled by caches as if an unqualified</td><td class="lineno" valign="top"></td></tr>
    196       <tr><td class="lineno" valign="top"></td><td class="lblock">   received; i.e., the special handling for the qualified form is not</td><td> </td><td class="rblock">   private directive was received; i.e., the special handling for the</td><td class="lineno" valign="top"></td></tr>
    197       <tr><td class="lineno" valign="top"></td><td class="lblock">   widely implemented.</td><td> </td><td class="rblock">   qualified form is not widely implemented.</td><td class="lineno" valign="top"></td></tr>
    198       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    199       <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.7.  proxy-revalidate</td><td> </td><td class="right">5.2.2.7.  proxy-revalidate</td><td class="lineno" valign="top"></td></tr>
    200       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    201       <tr><td class="lineno" valign="top"></td><td class="left">   The "proxy-revalidate" response directive has the same meaning as the</td><td> </td><td class="right">   The "proxy-revalidate" response directive has the same meaning as the</td><td class="lineno" valign="top"></td></tr>
    202       <tr><td class="lineno" valign="top"></td><td class="left">   must-revalidate response directive, except that it does not apply to</td><td> </td><td class="right">   must-revalidate response directive, except that it does not apply to</td><td class="lineno" valign="top"></td></tr>
    203       <tr><td class="lineno" valign="top"></td><td class="left">   private caches.</td><td> </td><td class="right">   private caches.</td><td class="lineno" valign="top"></td></tr>
    204       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    205       <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.8.  max-age</td><td> </td><td class="right">5.2.2.8.  max-age</td><td class="lineno" valign="top"></td></tr>
    206       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    207       <tr><td class="lineno" valign="top"></td><td class="left">   Argument syntax:</td><td> </td><td class="right">   Argument syntax:</td><td class="lineno" valign="top"></td></tr>
    208       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    209       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 32, line 11</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 32, line 11</em></th><td></td></tr>
    210       <tr><td class="lineno" valign="top"></td><td class="left">   previous representation even if it has expired.</td><td> </td><td class="right">   previous representation even if it has expired.</td><td class="lineno" valign="top"></td></tr>
    211       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    212       <tr><td class="lineno" valign="top"></td><td class="left">   This does not prohibit the history mechanism from telling the user</td><td> </td><td class="right">   This does not prohibit the history mechanism from telling the user</td><td class="lineno" valign="top"></td></tr>
    213       <tr><td class="lineno" valign="top"></td><td class="left">   that a view might be stale or from honoring cache directives (e.g.,</td><td> </td><td class="right">   that a view might be stale or from honoring cache directives (e.g.,</td><td class="lineno" valign="top"></td></tr>
    214       <tr><td class="lineno" valign="top"></td><td class="left">   Cache-Control: no-store).</td><td> </td><td class="right">   Cache-Control: no-store).</td><td class="lineno" valign="top"></td></tr>
    215       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    216       <tr><td class="lineno" valign="top"></td><td class="left">7.  IANA Considerations</td><td> </td><td class="right">7.  IANA Considerations</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">7.1.  Cache Directive Registry</td><td> </td><td class="right">7.1.  Cache Directive Registry</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><a name="diff0012" /></td></tr>
    221       <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">"Hypertext Transfer Protocol (HTTP)</span> Cache Directive Registry"</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Cache Directive Registry" defines the <span class="insert">name space</span> for the</td><td class="lineno" valign="top"></td></tr>
    222       <tr><td class="lineno" valign="top"></td><td class="lblock">   defines the <span class="delete">namespace</span> for the cache directives.  It has been created</td><td> </td><td class="rblock">   cache directives.  It has been created and is now maintained at</td><td class="lineno" valign="top"></td></tr>
    223       <tr><td class="lineno" valign="top"></td><td class="lblock">   and is now maintained at</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    224       <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-cache-directives&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-cache-directives&gt;.</td><td class="lineno" valign="top"></td></tr>
    225       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    226       <tr><td class="lineno" valign="top"></td><td class="left">7.1.1.  Procedure</td><td> </td><td class="right">7.1.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    227       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    228       <tr><td class="lineno" valign="top"></td><td class="left">   A registration MUST include the following fields:</td><td> </td><td class="right">   A registration MUST include the following fields:</td><td class="lineno" valign="top"></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">   o  Cache Directive Name</td><td> </td><td class="right">   o  Cache Directive Name</td><td class="lineno" valign="top"></td></tr>
    231       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    232       <tr><td class="lineno" valign="top"></td><td class="left">   o  Pointer to specification text</td><td> </td><td class="right">   o  Pointer to specification text</td><td class="lineno" valign="top"></td></tr>
    233       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    234       <tr><td><a name="diff0013" /></td></tr>
    235       <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this namespace require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this name<span class="insert"> </span>space require IETF Review (see</td><td class="lineno" valign="top"></td></tr>
    236       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5226], Section 4.1).</td><td> </td><td class="right">   [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr>
    237       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    238       <tr><td class="lineno" valign="top"></td><td class="left">7.1.2.  Considerations for New Cache Control Directives</td><td> </td><td class="right">7.1.2.  Considerations for New Cache Control Directives</td><td class="lineno" valign="top"></td></tr>
    239       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    240       <tr><td class="lineno" valign="top"></td><td class="left">   New extension directives ought to consider defining:</td><td> </td><td class="right">   New extension directives ought to consider defining:</td><td class="lineno" valign="top"></td></tr>
    241       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    242       <tr><td class="lineno" valign="top"></td><td class="left">   o  What it means for a directive to be specified multiple times,</td><td> </td><td class="right">   o  What it means for a directive to be specified multiple times,</td><td class="lineno" valign="top"></td></tr>
    243       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    244       <tr><td class="lineno" valign="top"></td><td class="left">   o  When the directive does not take an argument, what it means when</td><td> </td><td class="right">   o  When the directive does not take an argument, what it means when</td><td class="lineno" valign="top"></td></tr>
    245       <tr><td class="lineno" valign="top"></td><td class="left">      an argument is present,</td><td> </td><td class="right">      an argument is present,</td><td class="lineno" valign="top"></td></tr>
    246       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    247       <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 32, line 46</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 32, line 45</em></th><td></td></tr>
    248       <tr><td class="lineno" valign="top"></td><td class="left">   o  When the directive requires an argument, what it means when it is</td><td> </td><td class="right">   o  When the directive requires an argument, what it means when it is</td><td class="lineno" valign="top"></td></tr>
    249       <tr><td class="lineno" valign="top"></td><td class="left">      missing,</td><td> </td><td class="right">      missing,</td><td class="lineno" valign="top"></td></tr>
    250       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    251       <tr><td class="lineno" valign="top"></td><td class="left">   o  Whether the directive is specific to requests, responses, or able</td><td> </td><td class="right">   o  Whether the directive is specific to requests, responses, or able</td><td class="lineno" valign="top"></td></tr>
    252       <tr><td class="lineno" valign="top"></td><td class="left">      to be used in either.</td><td> </td><td class="right">      to be used in either.</td><td class="lineno" valign="top"></td></tr>
    253       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    254       <tr><td class="lineno" valign="top"></td><td class="left">   See also Section 5.2.3.</td><td> </td><td class="right">   See also Section 5.2.3.</td><td class="lineno" valign="top"></td></tr>
    255       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    256       <tr><td class="lineno" valign="top"></td><td class="left">7.1.3.  Registrations</td><td> </td><td class="right">7.1.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    257       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    258       <tr><td><a name="diff0014" /></td></tr>
    259       <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">registry has been</span> populated with the registrations below:</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Cache Directive Registry" shall be</span> populated with the</td><td class="lineno" valign="top"></td></tr>
    260       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   registrations below:</td><td class="lineno" valign="top"></td></tr>
    261       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    262       <tr><td class="lineno" valign="top"></td><td class="left">   +------------------------+----------------------------------+</td><td> </td><td class="right">   +------------------------+----------------------------------+</td><td class="lineno" valign="top"></td></tr>
    263       <tr><td class="lineno" valign="top"></td><td class="left">   | Cache Directive        | Reference                        |</td><td> </td><td class="right">   | Cache Directive        | Reference                        |</td><td class="lineno" valign="top"></td></tr>
    264       <tr><td class="lineno" valign="top"></td><td class="left">   +------------------------+----------------------------------+</td><td> </td><td class="right">   +------------------------+----------------------------------+</td><td class="lineno" valign="top"></td></tr>
    265       <tr><td class="lineno" valign="top"></td><td class="left">   | max-age                | Section 5.2.1.1, Section 5.2.2.8 |</td><td> </td><td class="right">   | max-age                | Section 5.2.1.1, Section 5.2.2.8 |</td><td class="lineno" valign="top"></td></tr>
    266       <tr><td class="lineno" valign="top"></td><td class="left">   | max-stale              | Section 5.2.1.2                  |</td><td> </td><td class="right">   | max-stale              | Section 5.2.1.2                  |</td><td class="lineno" valign="top"></td></tr>
    267       <tr><td class="lineno" valign="top"></td><td class="left">   | min-fresh              | Section 5.2.1.3                  |</td><td> </td><td class="right">   | min-fresh              | Section 5.2.1.3                  |</td><td class="lineno" valign="top"></td></tr>
    268       <tr><td class="lineno" valign="top"></td><td class="left">   | must-revalidate        | Section 5.2.2.1                  |</td><td> </td><td class="right">   | must-revalidate        | Section 5.2.2.1                  |</td><td class="lineno" valign="top"></td></tr>
    269       <tr><td class="lineno" valign="top"></td><td class="left">   | no-cache               | Section 5.2.1.4, Section 5.2.2.2 |</td><td> </td><td class="right">   | no-cache               | Section 5.2.1.4, Section 5.2.2.2 |</td><td class="lineno" valign="top"></td></tr>
    270       <tr><td class="lineno" valign="top"></td><td class="left">   | no-store               | Section 5.2.1.5, Section 5.2.2.3 |</td><td> </td><td class="right">   | no-store               | Section 5.2.1.5, Section 5.2.2.3 |</td><td class="lineno" valign="top"></td></tr>
    271       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    272       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 33, line 26</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 33, line 26</em></th><td></td></tr>
    273       <tr><td class="lineno" valign="top"></td><td class="left">   | private                | Section 5.2.2.6                  |</td><td> </td><td class="right">   | private                | Section 5.2.2.6                  |</td><td class="lineno" valign="top"></td></tr>
    274       <tr><td class="lineno" valign="top"></td><td class="left">   | proxy-revalidate       | Section 5.2.2.7                  |</td><td> </td><td class="right">   | proxy-revalidate       | Section 5.2.2.7                  |</td><td class="lineno" valign="top"></td></tr>
    275       <tr><td class="lineno" valign="top"></td><td class="left">   | public                 | Section 5.2.2.5                  |</td><td> </td><td class="right">   | public                 | Section 5.2.2.5                  |</td><td class="lineno" valign="top"></td></tr>
    276       <tr><td class="lineno" valign="top"></td><td class="left">   | s-maxage               | Section 5.2.2.9                  |</td><td> </td><td class="right">   | s-maxage               | Section 5.2.2.9                  |</td><td class="lineno" valign="top"></td></tr>
    277       <tr><td class="lineno" valign="top"></td><td class="left">   | stale-if-error         | [RFC5861], Section 4             |</td><td> </td><td class="right">   | stale-if-error         | [RFC5861], Section 4             |</td><td class="lineno" valign="top"></td></tr>
    278       <tr><td class="lineno" valign="top"></td><td class="left">   | stale-while-revalidate | [RFC5861], Section 3             |</td><td> </td><td class="right">   | stale-while-revalidate | [RFC5861], Section 3             |</td><td class="lineno" valign="top"></td></tr>
    279       <tr><td class="lineno" valign="top"></td><td class="left">   +------------------------+----------------------------------+</td><td> </td><td class="right">   +------------------------+----------------------------------+</td><td class="lineno" valign="top"></td></tr>
    280       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    281       <tr><td class="lineno" valign="top"></td><td class="left">7.2.  Warn Code Registry</td><td> </td><td class="right">7.2.  Warn Code Registry</td><td class="lineno" valign="top"></td></tr>
    282       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    283       <tr><td><a name="diff0015" /></td></tr>
    284       <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">"Hypertext Transfer Protocol (HTTP)</span> Warn Codes" registry defines</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Warn Codes" registry defines the <span class="insert">name space</span> for warn codes.</td><td class="lineno" valign="top"></td></tr>
    285       <tr><td class="lineno" valign="top"></td><td class="lblock">   the <span class="delete">namespace</span> for warn codes.  It has been created and is now</td><td> </td><td class="rblock">   It has been created and is now maintained at</td><td class="lineno" valign="top"></td></tr>
    286       <tr><td class="lineno" valign="top"></td><td class="lblock">   maintained at &lt;http://www.iana.org/assignments/http-warn-codes&gt;.</td><td> </td><td class="rblock">   &lt;http://www.iana.org/assignments/http-warn-codes&gt;.</td><td class="lineno" valign="top"></td></tr>
    287       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    288       <tr><td class="lineno" valign="top"></td><td class="left">7.2.1.  Procedure</td><td> </td><td class="right">7.2.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    289       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    290       <tr><td class="lineno" valign="top"></td><td class="left">   A registration MUST include the following fields:</td><td> </td><td class="right">   A registration MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    291       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    292       <tr><td class="lineno" valign="top"></td><td class="left">   o  Warn Code (3 digits)</td><td> </td><td class="right">   o  Warn Code (3 digits)</td><td class="lineno" valign="top"></td></tr>
    293       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    294       <tr><td class="lineno" valign="top"></td><td class="left">   o  Short Description</td><td> </td><td class="right">   o  Short Description</td><td class="lineno" valign="top"></td></tr>
    295       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    296       <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>
    297       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    298       <tr><td><a name="diff0016" /></td></tr>
    299       <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this name<span class="delete">s</span>pace require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this name<span class="insert"> </span>pace require IETF Review (see</td><td class="lineno" valign="top"></td></tr>
    300       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5226], Section 4.1).</td><td> </td><td class="right">   [RFC5226], Section 4.1).</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">7.2.2.  Registrations</td><td> </td><td class="right">7.2.2.  Registrations</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><a name="diff0017" /></td></tr>
    305       <tr><td class="lineno" valign="top"></td><td class="lblock">   The registry has been populated with the registrations below:</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Warn Codes"</span> registry has been populated with the</td><td class="lineno" valign="top"></td></tr>
    306       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   registrations below:</td><td class="lineno" valign="top"></td></tr>
    307       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    308       <tr><td class="lineno" valign="top"></td><td class="left">   +-----------+----------------------------------+---------------+</td><td> </td><td class="right">   +-----------+----------------------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    309       <tr><td class="lineno" valign="top"></td><td class="left">   | Warn Code | Short Description                | Reference     |</td><td> </td><td class="right">   | Warn Code | Short Description                | Reference     |</td><td class="lineno" valign="top"></td></tr>
    310       <tr><td class="lineno" valign="top"></td><td class="left">   +-----------+----------------------------------+---------------+</td><td> </td><td class="right">   +-----------+----------------------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    311       <tr><td class="lineno" valign="top"></td><td class="left">   | 110       | Response is Stale                | Section 5.5.1 |</td><td> </td><td class="right">   | 110       | Response is Stale                | Section 5.5.1 |</td><td class="lineno" valign="top"></td></tr>
    312       <tr><td class="lineno" valign="top"></td><td class="left">   | 111       | Revalidation Failed              | Section 5.5.2 |</td><td> </td><td class="right">   | 111       | Revalidation Failed              | Section 5.5.2 |</td><td class="lineno" valign="top"></td></tr>
    313       <tr><td class="lineno" valign="top"></td><td class="left">   | 112       | Disconnected Operation           | Section 5.5.3 |</td><td> </td><td class="right">   | 112       | Disconnected Operation           | Section 5.5.3 |</td><td class="lineno" valign="top"></td></tr>
    314       <tr><td class="lineno" valign="top"></td><td class="left">   | 113       | Heuristic Expiration             | Section 5.5.4 |</td><td> </td><td class="right">   | 113       | Heuristic Expiration             | Section 5.5.4 |</td><td class="lineno" valign="top"></td></tr>
    315       <tr><td class="lineno" valign="top"></td><td class="left">   | 199       | Miscellaneous Warning            | Section 5.5.5 |</td><td> </td><td class="right">   | 199       | Miscellaneous Warning            | Section 5.5.5 |</td><td class="lineno" valign="top"></td></tr>
    316       <tr><td class="lineno" valign="top"></td><td class="left">   | 214       | Transformation Applied           | Section 5.5.6 |</td><td> </td><td class="right">   | 214       | Transformation Applied           | Section 5.5.6 |</td><td class="lineno" valign="top"></td></tr>
    317       <tr><td class="lineno" valign="top"></td><td class="left">   | 299       | Miscellaneous Persistent Warning | Section 5.5.7 |</td><td> </td><td class="right">   | 299       | Miscellaneous Persistent Warning | Section 5.5.7 |</td><td class="lineno" valign="top"></td></tr>
    318       <tr><td class="lineno" valign="top"></td><td class="left">   +-----------+----------------------------------+---------------+</td><td> </td><td class="right">   +-----------+----------------------------------+---------------+</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">7.3.  Header Field Registration</td><td> </td><td class="right">7.3.  Header Field Registration</td><td class="lineno" valign="top"></td></tr>
    321       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    322       <tr><td><a name="diff0018" /></td></tr>
    323       <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP header fields are registered within the <span class="delete">"Message Headers"</span></td><td> </td><td class="rblock">   HTTP header fields are registered within the <span class="insert">Message Header Field</span></td><td class="lineno" valign="top"></td></tr>
    324       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   registry</span> maintained at</td><td> </td><td class="rblock"><span class="insert">   Registry</span> maintained at</td><td class="lineno" valign="top"></td></tr>
    325       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">&lt;http://www.iana.org/assignments/message-headers/&gt;.</span></td><td> </td><td class="rblock">   <span class="insert">&lt;http://www.iana.org/assignments/message-headers&gt;.</span></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="diff0019" /></td></tr>
    328       <tr><td class="lineno" valign="top"></td><td class="lblock">   This document defines the following HTTP header fields, so <span class="delete">the</span></td><td> </td><td class="rblock">   This document defines the following HTTP header fields, so <span class="insert">their</span></td><td class="lineno" valign="top"></td></tr>
    329       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   "Permanent Message Header Field Names"</span> registry <span class="delete">has</span> been updated</td><td> </td><td class="rblock"><span class="insert">   associated</span> registry <span class="insert">entries have</span> been updated <span class="insert">according to the</span></td><td class="lineno" valign="top"></td></tr>
    330       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">accordingly</span> (see <span class="delete">[BCP90]).</span></td><td> </td><td class="rblock"><span class="insert">   permanent registrations below</span> (see <span class="insert">[BCP90]):</span></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 class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+-------------+</td><td> </td><td class="right">   +-------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
    333       <tr><td class="lineno" valign="top"></td><td class="left">   | Header Field Name | Protocol | Status   | Reference   |</td><td> </td><td class="right">   | Header Field Name | Protocol | Status   | Reference   |</td><td class="lineno" valign="top"></td></tr>
    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">   | Age               | http     | standard | Section 5.1 |</td><td> </td><td class="right">   | Age               | http     | standard | Section 5.1 |</td><td class="lineno" valign="top"></td></tr>
    336       <tr><td class="lineno" valign="top"></td><td class="left">   | Cache-Control     | http     | standard | Section 5.2 |</td><td> </td><td class="right">   | Cache-Control     | http     | standard | Section 5.2 |</td><td class="lineno" valign="top"></td></tr>
    337       <tr><td class="lineno" valign="top"></td><td class="left">   | Expires           | http     | standard | Section 5.3 |</td><td> </td><td class="right">   | Expires           | http     | standard | Section 5.3 |</td><td class="lineno" valign="top"></td></tr>
    338       <tr><td class="lineno" valign="top"></td><td class="left">   | Pragma            | http     | standard | Section 5.4 |</td><td> </td><td class="right">   | Pragma            | http     | standard | Section 5.4 |</td><td class="lineno" valign="top"></td></tr>
    339       <tr><td class="lineno" valign="top"></td><td class="left">   | Warning           | http     | standard | Section 5.5 |</td><td> </td><td class="right">   | Warning           | http     | standard | Section 5.5 |</td><td class="lineno" valign="top"></td></tr>
    340       <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+-------------+</td><td> </td><td class="right">   +-------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
    341       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    342       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 35, line 48</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 35, line 48</em></th><td></td></tr>
     107      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 35, line 48</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 35, line 48</em></th><td></td></tr>
    343108      <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>
    344109      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    351116      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    352117      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
    353       <tr><td><a name="diff0020" /></td></tr>
     118      <tr><td><a name="diff0008" /></td></tr>
    354119      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    355120      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    356121      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    357122      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    358       <tr><td><a name="diff0021" /></td></tr>
     123      <tr><td><a name="diff0009" /></td></tr>
    359124      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Semantics and Content", <span class="insert">RFC 7231,</span></td><td class="lineno" valign="top"></td></tr>
    360125      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p2-semantics-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    362127      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    363128      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    364       <tr><td><a name="diff0022" /></td></tr>
     129      <tr><td><a name="diff0010" /></td></tr>
    365130      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
    366131      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
     
    369134      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
    370135      <tr><td class="lineno" valign="top"></td><td class="left">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr>
    371       <tr><td><a name="diff0023" /></td></tr>
     136      <tr><td><a name="diff0011" /></td></tr>
    372137      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    373138      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    374139      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    375140      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    376       <tr><td><a name="diff0024" /></td></tr>
     141      <tr><td><a name="diff0012" /></td></tr>
    377142      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    378143      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    388153      <tr><td class="lineno" valign="top"></td><td class="left">              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td> </td><td class="right">              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td class="lineno" valign="top"></td></tr>
    389154      <tr><td class="lineno" valign="top"></td><td class="left">              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</td><td> </td><td class="right">              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</td><td class="lineno" valign="top"></td></tr>
    390       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    391       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 37, line 22</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 37, line 16</em></th><td></td></tr>
    392       <tr><td class="lineno" valign="top"></td><td class="left">   invalid, because it's not possible to accurately guess.</td><td> </td><td class="right">   invalid, because it's not possible to accurately guess.</td><td class="lineno" valign="top"></td></tr>
    393       <tr><td class="lineno" valign="top"></td><td class="left">   (Section 4.2.3)</td><td> </td><td class="right">   (Section 4.2.3)</td><td class="lineno" valign="top"></td></tr>
    394       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    395       <tr><td class="lineno" valign="top"></td><td class="left">   The Content-Location response header field is no longer used to</td><td> </td><td class="right">   The Content-Location response header field is no longer used to</td><td class="lineno" valign="top"></td></tr>
    396       <tr><td class="lineno" valign="top"></td><td class="left">   determine the appropriate response to use when validating.</td><td> </td><td class="right">   determine the appropriate response to use when validating.</td><td class="lineno" valign="top"></td></tr>
    397       <tr><td class="lineno" valign="top"></td><td class="left">   (Section 4.3)</td><td> </td><td class="right">   (Section 4.3)</td><td class="lineno" valign="top"></td></tr>
    398       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    399       <tr><td class="lineno" valign="top"></td><td class="left">   The algorithm for selecting a cached negotiated response to use has</td><td> </td><td class="right">   The algorithm for selecting a cached negotiated response to use has</td><td class="lineno" valign="top"></td></tr>
    400       <tr><td class="lineno" valign="top"></td><td class="left">   been clarified in several ways.  In particular, it now explicitly</td><td> </td><td class="right">   been clarified in several ways.  In particular, it now explicitly</td><td class="lineno" valign="top"></td></tr>
    401       <tr><td class="lineno" valign="top"></td><td class="left">   allows header-specific canonicalization when processing selecting</td><td> </td><td class="right">   allows header-specific canonicalization when processing selecting</td><td class="lineno" valign="top"></td></tr>
    402       <tr><td><a name="diff0025" /></td></tr>
    403       <tr><td class="lineno" valign="top"></td><td class="lblock">   header fields.  (Section 4.1)</td><td> </td><td class="rblock">   header fields.  (Section 4.1)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>
    404       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    405       <tr><td class="lineno" valign="top"></td><td class="left">   Requirements regarding denial-of-service attack avoidance when</td><td> </td><td class="right">   Requirements regarding denial-of-service attack avoidance when</td><td class="lineno" valign="top"></td></tr>
    406       <tr><td class="lineno" valign="top"></td><td class="left">   performing invalidation have been clarified.  (Section 4.4)</td><td> </td><td class="right">   performing invalidation have been clarified.  (Section 4.4)</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" valign="top"></td><td class="left">   Cache invalidation only occurs when a successful response is</td><td> </td><td class="right">   Cache invalidation only occurs when a successful response is</td><td class="lineno" valign="top"></td></tr>
    409       <tr><td class="lineno" valign="top"></td><td class="left">   received.  (Section 4.4)</td><td> </td><td class="right">   received.  (Section 4.4)</td><td class="lineno" valign="top"></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">   Cache directives are explicitly defined to be case-insensitive.</td><td> </td><td class="right">   Cache directives are explicitly defined to be case-insensitive.</td><td class="lineno" valign="top"></td></tr>
    412       <tr><td class="lineno" valign="top"></td><td class="left">   Handling of multiple instances of cache directives when only one is</td><td> </td><td class="right">   Handling of multiple instances of cache directives when only one is</td><td class="lineno" valign="top"></td></tr>
    413       <tr><td class="lineno" valign="top"></td><td class="left">   expected is now defined.  (Section 5.2)</td><td> </td><td class="right">   expected is now defined.  (Section 5.2)</td><td class="lineno" valign="top"></td></tr>
    414       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    415       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 38, line 13</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 38, line 7</em></th><td></td></tr>
    416       <tr><td class="lineno" valign="top"></td><td class="left">   The Pragma header field is now only defined for backwards</td><td> </td><td class="right">   The Pragma header field is now only defined for backwards</td><td class="lineno" valign="top"></td></tr>
    417       <tr><td class="lineno" valign="top"></td><td class="left">   compatibility; future pragmas are deprecated.  (Section 5.4)</td><td> </td><td class="right">   compatibility; future pragmas are deprecated.  (Section 5.4)</td><td class="lineno" valign="top"></td></tr>
    418       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    419       <tr><td class="lineno" valign="top"></td><td class="left">   Some requirements regarding production and processing of the Warning</td><td> </td><td class="right">   Some requirements regarding production and processing of the Warning</td><td class="lineno" valign="top"></td></tr>
    420       <tr><td class="lineno" valign="top"></td><td class="left">   header fields have been relaxed, as it is not widely implemented.</td><td> </td><td class="right">   header fields have been relaxed, as it is not widely implemented.</td><td class="lineno" valign="top"></td></tr>
    421       <tr><td class="lineno" valign="top"></td><td class="left">   Furthermore, the Warning header field no longer uses RFC 2047</td><td> </td><td class="right">   Furthermore, the Warning header field no longer uses RFC 2047</td><td class="lineno" valign="top"></td></tr>
    422       <tr><td class="lineno" valign="top"></td><td class="left">   encoding, nor does it allow multiple languages, as these aspects were</td><td> </td><td class="right">   encoding, nor does it allow multiple languages, as these aspects were</td><td class="lineno" valign="top"></td></tr>
    423       <tr><td class="lineno" valign="top"></td><td class="left">   not implemented.  (Section 5.5)</td><td> </td><td class="right">   not implemented.  (Section 5.5)</td><td class="lineno" valign="top"></td></tr>
    424       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    425       <tr><td class="lineno" valign="top"></td><td class="left">   This specification introduces the Cache Directive and Warn Code</td><td> </td><td class="right">   This specification introduces the Cache Directive and Warn Code</td><td class="lineno" valign="top"></td></tr>
    426       <tr><td><a name="diff0026" /></td></tr>
    427       <tr><td class="lineno" valign="top"></td><td class="lblock">   Registries, and defines considerations for new cache <span class="delete">directives.</span></td><td> </td><td class="rblock">   Registries, and defines considerations for new cache <span class="insert">directives</span></td><td class="lineno" valign="top"></td></tr>
    428       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (Section</span> 7.1 and <span class="delete">Section 7.2)</span></td><td> </td><td class="rblock"><span class="insert">   (Sections</span> 7.1 and <span class="insert">7.2).</span></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">Appendix B.  Imported ABNF</td><td> </td><td class="right">Appendix B.  Imported ABNF</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">   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>
    433       <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.1 of [RFC5234]: ALPHA (letters), CR (carriage return),</td><td> </td><td class="right">   Appendix B.1 of [RFC5234]: ALPHA (letters), CR (carriage return),</td><td class="lineno" valign="top"></td></tr>
    434       <tr><td class="lineno" valign="top"></td><td class="left">   CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double</td><td> </td><td class="right">   CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double</td><td class="lineno" valign="top"></td></tr>
    435       <tr><td class="lineno" valign="top"></td><td class="left">   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any</td><td> </td><td class="right">   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any</td><td class="lineno" valign="top"></td></tr>
    436       <tr><td class="lineno" valign="top"></td><td class="left">   8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td> </td><td class="right">   8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII</td><td class="lineno" valign="top"></td></tr>
    437       <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>
    438       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    439155
    440156     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    441      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 26 change blocks.&nbsp;</a></th></tr>
    442      <tr class="stats"><td></td><th><i>73 lines changed or deleted</i></th><th><i> </i></th><th><i>51 lines changed or added</i></th><td></td></tr>
     157     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 12 change blocks.&nbsp;</a></th></tr>
     158     <tr class="stats"><td></td><th><i>44 lines changed or deleted</i></th><th><i> </i></th><th><i>21 lines changed or added</i></th><td></td></tr>
    443159     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
    444160   </table>
Note: See TracChangeset for help on using the changeset viewer.