File: http-upgrade-tokens

package info (click to toggle)
doc-iana 2001.08-1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 8,176 kB
  • ctags: 954
  • sloc: perl: 1,057; makefile: 83; sh: 27
file content (58 lines) | stat: -rw-r--r-- 2,060 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

HTTP Upgrade Token Registry - per [RFC2817]

The HTTP Upgrade Token Registry defines the name space for product
tokens used to identify protocols in the Upgrade HTTP header field.
Each registered token should be associated with one or a set of
specifications, and with contact information.

The Draft Standard for HTTP/1.1 specifies that these tokens
obey the production for 'product':

      product         = token ["/" product-version]
      product-version = token

Registrations should be allowed on a First Come First Served basis
as described in BCP 26. These specifications need not be IETF
documents or be subject to IESG review, but should obey the
following rules:

   1.  A token, once registered, stays registered forever.
   2.  The registration MUST name a responsible party for the
       registration.
   3.  The registration MUST name a point of contact.
   4.  The registration MAY name the documentation required for the
       token.
   5.  The responsible party MAY change the registration at any time.
       The IANA will keep a record of all such changes, and make them
       available upon request.
   6.  The responsible party for the first registration of a "product"
       token MUST approve later registrations of a "version" token
       together with that "product" token before they can be
       registered.
   7.  If absolutely required, the IESG MAY reassign the
       responsibility for a token. This will normally only be used in 
       the case when a responsible party cannot be contacted.

This specification defines the protocol token "TLS/1.0" as the
identifier for the protocol specified by The TLS Protocol.

It is NOT required that specifications for upgrade tokens be made
publicly available, but the contact information for the registration
SHOULD be.

HTTP Upgrade Token Registry

Description				Value		Reference
-----------				-----		---------


Reference
---------

[RFC2817]  Khare, R., Lawrence, S., "Upgrading to TLS Within
           HTTP/1.1", RFC 2817, May 2000.    

(last updated May 01 2001)

[]