
From cyrus@daboo.name  Mon Jun  7 08:18:32 2010
Return-Path: <cyrus@daboo.name>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5524A3A6359; Mon,  7 Jun 2010 08:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 7qXISAyG73dp; Mon,  7 Jun 2010 08:18:31 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id B826128CD04; Mon,  7 Jun 2010 06:57:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id ECF131706BD29; Mon,  7 Jun 2010 09:57:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BV3FP2+KmeMe; Mon,  7 Jun 2010 09:57:13 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 5AD011706BD1D; Mon,  7 Jun 2010 09:57:12 -0400 (EDT)
Date: Mon, 07 Jun 2010 09:57:09 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: w3c-dist-auth@w3.org
Message-ID: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=2011
Cc: caldav@ietf.org, vcarddav@ietf.org
Subject: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 15:18:32 -0000

Hi folks,
The latest WebDAV collection sync draft is here: 
<https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>. We believe we 
are close to done with this and would like to submit to the IESG soon. 
However, there is one open issue that we need feedback from implementors on.

The question is whether collection resources that are immediate children of 
the collection being targeted for the REPORT should be reported as 
"modified" if any of their child resources (depth infinity) are modified.

Key points:

1) We have deliberately scoped the REPORT defined in this draft to be 
Depth:1 only - i.e. it will only report changes to immediate children. 
Depth:infinity change reporting was ruled out at this time (though 
eventually we would expect to see it defined if there is interest).

2) The first real implementations of this REPORT are being done for CalDAV 
and CardDAV servers where typically calendar/addressbook collections only 
have immediate child resources and not collections - so the draft as 
currently written is fine. (BTW there are already several client and server 
implementations of this draft that have been tested at various interops). 
However, my concern is that more "general" WebDAV servers may wish to do 
reporting of changes to immediate child collections to allow clients to 
progressively sync an entire hierarchy.

3) Reporting changes to immediate child collections requires any change at 
depth:infinity within those collections to "bubble up" - i.e. a change with 
a collection changes its DAV:sync-token and the properties of all its 
parent collections. This potentially places a big performance burden on the 
server - particularly if it were to choose to support the REPORT on the 
root resource. In reality servers would probably limit the scope of the 
report to a reasonable "sub-hierarchy" set (e.g. CalDAV and CardDAV servers 
would only support the REPORT on calendar or address book home collections 
and not on any parents of those).

-- 
Cyrus Daboo


From cyrus@daboo.name  Mon Jun  7 08:40:44 2010
Return-Path: <cyrus@daboo.name>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1C7928C1E9; Mon,  7 Jun 2010 08:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 wArHnu5QcfB1; Mon,  7 Jun 2010 08:40:43 -0700 (PDT)
Received: from mail383c25.carrierzone.com (mail383c25.carrierzone.com [209.235.146.153]) by core3.amsl.com (Postfix) with ESMTP id 08CB428CD40; Mon,  7 Jun 2010 07:00:34 -0700 (PDT)
X-Authenticated-User: master.tencoassemblies.com
Received: from TENCOSERVER.TencoAssembliesInc.local (173-161-228-126-Philadelphia.hfc.comcastbusiness.net [173.161.228.126]) (authenticated bits=0) by mail383c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o57E0V2L024535; Mon, 7 Jun 2010 14:00:33 GMT
Received: from TENCOSERVER.TencoAssembliesInc.local ([10.0.0.2]) by TENCOSERVER.TencoAssembliesInc.local with Microsoft SMTPSVC(5.0.2195.6713); Mon, 7 Jun 2010 10:00:31 -0400
Received: by TENCOSERVER.TencoAssembliesInc.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download) id MSG06072010-100028-2200.MMD@TencoAssembliesInc.local; Mon, 7 Jun 2010 10:00:28 -0400
X-Envelope-From: w3c-dist-auth-request@frink.w3.org
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by mail368c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o57Dwt99004141 for <JTentilucci@tencoassemblies.com>; Mon, 7 Jun 2010 09:58:57 -0400
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1OLcqC-0003mB-FF for w3c-dist-auth-dist@listhub.w3.org; Mon, 07 Jun 2010 13:58:12 +0000
Received: from bart.w3.org ([128.30.52.63]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <cyrus@daboo.name>) id 1OLcqB-0003l7-P0 for w3c-dist-auth@listhub.w3.org; Mon, 07 Jun 2010 13:58:11 +0000
Received: from daboo.name ([151.201.22.177]) by bart.w3.org with esmtp (Exim 4.69) (envelope-from <cyrus@daboo.name>) id 1OLcq9-0006dj-Hl for w3c-dist-auth@w3.org; Mon, 07 Jun 2010 13:58:11 +0000
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id ECF131706BD29; Mon,  7 Jun 2010 09:57:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BV3FP2+KmeMe; Mon,  7 Jun 2010 09:57:13 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 5AD011706BD1D; Mon,  7 Jun 2010 09:57:12 -0400 (EDT)
Date: Mon, 07 Jun 2010 09:57:09 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: w3c-dist-auth@w3.org
Message-ID: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=2011
Received-SPF: none
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599
X-W3C-Scan-Sig: bart.w3.org 1OLcq9-0006dj-Hl 5e4f42a5a4e356601beada40c41c3b3c
X-Original-To: w3c-dist-auth@w3.org
Archived-At: <http://www.w3.org/mid/2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/13266
X-Loop: w3c-dist-auth@w3.org
Sender: w3c-dist-auth-request@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
Resent-Message-Id: <E1OLcqC-0003mB-FF@frink.w3.org>
Resent-Date: Mon, 07 Jun 2010 13:58:12 +0000
X-MMR: 0
X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com)
X-OriginalArrivalTime: 07 Jun 2010 14:00:31.0097 (UTC) FILETIME=[CA8F7690:01CB0649]
Cc: caldav@ietf.org, vcarddav@ietf.org
Subject: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 15:40:44 -0000

