Scenarios for Internet fax message confirmation
draft-ietf-fax-confirmation-scenarios-00
| Document | Type |
Expired Internet-Draft
(fax WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Graham Klyne | ||
| Last updated | 1998-04-06 | ||
| 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
The simple mode for Internet fax described in [1] does not provide positive confirmation of message delivery or disposition. There is a widespread view that an important benefit of traditional fax [2] is the fact that it provides a delivery confirmation which is trusted by fax system users. This memo describes some of the options for message confirmation in Internet fax, taking account of the particular nature and goals of the application [3], with a view to informing the debate over what mechanisms should be used for this purpose.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)