RE: Communication means in draft-ietf-impp-cpim-pidf-05
"Adrian Bateman" <[email protected]>
| Newsgroups | gmane.ietf.impp |
|---|---|
| Organization | VisionTech Limited |
| Message-ID | <00b601c24f87$d6319c70$6405010a@ADRIANXP> |
On 29 August 2002 19:02, [email protected] wrote: > > > The question is that how can the watcher figure out from > > the example > > > below what is the communication mean of the provided > > contact address. > > It could > > > be "voice", "video", even "im", etc. > > > > > > <tuple id="a67uyt76"> > > > <status> > > > <basic>open</basic> > > > </status> > > > <contact priority="1.0">sip:[email protected]</contact> > > > </tuple> > > > > The communication means looks like SIP to me. For example, if you > > want > > IM, I'd expect you to see something like im:[email protected]. > > As I see, sip: alone is not enough for defining the communication > mean. If I wanted to publish communication means like voice, video, > chat, game, etc., all of them would have probably SIP URIs. It would > be preferable to indicate for the watchers which SIP URI is for chat > and which one is for voice calls. Isn't that a problem with the SIP URI? If I was making up a URI scheme and these things were important, I'd probably include them. If I don't, it probably means use whatever my device can do that the other end supports, maybe tending towards the highest fidelity. I don't know about SIP specifically - what does the description of the SIP URI scheme say about this? Adrian.
smime.p7s
(application/x-pkcs7-signature, 3.1 KB) - not displayed