Re: [Enum] RE: Draft IETF ENUM usage scenarios

[Mats Dufberg <dufberg@telia.net>]

On Oct 16, 2002, 10:20 (-0400) Lind, Steven D, ALASO <sdlind@att.com> wrote:

> The ENUM WG is starting out with the premise that one only knows an
> E.164 telephone number instead of an email address. One could imagine
> that instead of a number, you could use a unique FQDN, e.g.,
> steven.d.lind.name, that could point to the various NAPTR records.
> That would require the application software to behave differently than
> looking up a telephone number. And the problem with uniqueness of the
> names would not guarantee that you've reached the right steven.d.lind
> (I know of several Steven Linds, not sure about those with same middle
> initial).

I don't think that we should try to force everything into DNS. There is
already a service responsible for mail addresses -- mail service.

To me it seems simpler to update the SMTP protocol by adding a new
command, say, INFO, to the nameserver in charge of the maildomain
telia.net according to the MX record.

  INFO dufberg@telia.net

which would or could return a list of URL:s for that address, or maybe a
referal to another SMTP server holding the data. Mailservers know about
mail addresses.

In order to force mailaddresses into DNS we would have to invent a
conversion from mailaddress into domain. The allowed characters in the
mailbox part is different from the characters that can normally be used in
DNS. The mailbox part is case sensitive.



Mats

----------------------------------------------------------------------
Mats Dufberg				             Registry TeliaNet
dufberg@telia.net                                          Skanova/Nwi
+46 8 71 354 38                                Mårbackagatan 11, hus L
+46 70 258 2588                                       SE-123 86 Farsta
----------------------------------------------------------------------

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum