[enum-wg] market potential/future for public ENUM

On 06/02/2011 10:45 PM, Jim Reid wrote:
> On 2 Jun 2011, at 14:15, Ričardas Pocius wrote:
> 
>> I do not understand people writing LNP/MNP data should no be in public
>> zones; there is no private data there, just technical information how
>> (where) to route calls properly.
> 
> Many telcos consider that sort of information to be not just private,
> but highly sensitive. For instance it discloses info about the ingress
> and egress points to/from their networks: where their SBCs and SS7
> switches are located, network topology, etc. The industry obviously
> needs to know this stuff. It's debatable whether it should be known to
> the general public.

That must depend on LNP/MNP solution. We only store number -> SP ID
(routing prefix) mappings. No INGRESS/EGRESS SPCs, no IP addreses of SBCs.

> 
> A public NP database brings other concerns too. It opens up a new vector
> for slamming. It would publish info about which numbers are active
> and/or ported in a number block. If I was running a telco, I'd not be
> too keen on making that sort of information available to my competitors.
> It would also be too easy for telemarketers to mine that public database
> and harvest all the unlisted phone numbers.

Again implementation specific ... we do not treat ported numbers as
exceptions in dial plan. We have no blocks anymore. An assignment can be
as small as one national number. We have mappings for all assigned
numbers (not just active) to SP ID (routing prefixes). Number porting is
process of re-assigning number from one SP to another. When you have all
assigned numbers in database it is not easy to find out what number are
ported and not just assigned. You can always compare whole dataset time
after time to find out changes ... hm hm with some harvesting effort.
Hey new killer application for botnets...


-- 
Best regards,
Ričardas Pocius
CTO
UAB „Mano numeris“
tel:+37068678511