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

> > I have no opinion on that yet.  I have an opinion that we should have a
> > database with length information that all services, and all devices, can
> > make use of.  Send-n is too limited, in my opinion.
> 
> What doesn't it do that your proposed new protocol would do?
It doesn't give you the dial plan.  It tells you how many digits are needed
to be collected until you get to the next step in the dial plan.

We have a language to describe dial plans.  See MGCP or Megaco's digit map.
We don't need to use that language, but it's representative of the kind of
information a dial plan has.  

I want something that determines the shape of the enum tree.  I need that
even before I create the tree.  The authoritative source for the information
is typically the regulator.  Today, it's typically published as a Word
document by the ITU.  I want to set up a mechanism for the regulator, or
someone operating on its behalf, publishes the data that currently is
published in that Word document as a database anyone, including the enum
operator, can use.

The way I want to use the data for a next generation phone is to download
something like the MGCP dial plan when an international number is dialed, so
the user can see/hear/feel, via a GUI, when they have a good number.  I want
to not even send one DNS query to ENUM unless I have a good number.

Brian