Hi folks,
The latest WebDAV collection sync draft is here: 
<https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>. We believe we 
are close to done with this and would like to submit to the IESG soon. 
However, there is one open issue that we need feedback from implementors on.

The question is whether collection resources that are immediate children of 
the collection being targeted for the REPORT should be reported as 
"modified" if any of their child resources (depth infinity) are modified.

Key points:

1) We have deliberately scoped the REPORT defined in this draft to be 
Depth:1 only - i.e. it will only report changes to immediate children. 
Depth:infinity change reporting was ruled out at this time (though 
eventually we would expect to see it defined if there is interest).

2) The first real implementations of this REPORT are being done for CalDAV 
and CardDAV servers where typically calendar/addressbook collections only 
have immediate child resources and not collections - so the draft as 
currently written is fine. (BTW there are already several client and server 
implementations of this draft that have been tested at various interops). 
However, my concern is that more "general" WebDAV servers may wish to do 
reporting of changes to immediate child collections to allow clients to 
progressively sync an entire hierarchy.

3) Reporting changes to immediate child collections requires any change at 
depth:infinity within those collections to "bubble up" - i.e. a change with 
a collection changes its DAV:sync-token and the properties of all its 
parent collections. This potentially places a big performance burden on the 
server - particularly if it were to choose to support the REPORT on the 
root resource. In reality servers would probably limit the scope of the 
report to a reasonable "sub-hierarchy" set (e.g. CalDAV and CardDAV servers 
would only support the REPORT on calendar or address book home collections 
and not on any parents of those).

-- 
Cyrus Daboo



From timhare@comcast.net  Mon Jun  7 17:47:57 2010
Return-Path: <timhare@comcast.net>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 048393A6843 for <caldav@core3.amsl.com>; Mon,  7 Jun 2010 17:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 d7wwjflO5QKX for <caldav@core3.amsl.com>; Mon,  7 Jun 2010 17:47:56 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id D1CA23A6879 for <caldav@ietf.org>; Mon,  7 Jun 2010 17:47:52 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta05.westchester.pa.mail.comcast.net with comcast id T82o1e0011swQuc55Cnuge; Tue, 08 Jun 2010 00:47:54 +0000
Received: from THARE ([71.203.98.77]) by omta15.westchester.pa.mail.comcast.net with comcast id TCnt1e00R1gAkVz3bCnuTi; Tue, 08 Jun 2010 00:47:54 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Cyrus Daboo'" <cyrus@daboo.name>, <w3c-dist-auth@w3.org>
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
In-Reply-To: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
Date: Mon, 7 Jun 2010 20:47:49 -0400
Message-ID: <001f01cb06a4$38a483a0$a9ed8ae0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsGVLQsWQQQKu0YRgSm0kkPCv6/AQAT1CZQ
Content-Language: en-us
Cc: caldav@ietf.org, vcarddav@ietf.org
Subject: Re: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 00:47:57 -0000

I am not an implementor, but it seems to me that many Calendar/addressbook
collections might be depth:2 to accomodate groups like mailing lists ?

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: caldav-bounces@ietf.org [mailto:caldav-bounces@ietf.org] On Behalf Of
Cyrus Daboo
Sent: Monday, June 07, 2010 9:57 AM
To: w3c-dist-auth@w3.org
Cc: caldav@ietf.org; vcarddav@ietf.org
Subject: [caldav] WebDAv collection sync: last issue

Hi folks,
The latest WebDAV collection sync draft is here: 
<https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>. We believe we 
are close to done with this and would like to submit to the IESG soon. 
However, there is one open issue that we need feedback from implementors on.

The question is whether collection resources that are immediate children of 
the collection being targeted for the REPORT should be reported as 
"modified" if any of their child resources (depth infinity) are modified.

Key points:

1) We have deliberately scoped the REPORT defined in this draft to be 
Depth:1 only - i.e. it will only report changes to immediate children. 
Depth:infinity change reporting was ruled out at this time (though 
eventually we would expect to see it defined if there is interest).

2) The first real implementations of this REPORT are being done for CalDAV 
and CardDAV servers where typically calendar/addressbook collections only 
have immediate child resources and not collections - so the draft as 
currently written is fine. (BTW there are already several client and server 
implementations of this draft that have been tested at various interops). 
However, my concern is that more "general" WebDAV servers may wish to do 
reporting of changes to immediate child collections to allow clients to 
progressively sync an entire hierarchy.

