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

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

  • To: "Marco bernardi" < >
    "Jim Reid" < >
    "Richard Shockey" < >
  • From: "Stastny Richard" < >
  • Date: Tue, 14 Dec 2004 10:08:23 +0100
  • Cc: "Andrzej Bartosiewicz" < >
    "Carsten Schiefner" < >
    < >

I fully agree 
and this is one of the problems I see by introducing carrier E**M via a backdoor in
e164.arpa. If I am a carrier, especially a carrier acting on an international basis,
I want to implement routing mechanisms within my network and
with other networks (peers) without having to go to a NRA begging first to opt-in in e164.arpa
and second to behave according to various and different national rules.
 
A carrier E**M implementation does not need a tier 0 and tier 1, and it
is questionable if it needs a tier 2.
It needs a centralisized database operated by someone, and who this is
will be decided by the community as will be the other rules. 
This is exactly the reason why no silver tree will exist in the near future
 
-richard

________________________________

Von: enum-wg-admin@localhost im Auftrag von Marco bernardi
Gesendet: Mo 13.12.2004 08:38
An: Jim Reid; Stastny Richard; Richard Shockey
Cc: Andrzej Bartosiewicz; Carsten Schiefner; enum-wg@localhost
Betreff: Re: [enum-wg] COCOM & ENUM ... 



The probem I see is that COCOM should be not involved in any Carrier ENUM
discussion. This may create some "dangerous" confusion on the role of EC and
governments on carrier ENUM

marco
----- Original Message -----
From: "Richard Shockey" richard@localhost
To: "Jim Reid" jim@localhost; "Stastny Richard"
<Richard.Stastny@localhost
Cc: "Andrzej Bartosiewicz" andrzejb@localhost; "Carsten Schiefner"
<enumvoipsip.cs@localhost; enum-wg@localhost
Sent: Sunday, December 12, 2004 5:00 PM
Subject: Re: [enum-wg] COCOM & ENUM ...


> At 04:03 AM 12/12/2004, 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.
>
> exactly .. and BTW this is now the #1 topic of discussion within CC 1
>
>
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> 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