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

Avshalom Houri <AVSHALOM@il.ibm.com> Mon, 07 January 2008 12:02 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 1JBqgR-0008GG-NS; Mon, 07 Jan 2008 07:02:23 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JBqgP-0008FR-NC for sip-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 07:02:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBqgP-0008F3-C9 for sip@ietf.org; Mon, 07 Jan 2008 07:02:21 -0500
Received: from mtagate1.de.ibm.com ([195.212.29.150]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JBqgO-0004ZH-J1 for sip@ietf.org; Mon, 07 Jan 2008 07:02:21 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.13.8/8.13.8) with ESMTP id m07C2JNI079972 for <sip@ietf.org>; Mon, 7 Jan 2008 12:02:19 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m07C2IIL2121886 for <sip@ietf.org>; Mon, 7 Jan 2008 13:02:18 +0100
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m07C2IkE011549 for <sip@ietf.org>; Mon, 7 Jan 2008 13:02:18 +0100
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m07C2I1a011535; Mon, 7 Jan 2008 13:02:18 +0100
To: sip@ietf.org, jari.urpalainen@nokia.com
MIME-Version: 1.0
X-KeepSent: E149880F:A529696C-C22573C9:00416690; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0NP August 02, 2007
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Message-ID: <OFE149880F.A529696C-ONC22573C9.00416690-C22573C9.00422603@il.ibm.com>
Date: Mon, 7 Jan 2008 14:02:17 +0200
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.0|August 02, 2007) at 07/01/2008 14:02:17, Serialize complete at 07/01/2008 14:02:17
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc:
Subject: [Sip] 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>
Content-Type: multipart/mixed; boundary="===============1258268591=="
Errors-To: sip-bounces@ietf.org

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

_______________________________________________
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