W3C home > Mailing lists > Public > ietf-discuss@w3.org > November 2001

Re: Request for comments

From: Keith Moore <moore@cs.utk.edu>
Date: Thu, 15 Nov 2001 12:13:16 -0500
Message-Id: <200111151713.fAFHDGT05456@astro.cs.utk.edu>
To: Jasdip Singh <jasdips@erols.com>
cc: discuss@apps.ietf.org
sounds much like what the RESCAP WG is working on.  perhaps you should 
bring your proposal there.

the question is not whether this will work, but whether it's better to
put stuff in DNS or to vector it to a separate lookup service.
 
> This message is a request for comments on draft
> http://www.ietf.org/internet-drafts/draft-singh-eaddr-00.txt. This memo
> simply extends the ENUM idea in RFC 2916 to get various contact URIs
> using an email address, instead of a telephone address, as the starting
> point. The question to this group is if this is a useful idea to pursue.
> 
> 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."
> 
Received on Thursday, 15 November 2001 12:15:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 March 2006 20:11:29 GMT