- enum-wg - mailman.ripe.net

4.4.e164.arpa
by Christian de Larrinaga 21 Dec '09

21 Dec '09

In http://www.itu.int/dms_pub/itu-t/oth/02/08/T02080000010005PDFE.pdf dated June 2009 It shows 44 UK as delegated to DTI/Nominum as of 16/05/02 Is this the correct official status of this zone? Christian Christian de Larrinaga

3 3

ENUM: Some conclusions
by Rui Ribeiro 21 Dec '09

21 Dec '09

Hi all, As you know, I'm writing a thisis on ENUM adoption in Portugal. Most of the conclusions can be extended worldwide, since the problems are a bit the same everywhere. I would like to get some answers/ideas from you about some of the conclusions I'm getting at: * lack of interest from operators (lots of things were writen already) * no very good business model (it is sustainable, but won't get you rich) * externality (the guy that receives the call has to pay for the registration, the benifit goes to the caller) * ... (many more were discribed on my presentation on RIPE-59) A couple of new ones: * the political mistake (user enum was designed to be delegate to each country. Although that makes somes sense it rises a lot of problems. If you realize that User ENUM is a service for User VoIP and that User VoIP runs over User IP (common known as Internet), than you understand that User ENUM should be managed somehow like User IP. I think that User ENUM should had got, in the early days, a all new prefix that should be delegated to the LIR's (just like the IP address space). That would solve a lot of issues...) [if anyone has some kind of documentation from the early days explaining why the country delegation, I would very, very appreciate] * lack of trust of the information on the tree (we all work on the internet, most of it is "benign", but "cheat happens"! For most of us this is bearable, and it's fine. But what about your grandma? What from the operator point of view? What about the "universal telephone service? I think that the concept of having information on the tree that isn't (for sure) reliable is the main drawback for operators to embrace user enum. The other issue is how do you charge a call... it is alot more dificult than you may think. What if the user enum record points to a international number using "tel:" prefix? what should the operator do? An IVR advising the user about the call? make the call and charge it quietly? What if it is a "value added number"? ...) I'm thinking on writing the thesis in English, opposing to Portuguese. What do you think? Will it worthwhile my extra effort? Do you think this kind of information would be usefull to you? Thanks for you time and Merry Christmas! Rui Ribeiro racribeiro(a)gmail.com

1 0

Query statistics
by Eduardo Júnior 07 Nov '09

07 Nov '09

Hi, is there some domain that publishes your query traffic statistics? Maybe 3.4.e164.arpa or 0.4.e164.arpa that have more ENUM entries? I'd like to have an estimate of request from the real environment to do some performance tests. Thanks, -- Eduardo Júnior GNU/Linux user #423272 :wq

1 0

ENUM - do you trust the other guy? are you ready to go without DNSSEC?
by Rui Ribeiro 02 Nov '09

02 Nov '09