3) Reporting changes to immediate child collections requires any change at 
depth:infinity within those collections to "bubble up" - i.e. a change with 
a collection changes its DAV:sync-token and the properties of all its 
parent collections. This potentially places a big performance burden on the 
server - particularly if it were to choose to support the REPORT on the 
root resource. In reality servers would probably limit the scope of the 
report to a reasonable "sub-hierarchy" set (e.g. CalDAV and CardDAV servers 
would only support the REPORT on calendar or address book home collections 
and not on any parents of those).

-- 
Cyrus Daboo

_______________________________________________
caldav mailing list
caldav@ietf.org
https://www.ietf.org/mailman/listinfo/caldav


From andrew@morphoss.com  Mon Jun  7 21:14:24 2010
Return-Path: <andrew@morphoss.com>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A19803A6925; Mon,  7 Jun 2010 21:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
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 2B6sATi+W7ro; Mon,  7 Jun 2010 21:14:23 -0700 (PDT)
Received: from mail.morphoss.com (hoppy.mcmillan.net.nz [202.78.240.82]) by core3.amsl.com (Postfix) with ESMTP id 2FED43A6888; Mon,  7 Jun 2010 21:14:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.morphoss.com (Postfix) with ESMTP id 063F22374D; Tue,  8 Jun 2010 16:14:10 +1200 (NZST)
X-Virus-Scanned: Debian amavisd-new at mail.morphoss.com
Received: from mail.morphoss.com ([127.0.0.1]) by localhost (hoppy.mcmillan.net.nz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xuN2dWpa9Y-q; Tue,  8 Jun 2010 16:13:54 +1200 (NZST)
Received: from [192.168.55.20] (home.mcmillan.net.nz [202.160.48.75]) (Authenticated sender: andrew@mail.morphoss.com) by mail.morphoss.com (Postfix) with ESMTPSA id DD8EA23757; Tue,  8 Jun 2010 16:13:53 +1200 (NZST)
From: Andrew McMillan <andrew@morphoss.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <001f01cb06a4$38a483a0$a9ed8ae0$@net> (sfid-20100608_124828_094303_CD91AB6B)
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <001f01cb06a4$38a483a0$a9ed8ae0$@net> (sfid-20100608_124828_094303_CD91AB6B)
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ejaWjkx6i6kFmrtII6i/"
Date: Tue, 08 Jun 2010 16:13:52 +1200
Message-ID: <1275970432.3820.9378.camel@happy.home.mcmillan.net.nz>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.1.2 
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 04:14:25 -0000

--=-ejaWjkx6i6kFmrtII6i/
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2010-06-07 at 20:47 -0400, Tim Hare wrote:
> I am not an implementor, but it seems to me that many Calendar/addressboo=
k
> collections might be depth:2 to accomodate groups like mailing lists ?

Hi Tim,

Yes, that could be one way of implementing such things, though the
specifications for CalDAV explicitly state that calendar collections may
not contain collections.

In DAViCal I did implement multiple-calendars-as-one-calendar by
allowing collections of calendars (or more typically bindings to
calendars) to present as if they were a calendar.  In order to avoid
stepping on the specification I gave these collections a special
resourcetype.

FWIW DAViCal's implementation of WebDAV sync is OK with depth infinity,
since (as the other poster points out) it makes little difference for
query based systems.

Regards,
					Andrew McMillan.

>=20
> Tim Hare
> Interested Bystander, Non-Inc.
>=20
> -----Original Message-----
> From: caldav-bounces@ietf.org [mailto:caldav-bounces@ietf.org] On Behalf =
Of
> Cyrus Daboo
> Sent: Monday, June 07, 2010 9:57 AM
> To: w3c-dist-auth@w3.org
> Cc: caldav@ietf.org; vcarddav@ietf.org
> Subject: [caldav] WebDAv collection sync: last issue
>=20
> Hi folks,
> The latest WebDAV collection sync draft is here:=20
> <https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>. We believe w=
e=20
> are close to done with this and would like to submit to the IESG soon.=
=20
> However, there is one open issue that we need feedback from implementors =
on.
>=20
> The question is whether collection resources that are immediate children =
of=20
> the collection being targeted for the REPORT should be reported as=20
> "modified" if any of their child resources (depth infinity) are modified.
>=20
> Key points:
>=20
> 1) We have deliberately scoped the REPORT defined in this draft to be=20
> Depth:1 only - i.e. it will only report changes to immediate children.=
=20
> Depth:infinity change reporting was ruled out at this time (though=20
> eventually we would expect to see it defined if there is interest).
>=20
> 2) The first real implementations of this REPORT are being done for CalDA=
V=20
> and CardDAV servers where typically calendar/addressbook collections only=
=20
> have immediate child resources and not collections - so the draft as=20
> currently written is fine. (BTW there are already several client and serv=
er=20
> implementations of this draft that have been tested at various interops).=
=20
> However, my concern is that more "general" WebDAV servers may wish to do=
=20
> reporting of changes to immediate child collections to allow clients to=
=20
> progressively sync an entire hierarchy.
>=20
> 3) Reporting changes to immediate child collections requires any change a=
t=20
> depth:infinity within those collections to "bubble up" - i.e. a change wi=
th=20
> a collection changes its DAV:sync-token and the properties of all its=20
> parent collections. This potentially places a big performance burden on t=
he=20
> server - particularly if it were to choose to support the REPORT on the=
=20
> root resource. In reality servers would probably limit the scope of the=
=20
> report to a reasonable "sub-hierarchy" set (e.g. CalDAV and CardDAV serve=
rs=20
> would only support the REPORT on calendar or address book home collection=
s=20
> and not on any parents of those).
>=20

