ACAP TYPE Extension
draft-ietf-acap-type-ext-01
| Document | Type |
Expired Internet-Draft
(acap WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Rob Earhart | ||
| Last updated | 1998-03-13 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | anonymous%20IMAP%3A%20cyrus.andrew.cmu.edu%3Aarchive.ietf-acap | ||
| 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
The Application Configuration Access Protocol [ACAP] defines rough typing information in the form of an attribute naming convention. This extension to ACAP allows a MIME content-type/subtype with parameters to be associated with a given piece of data, providing knowledgeable clients with useful information in a way which maintains compatability with innocent clients and servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)