Re: [Simple] PIDF "entity" attribute usage
Paul Kyzivat <pkyzivat@cisco.com> Tue, 11 January 2005 14:01 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24545; Tue, 11 Jan 2005 09:01:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoMoa-0005zr-HK; Tue, 11 Jan 2005 09:16:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoMV3-00029L-OP; Tue, 11 Jan 2005 08:55:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoMRd-0001iv-RF for simple@megatron.ietf.org; Tue, 11 Jan 2005 08:52:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24132 for <simple@ietf.org>; Tue, 11 Jan 2005 08:52:24 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoMfO-0005q4-SU for simple@ietf.org; Tue, 11 Jan 2005 09:06:43 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 11 Jan 2005 08:51:51 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0BDpmW0010620; Tue, 11 Jan 2005 08:51:48 -0500 (EST)
Received: from cisco.com ([161.44.79.149]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOF86111; Tue, 11 Jan 2005 08:50:28 -0500 (EST)
Message-ID: <41E3D9A4.702@cisco.com>
Date: Tue, 11 Jan 2005 08:50:28 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tim Rang <timrang@microsoft.com>
Subject: Re: [Simple] PIDF "entity" attribute usage
References: <1BEC4DA05ABCD34FACFCFC82086AC2470494F0B3@RED-MSG-43.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA24132
Cc: simple@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
Sender: simple-bounces@ietf.org
Errors-To: simple-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable
Tim Rang wrote: > Folks, > > > > In nearly all of the I-Ds related to presence, every example pidf > document I find contains an entity attribute with a “pres” scheme. The > schema for RFC 3863 indicates that any URI is acceptable here. However, > section 4.1.1 states- > > The value of the 'entity' attribute is the 'pres' URL of the PRESENTITY publishing this presence document. > > > > Recently, I’ve started to see some instances where the entity attribute contains a sip scheme (Ex- draft-ietf-simple-presence-data-model-01 > > ). > > > > My questions are: > > - What is the intended usage of this entity attribute in SIMPLE? It identifies the entity that the pidf document describes. In many cases you should already know that (because you subscribed to it) and in those cases it may be redundant. In other cases, such as when you have used an RLS to subscribe to a list of presentities, it is important information. The URI it contains also is usually what you use to request presence. > - What is the meaning of the ‘pres’ scheme and why should we > use it over something more relevant (i.e. ‘sip’)? The original work on presence was done by the IMPP WG. The PIDF and CPIM specifications were intended to be protocol independent - allowing multiple IM&Presence protocols to be developed that could interoperate. One aspect of this is having a presence URI scheme ("pres") that is itself independent of the protocols that are used to access it. SIMPLE is one protocol specific realization of the presence functionality defined by IMPP. Of course it is built on SIP, and so SIP URIs are natural for identifying presentities in SIMPLE. However the means by which pres URIs can be used with SIMPLE is also defined. So, at least in principle, when using SIMPLE, you can use either sip or pres URIs. However this assumes the specific implementation you are using actually supports this. In practice you should determine what the implementation you are using supports. Paul > Thanks, > > Tim Rang > > > ------------------------------------------------------------------------ > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple
- [Simple] PIDF "entity" attribute usage Tim Rang
- Re: [Simple] PIDF "entity" attribute usage Paul Kyzivat
- RE: [Simple] PIDF "entity" attribute usage Tim Rang
- Re: [Simple] PIDF "entity" attribute usage Paul Kyzivat
- Re: [Simple] PIDF "entity" attribute usage Ted Hardie
- Re: [Simple] PIDF "entity" attribute usage Paul Kyzivat
- Re: [Simple] PIDF "entity" attribute usage Jonathan Rosenberg
- Re: [Simple] PIDF "entity" attribute usage Paul Kyzivat
- Re: [Simple] PIDF "entity" attribute usage Hisham Khartabil