Skip to main content

Calendaring Extensions to WebDAV (CalDAV)
RFC 4791

Revision differences

Document history

Date Rev. By Action
2020-01-21
15 (System) Received changes through RFC Editor sync (added Verified Errata tag)
2015-10-14
15 (System) Notify list changed from lisa@osafoundation.org to (None)
2012-08-22
15 (System) post-migration administrative database adjustment to the No Objection position for Bill Fenner
2012-08-22
15 (System) post-migration administrative database adjustment to the No Objection position for Sam Hartman
2012-08-22
15 (System) post-migration administrative database adjustment to the No Objection position for Russ Housley
2007-04-08
15 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-04-08
15 Amy Vezza [Note]: 'RFC 4791' added by Amy Vezza
2007-03-15
15 (System) RFC published
2006-11-08
15 (System) Request for Early review by SECDIR Completed. Reviewer: Angelos Keromytis.
2006-10-24
15 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2006-10-22
15 (System) IANA Action state changed to In Progress from Waiting on RFC Editor
2006-10-19
15 (System) IANA Action state changed to Waiting on RFC Editor from Waiting on Authors
2006-10-17
15 (System) IANA Action state changed to Waiting on Authors from In Progress
2006-10-09
15 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2006-10-06
15 (System) IANA Action state changed to In Progress from Waiting on RFC Editor
2006-10-05
15 Amy Vezza IESG state changed to Approved-announcement sent
2006-10-05
15 Amy Vezza IESG has approved the document
2006-10-05
15 Amy Vezza Closed "Approve" ballot
2006-10-05
15 Ted Hardie State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Ted Hardie
2006-09-18
15 Sam Hartman [Ballot Position Update] Position for Sam Hartman has been changed to No Objection from Discuss by Sam Hartman
2006-09-15
15 (System) New version available: draft-dusseault-caldav-15.txt
2006-09-01
15 (System) Removed from agenda for telechat - 2006-08-31
2006-08-31
15 Amy Vezza State Changes to IESG Evaluation::AD Followup from IESG Evaluation by Amy Vezza
2006-08-31
15 Amy Vezza State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Amy Vezza
2006-08-31
15 Sam Hartman
[Ballot discuss]
The internationalization considerations section seems entirelyn
inadequate.  It seems clear that reportes provided in this
specification allow searching on text strings such as …
[Ballot discuss]
The internationalization considerations section seems entirelyn
inadequate.  It seems clear that reportes provided in this
specification allow searching on text strings such as location and
names. 

Section 9.6 contains a facility for doing substring matching on
internationalized strings but contains no discussion of normalization,
limited discussion of case folding, and no discussion of other
matching issues that have been problematic for LDAP, IMAP and other
IETF technologies.  This seems quite inadequate.  If the
internationalization community within the IETF is quite sure that this
is OK, I'll remove the discuss.  I just don't see why text matching in
caldav should be so much easier than IDN or LDAP.
2006-08-30
15 Ted Hardie Placed on agenda for telechat - 2006-08-31 by Ted Hardie
2006-08-30
15 Ted Hardie Removed from agenda for telechat - 2006-08-31 by Ted Hardie
2006-08-29
15 Ross Callon [Ballot Position Update] New position, No Objection, has been recorded by Ross Callon
2006-08-25
14 (System) New version available: draft-dusseault-caldav-14.txt
2006-08-15
15 Yoshiko Fong
IANA Last Call Comment:

Upon approval of this document, the IANA will make the following assignments in the XML Namespaces registry located at
http://www.iana.org/assignments/xml-registry/ns.html

id …
IANA Last Call Comment:

Upon approval of this document, the IANA will make the following assignments in the XML Namespaces registry located at
http://www.iana.org/assignments/xml-registry/ns.html

id URI Registration template Reference
caldev urn:ietf:params:xml:ns:caldav None specified RFCtobe-
dusseault-caldav

We understand the above to be the only IANA Actions for this document.
Note: The document defines a large collection of elements for the
namespace but does not request a registry for these elements.
2006-08-15
15 Yoshiko Fong
IANA Last Call Comment:

Upon approval of this document, the IANA will make the following assignments in the XML Namespaces registry located at
http://www.iana.org/assignments/xml-registry/ns.html

id …
IANA Last Call Comment:

Upon approval of this document, the IANA will make the following assignments in the XML Namespaces registry located at
http://www.iana.org/assignments/xml-registry/ns.html

id URI Registration template Reference
caldev urn:ietf:params:xml:ns:caldav None specified RFCtobe-
dusseault-caldav

We understand the above to be the only IANA Actions for this document.
Note: The document defines a large collection of elements for the
namespace but does not request a registry for these elements.
2006-08-14
15 Ted Hardie Placed on agenda for telechat - 2006-08-31 by Ted Hardie
2006-07-30
15 (System) State has been changed to Waiting for AD Go-Ahead from In Last Call by system
2006-07-26
15 Russ Housley [Ballot Position Update] Position for Russ Housley has been changed to No Objection from Discuss by Russ Housley
2006-07-18
15 Amy Vezza Last call sent
2006-07-18
15 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2006-07-18
15 Ted Hardie Last Call was requested by Ted Hardie
2006-07-18
15 Ted Hardie State Changes to Last Call Requested from IESG Evaluation::AD Followup by Ted Hardie
2006-07-14
15 (System) Sub state has been changed to AD Follow up from New Id Needed
2006-07-14
13 (System) New version available: draft-dusseault-caldav-13.txt
2006-06-22
15 Amy Vezza State Changes to IESG Evaluation::Revised ID Needed from IESG Evaluation by Amy Vezza
2006-06-22
15 (System) [Ballot Position Update] Position for Bill Fenner has been changed to No Objection from Discuss by IESG Secretary
2006-06-22
15 Bill Fenner
[Ballot comment]
Note:  reference to 2518bis is a potential blocker, since it's still in the WG; is 2518 good enough or will the bis be …
[Ballot comment]
Note:  reference to 2518bis is a potential blocker, since it's still in the WG; is 2518 good enough or will the bis be done soon enough?
2006-06-22
15 Bill Fenner [Ballot discuss]
The reference to 2818 is a normative downref
2006-06-22
15 Bill Fenner [Ballot Position Update] Position for Bill Fenner has been changed to Discuss from No Objection by Bill Fenner
2006-06-22
15 (System) [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson by IESG Secretary
2006-06-22
15 Sam Hartman
[Ballot discuss]
The internationalization considerations section seems entirelyn
inadequate.  It seems clear that reportes provided in this
specification allow searching on text strings such as …
[Ballot discuss]
The internationalization considerations section seems entirelyn
inadequate.  It seems clear that reportes provided in this
specification allow searching on text strings such as location and
names.  Can these strings be internationalized?  If not, what's the
plan to deal with that.  If so, how are normalization and other
internationalization issues handled?  Are there internationalization
concerns regarding sorting of entries?
2006-06-22
15 Sam Hartman [Ballot Position Update] New position, Discuss, has been recorded for Sam Hartman by Sam Hartman
2006-06-22
15 Bill Fenner
[Ballot comment]
Note: reference to 2818 is a normative downref.  reference to 2518bis is a potential blocker, since it's still in the WG; is 2518 …
[Ballot comment]
Note: reference to 2818 is a normative downref.  reference to 2518bis is a potential blocker, since it's still in the WG; is 2518 good enough or will the bis be done soon enough?
2006-06-22
15 Bill Fenner [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner
2006-06-22
15 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko by Jari Arkko
2006-06-22
15 Cullen Jennings
[Ballot comment]
I would have preferred to see the ETag issue driven to general consensus across HTTP, DAV, and this. I hope people still try …
[Ballot comment]
I would have preferred to see the ETag issue driven to general consensus across HTTP, DAV, and this. I hope people still try to drive that to consensus.
2006-06-22
15 Cullen Jennings [Ballot Position Update] New position, No Objection, has been recorded for Cullen Jennings by Cullen Jennings
2006-06-21
15 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2006-06-21
15 Dan Romascanu
[Ballot comment]
The second paragraph in the Introduction section says:

'Discussion of this Internet-Draft is taking place on the mailing list
  .'

Is this …
[Ballot comment]
The second paragraph in the Introduction section says:

'Discussion of this Internet-Draft is taking place on the mailing list
  .'

Is this sentence supposed to be taken out, or maybe refer to 'this memo' instead of 'this Internet-Draft'?
2006-06-21
15 Dan Romascanu [Ballot Position Update] New position, No Objection, has been recorded for Dan Romascanu by Dan Romascanu
2006-06-21
15 Mark Townsley [Ballot Position Update] New position, No Objection, has been recorded for Mark Townsley by Mark Townsley
2006-06-21
15 Lars Eggert [Ballot Position Update] New position, No Objection, has been recorded for Lars Eggert by Lars Eggert
2006-06-20
15 Russ Housley
[Ballot discuss]
Based on the SecDir review by Angelos Keromytis and the discussion
  that followed, I expected to see two paragraphs added to the …
[Ballot discuss]
Based on the SecDir review by Angelos Keromytis and the discussion
  that followed, I expected to see two paragraphs added to the
  Security Considerations section:

    "When rolling up free-busy information, more information about a 
    user's events is exposed if busy periods overlap or abut (this
    tells the client requesting the free-busy information that the
    calendar owner has at least two events, rather than knowing only
    that the calendar owner has one or more events during the busy
    period).  Thus, a conservative approach to calendar data privacy
    would have servers always coalesce busy periods of the same type."

    "Procedure alarms are a known security risk for either clients or 
    servers to handle, particularly when the alarm was created by
    another agent.  Clients and servers are NOT REQUIRED to execute
    such procedure alarms."
2006-06-20
15 Russ Housley [Ballot Position Update] New position, Discuss, has been recorded for Russ Housley by Russ Housley
2006-06-19
15 Brian Carpenter
[Ballot comment]
At the end of section 5.3.4:
  In the case where the data stored by a server as a result of a PUT …
[Ballot comment]
At the end of section 5.3.4:
  In the case where the data stored by a server as a result of a PUT
  request is not equivalent by octet equality to the submitted calendar
  object resource, the behavior of the ETag response header is
  undefined, with the exception that a strong entity tag MUST NOT be
  returned in the response.

This sentence is hard to interpret - what is the meaning of "the behavior
of the ETag response header is undefined" in addition to a strong enity tag
being forbidden?

(From Gen-ART review by Joel Halpern)
2006-06-19
15 Brian Carpenter [Ballot Position Update] New position, No Objection, has been recorded for Brian Carpenter by Brian Carpenter
2006-06-08
15 Ted Hardie Area acronymn has been changed to app from gen
2006-06-08
15 Ted Hardie
Author's response to Last Call comments on ETags

1) Best common practice in WebDAV

Currently very few, if any at all, WebDAV servers change the …
Author's response to Last Call comments on ETags

1) Best common practice in WebDAV

Currently very few, if any at all, WebDAV servers change the content of resource data during a PUT request. Most WebDAV servers do return an ETag on PUT. Thus clients have come to rely on the presence of the ETag to effectively mean that the resource data was stored unchanged and that the ETag can be used in subsequent GET requests etc. This justifies our statement that servers SHOULD return an ETag in a response when the data has not changed.

Now we have CalDAV servers where the resource data MAY be changed. Therefore to be compatible with existing client behavior a server MUST NOT send the ETag in a PUT response when the data changes, otherwise clients will misinterpret it. This justifies our 'MUST NOT' statement.

2) Restricted behavior

The ETag behavior we are talking about is restricted solely to calendar object resources being stored in calendar collections - i.e. it is very specific to CalDAV. This is not 'redefining' HTTP behavior by rather extending it for this one specific application need.

3) Future conflicts

One of Julian's arguments is that our requirement will "risk making CalDAV incompatible with other specs extending HTTP (or HTTP itself, for that matter)". Since we have been careful to require only behavior that already exists in deployed WebDAV servers, CalDAV adds no further incompatibility. If future work to better define the meaning of ETag on PUT ever happens, it will need to take into account the deployed base, and the subset of CalDAV servers will simply happen to be a consistently behaving subset. We believe that our requirements improve the interoperability of CalDAV, without making the future/potential incompatibility problem any worse than it already is.

4) Need/usefulness

In addition to the authors' evaluation of the usefulness of this feature for keeping an offline calendar correct, there have been other requests for predictable behavior w.r.t. PUT and ETags and calendar resources. This was one of the first feature requests from client implementors, including Dan Mosedale and Grant Baillie.
2006-06-06
15 (System) IANA Action state changed to In Progress from Waiting on RFC Editor
2006-06-05
15 Ted Hardie Telechat date was changed to 2006-06-22 from 2006-06-08 by Ted Hardie
2006-06-05
15 Ted Hardie Moved from 6/8/ agenda to allow time to resolve etags discussion
2006-06-02
15 Magnus Westerlund [Ballot Position Update] New position, No Objection, has been recorded for Magnus Westerlund by Magnus Westerlund
2006-05-30
15 Lisa Dusseault [Ballot Position Update] New position, Recuse, has been recorded for Lisa Dusseault by Lisa Dusseault
2006-05-25
15 Ted Hardie State Changes to IESG Evaluation from Waiting for Writeup by Ted Hardie
2006-05-25
15 Ted Hardie Placed on agenda for telechat - 2006-06-08 by Ted Hardie
2006-05-25
15 Ted Hardie [Ballot Position Update] New position, Yes, has been recorded for Ted Hardie
2006-05-25
15 Ted Hardie Ballot has been issued by Ted Hardie
2006-05-25
15 Ted Hardie Created "Approve" ballot
2006-05-24
15 (System) State has been changed to Waiting for Writeup from In Last Call by system
2006-05-02
15 Yoshiko Fong
ANA Last Call Comments:

Upon approval of this document the IANA will register the
urn:ietf:params:xml:ns:caldav XML Namespace in the following registry:
http://www.iana.org/assignments/xml-registry/ns.html

We understand this …
ANA Last Call Comments:

Upon approval of this document the IANA will register the
urn:ietf:params:xml:ns:caldav XML Namespace in the following registry:
http://www.iana.org/assignments/xml-registry/ns.html

We understand this to be the only IANA Action.
2006-04-26
15 (System) IANA Action state changed to In Progress
2006-04-26
15 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2006-04-26
15 Ted Hardie State Changes to Last Call Requested from Publication Requested by Ted Hardie
2006-04-26
15 Ted Hardie Last Call was requested by Ted Hardie
2006-04-26
15 (System) Ballot writeup text was added
2006-04-26
15 (System) Last call text was added
2006-04-26
15 (System) Ballot approval text was added
2006-04-26
12 (System) New version available: draft-dusseault-caldav-12.txt
2006-04-18
15 Ted Hardie Draft Added by Ted Hardie in state Publication Requested
2006-04-10
11 (System) New version available: draft-dusseault-caldav-11.txt
2006-02-23
10 (System) New version available: draft-dusseault-caldav-10.txt
2005-12-28
09 (System) New version available: draft-dusseault-caldav-09.txt
2005-10-03
08 (System) New version available: draft-dusseault-caldav-08.txt
2005-07-19
07 (System) New version available: draft-dusseault-caldav-07.txt
2005-05-25
06 (System) New version available: draft-dusseault-caldav-06.txt
2005-02-11
05 (System) New version available: draft-dusseault-caldav-05.txt
2004-12-14
04 (System) New version available: draft-dusseault-caldav-04.txt
2004-10-28
03 (System) New version available: draft-dusseault-caldav-03.txt
2004-09-21
02 (System) New version available: draft-dusseault-caldav-02.txt
2004-07-20
01 (System) New version available: draft-dusseault-caldav-01.txt
2004-06-24
00 (System) New version available: draft-dusseault-caldav-00.txt