Re: [Simple] tel URIs in common policy

[Henning Schulzrinne <hgs at cs.columbia.edu>]

Aki,

I have a few concerns about this:

- user interface: ENUM-style identifiers are not exactly the most 
user-friendly domain names, given the reversal of digits; I suspect that 
in many cases, applications will generate the rules, but probably not in 
all cases.

- confusion: There's lots of talk about carrier ENUM, using TLDs other 
than e164.arpa. I suspect we'd see "my number is in e164.org, so let me 
use that postfix instead".

- user expectation: it seems that a user would expect the ENUM entry to 
exist if one specifies the domain name; this is not likely to be the case;

- consistency: the presence of a "domain" parameter signals that this 
has 'id' entries with user names in that domain. This clearly makes no 
sense here.

I don't see which problem this would solve compared to the scheme 
parameter proposal. You'd still have to flag the domain as being 
"special", as "sip:alice at 4.3.2.1.5.5.5.2.3.2.1.e164.arpa" doesn't make a 
whole lot of sense.

Henning


Aki Niemi wrote:
> Hi,
>
> I kind of grew fond of the idea Cullen and I came up with in a private 
> conversation, namely treating telephone numbers as domains similar to 
> when issuing a DNS ENUM query.
>
> In essence, to match +1-232-555-1234, you'd have an identity conditions 
> such as:
>
> <many domain="4.3.2.1.5.5.5.2.3.2.1.e164.arpa" />
>
> This has an interesting additional property of being able to match based 
> on country code, area code, etc. For example, to match all Finnish 
> telephone numbers, you'd have:
>
> <many domain="8.5.3.e164.arpa" />
>
> Not being an expert on ENUM or E.164 in general, I suspect this is 
> horribly broken, but it pleases the aesthethic eye.

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