W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2005

RE: http-parameters registry vs RFC 2616

From: Larry Masinter <LMM@acm.org>
Date: Wed, 26 Oct 2005 15:01:25 -0700
To: "'IANA'" <iana@iana.org>
Cc: hardie@qualcomm.com, "'Scott Hollenbeck'" <sah@428cobrajet.net>, bjoern@hoehrmann.de, ietf-http-wg@w3.org, "'William A. Rowe, Jr.'" <wrowe@rowe-clan.net>
Message-id: <000301c5da78$cf87c780$fb822099@corp.adobe.com>

In http://www.iana.org/numbers.html, I suggest making them both
"FCFS with specification recommended", because it is not
explicitly required (says SHOULD).

Note that RFC 2817 HTTP status codes and HTTP upgrade tokens
are also HTTP parameters, so I wonder about combining these
two registries without combining all of the other ones associated
with HTTP. Also,
HTTP Status Codes 	RFC3293  	RFC and FCFS (section 10.2)
but this is really RFC 2817, isn't it?

In http://www.iana.org/assignments/http-parameters

I suggest you remove the text:

#   If you are looking for the HTTP data types, you should look in the
#   file "url-schemes". 
#   See:  http://www.iana.org/assignments/url-schemes

I think this text is confusing. HTTP relies on many IANA registered
values, including character sets, media types, and language tags, 
as well as the other above registries for status codes and upgrade
tokens, but doesn't directly rely on the URI scheme registry.

I think the specification for all of the transfer-coding and content-coding
values should be RFC 2616; do you want to give explicit section numbers?
For HTTP Transfer codings,  I would add "identity" and note that it
was withdrawn in the errata.

=======================================================================
HTTP Content-Coding Values
Name      Description                            Reference
------    ------------------------------------- ---------
compress UNIX "compress"  program method       [RFC2616] section 3.5
deflate  "zlib" format[RFC1950] with
          with "deflate" compression[RFC2616]  [RFC2616] section 3.5
gzip     Same as GNU zip[RFC1952]              [RFC2616] section 3.5



HTTP Transfer Coding Values

Name      Description                            Reference
------    ------------------------------------- ---------
chunked    Transfer in a series of chunks       [RFC2616] Section 3.6.1
compress   UNIX "compress"  program method      [RFC2616] section 3.6
deflate    "zlib" format[RFC1950] with
           with "deflate" compression[RFC2616]  [RFC2616] section 3.6
gzip       Same as GNU zip[RFC1952]             [RFC2616] section 3.6
identity   (withdrawn in errata to RFC 2616)    [RFC2616] section 3.6
Received on Wednesday, 26 October 2005 22:01:12 GMT

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