Changeset 1055 for draft-ietf-httpbis/12


Ignore:
Timestamp:
23/10/10 09:17:48 (9 years ago)
Author:
julian.reschke@…
Message:

Back-port clarification of trailer requirements to -12 (see #193 and [1053])

Location:
draft-ietf-httpbis/12
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/12/draft-ietf-httpbis-p1-messaging-12.txt

    r1051 r1055  
    20152015       described in Section 9.5; or,
    20162016
    2017    2.  the server is the origin server for the response, the trailer
    2018        fields consist entirely of optional metadata, and the recipient
    2019        could use the message (in a manner acceptable to the origin
    2020        server) without receiving this metadata.  In other words, the
    2021        origin server is willing to accept the possibility that the
    2022        trailer fields might be silently discarded along the path to the
    2023        client.
     2017   2.  the trailer fields consist entirely of optional metadata, and the
     2018       recipient could use the message (in a manner acceptable to the
     2019       server where the field originated) without receiving it.  In
     2020       other words, the server that generated the header (often but not
     2021       always the origin server) is willing to accept the possibility
     2022       that the trailer fields might be silently discarded along the
     2023       path to the client.
    20242024
    20252025   This requirement prevents an interoperability failure when the
    … …  
    48564856   Closed issues:
    48574857
     4858   o  <http://tools.ietf.org/wg/httpbis/trac/ticket/193>: "Trailer
     4859      requirements"
     4860
    48584861   o  <http://tools.ietf.org/wg/httpbis/trac/ticket/204>: "Text about
    48594862      clock requirement for caches belongs in p6"
    … …  
    48924895         gzip  38
    48934896      compress (Coding Format)  38
     4897
     4898
     4899
     4900Fielding, et al.         Expires April 28, 2011                [Page 86]
     4901
     4902
     4903Internet-Draft              HTTP/1.1, Part 1                October 2010
     4904
     4905
    48944906      connection  10
    48954907      Connection header  49
    48964908      Content-Length header  50
    4897 
    4898 
    4899 
    4900 Fielding, et al.         Expires April 28, 2011                [Page 86]
    4901 
    4902 
    4903 Internet-Draft              HTTP/1.1, Part 1                October 2010
    4904 
    49054909
    49064910   D
    … …  
    49484952         DIGIT  7
    49494953         DQUOTE  7
     4954
     4955
     4956
     4957Fielding, et al.         Expires April 28, 2011                [Page 87]
     4958
     4959
     4960Internet-Draft              HTTP/1.1, Part 1                October 2010
     4961
     4962
    49504963         extension-code  32
    49514964         extension-method  26
    49524965         field-content  20
    49534966         field-name  20
    4954 
    4955 
    4956 
    4957 Fielding, et al.         Expires April 28, 2011                [Page 87]
    4958 
    4959 
    4960 Internet-Draft              HTTP/1.1, Part 1                October 2010
    4961 
    4962 
    49634967         field-value  20
    49644968         general-header  26
    … …  
    50055009         Request  26
    50065010         Request-Line  26
     5011
     5012
     5013
     5014Fielding, et al.         Expires April 28, 2011                [Page 88]
     5015
     5016
     5017Internet-Draft              HTTP/1.1, Part 1                October 2010
     5018
     5019
    50075020         request-target  27
    50085021         Response  31
    50095022         rfc850-date  34
    50105023         rfc1123-date  33
    5011 
    5012 
    5013 
    5014 Fielding, et al.         Expires April 28, 2011                [Page 88]
    5015 
    5016 
    5017 Internet-Draft              HTTP/1.1, Part 1                October 2010
    5018 
    5019 
    50205024         RWS  9
    50215025         second  33
    … …  
    50625066         Host  52
    50635067         TE  53
     5068
     5069
     5070
     5071Fielding, et al.         Expires April 28, 2011                [Page 89]
     5072
     5073
     5074Internet-Draft              HTTP/1.1, Part 1                October 2010
     5075
     5076
    50645077         Trailer  54
    50655078         Transfer-Encoding  55
    50665079         Upgrade  55
    50675080         Via  57
    5068 
    5069 
    5070 
    5071 Fielding, et al.         Expires April 28, 2011                [Page 89]
    5072 
    5073 
    5074 Internet-Draft              HTTP/1.1, Part 1                October 2010
    5075 
    5076 
    50775081      headers  19
    50785082      Host header  52
    … …  
    51195123      Upgrade header  55
    51205124      upstream  12
     5125
     5126
     5127
     5128Fielding, et al.         Expires April 28, 2011                [Page 90]
     5129
     5130
     5131Internet-Draft              HTTP/1.1, Part 1                October 2010
     5132
     5133
    51215134      URI scheme
    51225135         http  16
    51235136         https  18
    51245137      user agent  10
    5125 
    5126 
    5127 
    5128 Fielding, et al.         Expires April 28, 2011                [Page 90]
    5129 
    5130 
    5131 Internet-Draft              HTTP/1.1, Part 1                October 2010
    5132 
    51335138
    51345139   V
    … …  
    51695174
    51705175
     5176
     5177
     5178
     5179
     5180
     5181
     5182
     5183
     5184
     5185Fielding, et al.         Expires April 28, 2011                [Page 91]
     5186
     5187
     5188Internet-Draft              HTTP/1.1, Part 1                October 2010
     5189
     5190
    51715191   Henrik Frystyk Nielsen
    51725192   Microsoft Corporation
    … …  
    51765196
    51775197   EMail: henrikn@microsoft.com
    5178 
    5179 
    5180 
    5181 
    5182 
    5183 
    5184 
    5185 Fielding, et al.         Expires April 28, 2011                [Page 91]
    5186 
    5187 
    5188 Internet-Draft              HTTP/1.1, Part 1                October 2010
    51895198
    51905199
    … …  
    52195228
    52205229
     5230
     5231
     5232
     5233
     5234
     5235
     5236
     5237
     5238
     5239
     5240
     5241
     5242Fielding, et al.         Expires April 28, 2011                [Page 92]
     5243
     5244
     5245Internet-Draft              HTTP/1.1, Part 1                October 2010
     5246
     5247
    52215248   Yves Lafon (editor)
    52225249   World Wide Web Consortium
    … …  
    52305257
    52315258
    5232 
    5233 
    5234 
    5235 
    5236 
    5237 
    5238 
    5239 
    5240 
    5241 
    5242 Fielding, et al.         Expires April 28, 2011                [Page 92]
    5243 
    5244 
    5245 Internet-Draft              HTTP/1.1, Part 1                October 2010
    5246 
    5247 
    52485259   Julian F. Reschke (editor)
    52495260   greenbytes GmbH
    … …  
    52865297
    52875298
    5288 
    5289 
    5290 
    5291 
    5292 
    5293 
    5294 
    5295 
    5296 
    5297 
    5298 
    52995299Fielding, et al.         Expires April 28, 2011                [Page 93]
    53005300

  • draft-ietf-httpbis/12/draft-ietf-httpbis-p1-messaging-12.xml

    r1051 r1055  
    20472047     acceptable in the transfer-coding of the  response, as described in
    20482048     <xref target="header.te"/>; or,</t>
    2049 
    2050     <t>the server is the origin server for the response, the trailer
    2051      fields consist entirely of optional metadata, and the recipient
    2052      could use the message (in a manner acceptable to the origin server)
    2053      without receiving this metadata.  In other words, the origin server
    2054      is willing to accept the possibility that the trailer fields might
    2055      be silently discarded along the path to the client.</t>
     2049     
     2050    <t>the trailer fields consist entirely of optional metadata, and the
     2051    recipient could use the message (in a manner acceptable to the server where
     2052    the field originated) without receiving it. In other words, the server that
     2053    generated the header (often but not always the origin server) is willing to
     2054    accept the possibility that the trailer fields might be silently discarded
     2055    along the path to the client.</t>
    20562056  </list>
    20572057</t>
    … …  
    56125612  <list style="symbols">
    56135613    <t>
     5614      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>:
     5615      "Trailer requirements"
     5616    </t>
     5617    <t>
    56145618      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/204"/>:
    56155619      "Text about clock requirement for caches belongs in p6"

  • draft-ietf-httpbis/12/p1-messaging.html

    r1051 r1055  
    16341634            described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section&nbsp;9.5</a>; or,
    16351635         </li>
    1636          <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient
    1637             could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin
    1638             server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
     1636         <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable
     1637            to the server where the field originated) without receiving it. In other words, the server that generated the header (often
     1638            but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded
     1639            along the path to the client.
    16391640         </li>
    16401641      </ol>
    … …  
    34553456      <p id="rfc.section.D.13.p.1">Closed issues: </p>
    34563457      <ul>
     3458         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>&gt;: "Trailer requirements"
     3459         </li>
    34573460         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
    34583461         </li>

  • draft-ietf-httpbis/12/p1-messaging.xml

    r1051 r1055  
    20862086     acceptable in the transfer-coding of the  response, as described in
    20872087     <xref target="header.te"/>; or,</t>
    2088 
    2089     <t>the server is the origin server for the response, the trailer
    2090      fields consist entirely of optional metadata, and the recipient
    2091      could use the message (in a manner acceptable to the origin server)
    2092      without receiving this metadata.  In other words, the origin server
    2093      is willing to accept the possibility that the trailer fields might
    2094      be silently discarded along the path to the client.</t>
     2088     
     2089    <t>the trailer fields consist entirely of optional metadata, and the
     2090    recipient could use the message (in a manner acceptable to the server where
     2091    the field originated) without receiving it. In other words, the server that
     2092    generated the header (often but not always the origin server) is willing to
     2093    accept the possibility that the trailer fields might be silently discarded
     2094    along the path to the client.</t>
    20952095  </list>
    20962096</t>
    … …  
    56575657  <list style="symbols">
    56585658    <t>
     5659      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>:
     5660      "Trailer requirements"
     5661    </t>
     5662    <t>
    56595663      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/204"/>:
    56605664      "Text about clock requirement for caches belongs in p6"
Note: See TracChangeset for help on using the changeset viewer.