RE: Communication means in draft-ietf-impp-cpim-pidf-05

Although this probably isn't the right forum to dive into the details of
this, I disagree strongly that the <contact> element in presence information
should express the capability of any particular SIP user agent. The
communication address for SIP in a PIDF <contact> element should be an
address-of-record. SIP addresses-of-record URIs do not have capabilities.
Devices that register under an address-of-record (like a phone, or an IM
client) may have specific capabilities, but the relationship between devices
and addresses-of-record is contingent. Registering device URIs in the
<contact> element should be discouraged for a number of reasons. 

In any event, I see no particular need to add any features to PIDF in
support of this.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, August 29, 2002 11:02 AM
> To: [email protected]; [email protected]
> Subject: RE: Communication means in draft-ietf-impp-cpim-pidf-05
> 
> 
> > > 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.
> 
> Thanks,
> Krisztian
> 
> 
> 
>   [reminder: [email protected] for non-technical 
> discussions, please]
> 



  [reminder: [email protected] for non-technical discussions, please]