| < draft-deutsch-gzip-spec-00.txt | draft-deutsch-gzip-spec-01.txt > | |||
|---|---|---|---|---|
| INTERNET-DRAFT L. Peter Deutsch | INTERNET-DRAFT L. Peter Deutsch | |||
| GZIP 4.3 Aladdin Enterprises | GZIP 4.3 Aladdin Enterprises | |||
| Expires: 06 Aug 1996 01 Feb 1996 | Expires: 17 Aug 1996 12 Feb 1996 | |||
| GZIP file format specification version 4.3 | GZIP file format specification version 4.3 | |||
| File draft-deutsch-gzip-spec-00.txt | File draft-deutsch-gzip-spec-01.txt | |||
| Status of this Memo | Status of this Memo | |||
| This document is an Internet-Draft. Internet-Drafts are working | This document is an Internet-Draft. Internet-Drafts are working | |||
| documents of the Internet Engineering Task Force (IETF), its areas, | documents of the Internet Engineering Task Force (IETF), its areas, | |||
| and its working groups. Note that other groups may also distribute | and its working groups. Note that other groups may also distribute | |||
| working documents as Internet-Drafts. | working documents as Internet-Drafts. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| skipping to change at line 450 ¶ | skipping to change at line 450 ¶ | |||
| The ISO 8859-1 (Latin-1) character set is a superset of 7-bit | The ISO 8859-1 (Latin-1) character set is a superset of 7-bit | |||
| ASCII. Files defining this character set may be obtained from | ASCII. Files defining this character set may be obtained from | |||
| ftp.uu.net:/graphics/png/documents/iso_8859-1.* | ftp.uu.net:/graphics/png/documents/iso_8859-1.* | |||
| ISO 3309 | ISO 3309 | |||
| ITU-T recommendation V.42 | ITU-T recommendation V.42 | |||
| 3.2. Other related publications | 3.2. Other related publications | |||
| Deutsch, L.P.,"'Deflate' Compressed Data Format Specification". | [1] Deutsch, L.P.,"'Deflate' Compressed Data Format | |||
| available in ftp.uu.net:/pub/archiving/zip/doc/deflate-*.doc | Specification". available in | |||
| ftp.uu.net:/pub/archiving/zip/doc/deflate-*.doc | ||||
| Gailly, J.-L., gzip documentation, available in | [2] Gailly, J.-L., gzip documentation, available in | |||
| prep.ai.mit.edu:/pub/gnu/gzip-*.tar | prep.ai.mit.edu:/pub/gnu/gzip-*.tar | |||
| [Sarwate88] Sarwate, D.V., "Computation of Cyclic Redundancy | [3] Sarwate, D.V., "Computation of Cyclic Redundancy Checks via | |||
| Checks via Table Look-Up", Communications of the ACM, 31(8), | Table Look-Up", Communications of the ACM, 31(8), pp.1008-1013. | |||
| pp.1008-1013. | ||||
| Schwaderer, W.D., "CRC Calculation", April 85 PC Tech Journal, | [4] Schwaderer, W.D., "CRC Calculation", April 85 PC Tech Journal, | |||
| pp.118-133. | pp.118-133. | |||
| ftp.adelaide.edu.au:/pub/rocksoft/papers/crc_v3.txt, describing | [5] ftp.adelaide.edu.au:/pub/rocksoft/papers/crc_v3.txt, | |||
| the CRC concept. | describing the CRC concept. | |||
| 4. Security considerations | 4. Security considerations | |||
| Any data compression method involves the reduction of redundancy in | Any data compression method involves the reduction of redundancy in | |||
| the data. Consequently, any corruption of the data is likely to have | the data. Consequently, any corruption of the data is likely to have | |||
| severe effects and be difficult to correct. Uncompressed text, on | severe effects and be difficult to correct. Uncompressed text, on | |||
| the other hand, will probably still be readable despite the presence | the other hand, will probably still be readable despite the presence | |||
| of some corrupted bytes. | of some corrupted bytes. | |||
| It is recommended that systems using this data format provide some | It is recommended that systems using this data format provide some | |||
| skipping to change at line 510 ¶ | skipping to change at line 510 ¶ | |||
| Questions about the technical content of this specification can be | Questions about the technical content of this specification can be | |||
| sent by email to | sent by email to | |||
| Jean-loup Gailly <gzip@prep.ai.mit.edu> and | Jean-loup Gailly <gzip@prep.ai.mit.edu> and | |||
| Mark Adler <madler@alumni.caltech.edu> | Mark Adler <madler@alumni.caltech.edu> | |||
| Editorial comments on this specification can be sent by email to | Editorial comments on this specification can be sent by email to | |||
| L. Peter Deutsch <ghost@aladdin.com> and | L. Peter Deutsch <ghost@aladdin.com> and | |||
| Glenn Randers-Pehrson <glennrp@arl.mil> | Glenn Randers-Pehrson <randeg@alumni.rpi.edu> | |||
| 7. Appendix: Jean-loup Gailly's gzip utility | 7. Appendix: Jean-loup Gailly's gzip utility | |||
| The most widely used implementation of gzip compression, and the | The most widely used implementation of gzip compression, and the | |||
| original documentation on which this specification is based, were | original documentation on which this specification is based, were | |||
| created by Jean-loup Gailly <gzip@prep.ai.mit.edu>. Since this | created by Jean-loup Gailly <gzip@prep.ai.mit.edu>. Since this | |||
| implementation is a de facto standard, we mention some more of its | implementation is a de facto standard, we mention some more of its | |||
| features here. Again, the material in this section is not part of | features here. Again, the material in this section is not part of | |||
| the specification per se, and implementations need not follow it to | the specification per se, and implementations need not follow it to | |||
| be compliant. | be compliant. | |||
| End of changes. 8 change blocks. | ||||
| 12 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||