Re: [Enum] I-D Action: New draft - draft-bellis-enum-send-n-00

["Brian Rosen" <br at brianrosen.net>]

One thing I don't think we have to do is give the black phone or black phone
connected to TA a BETTER experience than they have now.

Those of you in countries that allow this kind of "enterprise can define how
long the number is", what is the user experience?  You can route as soon as
the prefix is entered.  What is the user experience after that?  What if
there was a short or a long pause between the prefix and one of the
internally consumed digits?  After all, the originating switch doesn't know
how many digits the enterprise uses.

Brian

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat at cisco.com] 
Sent: Friday, April 04, 2008 12:33 PM
To: Richard Shockey
Cc: 'Brian Rosen'; enum at ietf.org; 'Clive D.W. Feather'; 'Duane'
Subject: Re: [Enum] I-D Action: New draft - draft-bellis-enum-send-n-00

I am certainly not going to argue with a Neustar employee about the 
realities of deploying and managing this sort of stuff.

But from a UAC perspective the solutions for variable length numbers 
suck. Overlap dialing is problematic at best, and timers don't give an 
adequate user experience. Provisioning is ok if you are deploying in a 
place with a simple, generally fixed length numbering plan, with few and 
easily knowable exceptions. But as soon as you throw in international 
dialing or deploy in a place with variable number lengths on anything 
approaching a per-number basis it doesn't work.

Requirements to solve this keep coming up from marketing.

A good (hypothentical) use case is:

- install a sip "pbx" in a german hotel, with a short main number
   and longer room numbers.

- connect that hotel to a sip service provider

- connect some other sip clients (unaffiliated with the hotel)
   to the same sip SP. Let these be adapters to black phones.

- try to call the desk and the rooms of the hotel from
   those clients. Give as good a user experience to the caller
   as before switching from pstn to sip on both sided.
   (Namely no lag after dialing the last digit before getting
   ringback.)

- also have those clients call another hotel that is still
   only on the PSTN, using redundant GWs on the SP network.
   Again give as good a user experience as before.

	Paul

Richard Shockey wrote:
> In line...
> 
>>  
>>  We still need a *workable* solution to the overlap dialing issue.
>>  (People don't consider timers to be adequate.)
>>  
>>  This seems like the only real solution to that.
>>  
>>  > 2. If such a standardization effort should be undertaken, should the
>>  IETF do
>>  > it?  Since we're trying to close down ENUM, this would be done
>>  somewhere
>>  > else I believe.
>>  
>>  If we want it available via a protocol (and I think that is far
>>  preferable to a word doc), and if it is to at least play nice with
>>  enum,
>>  then ietf seems like a suitable place. But I am not really familiar
>>  with>  the alternatives.
> 
> 
> I'm told Geneva is very pleasant in the springtime. I highly recommend Le
> boufe rouge restaurant. Excellent French bistro food. 
> 
>>  
>>  Re the numbering authorities: Obviously they must have a role in this.
>>  But it is not nice if we have to wait for a national numbering
>>  authority
>>  to report that some number that was assigned to a hotel in germany now
>>  may end in either "0" or "[1-9]xxx". The reporting needs to be more
>>  direct from those who implement the behavior.
> 
> Numbering is, has been and will continue to be a nation state issue. My
own
> sentiment is that this is a out of band data point that it will be very
> difficult implement as a protocol. For in country calls ..its a network
> element configuration issue.  
> 
> 
> For out of country calls ..give the call to your termination partner and
let
> them sort it out (a trunking decision). 
> 
>>  
>>  	Paul
>>  
> 
> 

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