[Bug 26866] add support for requesting handles for a vCard field or URI

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26866

--- Comment #21 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-08-25 07:07:15 PDT ---
(In reply to comment #20)
> What about making ENUM lookups to resolve a tel URI?

What about them, indeed...

How do these work? Is the idea that tel:+44123456789 somehow points (via ENUM)
to sip:office at example.com, and then you call office at example.com instead?

One way to represent this would be for RequestHandles("tel:+44123456789"), and
similar Addressing calls, to "normalize" to "sip:head-office at example.com", but
I think that's only right if the mapping is (semi-)permanent and meant to be
user-visible.

(Analogy: on an XMPP server example.com with an MSN transport, we could
consider "normalizing" ("x-msn", "example at passport.com") to
example%passport.com at msn.example.com. Maybe. I'm not sure whether it'd really
be appropriate to do this for transports either, though.)

The other way to represent it would be to have the handle represent the tel
URI, and do the ENUM lookup lazily when you actually interact with it (i.e.
request a Channel - as an implementation detail, the CM should cache the
mapping for a while, perhaps for the duration of the session). This would be
correct if the contact being called is conceptually "tel:+44123456789", and the
mapping via ENUM is considered to be an implementation detail of how we call
it, which I think is probably more appropriate?

(Analogy: we don't normalize example at gmail.com to example at talk.l.google.com or
to example at 209.85.229.125.)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.