--=20
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
               Chicken Little only has to be right once.
------------------------------------------------------------------------


--=-ejaWjkx6i6kFmrtII6i/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkwNw3wACgkQjJA0f48GgBJSfwCgressZTzmgNLG7rdZIqrH64P3
SMoAoL51F2PYhe3m0+noO3Q06w9LDDXM
=XrLh
-----END PGP SIGNATURE-----

--=-ejaWjkx6i6kFmrtII6i/--


From andrew@morphoss.com  Mon Jun  7 21:30:44 2010
Return-Path: <andrew@morphoss.com>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31B523A6888; Mon,  7 Jun 2010 21:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level: 
X-Spam-Status: No, score=-3.161 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_00=-2.599]
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 37dbT706OIi7; Mon,  7 Jun 2010 21:30:41 -0700 (PDT)
Received: from mail385c25.carrierzone.com (mail385c25.carrierzone.com [209.235.146.155]) by core3.amsl.com (Postfix) with ESMTP id 220703A67ED; Mon,  7 Jun 2010 21:30:40 -0700 (PDT)
X-Authenticated-User: master.tencoassemblies.com
Received: from TENCOSERVER.TencoAssembliesInc.local (173-161-228-126-Philadelphia.hfc.comcastbusiness.net [173.161.228.126]) (authenticated bits=0) by mail385c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o584UVTt001713; Tue, 8 Jun 2010 04:30:33 GMT
Received: from TENCOSERVER.TencoAssembliesInc.local ([10.0.0.2]) by TENCOSERVER.TencoAssembliesInc.local with Microsoft SMTPSVC(5.0.2195.6713); Tue, 8 Jun 2010 00:30:31 -0400
Received: by TENCOSERVER.TencoAssembliesInc.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download) id MSG06082010-003028-2509.MMD@TencoAssembliesInc.local; Tue, 8 Jun 2010 00:30:28 -0400
X-Envelope-From: w3c-dist-auth-request@frink.w3.org
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by mail367c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o584GF9c005069 for <JTentilucci@tencoassemblies.com>; Tue, 8 Jun 2010 00:16:17 -0400
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1OLqD7-0001nA-K8 for w3c-dist-auth-dist@listhub.w3.org; Tue, 08 Jun 2010 04:14:45 +0000
Received: from bart.w3.org ([128.30.52.63]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <andrew@morphoss.com>) id 1OLqD6-0001m6-1o for w3c-dist-auth@listhub.w3.org; Tue, 08 Jun 2010 04:14:44 +0000
Received: from hoppy.mcmillan.net.nz ([202.78.240.82] helo=mail.morphoss.com ident=postfix) by bart.w3.org with esmtp (Exim 4.69) (envelope-from <andrew@morphoss.com>) id 1OLqD2-00046T-Vm for w3c-dist-auth@w3.org; Tue, 08 Jun 2010 04:14:43 +0000
Received: from localhost (localhost [127.0.0.1]) by mail.morphoss.com (Postfix) with ESMTP id 063F22374D; Tue,  8 Jun 2010 16:14:10 +1200 (NZST)
X-Virus-Scanned: Debian amavisd-new at mail.morphoss.com
Received: from mail.morphoss.com ([127.0.0.1]) by localhost (hoppy.mcmillan.net.nz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xuN2dWpa9Y-q; Tue,  8 Jun 2010 16:13:54 +1200 (NZST)
Received: from [192.168.55.20] (home.mcmillan.net.nz [202.160.48.75]) (Authenticated sender: andrew@mail.morphoss.com) by mail.morphoss.com (Postfix) with ESMTPSA id DD8EA23757; Tue,  8 Jun 2010 16:13:53 +1200 (NZST)
From: Andrew McMillan <andrew@morphoss.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <001f01cb06a4$38a483a0$a9ed8ae0$@net> (sfid-20100608_124828_094303_CD91AB6B)
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <001f01cb06a4$38a483a0$a9ed8ae0$@net> (sfid-20100608_124828_094303_CD91AB6B)
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ejaWjkx6i6kFmrtII6i/"
Date: Tue, 08 Jun 2010 16:13:52 +1200
Message-ID: <1275970432.3820.9378.camel@happy.home.mcmillan.net.nz>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.1.2 
Received-SPF: pass
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599, SPF_PASS=-0.001
X-W3C-Scan-Sig: bart.w3.org 1OLqD2-00046T-Vm 660abe00d2bb237682fad0f3fdcccd87
X-Original-To: w3c-dist-auth@w3.org
Archived-At: <http://www.w3.org/mid/1275970432.3820.9378.camel@happy.home.mcmillan.net.nz>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/13269
X-Loop: w3c-dist-auth@w3.org
Sender: w3c-dist-auth-request@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
Resent-Message-Id: <E1OLqD7-0001nA-K8@frink.w3.org>
Resent-Date: Tue, 08 Jun 2010 04:14:45 +0000
X-MMR: 0
X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com)
X-OriginalArrivalTime: 08 Jun 2010 04:30:31.0521 (UTC) FILETIME=[54700D10:01CB06C3]
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 04:30:44 -0000

