Re: [Enum] IETF, ENUM and NGN

[Adrian Georgescu <ag at ag-projects.com>]

For my understanding, user ENUM consists of already existing telephone 
numbers already in use by end-users. Provider ENUM consists of blocks 
of numbers assigned to providers which in term get assigned to 
end-users.

These number ranges if PROPERLY delegated based on existing E164 
numbering plans in place in each country do NOT overlap so they could 
stay in the same tree. Or do they?

Adrian

On Jul 6, 2004, at 9:09 AM, James Seng wrote:

> how about not able to get a delegation needed in e164.arpa?
>
> it is like saying we design this wonderful DNS system but no one is 
> able to register anything under it.
>
> james
>
> Jim Reid wrote:
> > What matters is the operators agree on a domain name for
> > Infrastructure ENUM. This might as well be e164.arpa since (a) it's
> > vendor neutral; (b) already an agreed IETF standard; (c) not
> > controlled by any nation. It's hard to see how any other choice of
> > domain name could be better (technically or politically). And it
> > prevents VoIP/SIP applications from getting schizophrenia from
> > figuring out which domain name they should use based on what network
> > they're running in today.
> > _______________________________________________
> > enum mailing list
> > enum at ietf.org
> > https://www1.ietf.org/mailman/listinfo/enum
>
> _______________________________________________
> enum mailing list
> enum at ietf.org
> https://www1.ietf.org/mailman/listinfo/enum


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