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

Julian Reschke <[email protected]> Mon, 13 Jul 2009 22:12:22 +0200
Newsgroups gmane.ietf.webdav
Message-ID <[email protected]>
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