Re: [Enum] Reverse ENUM

["James Seng" <jseng@pobox.org.sg>]

I hate to be the one pouring cold water on this stuff but...I probably
should inform the group that there was a patent filed in Oct 2001 by my
previous employee on a titled 'Phone Name'. The broad claim involve using
the DNS to resolve a name into a tel: or fax: URL via NAPTR records.

In a couple of months, it should appear on the USPTO website.

Regardless of the merits of the patent filing, the group should take note of
this IPR.

-James Seng

> At the last Pulver Conference in Atlanta VON Fall2002 the idea
> of "Reverse ENUM" was discussed at various places. Even Vint Cerf
> mentioned it in his speech. BTW, Vint Cerf talked about 10 min about
> the importance of ENUM and Rich nearly got a heart-attack because
> he had no voice-recorder on ;-)
>
> The principle of "Reverse ENUM" should be, that in the same way
> you use a client querying for an E.164 Number in the format +1234xxx
> you may use the same client entering user@foo.bar. The idea is,
> that in the domain foo.bar somewhere a NAPTR? is stored pointing
> to the ENUM entry for the phone number (e.g. with a tel: or enum: URI).
>
> The user would always get the same information regardless if he
> is entering either the +431xxx or the user@foo.bar. One simple
> approach was (as proposed by Rich et.al) to store the NAPTRs?
> by convention in subdomains user.at.foo.bar of the domain foo.bar.
> A more sophisticated approach may retrieve the "user" part with a
> ldap pointer from the mail or sip server.
>
> Michael, since I do not fully understand your example and also your
> (soon to come) RFC3404, (I tried, but it gave me a headache)
> could you please elaborate more on your proposal, to enlighten me ;-)
>
> Best regards
> Richard Stastny
>
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www1.ietf.org/mailman/listinfo/enum
>


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