[Simple] Update to xcap package

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Mon, 16 February 2004 22:36 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04389 for <simple-archive@ietf.org>; Mon, 16 Feb 2004 17:36:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsrLz-0003TB-00 for simple-archive@ietf.org; Mon, 16 Feb 2004 17:36:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsrL0-0003P5-00 for simple-archive@ietf.org; Mon, 16 Feb 2004 17:35:39 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AsrKX-0003MH-00; Mon, 16 Feb 2004 17:35:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrKQ-0004sW-H7; Mon, 16 Feb 2004 17:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrK0-0004rt-5r for simple@optimus.ietf.org; Mon, 16 Feb 2004 17:34:36 -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 RAA04320 for <simple@ietf.org>; Mon, 16 Feb 2004 17:34:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsrJx-0003LI-00 for simple@ietf.org; Mon, 16 Feb 2004 17:34:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsrJ1-0003Hn-00 for simple@ietf.org; Mon, 16 Feb 2004 17:33:36 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1AsrI7-00039X-00 for simple@ietf.org; Mon, 16 Feb 2004 17:32:39 -0500
Received: from dynamicsoft.com ([63.113.46.68]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i1GMWDNr005315 for <simple@ietf.org>; Mon, 16 Feb 2004 17:32:14 -0500 (EST)
Message-ID: <403144E4.7080306@dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Simple WG <simple@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Simple] Update to xcap package
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
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>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Mon, 16 Feb 2004 17:32:04 -0500
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

Folks,

I've submitted a revision to the xcap event package. Until it appears in 
the archives, you can pick it up at:

http://www.jdrosen.net/papers/draft-ietf-simple-xcap-package-01.txt

The changes from the last version:

1. Notifications contain the before and after etags

2. Inclusion of the schema

3. defined a mechanism for subscribing to documents in the global tree
- define a well known user name to subscribe to.

4. changed MIME type of change documents to use +xml convention in rfc 3023.


There are really two major open issues.

The first is alignment with the config framework. Indeed, there has been 
some attempt at some alignment, and this will be reflected in the config 
framework revision that is pending. With documents in place, we will be 
able to have a look at how it might look so a decision can be made 
shortly. I am personally on the fence on this topic.

The second open issue is, what is the scope of this event package. That 
is, what is it that you are subscribing to? There are three possible things:

The first is that subscription is to the document itself, in which case 
a full state update in a NOTIFY contains the current document. The 
second is a subscription to the revision history, which gives you 
changes, but not the full state of the document. The third option is to 
just subscribe to the etag, so that you know that something changed, but 
the notifications don't tell you anything about what changed. Which do 
we need? The latter is the simplest, good for the case where third
party modification of documents is rare. If xcap is utilized in the 
scope for which it was proposed - management of a user's provisioned 
data, I do believe these events would be rare, and that this would be 
the ideal design choice. As such, my own preference would be to do that.

Thoughts?

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple