Re: Overlap dialing user experience (Re: I-D Action: New draft - draft-bellis-enum-send-n-00)

Brian

> You are missing the point.
> 
> The number of digits need to route the call to the correct domain is
> determined by a more static database which is not subject to public enum
> implementations. 

No I'm not missing the point - it the incorrect assumption in what you are 
saying above that I am disagreeing with.  The number of digits needed to 
route a call is not determined by an independent static database, it is 
determined by the numbers provisioned in the ENUM trees, which in turn 
creates the structure of that tree.  This draft is a way of describing 
that structure.

> Once you get to the domain, there is more routing to do.  I would prefer
> that the domain handle that directly.  That is, after all, how SIP 
works.
> We route to the domain using one set of mechanisms.  Then the domain 
uses
> another set of mechanisms to route to the device.
>
> Right now, route to the device with variable length TNs is .001% of the
> problem.  The other 99.999% is route to the domain.  I think a simple
> solution to that would be great.  I don't think that is an ENUM 
solution.

I have no objection to anyone working on that further routing.  But nobody 
in their right mind who runs a user ENUM tree (or other ENUM tree) would 
run a SIP server that just deals with that further routing and then add a 
NAPTR for that SIP server at every non-terminal point in their ENUM tree, 
if they could use send-n instead. 

Jay