[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

At 04:23 PM 6/29/2004 -0400, James McEachern wrote: 
Mike,

   > If I understand correctly this could be a 3-stage process:
   >
   > 1) PSTN call causes NP dip and resolves to an IP-domain indication
   >     Local database determines TDM routing to IP Gateway
   >     PSTN call routed to nearest IP Gateway
   >     (optional if call originates in IP)

Does this mean that ENUM is only available to numbers that have been
"ported out" to the IP-domain, and are marked as such in NP databases?

I was focusing on what happens to E.164 numbers that do port to the IP domain, but do not preclude the use for numbers that had not. My issue was not so much for those that do use ENUM as it is for those E.164 users in the IP domain that do not have some minimal ENUM presence even in the form of a fronting carrier.

   >
   > 2) Public ENUM search resolves to Service Provider (SP) URI address
   >     DNS search gives corresponding IP address
   >     IP setup message routed to SP
   >     (SP is public operator/carrier, enterprise, or opt-in end-user)

I thought that the ENUM search returned the full URI, although in the case
of SIP the initial routing might be on the basis of just the domain.  Again,
in the case of SIP, isn't step 3 really performed by the SIP proxy the
target user has registered with, rather than by ENUM?

I was leaving the nature of the content of the local part of the URI to the agreement between the operator and the subscriber regarding privacy. But, yes, in either case the routing of the call is a SIP operation, not an ENUM directory operation.

   >
   > 3) Private "ENUM" search (on local part of URI) resolves to Subscriber
   > URI
   > address
   >     DNS search gives corresponding IP address
   >     IP setup message sent to Subscriber
   >     (optional if SP was end-user; subscriber is operator/carrier
   > customer or
   >      enterprise end-point)

I thought that Private (or Carrier, or Infrastructure) "ENUM" was orthogonal
to all of this, and could potentially be used even if the E.164 had never
been ported to the IP-domain at all.

That is possible. I use the quotes around ENUM in this step, because the nature of the database operation is a local implementation issue, that could be structured as an ENUM database or not. But, at this point the local part could be an E.164 number or some random variable.

Mike



Jim 


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