proposed part 1 section 6.3

Good evening. To -hopefully- conclude my series of talking to myself about
section 6.3, here is a proposed new section 6.3. And following that a few
example User-Agent headers for reference when considering language to do
with what I call the "bonus" information generally referring to system
architecture, particularly the two alternative endings to the proposed
section 6.3.

 6.3.  Product Tokens


   Product tokens are used to allow communicating applications to
   identify themselves by software name and version.

   A product token SHOULD consist of a product and a product-version,
   separated by a slash “/”.

   Product tokens are separated by linear whitespace.

   When software versions change, the product SHOULD stay the same
   and only the product-version portion vary, to aid parseability and
   comparison.

   By convention, the products are listed in order of their significance
   for identifying the application.

   In practice, clients exhibit bonus information parenthetically
   between product tokens. This information is proprietary and SHOULD NOT
   be attempted to be used meaningfully.

-or-
   In practice, clients exhibit bonus information parenthetically
   following product tokens. This information refers to the preceding
   product token and identifies information about the host system
   architecture upon which the client runs.


User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
zlib/1.2.3.3 libidn/1.15

User-Agent: Wget/1.12 (linux-gnu)

User-Agent: Links (2.1pre32; Linux 2.6.24-16-generic x86_64; 80x24)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18)
Gecko/20110628 Ubuntu/10.04 (lucid) Firefox/3.6.18



Dale