]> CalDAV Managed Attachments Apple Inc.
1 Infinite Loop Cupertino CA 95014 USA cyrus@daboo.name http://www.apple.com/
Oracle Corporation
180, Avenue de l'Europe Saint Ismier cedex 38334 France arnaud.quillaud@oracle.com http://www.oracle.com/
FastMail US LLC
1429 Walnut St, Suite 1201 Philadephia PA 19102 USA murch@fastmailteam.com http://www.fastmail.com/
Applications and Real-Time Calendering Extensions CalDAV calendaring attachment ATTACH This specification defines an extension to the calendar access protocol (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server. This specification documents existing code deployed by multiple vendors. It is published as an Informational specification rather than Standards Track due to its noncompliance with multiple best current practices of HTTP.
The iCalendar data format is used to represent calendar data and is used with iCalendar Transport-independent Interoperability Protocol (iTIP) to handle scheduling operations between calendar users. defines the Calendaring Extensions to WebDAV (CalDAV), based on HTTP, for accessing calendar data stored on a server. Calendar users often want to include attachments with their calendar data events or tasks (for example a copy of a presentation, or the meeting agenda). iCalendar provides an "ATTACH" property whose value is either the inline Base64 encoded attachment data, or a URL specifying the location of the attachment data. Use of inline attachment data is not ideal with CalDAV because the data would need to be uploaded to the server each time a change to the calendar data is done - even minor changes such as a change to the summary. Whilst a client could choose to use a URL value instead, the problem then becomes where and how the client discovers an appropriate URL to use and how it ensures that only those attendees listed in the event or task are able to access it. This specification solves this problem by having the client send the attachment to the server, separately from the iCalendar data, and the server takes care of adding appropriate "ATTACH" properties in the iCalendar data as well as managing access privileges. The server can also provide additional information to the client about each attachment in the iCalendar data, such as the size and an identifier.
Although this extension to CalDAV has wide deployment, its design does not comply with some of the best current practices of HTTP, namely: All operations on attachments are modeled as HTTP POST operations, where the actual type of operation is specified using a query parameter, instead of using separate HTTP POST, PUT, and DELETE methods where appropriate. Specific query strings are hardwired into the protocol in violation of Section 2.4 of . Additionally, this extension misuses the Content-Disposition header field as a request header field to convey a filename for an attachment rather than using an existing request header field suitable for that purpose, such as "Slug" (see Section 9.7 of ). Rather than creating interoperability problems with deployed code by updating the design of this extension to be compliant with best current practices and to allow this specification to be placed on the Standards Track, it was decided to simply document how existing implementations interoperate and to publish the document as Informational.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The notation used in this memo is the ABNF notation of as used by iCalendar. Any syntax elements shown below that are not explicitly defined in this specification come from iCalendar.
There are four main operations a client needs to do with attachments for calendar data: add, update, remove, and retrieve. The first three operations are carried out by the client issuing an HTTP POST request on the calendar object resource to which the attachment is associated and specifying the appropriate "action" query parameter (see ). In the case of the remove operation, the client can alternatively directly update the calendar object resource and remove the relevant "ATTACH" properties (see ). The retrieve operation is accomplished by simply issuing an HTTP GET request targeting the attachment URI specified by the calendar resource's "ATTACH" property (see ). iCalendar data stored in a CalDAV calendar object resource can contain multiple components when recurrences are involved. In such a situation, the client needs to be able to target a specific recurrence instance or multiple instances when adding or deleting attachments. As a result, the POST request needs to provide a way for the client to specify which recurrence instances should be targeted for the attachment operation. This is accomplished through use of additional query parameters on the POST request-URI.
A server that supports the features described in this specification is REQUIRED to support the CalDAV "calendar-access" features. In addition, such a server SHOULD support the "return=representation" Prefer header field preference on successful HTTP PUT and POST requests targeting existing calendar object resources, by returning the new representation of that calendar resource (including its new ETag header field value) in the response.
A server supporting the features described in this specification MUST include "calendar-managed-attachments" as a token in the DAV response header field (as defined in Section 10.1 of ) from an OPTIONS request on a calendar home collection. A server might choose to not support storing managed attachments on a per-recurrence instance basis (i.e., they can only be added to all instances as a whole). If that is the case, the server MUST also include "calendar-managed-attachments-no-recurrence" as a token in the DAV response header field from an OPTIONS request on a calendar home collection. When that field is present, clients MUST NOT attempt any managed attachment operations that target specific recurrence instances.
An HTTP POST request is used to add, update, or remove attachments. These requests are subject to the preconditions listed in . The request-URI will contain various query parameters to specify the behavior.
The "action" query parameter is used to identify which attachment operation the client is requesting. This parameter MUST be present once on each POST request used to manage attachments. One of these three values MUST be used: Indicates an operation that is adding an attachment to a calendar object resource. See for more details. Indicates an operation that is updating an existing attachment on a calendar object resource. See for more details. Indicates an operation that is removing an attachment from a calendar object resource. See for more details.
Example: https://calendar.example.com/events/1.ics?action=attachment-add
The "rid" query parameter is used to identify which recurrence instances are being targeted by the client for the attachment operation. This query parameter MUST contain one or more items, separated by commas (0x2C). The item values can be in one of two forms: The value "M" (case-insensitive) refers to the "master" recurrence instance, i.e., the component that does not include a "RECURRENCE-ID" property. This item MUST be present only once. A specific iCalendar instance is targeted by using its "RECURRENCE-ID" value as the item value. That value MUST correspond to the RECURRENCE-ID value as stored in the calendar object resource (i.e. without any conversion to UTC). If multiple items of this form are used, they MUST be unique values. For example, to target a recurrence defined by property RECURRENCE-ID;TZID=America/Montreal:20111022T160000, the query parameter rid=20111022T160000 would be used. If the "rid" query parameter is not present, all recurrence instances in the calendar object resource are targeted. The "rid" query parameter MUST NOT be present in the case of an update operation, or if the server chooses not to support per-recurrence instance managed attachments (see ).
Example (targeting the master instance and a specific overridden instance): https://calendar.example.com/events/1.ics? action=attachment-add&rid=M,20111022T160000
The "managed-id" query parameter is used to identify which "ATTACH" property is being updated or removed. The value of this query parameter MUST match the "MANAGED-ID" property parameter value on the "ATTACH" property in the calendar object resource instance(s) targeted by the request. The "managed-id" query parameter MUST NOT be present in the case of an add operation.
Example: https://calendar.example.com/events/1.ics? action=attachment-update&managed-id=aUNhbGVuZGFy
To add an attachment to an existing calendar object resource, the following occurs: The client issues a POST request targeted at the calendar object resource. The request-URI will include an "action" query parameter with the value "attachment-add" (see ). If all recurrence instances are having an attachment added, the "rid" query parameter is not present in the request-URI. If one or more specific recurrence instances are targeted, then the request-URI will include a "rid" query parameter containing the list of instances (see ). The body of the request contains the data for the attachment. The client MUST include a valid Content-Type header field describing the media type of the attachment (as required by HTTP). The client SHOULD include a Content-Disposition header field with a "type" parameter set to "attachment", and a "filename" parameter that indicates the name of the attachment. Note that the use of Content-Disposition as a request header field is nonstandard and specific to this protocol. The client MAY include a Prefer header field with the "return=representation" preference to request that the modified calendar object resource be returned as the body of a successful response to the POST request. When the server receives the POST request it does the following: Validates that any recurrence instances referred to via the "rid" query parameter are valid for the calendar object resource being targeted. Stores the supplied attachment data into a resource and generates an appropriate URI for clients to access the resource. For each affected recurrence instance in the calendar object resource targeted by the request, the server adds an "ATTACH" property, whose value is the URI of the stored attachment. The "ATTACH" property MUST contain a "MANAGED-ID" parameter whose value is a unique identifier (within the context of the server as a whole). The "ATTACH" property SHOULD contain an "FMTTYPE" parameter whose value matches the Content-Type header field value from the request. The "ATTACH" property SHOULD contain an "FILENAME" parameter whose value matches the Content-Disposition header field "filename" parameter value from the request, taking into account the restrictions expressed in . The "ATTACH" property SHOULD include a "SIZE" parameter whose value represents the size in octets of the attachment. If a specified recurrence instance does not have a matching component in the calendar object resource, then the server MUST modify the calendar object resource to include an overridden component with the appropriate "RECURRENCE-ID" property. Upon successful creation of the attachment resource, and modification of the targeted calendar object resource, the server MUST return an appropriate HTTP success status response and include a "Cal-Managed-ID" header field containing the "MANAGED-ID" parameter value of the newly created "ATTACH" property. The client can use the "Cal-Managed-ID" header field value to correlate the attachment with "ATTACH" properties added to the calendar object resource. If the client included a Prefer header field with the "return=representation" preference in the request, the server SHOULD return the modified calendar object resource as the body of the response. Otherwise, the server can expect that the client will reload the calendar object resource with a subsequent GET request to refresh any local cache. In the following example, the client adds a new attachment to a non recurring event and asks the server (via the Prefer header field) to return the modified version of that event in the response.
>> Request <<

Agenda

]]>
>> Response <<
When an attachment is updated the server MUST change the associated "MANAGED-ID" parameter and MAY change the "ATTACH" property value. With this approach, clients are able to determine when an attachment has been updated by some other client by looking for a change to either the "ATTACH" property value, or the "MANAGED-ID" parameter value. To change the data of an existing managed attachment in a calendar object resource, the following occurs: The client issues a POST request targeted at the calendar object resource. The request-URI will include an "action" query parameter with the value "attachment-update" (see ). The request-URI will include a "managed-id" query parameter with the value matching that of the "MANAGED-ID" parameter for the "ATTACH" property being updated (see ). The body of the request contains the updated data for the attachment. The client MUST include a valid Content-Type header field describing the media type of the attachment (as required by HTTP). The client SHOULD include a Content-Disposition header field with a "type" parameter set to "attachment", and a "filename" parameter that indicates the name of the attachment. The client MAY include a Prefer header field with the "return=representation" preference to request that the modified calendar object resource be returned as the body of a successful response to the POST request. When the server receives the POST request it does the following: Validates that the "managed-id" query parameter is valid for the calendar object resource. Updates the content of the attachment resource corresponding to that managed-id with the supplied attachment data. For each affected recurrence instance in the calendar object resource targeted by the request, the server updates the "ATTACH" property whose "MANAGED-ID" property parameter value matches the "managed-id" query parameter. The "MANAGED-ID" parameter value is changed to allow other clients to detect the update, and the property value (attachment URI) might also be changed. The "ATTACH" property SHOULD contain a "FMTTYPE" parameter whose value matches the Content-Type header field value from the request - this could differ from the original value if the media type of the updated attachment is different. The "ATTACH" property SHOULD contain a "FILENAME" parameter whose value matches the Content-Disposition header field "filename" parameter value from the request, taking into account the restrictions expressed in . The "ATTACH" property SHOULD include a "SIZE" parameter whose value represents the size in octets of the updated attachment. Upon successful update of the attachment resource, and modification of the targeted calendar object resource, the server MUST return an appropriate HTTP success status response, and include a "Cal-Managed-ID" header field containing the new value of the "MANAGED-ID" parameter. The client can use the "Cal-Managed-ID" header field value to correlate the attachment with "ATTACH" properties added to the calendar object resource. If the client included a Prefer header field with the "return=representation" preference in the request, the server SHOULD return the modified calendar object resource as the body of the response. Otherwise, the server can expect that the client will reload the calendar object resource with a subsequent GET request to refresh any local cache. The update operation does not take a "rid" parameter and does not add, or remove, any "ATTACH" property in the targeted calendar object resource. To link an existing attachment to a new instance, the client simply does a PUT on the calendar object resource, adding an "ATTACH" property which duplicates the existing one (see ). In the following example, the client updates an existing attachment and asks the server (via the Prefer header field) to return the updated version of that event in the response.
>> Request <<

