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

>>>>> "Richard" == Richard Shockey <richard at shockey.us> writes:

    >> Carrier-based ENUM is probably the easiest (maybe not the best)
    >> way to protect the privacy of customer data.

    Richard> Which BTW is why it is a good idea to keep it out of
    Richard> e164.arpa

EH? The choice of domain name has no impact on whether that bit of the
name space is public. Or private. It's all down to what data goes on
what name servers and where those name servers are located (or accept
queries from).

    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.

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. 

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.