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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Please read carefully:
We only delegate a numberblock when it validates (the complete numberblock) to ONE end-customer.

So for example the office of a multinational.
Consumers usually don't own numberblocks.

We don't have pre-fixes like in DE or AT. We have a fixed numberplan. All numbers have the same length, but you can own a thousand of them in one numberblock.
(or 10, or 100, or 10.000) You are not allowed to extend your numbers (on the PSTN).

The numbering plan in NL is such that numberblocks assigned to end customers are not split up. The end customer has numberportability for the complete numberblock.
When that end-customer hands in their numberblock, the ENUM delegation for that block is deleted because it doesn't validate to the one end-customer anymore.

For example, SIDN has a numberblock of 100 numbers. +31263525500 - +31263525599.
All these 100 numbers have the same end customer: SIDN.
So we delegate 5.5.2.5.3.6.2.1.3.e164.arpa to SIDN's nameservers.


> 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?

There are suppliers that want to pay for this, or for the transactions generated by this.
Or let's give another question: how much do you pay for owning a creditcard ?

> 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...

Another identity number or identifier would be fine for this as well. But everybody in the world has a phone, and a phone number. It's an already deployed and maintained globally unique identifier.

I'm thinking of things like paying at the cashier with your mobile, doing transactions on ebay, identifying you're over 18 for a porn site, getting a discount at Amazon because you can prove -online- that you're a student at a certain university that Amazon has made a deal with. that sort of identification purposes.
Hey, if the US wasn't so paranoid, it could even hold your passport :-).

> 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.

Yes, the information is not in the DNS. Some sort of secured channel XML like schema that is encrypted and can be fetched with a new sort of protocol would hold the identity data signed by the publisher (your bank f.e, your university) and these "tokens" are maintained by you. You then decide for which transactions on a website you allow which data to be decrypted for use on that transaction only. ENUM only points to the place or places that you have stored these identification tokens.
The only thing you need to type in at Amazon's website is your phonenumber, and you are automagicaly transferred to an application or secured website where you approve Amazone to get one, more, or part of your many tokens that it requires by authenticating with your password, certificate, or what level of security YOU desire for your tokens. You might even set a higher level of security for your creditcard than for your library subscription number...


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/


-----BEGIN PGP SIGNATURE-----
Version: 9.6.3 (Build 3017)

wsBVAwUBSkvBnjqHrM883AgnAQis3Af/QErF2JtqAoSzmNe9zqxbXtH1OLYCRzm9
shRq5kq9353cG9aEEUmZRihTDBZ5+awOujfvKM0TyCTHhKcb8PUyXWgFKvXS1qfQ
AHCGoEJ+Q8sAhU8Y51OHP1enZzAbo+f2BzeEgCjUCbFtI8hmBovryns1X+ssL9/k
c/pxPUTp1+QevWloSi4YemZVOIE7PfLNXbYwGes1oyYBfFE00TPfJL++n9Kjls2k
j2RGz7ZBk5qRIp4sNScogGbOwPcszjNTbE3X3D8Gr2yDtLZdC/BpdGpZpBCTTL7K
H0yrj5EjcTChM+SGRO8nLhMZ3D7dZ817VTSKc6spyNgnYgxJcfQ2xw==
=7YzU
-----END PGP SIGNATURE-----