A new Request for Comments is now available in online RFC libraries.


        RFC 1950:

        Title:      ZLIB Compressed Data Format Specification
                    version 3.3
        Author:     P. Deutsch & J-L. Gailly
        Date:       May 1996
        Mailbox:    ghost@aladdin.com, gzip@prep.ai.mit.edu
        Pages:      11
        Characters: 20,502
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1950.txt


This specification defines a lossless compressed data format.  The
data can be produced or consumed, even for an arbitrarily long
sequentially presented input data stream, using only an a priori
bounded amount of intermediate storage.  The format presently uses the
DEFLATE compression method but can be easily extended to use other
compression methods.  It can be implemented readily in a manner not
covered by patents.  This specification also defines the ADLER-32
checksum (an extension and improvement of the Fletcher checksum), used
for detection of data corruption, and provides an algorithm for
computing it.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute