Deflate and Deflate-base64:Compression Content-Transfer-Encodings
draft-freed-newenc-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ned Freed | ||
| Last updated | 2000-04-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines two additional content-transfer- encodings, deflate and deflate-base64. Adding these CTEs to MIME that provide facilities for loss-less, adaptive, general-purpose compression. The first of these, deflate, produces binary output, while the second, deflate-base64, produces the same sort of output as the base64 content- transfer-encoding defined in [RFC-2045].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)