[Sip] Re: draft-ietf-sip-xcapevent-00.txt

Jari Urpalainen <jari.urpalainen@nokia.com> Mon, 14 January 2008 12:15 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JEOE3-0004aI-3O; Mon, 14 Jan 2008 07:15:35 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JEOE2-0004aD-43 for sip-confirm+ok@megatron.ietf.org; Mon, 14 Jan 2008 07:15:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JEOE1-0004a1-PH for sip@ietf.org; Mon, 14 Jan 2008 07:15:33 -0500
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JEOE1-0007nd-BQ for sip@ietf.org; Mon, 14 Jan 2008 07:15:33 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0ECGHhi025269; Mon, 14 Jan 2008 06:16:24 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 Jan 2008 14:15:15 +0200
Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 Jan 2008 14:15:15 +0200
Received: from [172.21.40.139] ([172.21.40.139]) by esebe105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 Jan 2008 14:15:15 +0200
Message-ID: <478B5239.7060803@nokia.com>
Date: Mon, 14 Jan 2008 14:14:49 +0200
From: Jari Urpalainen <jari.urpalainen@nokia.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: ext Avshalom Houri <AVSHALOM@il.ibm.com>
References: <OFE149880F.A529696C-ONC22573C9.00416690-C22573C9.00422603@il.ibm.com>
In-Reply-To: <OFE149880F.A529696C-ONC22573C9.00416690-C22573C9.00422603@il.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jan 2008 12:15:15.0222 (UTC) FILETIME=[1E8E2B60:01C856A7]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: sip@ietf.org
Subject: [Sip] Re: draft-ietf-sip-xcapevent-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sip-bounces@ietf.org

Avshalom, sorry for slow response...

ext Avshalom Houri wrote:
>
> Wish to get a clarification regarding what will happen when we 
> subscribe to the
> resources below and the first entry does not exist while the other two 
> do exist.
> Assume that we get a pending notification, when and how will it be 
> possible to
> know which resource does exist and which one does not.
>
> What will be the content of the pending notification and how it will 
> be possible
> to know which one exist?
>
>
>    <?xml version="1.0" encoding="UTF-8"?>
>    <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists">
>     <list>
>      <entry uri="resource-lists/users/sip:joe@example.com/index"/>
>      <entry uri="rls-services/users/sip:joe@example.com/index/
>    ~~/*/service%5b@uri='sip:marketing@example.com'%5d"/>
>      <entry uri="pidf-manipulation/"/>
>     </list>
>    </resource-lists>
> --Avshalom
>

The initial full notification will list all existing resources, so given 
the resource-lists document (index) doesn't exist it will not be 
indicated within the notification. So the element will be indicated and 
possibly zero or multiple documents within the pidf-manipulataion 
collection. So there are no reason indications like error codes within 
the notifications, the resources simply doesn't exist within the 
notification body. So a client knows what it tries to retrieve and the 
full notification will list what resources are available, i.e. some 
pretty simple logic on a client side.

br, jari


_______________________________________________
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