Re: [Enum] IETF, ENUM and NGN

[Jim Reid <jim at rfc1035.com>]

>>>>> "Marian" == Marian Durkovic <md at bts.sk> writes:

    >> AFAICT nobody is suggesting Infrastructure and User ENUM would
    >> use the same tree. The constraints and data models for these
    >> things are completely different. However some people seem to
    >> think that if these two flavours of ENUM use the same domain
    >> name, this means they both have to use the same tree with one
    >> model for ownership, administration and delegation. That
    >> doesn't necessarily follow. What some operator does with its
    >> private, internal-use-only version of e164.arpa and how they
    >> populate and manage that is nobody else's concern, apart from
    >> the usual regulatory issues like universal service obligations,
    >> fair competition and so on.

    Marian> Yes it is - as soon, as you start getting complaints from
    Marian> cutomers of this operator like "why did you put into the
    Marian> e164.arpa. records which routed me to such expensive
    Marian> path?"

I think you've missed the point. If an operator has a private tree
which they use for the operation of their network, it won't ever be
visible to their end customers. No matter what that domain name is. And
if we take the way the phone system works today, nobody apart from
some telco network engineers know how calls get routed. Presumably
this is done to minimise the telco's costs and maximise its revenues.
But who can tell? You and I have no idea if our calls from Europe to
America go by satellite or under the sea or even if they're carried
over VoIP. That isn't going to change once our telcos deploy their own
DNS trees for Infrastructure ENUM.

    Marian> I'd be quite interested what will be your reaction, if
    Marian> someone makes a "private" tree overlaying the .UK TLD with
    Marian> any sort of (possibly invalid) data.

People do this already. Some people even do this on the internet for
the root zone. Provided these silly things don't interfere with the
operation of real internet, who cares what these people get up to in
their private little clubs? DNSSEC will eventually take care of those
who impersonate a domain and try to propagate bogus data.

    Marian> Generally, using the same domain name for completely
    Marian> different purposes is IMHO _very_ bad idea. There's
    Marian> absolutely no problem to avoid this by agreeing on
    Marian> different domain name - and for completely private
    Marian> purposes even non-existent TLD like e164.nxd. could be
    Marian> used which definitely can't be reached from the public
    Marian> internet.

Choosing a non-existent TLD is very unwise. What happens when ICANN in
its infinite wisdom decides to one day create the .nxd TLD?  Domain
names should never just be plucked out of the air. Especially for
infrastructure things. And yes, I am aware of the bogus .gprs TLD that
mobile telcos are using on the internet today.

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum