Re: Send-N draft: draft-bellis-enum-send-n-02 published

It doesn't tell you the length of a number; it tells you how many digits you
have to enter to get to the next step in the revealing of the length of the
number.

The entire problem is that there are a significant number of applications
and systems that need to understand, in detail, the number plan for a
country.  Those include applications such as the one you are describing
(overlapped dialing systems) as well as:
1) An ENUM operator wishing to validate the shape of the tree
2) A smart device wishing to implement a sophisticated digit map
3) A routing engine trying to diagnose why a call is not routing
4) Rating and routing entities who merely need to understand what carrier is
allocated a number block (where not all blocks are number portability
enabled)

Brian

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Friday, June 27, 2008 3:23 PM
> To: Brian Rosen
> Cc: [email protected]
> Subject: RE: [Enum] Send-N draft: draft-bellis-enum-send-n-02 published
> 
> > I think there is a problem, I think IETF can solve it.  I've provided
> one
> > alternative, I'm happy to discuss others.
> >
> > Your proposal, in my opinion, is too limiting, and doesn't solve the
> entire
> > problem.
> 
> Brian,
> 
> Can you please explain exactly *how* you find it limiting, and what you
> believe the rest of the "entire problem" is that that's apparently not
> solved?
> 
> Ray