Changeset 190 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

03/02/08 19:07:03 (13 years ago)

Author:

julian.reschke@…

Message:

Move Section "Product Tokens" from P2 into P1 (back below "Protocol Parameters") ("token" is used in the definition of the Upgrade header); addresses #36.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1331 +1331 @@
 </section>
 
+<section title="Product Tokens" anchor="product.tokens">
+<t>
+   Product tokens are used to allow communicating applications to
+   identify themselves by software name and version. Most fields using
+   product tokens also allow sub-products which form a significant part
+   of the application to be listed, separated by white space. By
+   convention, the products are listed in order of their significance
+   for identifying the application.
+</t>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
+  product         = token ["/" product-version]
+  product-version = token
+</artwork></figure>
+<t>
+   Examples:
+</t>
+<figure><artwork type="example">
+    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
+    Server: Apache/0.8.4
+</artwork></figure>
+<t>
+   Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
+   used for advertising or other non-essential information. Although any
+   token character &MAY; appear in a product-version, this token &SHOULD;
+   only be used for a version identifier (i.e., successive versions of
+   the same product &SHOULD; only differ in the product-version portion of
+   the product value).
+</t>
+</section>
+
 </section>
 
@@ -4195 +4225 @@
   <list style="symbols"> 
     <t>
-       Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
-       "trailer-part").
-    </t>
-    <t>
-       Avoid underscore character in rule names ("http_URL" ->
-       "http-URL", "abs_path" -> "path-absolute").
-    </t>
-    <t>
-       Add rules for terms imported from URI spec ("absoluteURI", "authority",
-       "path-absolute", "port", "query", "relativeURI", "host) -- these will
-       have to be updated when switching over to RFC3986. 
-    </t>
-    <t>
-       Synchronize core rules with RFC5234 (this includes a change to CHAR
-       which now excludes NUL).
-    </t>
-    <t>
-       Get rid of prose rules that span multiple lines.
-    </t>
-    <t>
-       Get rid of unused rules LOALPHA and UPALPHA.
+      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
+      "trailer-part").
+    </t>
+    <t>
+      Avoid underscore character in rule names ("http_URL" ->
+      "http-URL", "abs_path" -> "path-absolute").
+    </t>
+    <t>
+      Add rules for terms imported from URI spec ("absoluteURI", "authority",
+      "path-absolute", "port", "query", "relativeURI", "host) -- these will
+      have to be updated when switching over to RFC3986. 
+    </t>
+    <t>
+      Synchronize core rules with RFC5234 (this includes a change to CHAR
+      which now excludes NUL).
+    </t>
+    <t>
+      Get rid of prose rules that span multiple lines.
+    </t>
+    <t>
+      Get rid of unused rules LOALPHA and UPALPHA.
+    </t>
+    <t>
+      Move "Product Tokens" section (back) into Part 1, as "token" is used
+      in the definition of the Upgrade header.
     </t>
   </list>