ENUM, E.164, and Internet Fax
draft-gallant-enum-ifax-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Gallant | ||
| Last updated | 2000-11-30 | ||
| 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
E.164 numbers are often used for fax addresses. Internet fax provides store-and-forward (T.37) and real-time (T.38) modes. Subscribers could use ENUM to store Internet fax preferences in DNS under their fax numbers. Network devices could then query DNS to retrieve that information. An example is subscriber preferences for receiving faxes via Internet mail or SIP delivery. Further work on ENUM for Internet Fax is indicated, one example being H.323 delivery. Policy aspects are out of scope of this draft. This document is not associated with any working group. Comments may be sent to the author.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)