Re: [Sip] querying the current event state of a publication

Paul Kyzivat <pkyzivat@cisco.com> Tue, 30 March 2004 23:47 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05463 for <sip-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:47:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8Rj2-0006a4-6z for sip-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:52 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S021ej027338 for sip-archive@odin.ietf.org; Tue, 27 Jan 2004 19:02:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ald7J-0006gi-A1; Tue, 27 Jan 2004 18:59:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Al9xy-0002Rv-Aa for sip@optimus.ietf.org; Mon, 26 Jan 2004 11:52:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12750 for <sip@ietf.org>; Mon, 26 Jan 2004 11:51:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Al9xx-0000Lp-00 for sip@ietf.org; Mon, 26 Jan 2004 11:52:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Al9x1-0000J7-00 for sip@ietf.org; Mon, 26 Jan 2004 11:51:03 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1Al9wd-0000Gx-00 for sip@ietf.org; Mon, 26 Jan 2004 11:50:39 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by sj-iport-5.cisco.com with ESMTP; 26 Jan 2004 08:52:15 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0QGo6Ie016884; Mon, 26 Jan 2004 11:50:06 -0500 (EST)
Received: from cisco.com ([161.44.79.239]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFN43119; Mon, 26 Jan 2004 11:50:04 -0500 (EST)
Message-ID: <4015453B.3070902@cisco.com>
Date: Mon, 26 Jan 2004 11:50:03 -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: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sip@ietf.org
Subject: Re: [Sip] querying the current event state of a publication
References: <4012E741.5000809@dynamicsoft.com> <40152C68.8030802@cisco.com> <40154262.9010400@dynamicsoft.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Jonathan Rosenberg wrote:
> inline.
> 
> Paul Kyzivat wrote:
> 
>>> If we want this functionality, I have an idea for an alternative 
>>> approach that works much better, triggered by some conversations I 
>>> had with Ben C. recently.
>>
>> That's a big IF. Do we really want to mandate that every compositor 
>> must be prepared to provide this? It certainly puts contraints on the 
>> implementations, and in most cases I think publishers can be 
>> constructed so that they don't need this capability.
> 
> The main constraint I think it introduces is that the compositor needs 
> to keep around the presence documents from each individual source, in 
> addition to the final result of composition. I am not sure if this is 
> new; I don't know how it couuld do composition without keeping these 
> around.

I think there may be plausible implementations that separate the 
compositor from the PA handling subscribes and generating notifies.

In that case the compositor may have the individual presence document, 
but the PA doesn't.

I'm just concerned about layering on additional behavior that everybody 
must implement.

> My suggestion was mostly along the lines of - this is a good way to do 
> it, rather than, we should have this feature. I recall there was a 3gpp 
> requrement for it, and  I remember asking why it was there, and I dont 
> remember the answer, in fact.

I'm in agreement as long as the discussion about IF has yet to happen.

	Paul


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip