[#XWM-610908]: Re: [enum-wg] ENUM Adoption - Does a business case matter?

Hi all,

> But because in NL we have a fixed number plan, we can
> also delegate numberblocks of 10, 100, 1000 or 10.000 numbers.

!!! But the delegation from the registry is by prefix (only one
register for each kind of delegation), or by number (there is a price
reduction, but each number has it's own register)

For me, only the second solution can be used. The first one, while
more pratical and easy to deploy, may have a hard time longer on when
the numbers start to "float" away in things like: renumbering, number
portability, fusion/cisions of companies/users, ...

If you delegate to the registrar A, 1000 numbers and the 352, for some
reason (later), has to be moved away or unregistred from the tree on
that registrar, how do you/they handle that?
1. substitution of 1 record for 999 records ant the registry?
2. substitution of 1 record by the last numbers of records possible,
at least: 27 records...

Either way, there are changes that have to be coordenated by the
several DNS administrators. This is why I defend the solution, one
number, one delegation.

> I think ENUM has 4 use cases:
>
> 1. Service operability
> 2. More efficient routing
> 3. Numberportability
> 4. Identity management

> The second is the telco game, or individuals that have enough knowledge and effort to bypass telco's. This is the voice game. Too political. Too financial

I believe that terminals will be easy enough to use directly, without
"savy users". The miss of terminals is because of the lack of
infrastructure... (ENUM isn't in place)

> The last one is often forgotten, but I predict this will be a big one in the time to come.
> It's OAUTH, OPENID, that sort of game.
> It's everyone that seeks a way to identify customers, customers need, or customers preferences to be able to give the customer what he wants the easy way.
> Almost every bank, webshop, bookstore club or social network has identity information stored, and is seeking for a global, standardized identity parameter to address an end user.
> Everybody has invented or is using his/her own system.

Do you think that users are willing to pay for this? What about
companies? Would they make public this "ENUM" tree? or would be for
internal use?

Do you think that identity management makes sense? why? Are you
thinking about "presence", emergency location, or other? Should a
"identity management" system be based on another number rather then on
the telephone number? Should ENUM "tecnology" be used on other
services like... the index number insted of being the phone number
could be the social security number... We then could call the Id, not
the phone...

> User ENUM can be that technical identifier. The only thing that's missing is a safe and standardized protocol to exchange the identity information.

There are a few things... but clearly much "bigger" than what a DNS
register would hold. Maybe a URI to another locaion where there would
be a XML file would be ok.

> This is what we focus on in NL at the moment where our efforts to ENUM are concerned.

Thanks for you contribution!

Rui Ribeiro
racribeiro at gmail.com