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

Subscribers pay per delegation.
But because in NL we have a fixed number plan, we can also delegate numberblocks of 10, 100, 1000 or 10.000 numbers.
If a numberblock can be validated against 1 single enduser, we delegate higher in the tree, and the price for 1 such delegation is higher than delegating a single number, but lower than delegating all the numbers individually.
This is usefull because our regulator does make numberblock allocation directly to endcustomers without the intervention of a real telco for medium or large companies.

What I sort of miss in this discussion is other use cases than voice.

I think ENUM has 4 use cases:

1. Service operability
2. More efficient routing
3. Numberportability
4. Identity management

The first depends on adoption of ENUM by applications. Will Skype do ENUM. Will MSN do ENUM. We have no influence on that other than promotion.

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

The third one is the regulator game. Competition and markets, replacement of SS7. It will come, but not in User ENUM.

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.
User ENUM can be that technical identifier. The only thing that's missing is a safe and standardized protocol to exchange the identity information.
ENUM can be your pointer to where my identity info is stored, possibly on multiple targets.
What is missing is the standard protocol how to retrieve my identity info, how to decrypt it with the credentials I supply during the transaction (I decide if and what info I supply to which counter party during the transaction) how to manage it as an end user, and how to verify the authenticity of the data.
I think OAUTH is a good first step, but as far as I understand it the first iteration of the protocol only has a supplier and receiver defined.
What I miss is the definition of a trusted third party that signs the authenticity of the data so the receiver can trust the data if he trusts the third party.

This is what we focus on in NL at the moment where our efforts to ENUM are concerned.
So we talk with banks, identity management startups, etc, and they are greatly interested. They only lack some experience in the standard bodies and protocol development.


Antoin Verschuren

Technical Policy Advisor SIDN
Utrechtseweg 310, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  F: +31 26 3525505  M: +31 6 23368970
mailto:antoin.verschuren at sidn.nl  xmpp:antoin at jabber.sidn.nl  http://www.sidn.nl/



> -----Original Message-----
> From: Rui Ribeiro [mailto:racribeiro at gmail.com]
> Sent: Tuesday, June 30, 2009 6:06 PM
> To: Florian Weimer
> Cc: Antoin Verschuren; enum-wg at ripe.net
> Subject: Re: [#XWM-610908]: Re: [enum-wg] ENUM Adoption - Does a business
> case matter?
> 
> 2009/6/30 Florian Weimer <fweimer at bfk.de>:
> > * Antoin Verschuren:
> >
> >> And for lager numberblocks there are different prices. One
> >> delegation of 10.000 numbers will cost 2500,-, discounts negotiable,
> >> so effectively this is 0,25 Euro per number.
> >
> > Does this mean that subscribers have to pay per extension/subdomain
> > and are not free to create all the subdomains they want?
> 
> That is a great question. What kind of services are provided by
> registrars?
> 
> - just number delegation towards the client DNS server? (the user can
> make any update, at any time, of any information. User must be savy)
> - DNS hosting for any kind of registers? (the user accesses through a
> web interface to it's own profile, and ads any kind of information in
> type, and in number. Less savy, but has to have some knowledge)
> - DNS hosting for predefined registers? (the user acesses through a
> web interface to it's own profile, and selects from predefined
> registers)
> - DNS hosting for limited predefined registers? (as above, but with a
> limited number of registers. How many?)
> - DNS hosting limited for SIP? (as above, but only allowing SIP
> records. Maybe even accepting only URI putting all the information
> "around" them automaticly)
> 
> Do you have others?
> 
> Thanks,
> 
> Rui Ribeiro
> racribeiro at gmail.com