About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: [enum-wg] COCOM & ENUM ...

  • To: "Conroy, Lawrence (SMTP)" < >
    Jim Reid < >
  • From: Richard Shockey < >
  • Date: Sun, 12 Dec 2004 12:38:39 -0500
  • Cc: Stastny Richard < >
    Andrzej Bartosiewicz < >
    Carsten Schiefner < >

At 04:41 AM 12/12/2004, Conroy, Lawrence (SMTP) wrote:

Hi Jim, Richard, Andrzej, Carsten, Folks,

  Andrzej does have a production system up and running, which is a
heck of a lot faster than some countries.
Its easy when you can start from scratch and have intelligent and sympathetic regulators.


It's a shame if an end user (you know, the person who pays for all these
high quality services) can't choose their own ENUM entries. However, that's
no change from the current situation, so maybe this is no big deal.
This IMHO will cause Poland a problem over time as ISP who want to sell advanced services then realize they have to go through the incumbent to get registrations processed. But this is as we all know is a national matter and seeing how Poland deals with this will be very interesting to watch.


Poland has also avoided the hoops over Authentication that have hypnotised
other Countries. I am a little concerned that any TSP can register any number,
but that's something for them to argue about amongst themselves.
Authentication is not hard if your country has independent databases that can confirm the number holder. North America will not have that problem.


The only way we could have a more efficient system is to de-couple telephone
number service provision from eligibility for registration entirely - say, if
some named person or organisation had the delegation for a CC, and then chose
their own policy on who got what.
Or make all the service providers all go back to the ITU and get e164.int so they can do their own thing and not bother the rest of us.

Or they could use existing LNP databases ... ( ok that sounds really self serving )

Its my intention to have some sort of ID on Infrastructure TN2URI issues available shortly but I've been completely tied up here with US service providers who have begun to wake up to the fact that the lights they see in the distance really is a freight train. [news item below]

Note here 70% of US consumers who switch to Cable Based VoIP telephony actually port their primary number.

IFrom: "Bourkoff, Aryeh" <aryeh.bourkoff@localhost
To: "Bourkoff, Aryeh" <Aryeh.Bourkoff@localhost
Cc: abourkoff@localhost
X-OriginalArrivalTime: 09 Dec 2004 15:02:28.0767 (UTC) FILETIME=[19D062F0:01C4DE00]
Sender: owner-ml-stm-Aryeh-Telecom-ext@localhost
Precedence: bulk
X-UBS-Disclaimer: Version $Revision: 1.26 $
X-IMAPbase: 1100136599 4982
Status: O
X-UID: 4977
Content-Length: 80823
X-Keywords:


Time Warner Cable: Takeaways - 32nd Annual UBS Global Media Week Conf

* Time Warner Cable: Presentation at Media Week
Today, Time Warner Cable Chairman & CEO Glenn Britt, presented at UBS' 32nd Annual Media Week Conference.

* VoIP Rollout On Track, Anticipate 200K YE Subs
VoIP has been launched in 30 of 31 systems & remains on track for YE04 full rollout, with est'd cap investment ~50% lower vs. circuit switched. Mgmt expects 200K YE subs, & is approaching 10K weekly adds. 75% of new phone customers are porting numbers, indicating a switch of primary lines.


At least we would be saved from the endless discussions on industry self-regulation
and policy advisory groups (plus their membership, whether or not they are
representative, and the powers of the groups).

At present, I can't officially register "my" ENUM in a production system.
If someone else registers it (or a TSP registers it) I can't either. What's the
difference (apart from years of fruitful discussion on the interpretation of the
framework directives and whether they apply to a DNS system or IP addresses)?

all the best,
Lawrence

On 12 Dec 2004, at 09:03, Jim Reid wrote:
"Richard" == Stastny Richard <Richard.Stastny@localhost writes:
    Richard> There is only one "minor" problem with the implementation
    Richard> in Poland: It is Carrier E**M in e164.arpa

And the problem is......? IMO the only potential problem with this is
that private data could be made public through the DNS.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza - Sterling, VA 20166
sip:rshockey(at)iptel.org sip:57141@localhost
ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community