Email Address and NAPTR RR (EADDR)
draft-singh-eaddr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jasdip Singh | ||
| Last updated | 2001-10-23 | ||
| 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
ENUM uses NAPTR DNS Resource Records (RRs) to map an E.164 telephone number to Uniform Resource Identifiers (URIs) of other ways of contacting (for example, by email) a specific resource. This memo proposes an ENUM-like service called EADDR where an email address, instead of a telephone number, is used as the key to fetch other contact URIs. At human level, EADDR seems more useful than ENUM because it is easier to remember an email address than a telephone number as the key. At machine level, both services are equally useful.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)