[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Enum] A proposal for Carrier ENUM



Title: Re: [Enum] A proposal for Carrier ENUM
Lupton, Ronan wrote:

Klaus, Rick, Richard,

Maybe NRAs don't have detailed numbering data, for the purposes of daily admin.

But at least they will have administrative or strategic visibility and statistics on national porting activities and know who donors and recipients of numbers are, exactly.

In the EU 25 countries the European New Electronic Communications Regulatory Framework directive and Universal Service directives mandate the NRA ownership of national numbering resources along with the national administrations.

Provisions are in built to the USO directive recitals 40 to 42 and Article 30 is where you can find the suite of porting reference data.

But without Thick Registries of data NP is very difficult to maintain or adminster. There is a wide body of experience on this matter  in the US and Canada as you well know. The centralized database system here works, works well and has proven to have enormous advantages to carriers that they did not immediately realize such as fast technology upgrading and "network grooming" of switch resources. The EU needs to reckgonize this ..especially now with emerging ENUM adminstrations.

Note the consumer aspects and pro competitive aspects of same.

From a PSTN point of view, both databases and onward routing can unilaterally or co-exist. These decisions are historically entrenched in administration matters including numbering policy and costs of implementation at a national, fixed line and mobile/GSM level.

Well ..its really a cost issue first ..some one has to pay for centralized databases. Second incumbents do not like LNP, never have and never will. NRA's simply have to put their foot down and demand compliance.

For ENUM and its origins at the beginning, my understanding is that if was derived in order to assist with Number and address portability in the Swedish market.

Yes ..that was Patrik's first thought on the matter ....long long ago.

This discussion might assist in a numbering administration and spectrum tidy up. E.g. ENUM early days.

I can send these directives out for your perusal if you like.

URL's might be useful here ...but again I'm emphasizing the critical requirement for Thick ENUM Registries irrespective of its use in Public or Carrier only environments.

Build it right the first time and you save the industry and the regulators huge headache's in the future.

This, of course, leads to one of my favorite topics which is standardized provisioning interfaces to the ENUM registries.

Nothing will work if you cant get the data into the ENUM Registry in the first place.

Ronan Lupton

MCI International Regulatory Affairs.




-- 


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Director - Member of Technical Staff
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   sip:57141(at)fwd.pulver.com
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>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum