W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

[Fwd: I-D ACTION:draft-dusseault-caldav-08.txt]

From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Date: Mon, 03 Oct 2005 21:35:13 -0400
Message-ID: <4341DC51.4050401@oracle.com>
To: CalDAV DevList <ietf-caldav@osafoundation.org>
CC: Calsify WG <ietf-calsify@osafoundation.org>, WebDAV WG <w3c-dist-auth@w3.org>, Lisa Dusseault <lisa@osafoundation.org>, Cyrus Daboo <cyrus@daboo.name>
We submitted CalDAV draft -08 to the IETF last Friday.
It is now available at the following URL:


We are planning to submit a new revision in a few weeks for
an informal Last-Call on the ietf-caldav, ietf-calsify and
w3c-dist-auth (WebDAV) mailing lists before we actually submit
it to the IESG.

Please review the draft and send us feedback/questions/comments.


B.1.  Changes in -08

    a.  Removed statement that said that client SHOULD always request
        DAV:getetag in calendar REPORTs.

    b.  Removed redefiniton of DAV:response.

    c.  Removed XML elements CALDAV:calendar-data-only.

    d.  Removed resource type CALDAV:calendar-home.

    e.  Moved the CALDAV:calendar-data element in the DAV:prop element in
        requests, and in the DAV:propstat element in responses.

    f.  Further defined the request body of MKCALENDAR to allow clients
        to set properties at calendar collection creation time.

    g.  Renamed CALDAV:calendar-home-URL to CALDAV:calendar-home-set

    h.  Clarified the fact that calendar collections may only contain
        calendar object resources and ordinary collections.

    i.  Clarified that calendar REPORTs should only be applied to
        calendar object resources contained in calendar collections.

    j.  Changed the CALDAV:calendar-component-restriction-set and CALDAV:
        calendar-restriction properties to always be protected.

    k.  Changed to use existing postcondition DAV:needs-privileges
        instead of a new CALDAV:insufficient-privilege postcondition.

    l.  Added example for limit-recurrence-set.

    m.  Added example for expand-recurrence-set.

    n.  Moved CALDAV:calendar-address-set in the calendar-schedule draft
        and renamed it to CALDAV:calendar-user-address-set.

    o.  Added guidelines on attachments and alarms.

-------- Original Message --------
Subject: I-D ACTION:draft-dusseault-caldav-08.txt
Date: Mon, 03 Oct 2005 15:50:02 -0400
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 

	Title		: Calendaring Extensions to WebDAV (CalDAV)
	Author(s)	: L. Dusseault, et al.
	Filename	: draft-dusseault-caldav-08.txt
	Pages		: 75
	Date		: 2005-10-3
This document specifies a set of methods, headers, message bodies,
    properties, and reports that define calendar access extensions to the
    WebDAV protocol.  The new protocol elements are intended to make
    WebDAV-based calendaring and scheduling an interoperable standard
    that supports calendar access, calendar management, calendar sharing,
    and calendar publishing.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-dusseault-caldav-08.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-dusseault-caldav-08.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

Received on Tuesday, 4 October 2005 01:35:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:33 UTC