Changeset 2176 for draft-ietf-httpbis-http2

Timestamp:

01/02/13 01:17:04 (9 years ago)

Author:

martin.thomson@…

Message:

Changing protocol label.

File:

• draft-ietf-httpbis-http2/latest/draft-ietf-httpbis-http2.xml (modified) (4 diffs)

draft-ietf-httpbis-http2/latest/draft-ietf-httpbis-http2.xml

@@ -196 +196 @@
 </t>
 <t>
-  Implementations of draft versions of the protocol MUST add the corresponding draft number to the
-  identifier before the separator ('/').  For example, draft-ietf-httpbis-http2-03 is identified
-  using the string "HTTP-03/2.0".
-</t>
-<t>
-  Non-compatible experiments that are based on these draft versions MUST include a further
-  identifier.  For example, an experimental implementation of packet mood-based encoding based on
-  draft-ietf-httpbis-http2-07 might identify itself as "HTTP-07-emo/2.0".  Note that any label MUST
-  conform with the "token" syntax defined in Section 3.2.4 of <xref target="HTTP-p1"/>.
-  Experimenters are encouraged to coordinate their experiments on the ietf-http-wg@w3.org mailing
-  list.
+  Implementations of draft versions of the protocol MUST add the string "-draft-" and the
+  corresponding draft number to the identifier before the separator ('/').  For example,
+  draft-ietf-httpbis-http2-03 is identified using the string "HTTP-draft-03/2.0".
+</t>
+<t>
+  Non-compatible experiments that are based on these draft versions MUST instead replace the string
+  "draft" with a different identifier.  For example, an experimental implementation of packet
+  mood-based encoding based on draft-ietf-httpbis-http2-07 might identify itself as
+  "HTTP-emo-07/2.0".  Note that any label MUST conform with the "token" syntax defined in
+  Section 3.2.4 of <xref target="HTTP-p1"/>.  Experimenters are encouraged to coordinate their
+  experiments on the ietf-http-wg@w3.org mailing list.
 </t>
 </section>
@@ -1370 +1370 @@
 <section title="Cacheability of Pushed Resources">
 <t>
-  Resources that are pushed is possible, based on the guidance provided by the origin server in
-  the Cache-Control header field.  However, this can cause issues if a single server hosts more
-  than one tenant.  For example, a server might offer multiple users each a small portion of its
-  URI space.
+  Caching resources that are pushed is possible, based on the guidance provided by the origin
+  server in the Cache-Control header field.  However, this can cause issues if a single server
+  hosts more than one tenant.  For example, a server might offer multiple users each a small
+  portion of its URI space.
 </t>
 <t>
@@ -1380 +1380 @@
   Failure to enforce this would allow a tenant to provide a representation that would be served
   out of cache, overriding the actual representation that the authoritative tenant provides.
+</t>
+<t>
+  Pushed resources for which an origin server is not authoritative are never cached or used.
 </t>
 </section>
@@ -1655 +1658 @@
   Added note on cacheability of pushed resources and multiple tenant servers.
 </t>
+<t>
+  Changed protocol label form based on discussions.
+</t>
 </section>
 <section title="Since draft-ietf-httpbis-http2-00" anchor="changes.since.draft-ietf-httpbis-http2-00">