--=-ejaWjkx6i6kFmrtII6i/
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2010-06-07 at 20:47 -0400, Tim Hare wrote:
> I am not an implementor, but it seems to me that many Calendar/addressboo=
k
> collections might be depth:2 to accomodate groups like mailing lists ?

Hi Tim,

Yes, that could be one way of implementing such things, though the
specifications for CalDAV explicitly state that calendar collections may
not contain collections.

In DAViCal I did implement multiple-calendars-as-one-calendar by
allowing collections of calendars (or more typically bindings to
calendars) to present as if they were a calendar.  In order to avoid
stepping on the specification I gave these collections a special
resourcetype.

FWIW DAViCal's implementation of WebDAV sync is OK with depth infinity,
since (as the other poster points out) it makes little difference for
query based systems.

Regards,
					Andrew McMillan.

>=20
> Tim Hare
> Interested Bystander, Non-Inc.
>=20
> -----Original Message-----
> From: caldav-bounces@ietf.org [mailto:caldav-bounces@ietf.org] On Behalf =
Of
> Cyrus Daboo
> Sent: Monday, June 07, 2010 9:57 AM
> To: w3c-dist-auth@w3.org
> Cc: caldav@ietf.org; vcarddav@ietf.org
> Subject: [caldav] WebDAv collection sync: last issue
>=20
> Hi folks,
> The latest WebDAV collection sync draft is here:=20
> <https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>. We believe w=
e=20
> are close to done with this and would like to submit to the IESG soon.=20=

> However, there is one open issue that we need feedback from implementors =
on.
>=20
> The question is whether collection resources that are immediate children =
of=20
> the collection being targeted for the REPORT should be reported as=20
> "modified" if any of their child resources (depth infinity) are modified.
>=20
> Key points:
>=20
> 1) We have deliberately scoped the REPORT defined in this draft to be=20
> Depth:1 only - i.e. it will only report changes to immediate children.=20=

> Depth:infinity change reporting was ruled out at this time (though=20
> eventually we would expect to see it defined if there is interest).
>=20
> 2) The first real implementations of this REPORT are being done for CalDA=
V=20
> and CardDAV servers where typically calendar/addressbook collections only=
=20
> have immediate child resources and not collections - so the draft as=20
> currently written is fine. (BTW there are already several client and serv=
er=20
> implementations of this draft that have been tested at various interops).=
=20
> However, my concern is that more "general" WebDAV servers may wish to do=
=20
> reporting of changes to immediate child collections to allow clients to=
=20
> progressively sync an entire hierarchy.
>=20
> 3) Reporting changes to immediate child collections requires any change a=
t=20
> depth:infinity within those collections to "bubble up" - i.e. a change wi=
th=20
> a collection changes its DAV:sync-token and the properties of all its=20
> parent collections. This potentially places a big performance burden on t=
he=20
> server - particularly if it were to choose to support the REPORT on the=
=20
> root resource. In reality servers would probably limit the scope of the=
=20
> report to a reasonable "sub-hierarchy" set (e.g. CalDAV and CardDAV serve=
rs=20
> would only support the REPORT on calendar or address book home collection=
s=20
> and not on any parents of those).
>=20

--=20
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
               Chicken Little only has to be right once.
------------------------------------------------------------------------


--=-ejaWjkx6i6kFmrtII6i/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkwNw3wACgkQjJA0f48GgBJSfwCgressZTzmgNLG7rdZIqrH64P3
SMoAoL51F2PYhe3m0+noO3Q06w9LDDXM
=XrLh
-----END PGP SIGNATURE-----

--=-ejaWjkx6i6kFmrtII6i/--



From julian.reschke@gmx.de  Tue Jun  8 00:11:52 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0158F3A69AC for <caldav@core3.amsl.com>; Tue,  8 Jun 2010 00:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.967
X-Spam-Level: 
X-Spam-Status: No, score=-5.967 tagged_above=-999 required=5 tests=[AWL=-3.368, BAYES_00=-2.599]
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 ijmDYs2T2bH6 for <caldav@core3.amsl.com>; Tue,  8 Jun 2010 00:11:47 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 4BF773A69A4 for <caldav@ietf.org>; Tue,  8 Jun 2010 00:11:46 -0700 (PDT)
Received: (qmail invoked by alias); 08 Jun 2010 07:11:46 -0000
Received: from p508FDFE6.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.223.230] by mail.gmx.net (mp069) with SMTP; 08 Jun 2010 09:11:46 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX193mP9tOZR3eJ3GEgTfEZafoHkf8LiTm9vRplymww tiRwAhBk872bMY
Message-ID: <4C0DED2A.80701@gmx.de>
Date: Tue, 08 Jun 2010 09:11:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: Tim Hare <TimHare@comcast.net>
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <001f01cb06a4$38a483a0$a9ed8ae0$@net>
In-Reply-To: <001f01cb06a4$38a483a0$a9ed8ae0$@net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV]  WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 07:11:52 -0000

