W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: #172 (take over HTTP Upgrade Token Registry) httpbis

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 05 Jun 2009 16:35:49 +0200
Message-ID: <4A292D45.1020703@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
Looking a bit closer at RFC 2817 and the IANA registry resulted in the 
mail below being sent to IANA :-)

-- snip --

<http://www.iana.org/assignments/http-upgrade-tokens/>, as of today 
(June 05 2009) says:

 > Registry:
 > Value  Description       Reference
 > -----  ----------------  ---------
 > There are no registrations at this time

As a matter of fact, RFC 2817, the document that created that registry, 
registered the value below:

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

(<http://tools.ietf.org/html/rfc2817#section-7.2>)

Furthermore, RFC 2616 has:

 >    This specification only defines the protocol name "HTTP" for use by
 >    the family of Hypertext Transfer Protocols, as defined by the HTTP
 >    version rules of section 3.1 and future updates to this
 >    specification. Any token can be used as a protocol name; however, it
 >    will only be useful if both the client and server associate the name
 >    with the same protocol.

(<http://tools.ietf.org/html/rfc2616#section-14.42>), so essentially it 
reserves all tokens starting with "HTTP" for use by HTTP specifications.

-- snip --

NR, Julian
Received on Friday, 5 June 2009 14:36:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT