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: "Jim Reid" < >
  • From: "Stastny Richard" < >
  • Date: Mon, 13 Dec 2004 11:23:46 +0100
  • Cc: "Andrzej Bartosiewicz" < >
    "Carsten Schiefner" < >
    < >

>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 [
] Gesendet: So 12.12.2004 10:03 An: Stastny Richard Cc: Andrzej Bartosiewicz; Carsten Schiefner; enum-wg@localhost Betreff: Re: [enum-wg] COCOM & ENUM ... >>>>> "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.

<<< 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