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

--On Tuesday, 14 December, 2004 19:57 +0000 Jim Reid
<jim at rfc1035.com> 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.

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

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