Re: Section 1.2 & 2 of 3761bis

Hi Patrik, folks,
 That's my problem -- there are two elements: the technology (mapping phone numbers to domain names within SOME apex) and the IAB/ITU-T+IANA agreement on e164.arpa.
The technology is usable regardless of whether it's in public or within a private federated net, or using an alternative root, or ...

This is not just a name (ENUM == use of this technology in public within the e164.arpa apex). It's also who or what can use the technology.
This matters for Send-N and Unused, where there may be records elsewhere that in leaf zones associated with E.164 numbers.

The technology is common; the restrictions on E.164 numbers are tied to the IAB agreement. We have a mixture of the two.

all the best,
  Lawrence


On 19 May 2010, at 09:23, Patrik Fältström wrote:

> On 19 maj 2010, at 11.06, Bernie Hoeneisen <[email protected]> wrote:
> 
>> Section 2 on the other hand makes it practically impossible to use ENUM with non-E.164 numbering plans:
>> 
>> To mitigate this risk, the "E2U" token MUST NOT
>> provisioned in domains associated with non-E.164 numbers.
> 
> It all depends on what we mean by ENUM. We do not agree if ENUM stands only for the technology (look things up in dns, given some root) or only when the root is e164.arpa.
> 
> I thought we had this discussion in the enum wg, and concluded that enum (without any prefix or suffix) always implies use of e164.arpa.
> 
> Other things are called infrastructure enum, enum-like, use of enum technology, private enum or such.
> 
> Which I think is what the text quoted says.
> 
>   Patrik
>