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

["Christian de Larrinaga" <cdel at firsthand.net>]

-----Original Message-----
From: Jim Reid [mailto:jim at rfc1035.com]
Sent: 29 June 2004 17:49
To: cdel at firsthand.net
Cc: Stastny Richard; enum at ietf.org
Subject: Re: ENUM Privacy (was RE: [Enum] User ENUM vs Operator ENUM)


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

    Christian> cdel:--< what specifically do you propose? It sounds
    Christian> like you are proposing non routable private e164.arpa
    Christian> zones behind firewalls?

In simple terms, yes. Sort of. Each operator has their own e164.arpa
tree which is private to them and used for internal purposes like call
routing. These trees won't need any opt-in principle as they could be
used for all numbers served by the operator, including unlisted ones.
Some operators may want to share or link their private trees, for
example in some sort of joint venture. This is one reason why these
trees should be anchored under a single domain name.


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

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

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

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

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



    Christian> cdel:---< By infrasructure ENUM do you mean ENUM that
    Christian> is not e164.arpa and is established for and by
    Christian> operators to interoperate between each other in
    Christian> particular when a e164 number is not entered into the
    Christian> e164.arpa tree? i.e., not the operator's internal
    Christian> private ENUM tree nor e164.arpa but something else?

No. ENUM is when an E.164 number is entered under e164.arpa according
to RFC3761. Infrastructure ENUM is when an operator populates their
private e164.arpa tree and uses the data there for internal purposes
such as call routing. End users will have no access to this tree or
direct control over what's stored there. Operators might or might not
choose to expose these private trees to each other.

E.164 numbers entered under any domain name other than e164.arpa don't
comply with my understanding of ENUM: ie RFC3761.

cdel:--> a point well made :-)


Christian


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