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

PFAUTZ, PENN L, ATTCORP said:
> I'm having a little trouble understanding the real need for this
> enumservice. I would think that any network element  receiving a dial
> string would have its own local information about dial patterns and
> numbers and so be able to tell when dialing is complete and then be able
> to formulate an ENUM query on the appropriate full E.164 number.
> Since the number length information should be relatively static, why not
> just provision it locally? 

While the information should be static, it's also very complicated and it
might not be practical for the network element to store it all. In the UK
we have number ranges where the length varies in a very localised way; it
might be that:
     0456 789 0xx    numbers are all 10 digits
     0456 789 1xxx   numbers are all 11 digits
(these are hypothetical examples because I can't get to the relevant
database right now).

Germany has situations where the customer determines the length of numbers.

> Also, it's not clear to me when the client would initiate the initial
> query in the example that told it to expect 5-6 more digits.

The client would know, perhaps, that *every* number beginning 0 has at
least 7 digits. So it would initiate the query after receiving those 7.

> And, if
> it's 5-6, then if the number has only 5, don't I still have to use a
> timeout algorithm to determine the user is finished dialing.
> Am I missing something?

In the UK there are no numbers that are prefixes of other numbers. That is,
when you've received enough digits, you'll know you've reached the end. But
you may need several digits to do so - see the above examples.

-- 
Clive D.W. Feather  | Work:  <[email protected]>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <[email protected]>  | Fax:    +44 870 051 9937
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
THUS plc            |                            |