On 08.06.2010 02:47, Tim Hare wrote:
> I am not an implementor, but it seems to me that many Calendar/addressbook
> collections might be depth:2 to accomodate groups like mailing lists ?
>
> Tim Hare
> Interested Bystander, Non-Inc.

There is no "Depth: 2" unless we introduce it. The Depth header is 
inherited from RFC 4918 (see 
<http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.10.2>).

Best regards, Julian

From julian.reschke@gmx.de  Tue Jun  8 00:14:25 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DAE23A69B1 for <caldav@core3.amsl.com>; Tue,  8 Jun 2010 00:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.866
X-Spam-Level: 
X-Spam-Status: No, score=-2.866 tagged_above=-999 required=5 tests=[AWL=-3.167, BAYES_50=0.001, 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 MUPYVVvijiP0 for <caldav@core3.amsl.com>; Tue,  8 Jun 2010 00:14:24 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id EB3123A69A4 for <caldav@ietf.org>; Tue,  8 Jun 2010 00:14:22 -0700 (PDT)
Received: (qmail invoked by alias); 08 Jun 2010 07:14:22 -0000
Received: from p508FDFE6.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.223.230] by mail.gmx.net (mp041) with SMTP; 08 Jun 2010 09:14:22 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18W8Xs7hZIWxYrG+8QmIKtXa4KaEtNgsuvsjZX8lT EA5vhy5+4SsvOy
Message-ID: <4C0DEDC8.1090200@gmx.de>
Date: Tue, 08 Jun 2010 09:14:16 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Werner_Donn=E9?= <werner.donne@pincette.biz>
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <0296DA16-10E8-47A9-959D-2B9681BEAB36@pincette.biz>
In-Reply-To: <0296DA16-10E8-47A9-959D-2B9681BEAB36@pincette.biz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 07:14:25 -0000

On 07.06.2010 17:11, Werner Donné wrote:
> Hi,
>
> I don't see why Depth:infinity should be ruled out from the start. You can let the server decide if the performance penalty is too high or not. A server with a relational system underneath it, for example, can do this with one query.
>
> I don't agree with the "bubble up" principle. A collection changes when its member set changes. Changing a resource that is referred to by one of the members doesn't affect the collection, whether that resource is a collection or not. I think the "bubble up" principal is not consistent with the "getlastmodified" property. It is also not needed if Depth:infinity is supported.
>
> Best regards,
>
> Werner.

Agreed.

In particular: defining a report works by defining it for Depth: 0. The 
semantics for Depth: 1 and Depth: infinity follow by the definition in 
RFC 3253.

It's probably *really* time to pull the definition of REPORT out of RFC 
3253 and place it into a separate spec, including more rationale, 
recommendations for defining new reports, and examples.

Best regards, Julian

