Last Call: <draft-ietf-httpbis-cice-01.txt> (Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The IESG has received a request from the Hypertext Transfer Protocol WG
(httpbis) to consider the following document:
- 'Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding'
  <draft-ietf-httpbis-cice-01.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-08-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   In HTTP, content codings allow for payload encodings such as for
   compression or integrity checks.  In particular, the "gzip" content
   coding is widely used for payload data sent in response messages.

   Content codings can be used in request messages as well, however
   discoverability is not on par with response messages.  This document
   extends the HTTP "Accept-Encoding" header field for use in responses,
   to indicate that content codings are supported in requests.


The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-cice/

IESG discussion, once it begins, can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-cice/ballot/

No IPR declarations have been submitted directly on this I-D.





[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux