RE: [Simple] tel URIs in common policy

["Brian Rosen" <br at brianrosen.net>]

Paul

Not sure yet what I think of the basic idea, but
   sip:+1-232-1234 at foo.com;user=phone
should be equivalent to
   tel:+1-232-1234

So I think you CAN convert it to "enum" form.

You might have more problems with
   sip:1234 at foo.com

That may be equivalent to
   tel:1234;phone-context=foo.com
but you don't know that a priori.

Brian

-----Original Message-----
From: simple-bounces at ietf.org [mailto:simple-bounces at ietf.org] On Behalf Of
Paul Kyzivat
Sent: Wednesday, August 10, 2005 2:19 PM
To: Aki Niemi
Cc: simple at ietf.org; ext Henning Schulzrinne
Subject: Re: [Simple] tel URIs in common policy

Aki,



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" />

Then what do you do with sip:+1-232-555-1234 at foo.com;user=phone ?

I don't think you can convert it to:

    4.3.2.1.5.5.5.2.3.2.1.foo.com

and if you could then it it wouldn't match the e164.arpa form.

> 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" />

It only does if you declare that a domain matches anything it is the 
tail of. You may sometimes want that, but I don't think you do in general.

	Paul

> Not being an expert on ENUM or E.164 in general, I suspect this is 
> horribly broken, but it pleases the aesthethic eye.
> 
> Cheers,
> Aki
> 
> ext Henning Schulzrinne wrote:
> 
>> In a side conversation, Hannes suggested a solution to the tel URI 
>> problem we discussed during the WG meeting, akin to what's done in the 
>> geopriv coordinate system parameter, namely to have a parameter that 
>> identifies the scheme, as in
>>
>> <one scheme="tel" id="+1-212-555-1234"/>
>>
>> or
>>
>> <one scheme="sip" id="alice at example.com"/>
>>
>> if you really only want to match SIP identity sip:alice at example.com.
>>
>> The default with no scheme parameter is "matches any user at domain scheme".
>>
>> In order to complete finishing the section of the spec, I'd value 
>> quick feedback on the idea.
>>
>> Henning
>>
>> _______________________________________________
>> Simple mailing list
>> Simple at ietf.org
>> https://www1.ietf.org/mailman/listinfo/simple
>>
> 
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
> 

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



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