Ignore:
Timestamp:
Aug 7, 2009, 9:46:40 AM (10 years ago)
Author:
julian.reschke@…
Message:

Move definitions of compression codings (compress/deflate/gzip) into Part 1, as they also can be used as Transfer Codings (see #189)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r670 r673  
    17561756</t>
    17571757<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
    1758   <x:ref>transfer-coding</x:ref>         = "chunked" / <x:ref>transfer-extension</x:ref>
     1758  <x:ref>transfer-coding</x:ref>         = "chunked" ; <xref target="chunked.encoding"/>
     1759                          / "compress" ; <xref target="compress.coding"/>
     1760                          / "deflate" ; <xref target="deflate.coding"/>
     1761                          / "gzip" ; <xref target="gzip.coding"/>
     1762                          / <x:ref>transfer-extension</x:ref>
    17591763  <x:ref>transfer-extension</x:ref>      = <x:ref>token</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>transfer-parameter</x:ref> )
    17601764</artwork></figure>
     
    18011805</t>
    18021806
    1803 <section title="Chunked Transfer Coding" anchor="chunked.transfer.encoding">
     1807<section title="Chunked Transfer Coding" anchor="chunked.encoding">
     1808  <iref item="chunked (Coding Format)"/>
     1809  <iref item="Coding Format" subitem="chunked"/>
    18041810  <x:anchor-alias value="chunk"/>
    18051811  <x:anchor-alias value="Chunked-Body"/>
     
    18981904   they do not understand.
    18991905</t>
     1906</section>
     1907
     1908<section title="Compression Codings" anchor="compression.codings">
     1909<t>
     1910   The codings defined below can be used to compress the payload of a
     1911   message.
     1912</t>
     1913<x:note><t>
     1914   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
     1915   is not desirable and is discouraged for future encodings. Their
     1916   use here is representative of historical practice, not good
     1917   design.
     1918</t></x:note>
     1919<x:note><t>
     1920   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
     1921   applications &SHOULD; consider "x-gzip" and "x-compress" to be
     1922   equivalent to "gzip" and "compress" respectively.
     1923</t></x:note>
     1924
     1925<section title="Compress Coding" anchor="compress.coding">
     1926<iref item="compress (Coding Format)"/>
     1927<iref item="Coding Format" subitem="compress"/>
     1928<t>
     1929   The "compress" format is produced by the common UNIX file compression
     1930   program "compress". This format is an adaptive Lempel-Ziv-Welch
     1931   coding (LZW).
     1932</t>
     1933</section>
     1934
     1935<section title="Deflate Coding" anchor="deflate.coding">
     1936<iref item="deflate (Coding Format)"/>
     1937<iref item="Coding Format" subitem="deflate"/>
     1938<t>
     1939   The "zlib" format is defined in <xref target="RFC1950"/> in combination with
     1940   the "deflate" compression mechanism described in <xref target="RFC1951"/>.
     1941</t>
     1942</section>
     1943
     1944<section title="Gzip Coding" anchor="gzip.coding">
     1945<iref item="gzip (Coding Format)"/>
     1946<iref item="Coding Format" subitem="gzip"/>
     1947<t>
     1948   The "gzip" format is produced by the file compression program
     1949   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
     1950   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
     1951</t>
     1952</section>
     1953
    19001954</section>
    19011955
     
    26832737   The presence of the keyword "trailers" indicates that the client is
    26842738   willing to accept trailer fields in a chunked transfer-coding, as
    2685    defined in <xref target="chunked.transfer.encoding"/>. This keyword is reserved for use with
     2739   defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with
    26862740   transfer-coding values even though it does not itself represent a
    26872741   transfer-coding.
     
    27612815<t>
    27622816   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
    2763    any header fields. See <xref target="chunked.transfer.encoding"/> for restrictions on the use of
     2817   any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of
    27642818   trailer fields in a "chunked" transfer-coding.
    27652819</t>
     
    32143268<section title="Transfer Coding Registry" anchor="transfer.coding.registration">
    32153269<t>
    3216    The registration procedure for HTTP Transfer Codings is now defined
    3217    by <xref target="transfer.coding.registry"/> of this document.
     3270   The registration procedure for HTTP Transfer Codings is now defined by
     3271   <xref target="transfer.coding.registry"/> of this document.
    32183272</t>
    32193273<t>
    32203274   The HTTP Transfer Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>
    3221    should be updated with the registration below:
     3275   should be updated with the registrations below:
    32223276</t>
    32233277<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
     
    32253279   <ttcol>Description</ttcol>
    32263280   <ttcol>Reference</ttcol>
    3227    <c>Chunked</c>
     3281   <c>chunked</c>
    32283282   <c>Transfer in a series of chunks</c>
    32293283   <c>
    3230       <xref target="chunked.transfer.encoding"/>
     3284      <xref target="chunked.encoding"/>
     3285   </c>
     3286   <c>compress</c>
     3287   <c>UNIX "compress" program method</c>
     3288   <c>
     3289      <xref target="compress.coding"/>
     3290   </c>
     3291   <c>deflate</c>
     3292   <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c>
     3293   <c>
     3294      <xref target="deflate.coding"/>
     3295   </c>
     3296   <c>gzip</c>
     3297   <c>Same as GNU zip <xref target="RFC1952"/></c>
     3298   <c>
     3299      <xref target="gzip.coding"/>
    32313300   </c>
    32323301</texttable>
     
    37233792</reference>
    37243793
     3794<reference anchor="RFC1950">
     3795  <front>
     3796    <title>ZLIB Compressed Data Format Specification version 3.3</title>
     3797    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
     3798      <organization>Aladdin Enterprises</organization>
     3799      <address><email>ghost@aladdin.com</email></address>
     3800    </author>
     3801    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
     3802      <organization/>
     3803    </author>
     3804    <date month="May" year="1996"/>
     3805  </front>
     3806  <seriesInfo name="RFC" value="1950"/>
     3807  <annotation>
     3808    RFC 1950 is an Informational RFC, thus it may be less stable than
     3809    this specification. On the other hand, this downward reference was
     3810    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     3811    therefore it is unlikely to cause problems in practice. See also
     3812    <xref target="BCP97"/>.
     3813  </annotation>
     3814</reference>
     3815
     3816<reference anchor="RFC1951">
     3817  <front>
     3818    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
     3819    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
     3820      <organization>Aladdin Enterprises</organization>
     3821      <address><email>ghost@aladdin.com</email></address>
     3822    </author>
     3823    <date month="May" year="1996"/>
     3824  </front>
     3825  <seriesInfo name="RFC" value="1951"/>
     3826  <annotation>
     3827    RFC 1951 is an Informational RFC, thus it may be less stable than
     3828    this specification. On the other hand, this downward reference was
     3829    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     3830    therefore it is unlikely to cause problems in practice. See also
     3831    <xref target="BCP97"/>.
     3832  </annotation>
     3833</reference>
     3834
     3835<reference anchor="RFC1952">
     3836  <front>
     3837    <title>GZIP file format specification version 4.3</title>
     3838    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
     3839      <organization>Aladdin Enterprises</organization>
     3840      <address><email>ghost@aladdin.com</email></address>
     3841    </author>
     3842    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
     3843      <organization/>
     3844      <address><email>gzip@prep.ai.mit.edu</email></address>
     3845    </author>
     3846    <author initials="M." surname="Adler" fullname="Mark Adler">
     3847      <organization/>
     3848      <address><email>madler@alumni.caltech.edu</email></address>
     3849    </author>
     3850    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
     3851      <organization/>
     3852      <address><email>ghost@aladdin.com</email></address>
     3853    </author>
     3854    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
     3855      <organization/>
     3856      <address><email>randeg@alumni.rpi.edu</email></address>
     3857    </author>
     3858    <date month="May" year="1996"/>
     3859  </front>
     3860  <seriesInfo name="RFC" value="1952"/>
     3861  <annotation>
     3862    RFC 1952 is an Informational RFC, thus it may be less stable than
     3863    this specification. On the other hand, this downward reference was
     3864    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     3865    therefore it is unlikely to cause problems in practice. See also
     3866    <xref target="BCP97"/>.
     3867  </annotation>
     3868</reference>
     3869
    37253870</references>
    37263871
     
    40804225  </front>
    40814226  <seriesInfo name="RFC" value="5322"/>
     4227</reference>
     4228
     4229<reference anchor='BCP97'>
     4230  <front>
     4231    <title>Handling Normative References to Standards-Track Documents</title>
     4232    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
     4233      <organization />
     4234      <address>
     4235        <email>klensin+ietf@jck.com</email>
     4236      </address>
     4237    </author>
     4238    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
     4239      <organization>MIT</organization>
     4240      <address>
     4241        <email>hartmans-ietf@mit.edu</email>
     4242      </address>
     4243    </author>
     4244    <date year='2007' month='June' />
     4245  </front>
     4246  <seriesInfo name='BCP' value='97' />
     4247  <seriesInfo name='RFC' value='4897' />
    40824248</reference>
    40834249
     
    43454511   interoperability problem that could have occurred due to interactions
    43464512   between authentication trailers, chunked encoding and HTTP/1.0
    4347    clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked.transfer.encoding" format="counter"/>,
     4513   clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked.encoding" format="counter"/>,
    43484514   and <xref target="header.te" format="counter"/>)
    43494515</t>
     
    43764542  Clarification that the chunk length does not include
    43774543  the count of the octets in the chunk header and trailer.
    4378   (<xref target="chunked.transfer.encoding"/>)
     4544  (<xref target="chunked.encoding"/>)
    43794545</t>
    43804546<t>
     
    50025168      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
    50035169    </t>
     5170    <t>
     5171      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/189"/>:
     5172      "move definitions of gzip/deflate/compress to part 1"
     5173    </t>
    50045174  </list>
    50055175</t>
Note: See TracChangeset for help on using the changeset viewer.