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

[email protected]
Newsgroups gmane.ietf.enum
Message-ID <OF52C92B23.8E225BD5-ON80257421.0066CD6F-80257421.006810BC@nominet.org.uk>
> But anyone familiar with the realities of the E.164 plan and its 
national
> implementations would tell you exactly the same thing. There is no
> centralized registry describing the structure of the totality of E.164 
plan.

I rather thought the point of this was that in the DNS it doesn't have to 
be centralized :)

In the future hypothetical use case of multiple countries allowing 
interconnection between their national portability databases [i.e. my 
justification for trying to standardise this] then each database 
administrator can publish their own portion of the E.164 numbering plan.

NB: I don't currently expect to see this in public ENUM, it really is a 
private ENUM application.  However it does have theoretical benefits in 
public ENUM, and several people have said the data would be useful (even 
if some of them aren't happy with the current proposed implementation). 
Hence I think it's worth making the effort to ensure that it wouldn't 
break anything were it to be deployed.

Ray
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.