Re: ENUM Privacy (was RE: [Enum] User ENUM vs Operator ENUM)

[Jim Reid <jim at rfc1035.com>]

>>>>> "Christian" == Christian de Larrinaga <cdel at firsthand.net> writes:

    Christian> just so I've got this straight! You
    Christian> propose we use the name of the domain e164.arpa (ONLY)
    Christian> by all operators on their private DNS (for
    Christian> infrastructure use and some intra-operator connections)
    Christian> as well as e164.arpa for public (for public open
    Christian> delegations)?

Yes.

    Christian> i.e., rather than setup a separate domain name by
    Christian> operators such as e164.operator.foo all ENUM is handled
    Christian> in e164.arpa public and private trees.

Yes. ENUM => e164.arpa. Always. Anywhere else isn't ENUM.

    Christian> And then to rely on the network configuration around
    Christian> that DNS to route ENUM lookups to the appropriate DNS
    Christian> server whether public or private (infrastructure)?

Yes.

    Christian> This suggests to me that you might get different
    Christian> answers to an ENUM (e164.arpa) look up depending on
    Christian> where you are?

Yes.

    Christian> How do you ensure that public e164.arpa has first
    Christian> priority so that users public ENUM NAPTR records take
    Christian> precedence over operator (private ENUM)?

You don't: that's a policy decision and implementation detail. And
anyway who's to say whether the public or private tree takes
precedence? Or even if precedence is appropriate? If my application is
in some operator's net, it looks up <number>.e164.arpa in their
private tree and the answer determines what the application
does. Likewise if it's on the internet, the application will query the
public e164.arpa tree and uses that answer. ie Where the application
lives determines what name space it gets to see and what answer the
application gets *for the same query*.

This is no different from how most big organisations do DNS today. If
something's on the corporate intranet, they see the internal name
space for example.com, complete with internal-only reachable web
sites, mail servers and so on. When something's on the internet, they
see the public face of example.com. That may or may not be very
different from the internal name space.

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