From julian.reschke@gmx.de  Tue Jun  8 00:30:42 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D95EB3A69B3; Tue,  8 Jun 2010 00:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level: 
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[AWL=-1.649, BAYES_00=-2.599, 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 KfkH3NraXJ2u; Tue,  8 Jun 2010 00:30:42 -0700 (PDT)
Received: from mail383c25.carrierzone.com (mail383c25.carrierzone.com [209.235.146.153]) by core3.amsl.com (Postfix) with ESMTP id C390B3A690D; Tue,  8 Jun 2010 00:30:41 -0700 (PDT)
X-Authenticated-User: master.tencoassemblies.com
Received: from TENCOSERVER.TencoAssembliesInc.local (173-161-228-126-Philadelphia.hfc.comcastbusiness.net [173.161.228.126]) (authenticated bits=0) by mail383c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o587UZDP015272; Tue, 8 Jun 2010 07:30:36 GMT
Received: from TENCOSERVER.TencoAssembliesInc.local ([10.0.0.2]) by TENCOSERVER.TencoAssembliesInc.local with Microsoft SMTPSVC(5.0.2195.6713); Tue, 8 Jun 2010 03:30:34 -0400
Received: by TENCOSERVER.TencoAssembliesInc.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download) id MSG06082010-033029-2538.MMD@TencoAssembliesInc.local; Tue, 8 Jun 2010 03:30:29 -0400
X-Envelope-From: w3c-dist-auth-request@frink.w3.org
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by mail368c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o587GHTo008153 for <JTentilucci@tencoassemblies.com>; Tue, 8 Jun 2010 03:16:20 -0400
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1OLt1W-00038u-By for w3c-dist-auth-dist@listhub.w3.org; Tue, 08 Jun 2010 07:14:58 +0000
Received: from bart.w3.org ([128.30.52.63]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OLt1U-00036A-MZ for w3c-dist-auth@listhub.w3.org; Tue, 08 Jun 2010 07:14:56 +0000
Received: from mail.gmx.net ([213.165.64.20]) by bart.w3.org with smtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OLt1S-00067h-Nh for w3c-dist-auth@w3.org; Tue, 08 Jun 2010 07:14:56 +0000
Received: (qmail invoked by alias); 08 Jun 2010 07:14:22 -0000
Received: from p508FDFE6.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.223.230] by mail.gmx.net (mp041) with SMTP; 08 Jun 2010 09:14:22 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18W8Xs7hZIWxYrG+8QmIKtXa4KaEtNgsuvsjZX8lT EA5vhy5+4SsvOy
Message-ID: <4C0DEDC8.1090200@gmx.de>
Date: Tue, 08 Jun 2010 09:14:16 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Werner_Donn=E9?= <werner.donne@pincette.biz>
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <0296DA16-10E8-47A9-959D-2B9681BEAB36@pincette.biz>
In-Reply-To: <0296DA16-10E8-47A9-959D-2B9681BEAB36@pincette.biz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Received-SPF: pass
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599, SPF_PASS=-0.001
X-W3C-Scan-Sig: bart.w3.org 1OLt1S-00067h-Nh dfeccd05ff6bff8fd01d74b305c6e4fb
X-Original-To: w3c-dist-auth@w3.org
Archived-At: <http://www.w3.org/mid/4C0DEDC8.1090200@gmx.de>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/13270
X-Loop: w3c-dist-auth@w3.org
Sender: w3c-dist-auth-request@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
Resent-Message-Id: <E1OLt1W-00038u-By@frink.w3.org>
Resent-Date: Tue, 08 Jun 2010 07:14:58 +0000
X-MMR: 0
X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com)
X-OriginalArrivalTime: 08 Jun 2010 07:30:34.0896 (UTC) FILETIME=[7BC04100:01CB06DC]
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 07:30:43 -0000

On 07.06.2010 17:11, Werner Donné wrote:
> Hi,
>
> I don't see why Depth:infinity should be ruled out from the start. You can let the server decide if the performance penalty is too high or not. A server with a relational system underneath it, for example, can do this with one query.
>
> I don't agree with the "bubble up" principle. A collection changes when its member set changes. Changing a resource that is referred to by one of the members doesn't affect the collection, whether that resource is a collection or not. I think the "bubble up" principal is not consistent with the "getlastmodified" property. It is also not needed if Depth:infinity is supported.
>
> Best regards,
>
> Werner.

Agreed.

In particular: defining a report works by defining it for Depth: 0. The 
semantics for Depth: 1 and Depth: infinity follow by the definition in 
RFC 3253.

It's probably *really* time to pull the definition of REPORT out of RFC 
3253 and place it into a separate spec, including more rationale, 
recommendations for defining new reports, and examples.

Best regards, Julian


From rpolli@babel.it  Tue Jun  8 02:15:54 2010
Return-Path: <rpolli@babel.it>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9CB93A69A8; Tue,  8 Jun 2010 02:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.081
X-Spam-Level: ***
X-Spam-Status: No, score=3.081 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_13=0.6, J_CHICKENPOX_55=0.6]
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 y3u1+nkp5Qkk; Tue,  8 Jun 2010 02:15:33 -0700 (PDT)
Received: from smtp.babel.it (ns1.babel.it [89.97.242.210]) by core3.amsl.com (Postfix) with ESMTP id 81FE828C149; Tue,  8 Jun 2010 02:15:30 -0700 (PDT)
Received: from smtp.babel.it (localhost [127.0.0.1]) by smtp.babel.it (Postfix) with ESMTP id 6910B4D492; Tue,  8 Jun 2010 11:15:26 +0200 (CEST)
Received: from rpolli.localnet (rpolli.dhcp.babel.it [10.0.10.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rpolli) by smtp.babel.it (Postfix) with ESMTPSA id 3F5FE4D478; Tue,  8 Jun 2010 11:15:26 +0200 (CEST)
From: Roberto Polli <rpolli@babel.it>
Organization: Babel s.r.l
To: caldav@ietf.org
Date: Tue, 8 Jun 2010 11:15:47 +0200
User-Agent: KMail/1.12.2 (Linux/2.6.31-21-generic; KDE/4.3.2; i686; ; )
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
In-Reply-To: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201006081115.47308.rpolli@babel.it>
X-AV-Checked: ClamAV using ClamSMTP
Cc: w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 09:15:55 -0000

On Monday 07 June 2010 15:57:09 Cyrus Daboo wrote:
> The question is whether collection resources that are immediate children =
of
> the collection being targeted for the REPORT should be reported as
> "modified" if any of their child resources (depth infinity) are modified.
aware of the performance issue, I think that the right behavior should be=20
depth: infinity.

while the performance issue should be solved by the storage layer (eg.=20
filesystem or database, which perform that op quite nicely)
and while the average depth level rarely goes above 4 (and in most cases it=
's=20
3 or 2)=20

Having depth:1 can be confusing, as that feature is supposed to notify whet=
her=20
I have to sync or not a given folder.

My 2 cents+Peace,
R.

=2D-=20

Roberto Polli
Babel S.r.l. - http://www.babel.it
Tel. +39.06.91801075 - fax +39.06.91612446
Tel. cel +39.340.6522736
P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma)

