Ignore:
Timestamp:
Apr 6, 2010, 8:07:48 AM (10 years ago)
Author:
julian.reschke@…
Message:

"deflate": make the IANA entry more consistent with the actual description (related to #73)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r799 r806  
    16681668   </c>
    16691669   <c>deflate</c>
    1670    <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c>
     1670   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
     1671   the "zlib" data format (<xref target="RFC1950"/>)
     1672   </c>
    16711673   <c>
    16721674      &deflate-coding;
     
    20252027  <annotation>
    20262028    RFC 1950 is an Informational RFC, thus it may be less stable than
     2029    this specification. On the other hand, this downward reference was
     2030    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     2031    therefore it is unlikely to cause problems in practice. See also
     2032    <xref target="BCP97"/>.
     2033  </annotation>
     2034</reference>
     2035
     2036<reference anchor="RFC1951">
     2037  <front>
     2038    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
     2039    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
     2040      <organization>Aladdin Enterprises</organization>
     2041      <address><email>ghost@aladdin.com</email></address>
     2042    </author>
     2043    <date month="May" year="1996"/>
     2044  </front>
     2045  <seriesInfo name="RFC" value="1951"/>
     2046  <annotation>
     2047    RFC 1951 is an Informational RFC, thus it may be less stable than
    20272048    this specification. On the other hand, this downward reference was
    20282049    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
Note: See TracChangeset for help on using the changeset viewer.