[asterisk-dev] ENUM changes: discussion

[Klaus Darilion]

On Wed, February 15, 2006 11:00, Mark Elkins said:
> On Tue, 2006-02-14 at 20:44 -0800, John Todd wrote:
>> I saw the changes to the ENUMLOOKUP function below, and one of them
>> raises a question in my mind.  It seems to be going backwards to
>> continue using the "enum.conf" file when this is easily specified in
>> the function call itself, or assuming the "default" of e164.arpa.
>> The RFC for ENUM describes e164.arpa as the "only" ENUM suffix, so
>> while I don't agree that it is the "only" suffix that is useful for
>> ENUM lookups, having it as a default seems perfectly reasonable.
>
> The RFC may state that e164.arpa is the one and only suffix - but in the
> real world - we need alternatives. For example - how many countries
> (governments?) are even aware that e164 exists? Certainly in South
> Africa - ICASA (the regulator) is aware of e164 - but does nothing.
> Meanwhile, there are a few thousand entries in e164.org for South
> Africa.

Just because of having e164.arpa the default one does not restrict the
usage to other trees. Any tree is supported. But if there is a default
tree, which one should it be? e164.org? e164.info?... IMO, the default
tree should be the standard one.

regards
klaus