[enum-wg] COCOM & ENUM ...

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

He Jim, not again this one.

This is exactly the reason why ENUM is end-user opt-in.

BTW, in some countries there exists already a database (in this case 
opt-out) where even the names and addresses of telephone subscribers
are stored -

it is called the "public phone directory"

Of course, because of the opt-in/opt-out feature you may not use these
directories for call routing

-richard




________________________________

Von: Jim Reid [mailto:jim at rfc1035.com]
Gesendet: So 12.12.2004 10:03
An: Stastny Richard
Cc: Andrzej Bartosiewicz; Carsten Schiefner; enum-wg at ripe.net
Betreff: Re: [enum-wg] COCOM & ENUM ... 



>>>>> "Richard" == Stastny Richard <Richard.Stastny at oefeg.at> 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.