Changeset 2176


Ignore:
Timestamp:
Jan 31, 2013, 5:17:04 PM (7 years ago)
Author:
martin.thomson@…
Message:

Changing protocol label.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-http2/latest/draft-ietf-httpbis-http2.xml

    r2175 r2176  
    196196</t>
    197197<t>
    198   Implementations of draft versions of the protocol MUST add the corresponding draft number to the
    199   identifier before the separator ('/').  For example, draft-ietf-httpbis-http2-03 is identified
    200   using the string "HTTP-03/2.0".
    201 </t>
    202 <t>
    203   Non-compatible experiments that are based on these draft versions MUST include a further
    204   identifier.  For example, an experimental implementation of packet mood-based encoding based on
    205   draft-ietf-httpbis-http2-07 might identify itself as "HTTP-07-emo/2.0".  Note that any label MUST
    206   conform with the "token" syntax defined in Section 3.2.4 of <xref target="HTTP-p1"/>.
    207   Experimenters are encouraged to coordinate their experiments on the ietf-http-wg@w3.org mailing
    208   list.
     198  Implementations of draft versions of the protocol MUST add the string "-draft-" and the
     199  corresponding draft number to the identifier before the separator ('/').  For example,
     200  draft-ietf-httpbis-http2-03 is identified using the string "HTTP-draft-03/2.0".
     201</t>
     202<t>
     203  Non-compatible experiments that are based on these draft versions MUST instead replace the string
     204  "draft" with a different identifier.  For example, an experimental implementation of packet
     205  mood-based encoding based on draft-ietf-httpbis-http2-07 might identify itself as
     206  "HTTP-emo-07/2.0".  Note that any label MUST conform with the "token" syntax defined in
     207  Section 3.2.4 of <xref target="HTTP-p1"/>.  Experimenters are encouraged to coordinate their
     208  experiments on the ietf-http-wg@w3.org mailing list.
    209209</t>
    210210</section>
     
    13701370<section title="Cacheability of Pushed Resources">
    13711371<t>
    1372   Resources that are pushed is possible, based on the guidance provided by the origin server in
    1373   the Cache-Control header field.  However, this can cause issues if a single server hosts more
    1374   than one tenant.  For example, a server might offer multiple users each a small portion of its
    1375   URI space.
     1372  Caching resources that are pushed is possible, based on the guidance provided by the origin
     1373  server in the Cache-Control header field.  However, this can cause issues if a single server
     1374  hosts more than one tenant.  For example, a server might offer multiple users each a small
     1375  portion of its URI space.
    13761376</t>
    13771377<t>
     
    13801380  Failure to enforce this would allow a tenant to provide a representation that would be served
    13811381  out of cache, overriding the actual representation that the authoritative tenant provides.
     1382</t>
     1383<t>
     1384  Pushed resources for which an origin server is not authoritative are never cached or used.
    13821385</t>
    13831386</section>
     
    16551658  Added note on cacheability of pushed resources and multiple tenant servers.
    16561659</t>
     1660<t>
     1661  Changed protocol label form based on discussions.
     1662</t>
    16571663</section>
    16581664<section title="Since draft-ietf-httpbis-http2-00" anchor="changes.since.draft-ietf-httpbis-http2-00">
Note: See TracChangeset for help on using the changeset viewer.