[enum-wg] ENUM contact info should show up in LDAP

-----Original Message-----
From: enum-wg-bounces at ripe.net [mailto:enum-wg-bounces at ripe.net] On Behalf
Of Jim Reid
Sent: Monday, March 18, 2013 12:32 PM
To: Rick van Rein (OpenFortress)
Cc: RIPE ENUM WG
Subject: Re: [enum-wg] ENUM contact info should show up in LDAP

On 18 Mar 2013, at 15:47, "Rick van Rein (OpenFortress)"
<rick at openfortress.nl> wrote:

> What is the opinion about such a translator on this list?

I think it's a waste of time. User ENUM is dead. Sorry. Some sort of
LDAP-DNS shim might be interesting as an academic exercise but its
real-world utility seems doubtful at best.
[RS> ] Totally agree.  

I don't understand how or why LDAP could be better than DNS for publishing
or updating contact data. Sure, you could get better authentication with
LDAP, but is that scalable and worth the effort? It's not clear to me why
someone would choose to use a heavyweight LDAP transaction instead of a
lightweight DNS lookup or dynamic update. There could be a role for LDAP in
Carrier ENUM (handwave!), 
[RS> ] 
[RS> ]  The only activity now deploying is Carrier ENUM.  The private closed
exchange of SIP interconnection data by some mutually agreed to methodology,
which more often than not, ends up being an Excel spreadsheet.  Even the
access to the Carrier ENUM data is probably evenly divided now between 6116
and SIP Redirect. You get a lot of advantages by using SIP as a localized
the interconnection database. LDAP performance is the key issue.  



though how that would intersect stuff running on desktops or mobile devices
is a bit of a challenge.

User ENUM-based applications and services using DNS have pretty much
flopped. How would new stuff based on LDAP change that?