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

RE: [enum-wg] Concerning Wildcards and I-ENUM

  • From: "Antoin Verschuren" <Antoin.Verschuren@localhost
  • Date: Mon, 9 Oct 2006 13:24:41 +0200

Otmar Lendl wrote:

> Corrolary: The ENUM v2 scheme that Patrick and Olof came up with will
> neither solve User-ENUM vs. I-ENUM branching, nor will it be suitable
> for an I-ENUM deployment in a country with an open numbering plan.
> 
> Please convince me that I'm wrong about this one.

Hi Otmar,

I have expressed the same worries about it, and Patrick and Olaf
considder this a layer nine issue rather than something they're trying
to solve.
Not only for open numbering plans, but also for block allocations, ENUM
v2 offers no solution for the authority over the delegation problem.
I considder this the real issue, and even though ENUM v2 will solve
direct querying for specific records, the increase in delegation points
will not have any value for non fixed length numbers, and might even
confuse people even more.
But they do have a valid point when they say that any (new) type of
operator might claim their own tree to control their ENUM space, and we
need a solution for that. I think that differentiating should take place
as close to the root as possible to make sure that implementation is the
same around the world, and applications know where to query.

Antoin Verschuren

Technical Advisor
Policy & Business Development
SIDN
Utrechtseweg 310
PO Box 5022
6802 EA Arnhem
The Netherlands

T +31 26 3525510
F +31 26 3525505
M +31 6 23368970
E antoin.verschuren@localhost
W http://www.sidn.nl/




 

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