"Il seguente messaggio contiene informazioni riservate. Qualora questo=20
messaggio fosse da Voi ricevuto per errore, Vogliate cortesemente darcene=20
notizia a mezzo e-mail. Vi sollecitiamo altres=EC a distruggere il messaggi=
o=20
erroneamente ricevuto. Quanto precede Vi viene chiesto ai fini del rispetto=
=20
della legge in materia di protezione dei dati personali."

From julian.reschke@gmx.de  Tue Jun  8 03:00:36 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A96E028C15D; Tue,  8 Jun 2010 03:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.352
X-Spam-Level: 
X-Spam-Status: No, score=-8.352 tagged_above=-999 required=5 tests=[AWL=2.247,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 zfdQmX2v7o4W; Tue,  8 Jun 2010 03:00:36 -0700 (PDT)
Received: from mail382c25.carrierzone.com (mail382c25.carrierzone.com [209.235.146.152]) by core3.amsl.com (Postfix) with ESMTP id 4388F28C15B; Tue,  8 Jun 2010 03:00:35 -0700 (PDT)
X-Authenticated-User: master.tencoassemblies.com
Received: from TENCOSERVER.TencoAssembliesInc.local (173-161-228-126-Philadelphia.hfc.comcastbusiness.net [173.161.228.126]) (authenticated bits=0) by mail382c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o58A0WkG027578; Tue, 8 Jun 2010 10:00:33 GMT
Received: from TENCOSERVER.TencoAssembliesInc.local ([10.0.0.2]) by TENCOSERVER.TencoAssembliesInc.local with Microsoft SMTPSVC(5.0.2195.6713); Tue, 8 Jun 2010 06:00:31 -0400
Received: by TENCOSERVER.TencoAssembliesInc.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download) id MSG06082010-060029-2559.MMD@TencoAssembliesInc.local; Tue, 8 Jun 2010 06:00:29 -0400
X-Envelope-From: w3c-dist-auth-request@frink.w3.org
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by mail367c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id o589xhEc012361 for <JTentilucci@tencoassemblies.com>; Tue, 8 Jun 2010 05:59:45 -0400
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1OLvaI-0001K2-Tn for w3c-dist-auth-dist@listhub.w3.org; Tue, 08 Jun 2010 09:59:02 +0000
Received: from bart.w3.org ([128.30.52.63]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OLvaI-0001Is-7v for w3c-dist-auth@listhub.w3.org; Tue, 08 Jun 2010 09:59:02 +0000
Received: from mail.gmx.net ([213.165.64.20]) by bart.w3.org with smtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1OLvaD-0003e2-F6 for w3c-dist-auth@w3.org; Tue, 08 Jun 2010 09:59:02 +0000
Received: (qmail invoked by alias); 08 Jun 2010 07:11:46 -0000
Received: from p508FDFE6.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.223.230] by mail.gmx.net (mp069) with SMTP; 08 Jun 2010 09:11:46 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX193mP9tOZR3eJ3GEgTfEZafoHkf8LiTm9vRplymww tiRwAhBk872bMY
Message-ID: <4C0DED2A.80701@gmx.de>
Date: Tue, 08 Jun 2010 09:11:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: Tim Hare <TimHare@comcast.net>
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com> <001f01cb06a4$38a483a0$a9ed8ae0$@net>
In-Reply-To: <001f01cb06a4$38a483a0$a9ed8ae0$@net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Received-SPF: pass
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599, SPF_PASS=-0.001
X-W3C-Scan-Sig: bart.w3.org 1OLvaD-0003e2-F6 d10de9864103b3f26913363220a9c811
X-Original-To: w3c-dist-auth@w3.org
Archived-At: <http://www.w3.org/mid/4C0DED2A.80701@gmx.de>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/13272
X-Loop: w3c-dist-auth@w3.org
Sender: w3c-dist-auth-request@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
Resent-Message-Id: <E1OLvaI-0001K2-Tn@frink.w3.org>
Resent-Date: Tue, 08 Jun 2010 09:59:02 +0000
X-MMR: 0
X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com)
X-OriginalArrivalTime: 08 Jun 2010 10:00:31.0692 (UTC) FILETIME=[6E4260C0:01CB06F1]
Cc: caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV]  WebDAv collection sync: last issue
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 10:00:36 -0000

On 08.06.2010 02:47, Tim Hare wrote:
> I am not an implementor, but it seems to me that many Calendar/addressbook
> collections might be depth:2 to accomodate groups like mailing lists ?
>
> Tim Hare
> Interested Bystander, Non-Inc.

There is no "Depth: 2" unless we introduce it. The Depth header is 
inherited from RFC 4918 (see 
<http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.10.2>).

Best regards, Julian

