[Simple] SUBSCRIBE for xcap-diff event sent by the presence server to the XCAP server
Iñaki Baz Castillo <ibc@aliax.net> Sun, 27 December 2009 23:36 UTC
Return-Path: <ibc@aliax.net>
X-Original-To: simple@core3.amsl.com
Delivered-To: simple@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2955C3A682E for <simple@core3.amsl.com>; Sun, 27 Dec 2009 15:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.07
X-Spam-Level:
X-Spam-Status: No, score=-0.07 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dc8--5dNmcDs for <simple@core3.amsl.com>; Sun, 27 Dec 2009 15:36:42 -0800 (PST)
Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by core3.amsl.com (Postfix) with ESMTP id 1D48B3A6817 for <simple@ietf.org>; Sun, 27 Dec 2009 15:36:41 -0800 (PST)
Received: by fxm7 with SMTP id 7so9301674fxm.29 for <simple@ietf.org>; Sun, 27 Dec 2009 15:36:19 -0800 (PST)
Received: by 10.223.161.212 with SMTP id s20mr5728780fax.2.1261956979290; Sun, 27 Dec 2009 15:36:19 -0800 (PST)
Received: from ibc-laptop.localnet (16.85-84-188.dynamic.clientes.euskaltel.es [85.84.188.16]) by mx.google.com with ESMTPS id 16sm3818025fxm.4.2009.12.27.15.36.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 27 Dec 2009 15:36:18 -0800 (PST)
From: Iñaki Baz Castillo <ibc@aliax.net>
To: simple@ietf.org
Date: Mon, 28 Dec 2009 00:36:15 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200912280036.15514.ibc@aliax.net>
Subject: [Simple] SUBSCRIBE for xcap-diff event sent by the presence server to the XCAP server
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Dec 2009 23:36:43 -0000
Hi, the way a presence server receives notifications for changes in XCAP documents (so it can notify the watchers) is by subscribing to the XCAP server for the event "xcap-diff" as specified in: http://tools.ietf.org/html/draft-ietf-sip-xcapevent I would like to understand how such SUBSCRIBE sent by the presence server looks. The above draft just shows examples when a SIP user send such SUBSCRIBE but no one example when the subscriber is the presence server. For example, let's imagine a simplified case in which there are just two XCAP applications ("pres-rules" and "resource-lists"). The presence server should subscribe to users documents. AFAIK the presence server would send a SUBSCRIBE as follows: SUBSCRIBE sip:xcap-server@domain.org SIP/2.0 From: sip:presence-server@domain.org Accept: application/xcap-diff+xml Event: xcap-diff; diff-processing=no-patching Content-Type: application/resource-lists+xml <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list> <entry uri="pres-users/users/" /> <entry uri="resource-lists/users/" /> </list> </resource-lists> Then when any user creates or modifies a XCAP document for those auids, then XCAP server would sent a NOTIFY to the presence-server telling the document addition/modification. Doubts: - Is the above correct? (is it defined somewhere?) - Most probably the presence-server is just interested in "index" documents for both XCAP applications. However it would receive notifications for every document created by any user even if it's not called "index". Is it the expected behavior? How to ask in the SUBSCRIBE that there is noly interest on "index" called documents? - Could the notification from the XCAP server to the presence server work with PUBLISH rather than SUBSCRIBE & NOTIFY? This is: when a XCAP document is modified the XCAP server sends a PUBLISH to the presence server with xcap-diff body. Does it make sense? - And last question. Are all my questions defined in IETF docs? or do they require specifications on top of IETF docs as OMA specs? Thanks a lot and best regards. By sending the above XML body the -- Iñaki Baz Castillo <ibc@aliax.net>
- [Simple] SUBSCRIBE for xcap-diff event sent by th… Iñaki Baz Castillo
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Iñaki Baz Castillo
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Ben Campbell
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Jari Urpalainen
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Adrian Georgescu
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Iñaki Baz Castillo
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Adrian Georgescu
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Iñaki Baz Castillo
- Re: [Simple] SUBSCRIBE for xcap-diff event sent b… Adrian Georgescu