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: AW: [enum-wg] COCOM & ENUM ...

  • To: John C Klensin < >
    Jim Reid < >
  • From: Richard Shockey < >
  • Date: Tue, 14 Dec 2004 16:24:27 -0500
  • Cc: John-Erik Horn < >
    "'Stastny Richard'" < >

At 03:33 PM 12/14/2004, John C Klensin wrote:



--On Tuesday, 14 December, 2004 19:57 +0000 Jim Reid
jim@localhost wrote:

>     Richard> ..maybe the carriers will go back to the ITU and
> get     Richard> e164.int and we can end this issue once and
> for all.

Richard, independent of any other issues, e164.int would violate
the narrow reading of "international organization" that ITU
itself has been advocating for .INT.   Whatever "e164" might be,
it is not an international organization under that, or any
sensible other, definition.
Fair enough John .. but you understand the basic problem here. The pressure to force the architecture of 3761 into doing things it was not generally intended to do is creating yet another barrier to adoption.

At the request of the AD's I'm working on a draft right now that is trying to at least scope the problem and I'd be personally delighted if you'd take a look at it and add your thoughts and or comments. You certainly have a unique insight into the historical problem statement.


> Hmm... How long do you think it would take ITU to set up
> processes and cost-recovery mechanisms for this? IIUC ITU has
> still not decided whether ENUM should be anchored in the
> public e164.arpa infrastructure or a new TLD owned and
> operated by ITU.

Assuming ITU could get such a new TLD, which raises a whole
group of additional questions.  To summarize them, don't hold
your breath.
I wont I'm hoping to live a bit longer . :-) I'm just thrashing around looking for a solution that meets the carrier requirements but at the same time does not break SIP behavior or 3761.


> According to IANA, it's the IANA registry that manages .int,
> not the ITU. BTW the DNS infrastructure for .int is nowhere
> near the levels of robustness and global presence that .arpa
> has.

It is perhaps not an accident that .ARPA was chosen ;-/

     john (one of the guilty parties)
yes indeed ...present at the creation so to speak .. :-)



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




  • Post To The List:
<<< 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