Agenda

Discuss attachment draft

]]>
>> Response <<
To remove an existing attachment from a calendar object, the following occurs: The client issues a POST request targeted at the calendar object resource. The request-URI will include an "action" query parameter with the value "attachment-remove" (see ). If all recurrence instances are having an attachment removed, the "rid" query parameter is not present in the request-URI. If one or more specific recurrence instances are targeted, then the request-URI will include a "rid" query parameter containing the list of instances (see ). The request-URI will include a "managed-id" query parameter with the value matching that of the "MANAGED-ID" property parameter for the "ATTACH" property being removed (see ). The body of the request will be empty. The client MAY include a Prefer header field with the "return=representation" preference to request that the modified calendar object resource be returned as the body of a successful response to the POST request. When the server receives the POST request it does the following: Validates that any recurrence instances referred to via the "rid" query parameter are valid for the calendar object resource being targeted. Validates that the "managed-id" query parameter is valid for the calendar object resource and specific instances being targeted. For each affected recurrence instance in the calendar object resource targeted by the request, the server removes the matching "ATTACH" property. Note that if a specified recurrence instance does not have a matching component in the calendar object resource, then the server MUST modify the calendar object resource to include an overridden component with the appropriate "RECURRENCE-ID" property, and the matching "ATTACH" property removed. This later case is actually valid only if the master component does include the referenced "ATTACH" property. If the attachment resource is no longer referenced by any instance of the calendar object resource, the server can delete the attachment resource to free up storage space. Upon successful removal of the attachment resource and modification of the targeted calendar object resource, the server MUST return an appropriate HTTP success status response. If the client included a Prefer header field with the "return=representation" preference in the request, the server SHOULD return the modified calendar object resource as the body of the response. Otherwise, the server can expect that the client will reload the calendar object resource with a subsequent GET request to refresh any local cache. In the following example, the client deletes an existing attachment by passing its managed-id in the request. The Prefer header field is not set in the request so the calendar object resource data is not returned in the response.
>> Request <<
>> Response <<
Clients can make use of existing managed attachments by adding the corresponding "ATTACH" property to calendar object resources (subject to the restrictions described in ) If a managed attachment is used in more than calendar resource, servers SHOULD NOT change either the "MANAGED-ID" parameter value or the "ATTACH" property value for these attachments - this ensures that clients do not have to download the attachment data again if they already have it cached. Additionally, servers SHOULD validate "SIZE" parameter values and replace incorrect values with the actual sizes of existing attachments. These PUT requests are subject to the preconditions listed in .
Servers MUST NOT allow clients to update attachment data directly via a PUT on the attachment URI (or via any other HTTP method that modifies content). Instead, attachments can only be updated via use of POST requests on the calendar data.
Clients can remove attachments by simply re-writing the calendar object resource data to remove the appropriate "ATTACH" properties. Servers MUST NOT allow clients to delete attachments directly via a DELETE request on the attachment URI.
Clients retrieve attachments by issuing an HTTP GET request using the value of the corresponding "ATTACH" property as the request-URI, taking into account the substitution mechanism associated with the "CALDAV:managed-attachments-server-URL" property (see ).
This specification creates additional preconditions for the POST method. The new preconditions are: (CALDAV:max-attachment-size): The attachment submitted in the POST request MUST have an octet size less than or equal to the value of the CALDAV:max-attachment-size property value () on the calendar collection of the target calendar resource; (CALDAV:max-attachments-per-resource): The addition of the attachment submitted in the POST request MUST result in the target calendar resource having a number of managed attachments less than or equal to the value of the CALDAV:max-attachments-per-resource property value () on the calendar collection of the target calendar resource; (CALDAV:valid-action): The action query parameter in the POST request MUST contain one of "attachment-add", "attachment-update", or "attachment-remove". (CALDAV:valid-rid): The rid query parameter in the POST request MUST NOT be present for an attachment-update action, and MUST contain the value "M" and/or values corresponding to "RECURRENCE-ID" property values in the iCalendar data targeted by the request. (CALDAV:valid-managed-id): The managed-id query parameter in the POST request MUST NOT be present for an attachment-add action, and MUST contain a value corresponding to a "MANAGED-ID" property parameter value in the iCalendar data targeted by the request. A POST request to add, modify, or delete a managed attachment results in an implicit modification of the targeted calendar resource (equivalent of a PUT). As a consequence, clients should also be prepared to handle preconditions associated with this implicit PUT. This includes (but is not limited to): (CALDAV:max-resource-size) (from Section 5.3.2.1 of ) (DAV:quota-not-exceeded) (from Section 6 of ) (DAV:sufficient-disk-space) (from Section 6 of ) A PUT request to add or modify and existing calendar object resource can make reference to an existing managed attachment. The following new preconditions is defined: (CALDAV:valid-managed-id-parameter): a "MANAGED-ID" property parameter value in the iCalendar data in the PUT request is not valid (e.g., does not match any existing managed attachment). If a precondition for a request is not satisfied: The response status of the request MUST either be 403 (Forbidden), if the request should not be repeated because it will always fail, or 409 (Conflict), if it is expected that the user might be able to resolve the conflict and resubmit the request. The appropriate XML element MUST be returned as the child of a top-level DAV:error element in the response body.
The WebDAV Quotas specification defines two live WebDAV properties (DAV:quota-available-bytes and DAV:quota-used-bytes) to communicate storage quota information to clients. Server implementations MAY choose to include managed attachments sizes when calculating the amount of storage used by a particular resource.
Access to the managed attachments store in a calendar object resource SHOULD be restricted to only those calendar users who have access to that calendar object either directly, or indirectly (via being an attendee who would receive a scheduling message). When accessing a managed attachment, clients SHOULD be prepared to authenticate with the server storing the attachment resource. The credentials required to access the managed attachment store could be different from the ones used to access the CalDAV server. This specification only allows organizers of scheduled events to add managed attachments. Servers MUST prevent attendees of scheduled events from adding, updating or removing managed attachments. In addition, the server MUST prevent a calendar user from re-using a managed attachment (based on its managed-id value), unless that user is the one who originally created the managed attachment.
For POST requests that add or update attachment data, the server MAY issue a 307 (Temporary Redirect) or 308 (Permanent Redirect) response to require the client to re-issue the POST request using a different request-URI. As a result, clients SHOULD use the "100-continue" expectation defined in Section 5.1.1 of . Using this mechanism ensures that, if a redirect does occur, the client does not needlessly send the attachment data.
Clients can expect servers to take a while to respond to POST requests that include large attachment bodies. Servers SHOULD use the "102 (Processing)" interim response defined in Section 10.1 of to keep the client connection alive if the POST request will take significant time to complete.
Servers MAY automatically remove attachment data, for example to regain the storage taken by unused attachments, or as the result of a virus scanning. When doing so they SHOULD NOT modify calendar data referencing those attachments. Instead they SHOULD respond with "410 (Gone)" to any request on the removed attachment URI.
When a managed attachment is added, updated or removed from a calendar object resource, the server MUST ensure that a scheduling message is sent to update any attendees with the changes, as per .
When exporting calendar data from a CalDAV server supporting managed attachments, clients SHOULD remove all "MANAGED-ID" property parameters from "ATTACH" properties in the calendar data. Similarly when importing calendar data from another source, clients SHOULD remove any "MANAGED-ID" property parameters on "ATTACH" properties (failure to do so will likely result in the server removing those properties automatically).
SIZE To specify the size of an attachment. This property parameter is defined by the following notation:
This property parameter MAY be specified on "ATTACH" properties. It indicates the size in octets of the corresponding attachment data. Since iCalendar integer values are restricted to a maximum value of 2147483647, the current parameter is defined as text to allow an extended range to be used.
FILENAME To specify the file name of a managed attachment. This property parameter is defined by the following notation:
This property parameter MAY be specified on "ATTACH" properties corresponding to managed attachments. Its value provides information on how to construct a filename for storing the attachment data. This parameter is very similar in nature to the Content-Disposition HTTP header field "filename" parameter and exposes the same security risks. As a consequence, clients MUST follow the guidelines expressed in Section 4.3 of when consuming this parameter value. Similarly, servers MUST follow those same guidelines before storing a value.
MANAGED-ID To uniquely identify a managed attachment. This property parameter is defined by the following notation:
This property parameter MUST be specified on "ATTACH" properties corresponding to managed attachments. Its value is generated by the server and uniquely identifies a managed attachment within the scope of the CalDAV server. This property parameter MUST NOT be present in the case of non-managed attachments.
The Cal-Managed-ID response header field provides the value of the MANAGED-ID parameter corresponding to a newly added ATTACH property.
ABNF:
Example:
The Cal-Managed-ID header field MUST only be sent by an origin server in response to a successful POST request with an action set to attachment-add or attachment-update. It MUST only appear once in a response and MUST NOT appear in trailers. The Cal-Managed-ID header field is end to end and MUST be forwarded by intermediaries. Intermediaries MUST NOT insert, delete, or modify a Cal-Managed-ID header field.
managed-attachments-server-URL urn:ietf:params:xml:ns:caldav Specifies the server base URI to use when retrieving managed attachments. This property MUST be protected as only the server can update the value. This property is only defined on a calendar home collection which cannot be moved or copied. SHOULD NOT be returned by a PROPFIND DAV:allprop request. This property MAY be defined on a calendar home collection. If present, it contains zero or one DAV:href XML elements. When one DAV:href element is present, its value MUST be an absolute HTTP URI containing only the scheme (i.e. "https") and authority (i.e. host and port) parts . Whenever a managed attachment is to be retrieved via an HTTP GET, the client MUST construct the actual URL of the attachment by substituting the scheme and authority parts of the attachment URI (as stored in the iCalendar "ATTACH" property) with the present WebDAV property value. When no DAV:href element is present, the client MUST substitute the scheme and authority parts of the attachment URI with the scheme and authority part of the calendar home collection absolute URI. In the absence of this property, the client can consider the attachment URI as its actual URL.
]]>
https://attachstore.example.com ]]>
max-attachment-size urn:ietf:params:xml:ns:caldav Provides a numeric value indicating the maximum attachment size, in octets, that the server is willing to accept when a managed attachment is stored on the server. MUST be protected as it indicates limits provided by the server. This property value MUST be preserved in COPY and MOVE operations. SHOULD NOT be returned by a PROPFIND DAV:allprop request. The CALDAV:max-attachment-size property is used to specify a numeric value that represents the maximum attachment size, in octets, that the server is willing to accept when a managed attachment is stored on the server. The property is defined on the parent collection of the calendar object resource to which the attachment is associated. Any attempt to store a managed attachment exceeding this size MUST result in an error, with the CALDAV:max-attachment-size precondition () being violated. In the absence of this property, the client can assume that the server will allow storing an attachment of any reasonable size.
]]>
102400000 ]]>
max-attachments-per-resource urn:ietf:params:xml:ns:caldav Provides a numeric value indicating the maximum number of managed attachments across all instances of a calendar object resource stored in a calendar collection. MUST be protected as it indicates limits provided by the server. This property value MUST be preserved in COPY and MOVE operations. SHOULD NOT be returned by a PROPFIND DAV:allprop request. The CALDAV:max-attachments-per-resource property is used to specify a numeric value that represents the maximum number of managed attachments across all instances of a calendar object resource stored in a calendar collection. Non-managed attachments are not counted toward that limit. The property is defined on the parent collection of the calendar object resource to which the attachment is associated. Any attempt to add a managed attachment that would cause the calendar resource to exceed this limit MUST result in an error, with the CALDAV:max-attachments-per-resource precondition () being violated. In the absence of this property, the client can assume that the server can handle any number of managed attachments per calendar resource.
]]>
12 ]]>
< RFC Editor: before publication please remove this section, the reference to , and any resulting "URIs" references sub-section. > This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".
The open source Calendar and Contacts Server project is a standards-compliant server implementing the CalDAV protocol. This production level implementation supports all of the requirements described in this document and successfully interoperates with the , , , and client implementations described below. This implementation is freely distributable under the terms of the Apache License, Version 2.0.
The open source Cyrus Server project is a highly scalable enterprise mail system which also supports calendaring. This production level CalDAV implementation supports all of the requirements described in this document and successfully interoperates with the and client implementations described below. This implementation is freely distributable under a BSD style license from Computing Services at Carnegie Mellon University.
The Oracle Communications Calendar Server project is a standards-compliant, scalable, enterprise-ready calendaring solution. This production level CalDAV implementation supports all of the requirements described in this document and successfully interoperates with the and client implementations described below. This implementation is proprietary and available for a free trial and/or purchase from the vendor.
The widely used Apple Calendar client is a standards-compliant client implementing the CalDAV protocol. This production level implementation supports all the requirements described in this document and successfully interoperates with the , , and implementations described above. This client implementation is proprietary and is distributed as part of Apple's desktop operating systems.
BusyCal is a standards-compliant calendar client for MacOS implementing the CalDAV protocol. This implementation supports all of the requirements described in this document and successfully interoperates with the and implementations described above. This implementation is proprietary and available for a free trial and/or purchase from the vendor.
CalDAVTester is an open source test and performance application designed to work with CalDAV servers and tests various aspects of their protocol handling as well as performance. This widely used implementation supports all of the requirements described in this document and successfully interoperates with the server implementations described above. This implementation is freely distributable under the terms of the Apache License, Version 2.0.
2Do is a standards-complient calendar client for iOS which uses the CalDAV standard for communication. This implementation supports all of the requirements described in this document and successfully interoperates with the implementation described above. This implementation is proprietary and available for purchase from the vendor.
The security considerations in and apply to this extension. Additionally, servers need to be aware that a client could attack underlying storage by POSTing extremely large attachments and could attack processing time by uploading a recurring event with a large number of overrides and then repeatedly adding, updating, and deleting attachments. Malicious content could be introduced into the calendar server by way of a managed attachment, and propagated to many end users via scheduling. Servers SHOULD check managed attachments for malicious or inappropriate content. Upon detecting of such content, servers SHOULD remove the attachment, following the rules described in .
This specification defines the following new iCalendar property parameters to be added to the registry defined in Section 8.2.3 of : Property Parameter Status Reference SIZE Current RFCXXXX, FILENAME Current RFCXXXX, MANAGED-ID Current RFCXXXX,
The message header fields below should be added to the Permanent Message Header Field Registry (see ).
Header field name: Cal-Managed-ID Applicable protocol: http Status: standard Author/Change controller: IETF Specification document(s): this specification () Related information: none
This specification came about via discussions at the Calendaring and Scheduling Consortium. Thanks in particular to Mike Douglass and Eric York.
&rfc2119; &rfc2518; &rfc3864; &rfc4331; &rfc4791; &rfc4918; &rfc5234; &rfc5545; &rfc6266; &rfc6638; &rfc7230; &rfc7231; &rfc7240; &rfc7538; &rfc8174; &rfc5023; &rfc5546; &rfc7320; &rfc7942; &rfc8144;
Changes in calext-04: Added text explaining why this document is being published as Informational. Further specified Cal-Managed-ID per Section 8.3.1 of RFC 7231. Specified that the MANAGED-ID parameter value is unique within the scope of the server. Added more text regarding preconditions. Added text about specific DoS attack vectors. Editorial changes from Gren Elliot and Phillip Kewisch. Editorial changes from Adam Roach. Editorial changes from Alexey Melnikov. Added reference to RFC4918. Minor editorial changes. Changes in calext-03: Changed to Informational based on feedback regarding non-standard method of updating an existing resource. Added references to sub-sections in Overview. Made support for Prefer header field a SHOULD for servers. Expanded recurring event examples to use conditional requests and to include the Expect header field. Minor editorial changes. Changes in calext-02: Moved "Error Handling" into its own sub-section. Split "Other Client Considerations" into "Processing Time" and "Migrating Calendar Data". Changes in calext-01: Changed all instances of "header" to "header field". Reworked wording of Prefer header field handling. Switched to recommending 102 (Processing) interim response to keep the client connection alive. Fixed description of Cal-Managed-ID response header field to state that it is also required in responses to successful attachment-update. Minor editorial changes. Changes in calext-00: Added Murchison as editor. Updated HTTP references to RFC7230 and RFC7231. Updated Prefer header field references to RFC7240. Added Implementation Status section. Minor editorial changes. Changes in daboo-03: Fixed some examples. Fixed return-representation -> return=representation. Added statement that servers must not allow clients to DELETE attachments directly. Added new preconditions for valid managed-id values. Filled out Access Control section. Allow servers to not support per-instance attachments and advertise that fact to clients. Changes in daboo-02: MANAGED-ID changes on PUT. MTAG has been removed. Error pre-conditions added. Interaction with WebDAV QUOTA discussed. max-attachment-* limits added. Updated references. Removed MUST for specific 2xx codes in favor of generic success code. Changes in daboo-01: Tweaked OPTIONS capability wording. Added section on clients expecting 100-Continue for delayed response. Added text for clean-up and use of HTTP 410 on orphans. Added text on removing "MANAGED-ID" when exporting/importing calendar data. Added protocol examples. Added MTAG property parameter on ATTACH property Added FILENAME property parameter on ATTACH property "id" query parameter is now "managed-id". Use of Cal-Managed-ID header instead of Location header in responses. rid query param MUST contain RECURRENCE-ID without any conversion to UTC (case of floating events). Introduced CALDAV:managed-attachments-server-URL property Made support for Prefer header a MUST for servers.
In the following example, the organizer of a recurring meeting makes an unsuccessful attempt to add an agenda (HTML attachment) to the corresponding calendar resource with a conditional request. Note that the client includes both the Expect and Prefer header fields in the request, thereby preventing itself from needlessly sending the attachment data, and requesting that the current resource be returned in the failure response (see Section 3.2 of ).
>> Request <<
>> Final Response <<
The organizer of a recurring meeting successfully adds an agenda (HTML attachment) to the corresponding calendar resource. Attendees of the meeting are granted read access to the newly created attachment resource. Their own copy of the meeting is updated to include the new ATTACH property pointing to the attachment resource and they are notified of the change via their scheduling inbox.
>> Request <<
>> Interim Response <<
>> Request Body <<

Agenda

As usual

]]>
>> Final Response <<
The organizer has a more specific agenda for the 20th of February meeting. It is added to that particular instance of the meeting by specifying the rid parameter. Note that an overridden instance is created with the RECURRENCE-ID property value matching the value of the "rid" query parameter in the request. Also note that the server takes significant time to complete the request and notifies the client accordingly.
>> Request <<
>> Interim Response <<
>> Request Body <<

Agenda

Something different, for a change

]]>
>> Interim Response <<
>> Final Response <<