Some comments on the TIFF 'application' parameter
draft-ietf-fax-tiff-application-00
| Document | Type |
Expired Internet-Draft
(fax WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Graham Klyne | ||
| Last updated | 1997-12-23 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 draft attempts to clarify some misunderstandings concerning use of the 'Application' parameter with the MIME type 'image/tiff'. It is not intended to prescribe or proscribe future use of the 'Application' parameter, but simply to indicate the intention behind its introduction.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)