Hi all, Last week I was talking with some guys, and I had same new/old view of the ENUM problem... do you think that the DNS records are reliable? will they allways be reliable? Let's supose something... I have this problem... I have a register on ENUM, but there isn't any gain for me with it. What if I register on my number a "tel:" (or any other kind of) register to a "number" that I receive a fee when someone calls? Since most of the VoIP systems are enabled to try to reach the number, what ever is the answer (sip, tel, ...), it will (most likely) call the "tel:" register, no questions asked! The user would get the call and pay (a lot more than e could anticipated), the callee would answer the call and receive money from it. Would you trust an ENUM record to a number/address that you don't no nothing about? I don't know how the valued added numbers are on the other countries. As well as I know, any number can be a legit number... but, in fact, it may be a really expensive number! You may say... well, that's not a bad thing and there are ways to prevent it, and so on... are there really? Some possibilities: 1. IVR on each caller PBX stating that the number being called is not what the user has dialled; 2. caller PBX understands that the number being called is not what the user has dialled, blocks call; 3. don't look/accept at "tel:" records to numbers/prefixes that aren't trusted/allowed; 4. list the ENUM records prior to effectivly dial the call (as I've seen on the ENUM android client, but impossible to make available to all the user terminals worldwide). This has a faillure... it depends on the caller PBX (permanent) configuration and the hability for the user to understand what it implies. Let's say that you trust the other guy. Are you ready to go without DNSSEC? What if, someone (aka hacker) has changed your good and reliable ENUM records to some kind of trickery like described above? The more it goes, the more I think that "User ENUM" shouldn't aspire to superimpose the numbering of telcos worldwide. The user my be "confused", the regulators and telcos are getting crazy, ENUM doesn't start althought it is very promissing to some parts of the emerging markets. Is there any (wild) chance that RIPE would start to manage E164 numbers on e164.arpa tree? The e164 CC would be some unused yet (refering to the Internet and not any geo-location), It could be IP style managed where LIR's would be tier-2 registrars. This way we, the users, could benifit from being on "the" big, oficial, reliable, trusted tree without the hassle of managing the numbers with regulators and operators. That prefix would define "User Internet VoIP" worldwide, which would be much easier to market and for operators to interconnect with later on. (please flame me... I feel I'm going into the dark side!) Rui Ribeiro racribeiro(a)gmail.com

1 0

Could Web 2.0 be the killer application for ENUM?
by Rui Ribeiro 29 Oct '09

29 Oct '09

Hi All, Today I was thinking on diferente applications for ENUM. While VoIP is a nice (killer app), it "seems" to confict with established businesse models and services. What about if there is other applications that could use ENUM that are based on a completly different model? Some of the biggest rising applications on the WEB are Facebook, Twitter, ... and so on. They provide some kind of communication, in fact, it's a mix of: instant messaging, picture sharing, presence, ... and all together. In fact, there are some subset web applications that, together, can provide to the used most of their digital needs. If you have visited and used them you may know that there are some features that are better on one site, and others better on others. Not because they are technicaly better, but because you, as a user, like them better. Then I was thinking about ID's on this diferent web 2.0 services. If you have a bizard name, you are lucky, but if your name that conflicts with another user on the Internet, you are in trouble. You have to come up with lots of diferent ID's for diferent services. Then there is another issue... what if I don't like "facebook" anymore and now the hipe is on "bookface" (another web 2.0 application, similar to facebook)? My social network will just paralise on facebook, and I would have to republish on "bookface". What if my microblogging site starts to be other than twitter, what would happen to all my followers? What if ENUM could provide references to microblogging site, to presence site, picture sharing, ...? Yes, I now that Web URL's are already enabled on ENUM, but I'm thinking a little further... what if we could publish the URL with the application type reference, not just the WEB site. It happens already with VoIP, where the register states the type of protocol that should be used: SIP, h323, tel, ... Technically everything is possible on ENUM, as it is a swissknife where each blade is made out of RFC's. ;-) The benifit for the user could be the ability to point all the applications to the ENUM number, and the applications would then go and get the information on the right place. Why publish the microblogging link, the presence/status link and so on if you could just publish your ENUM number? All the followers would just following you any way, even if you change the application. For ENUM, it could be an application outside of the "voip box" that could push to the forefront of the innovation wave. Think of ENUM register as a personal ID, and not as a phone number... is this a bad assumption? I know that the number is given by the teleco industry/regulator and not by the state it self, but what is you phone number other than you personal ID? With portability services (hopefully) we could maintain the same number for ever, right? Thanks, Rui Ribeiro racribeiro(a)gmail.com

1 0

British Telecom ENUM service???
by Richard Shockey 13 Oct '09

13 Oct '09

I thought I'd share here ... http://www.globaltelecomsbusiness.com/Article/2308733/Sectors/25205/Business -models-through-interoperability.html Richard Shockey PSTN Mobile: +1 703.593.2683 <mailto:richard(at)shockey.us> skype/AIM: rshockey101 LinkedIn : http://www.linkedin.com/in/rshockey101

3 6

Start of the ENUM WG session at RIPE 59 on Friday
by Carsten Schiefner 07 Oct '09

07 Oct '09

Dear RIPE 59 attendees, due to the fact that the ENUM WG has a rather short agenda this time the two ENUM WG Co-Chairs, Niall O'Reilly and me, came to the conclusion that 60 minutes should be enough to cover all agenda items. We are therefore happy to be able to resurrect an old tradition - at least for this meeting - and have the Friday morning session starting at 9:30 only. :-) Please spread the word amongst those of your attending colleagues that might not yet have heard about it. Thanks and best regards, Carsten Schiefner ENUM WG Co-Chair

1 0

Agenda for ENUM-WG at RIPE 59
by Niall O'Reilly 21 Sep '09

21 Sep '09

ENUM-WG Colleagues, Here is the proposed agenda for the ENUM-WG session at RIPE 59. There is time for a little more, in case of any last-minute inspirations. If so, please let Carsten or me know. Meeting Team, could you please do the magic to place this on the meeting web-site? Thanks in advance. /Niall -- 09:00 Friday, 9 October 2009, Corinthia Hotel, Lisbon -- A: Administrivia (5 min) Welcome, Scribe, Jabberwok, Microphone etiquette, Agenda B: Note Minutes of ENUM-WG at RIPE 58, Amsterdam (1 min) C: Review Action List (4 min) 58.1: question to list re statistics on non-delegated country codes (Carsten Schiefner) [DONE] D: (09:10) Main presentations (30 min: 40/90 09:40) D1: NRENUM.net on the Portuguese NREN (VoIP@RCTS) (Rui Ribeiro, 15 min) D2: Portuguese ENUM, why doesn't it rise, why doesn't it die! (Rui Ribeiro, 15 min) ... E: (09:40) ENUM Operations (15 min: 55/90: 09:55) E1: Tier-0 Report (Anand Buddhev, 15 min) ... F: (09:55) Short News F1: enumdata.org update (5 min: 60/90: 10:00) ... G: Discussion on Plenary presentation: [Placeholder for 'G': nothing planned this time] X: Interaction with other working groups [Placeholder] Y: AOB Z: Close (5 min) Summary of action items -- 10:30 Coffee --

1 0

issues with tinnie.arin.net?
by Alexander Mayrhofer 08 Sep '09

08 Sep '09

Hi everyone, Sorry if this is OT to this list - but it seems as if "tinnie.arin.net" (one of the authoritative DNS for e164.arpa) seems to have issues: It *looks* as if one of the two nodes (?) is not configured for e164.arpa anymore (see below - one try successful, one fails - and that changes pretty much on every try) Could someone from RIPE staff look into that problem, please? Thanks, Alex Mayrhofer Nic.at/enum.at axelm@kahua:~$ dig @tinnie.arin.net ns e164.arpa. ; <<>> DiG 9.5.1-P3 <<>> @tinnie.arin.net ns e164.arpa. ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2533 ;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;e164.arpa. IN NS ;; ANSWER SECTION: e164.arpa. 14400 IN NS tinnie.arin.net. e164.arpa. 14400 IN NS e164-arpa.cnnic.net.cn. e164.arpa. 14400 IN NS ns-pri.ripe.net. e164.arpa. 14400 IN NS sec3.apnic.net. e164.arpa. 14400 IN NS sunic.sunet.se. e164.arpa. 14400 IN NS ns0.verio.net. ;; ADDITIONAL SECTION: sec3.apnic.net. 3600 IN A 202.12.28.140 sec3.apnic.net. 3600 IN AAAA 2001:dc0:1:0:4777::140 ;; Query time: 121 msec ;; SERVER: 2001:500:13::c7d4:35#53(2001:500:13::c7d4:35) ;; WHEN: Tue Sep 8 15:57:05 2009 ;; MSG SIZE rcvd: 239 axelm@kahua:~$ dig @tinnie.arin.net ns e164.arpa. ; <<>> DiG 9.5.1-P3 <<>> @tinnie.arin.net ns e164.arpa. ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 24369 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;e164.arpa. IN NS ;; Query time: 127 msec ;; SERVER: 2001:500:13::c7d4:35#53(2001:500:13::c7d4:35) ;; WHEN: Tue Sep 8 15:57:06 2009 ;; MSG SIZE rcvd: 27

2 1

Second call for RIPE 59 ENUM WG agenda
by Carsten Schiefner 04 Sep '09

04 Sep '09

Dear ENUM WG colleagues, we are just a little more than four weeks away from RIPE 59 (5-9 October in Lisbon, http://www.ripe.net/ripe/meetings/ripe-59/ ) - and time flies even more now. Niall and I are still looking for input from you all for the agenda of the ENUM WG for this meeting: offers to give presentations, suggestions for presentations from others, and warnings of topics to avoid for lack of interest. To begin with, here is a list of 'regular' topics we usually cover during an ENUM WG session: - Updates from countries with 'significant' developments - ENUM in production: operations, uptake, strategy Best regards - and we look forward to seeing many of you in Lisbon in early October: Carsten Schiefner Co-Chair, RIPE ENUM Working Group

1 0