IETF Logo Mail Archive

Re: [caldav] Informal Last Call: CalDAV Scheduling Extensions to WebDAV [Fwd: I-D Action:draft-desruisseaux-caldav-sched-07.txt]

Julian Reschke <julian.reschke@gmx.de> Mon, 13 July 2009 20:12 UTC

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 23BE528C4CC for <caldav@core3.amsl.com>; Mon, 13 Jul 2009 13:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.211
X-Spam-Level:
X-Spam-Status: No, score=-5.211 tagged_above=-999 required=5 tests=[AWL=-2.612, 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 7yp2DPR7vwBO for <caldav@core3.amsl.com>; Mon, 13 Jul 2009 13:12:06 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 4D66C28C4AC for <caldav@ietf.org>; Mon, 13 Jul 2009 13:12:05 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jul 2009 20:12:34 -0000
Received: from p508FE94A.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.233.74] by mail.gmx.net (mp034) with SMTP; 13 Jul 2009 22:12:34 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+/QPNxOVy/VFnwHbmL3SfDSmRe9yRLWjWqIuFLU9 bQYIGCxsQcrflX
Message-ID: <4A5B9526.1010900@gmx.de>
Date: Mon, 13 Jul 2009 22:12:22 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
References: <4A40F50F.3030002@oracle.com> <4A5B1E76.7020803@gmx.de>
In-Reply-To: <4A5B1E76.7020803@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Cc: w3c-dist-auth@w3.org, caldav@ietf.org, calsify@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, Lisa Dusseault <Lisa.Dusseault@messagingarchitects.com>
Subject: Re: [caldav] Informal Last Call: CalDAV Scheduling Extensions to WebDAV [Fwd: I-D Action:draft-desruisseaux-caldav-sched-07.txt]
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, 13 Jul 2009 20:12:07 -0000

Julian Reschke wrote:
> ...
> 8.  Conditional Requests on Scheduling Object Resources
> 
>    In order to do that, this specification introduces a new WebDAV
>    resource property CALDAV:schedule-tag with a corresponding response
>    header "Schedule-Tag", and a new "If-Schedule-Tag-Match" request
>    header to allow client changes to be appropriately merged with server
>    changes in the case where the changes on the server were the result
>    of an "inconsequential" scheduling message update.  An
>    "inconsequential" scheduling message is one which simply updates the
>    status information of Attendees due to a reply from an Attendee.
> 
> JR: that sounds really heavy-weight; I think it would be good to discuss
> this scenario over on the HTTPbis working group's mailing list. Even if new
> state tokens need to be added it is not totally clear why the RFC4918
> can not be used for checking.
> ...

Sorry. I meant to say: "...why the RFC4918 'If' header can not be used...".

BR, Julian

v2.8.7 | Report a Bug | By Email