Scheduling Extensions to CalDAVApple Inc.1 Infinite LoopCupertinoCA95014USAcyrus@daboo.namehttp://www.apple.com/Oracle Corporation600 Blvd. de Maisonneuve WestSuite 1900MontrealQCH3A 3J2CANADAbernard.desruisseaux@oracle.comhttp://www.oracle.com/
Applications
calsifycalschedcalschcaldavcalendarcalendaringschedulingwebcalwebdavicalicalendarischeduleitipimiptext/calendarhttp
This document defines extensions to the Calendaring Extensions to WebDAV
(CalDAV) "calendar-access" feature to specify a standard way of
performing scheduling operations with iCalendar-based calendar
components. This document defines the "calendar-auto-schedule" feature
of CalDAV.
This document specifies extensions to the
CalDAV "calendar-access"
feature to enable scheduling of
iCalendar-based
calendar components between calendar users.This extension
leverages the scheduling methods defined in the iCalendar
Transport-independent Interoperability Protocol (iTIP) to permit calendar
users to perform scheduling operations such as schedule,
reschedule, respond to scheduling request, or cancel
calendar components, as well as search for busy time information.
However, the following iTIP
features are not covered: publishing, countering, delegating,
refreshing, and forwarding calendar components, as well as replacing
the "Organizer" of a calendar component. It is expected that future
extensions will be developed to address these.
This specification defines a client/server scheduling protocol, where the
server is made responsible for sending scheduling messages and processing
incoming scheduling messages. The client operations of creating, modifying, or
deleting a calendar component in a calendar are enough to trigger the server to
deliver the necessary scheduling messages to the appropriate calendar
users. This approach is sometimes referred to as "implicit scheduling".
This specification only addresses how scheduling occurs with users on a
single system (i.e., scheduling between CalDAV servers, or some other
calendaring and scheduling system, is not defined). However, this specification
is compatible with servers being able to send or receive scheduling messages
with "external" users (e.g., using the iCalendar
Message-Based Interoperability Protocol (iMIP)).
defines the automated "Scheduling
Operations" that allow a client to store iCalendar data on a CalDAV server,
with the server taking specific actions in response. One of three scheduling
operations can take place -- "create", "modify", or "remove", based on the HTTP
method used for the request -- in addition to a comparison between any
existing and any new iCalendar data.
defines how the server processes
scheduling messages sent as the result of a scheduling operation.
defines how freebusy requests with an
immediate response are accomplished.
defines access control privileges for the scheduling operations defined in this specification.
For the majority of the following discussion, scheduling of events will be
discussed. However, scheduling of to-dos is
also fully supported by this specification.
This specification has been under development for a number of years,
and most current implementations of CalDAV support it. With the
publication of this document, it is expected that all new CalDAV
implementations will support it by default. Interoperability tests
have been performed regularly. Significant issues with incompatible
CalDAV implementations are not anticipated.
This specification reuses much of the same terminology as
iCalendar,
iTIP,
WebDAV, and
CalDAV.
Additional terms used by this specification are as follows:
A calendar object resource contained in a calendar
collection for which the server will take care of sending
scheduling messages on behalf of the owner of the calendar
collection.
A scheduling object resource owned by the "Organizer".
A scheduling object resource owned by an "Attendee".
Add, change, or remove operations on a scheduling object
resource for which the server will deliver scheduling
messages to other calendar users.
A calendar object that describes a scheduling
operation such as schedule, reschedule, reply, or
cancel.
A resource at which busy time information requests are
targeted.
A collection in which incoming scheduling messages are
delivered.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in .
The Augmented BNF (ABNF) syntax used by this document to specify
the format definition of new iCalendar elements is defined in
.
The ABNF syntax used by this document to specify
the format definition of new message header fields to be used
with the HTTP/1.1 protocol is described in Section 2.1 of
. Since this Augmented BNF uses the
basic production rules provided in Section 2.2 of
, these rules apply to this document
as well.
The term "protected" is used in the Conformance field of WebDAV
property definitions as defined in Section 15 of
.
Calendaring and scheduling roles are referred to in quoted-strings of
text with the first character of each word in uppercase. For example,
"Organizer" refers to a role of a calendar user within the scheduling
protocol defined by .
This document uses XML DTD fragments (, Section 3.2) as a purely notational
convention. WebDAV request and response bodies cannot be validated by a DTD
due to the specific extensibility rules defined in Section 17
of and
due to the fact that all XML elements defined by that specification use the XML
namespace name "DAV:". In particular,
element names use the "DAV:" namespace,element ordering is irrelevant unless explicitly stated,extension elements (elements not already defined as valid
child elements) can be added anywhere, except when explicitly stated otherwise,
andextension attributes (attributes not already defined as valid for this element) can be added anywhere, except when explicitly stated otherwise.
The XML elements specified in this document are defined in the
"urn:ietf:params:xml:ns:caldav" XML namespace registered by
CalDAV.
When XML element types in the namespaces "DAV:" and "urn:ietf:params:xml:ns:caldav" are referenced in this document outside of the context of an XML fragment, the strings "DAV:" and "CALDAV:" will be prefixed to the element types, respectively.
This document inherits, and sometimes extends, DTD productions from Section 14 of .
Also note that some CalDAV XML element names are identical to WebDAV XML element names, though their namespace differs. Care needs to be taken not to confuse the two sets of names.
A server that supports the features described in this document is REQUIRED to support the CalDAV "calendar-access" feature. Servers include "calendar-auto-schedule" as a field in the DAV response header from an OPTIONS request on any resource that supports any scheduling operations, properties, privileges, or methods.
This specification introduces new collection resource types
that are used to manage scheduling object resources, and scheduling
privileges (as per ), as well as
provide scheduling functionality. It is the server's responsibility to create
these collection resources, and clients have no way to create or delete them.
A scheduling Outbox collection is used as the target for
busy time information requests, and to manage privileges that apply to outgoing scheduling requests.
A scheduling Outbox collection MUST report the DAV:collection
and CALDAV:schedule-outbox XML elements in the value of the
DAV:resourcetype property. The element type declaration for
CALDAV:schedule-outbox is
<!ELEMENT schedule-outbox EMPTY>
Example:
<D:resourcetype xmlns:D="DAV:">
<D:collection/>
<C:schedule-outbox xmlns:C="urn:ietf:params:xml:ns:caldav"/>
</D:resourcetype>
A scheduling Outbox collection MUST NOT be a child (at any depth)
of a calendar collection resource.
The following WebDAV properties specified in CalDAV "calendar-access"
MAY also be defined on scheduling Outbox collections and apply to scheduling messages submitted to the scheduling Outbox collection with the POST method:
CALDAV:supported-calendar-component-set
CALDAV:supported-calendar-data
CALDAV:max-resource-size
CALDAV:min-date-time
CALDAV:max-date-time
CALDAV:max-attendees-per-instance
The use of child resources in a scheduling Outbox collection is reserved for future revisions or extensions of this specification.
The following WebDAV property is defined on principal resources and used to locate the corresponding Outbox collection for the associated principal.schedule-outbox-URLurn:ietf:params:xml:ns:caldavIdentify the URL of the scheduling Outbox collection owned by the associated principal resource.This property MAY be protected.This property SHOULD NOT be returned by a PROPFIND DAV:allprop request (as defined in Section 14.2 of ).This property value SHOULD be preserved in COPY and MOVE operations.This property is needed for a client to determine where the scheduling Outbox collection of the current user is located so that sending of scheduling messages can occur. If not present, then the associated calendar user is not enabled for the sending of scheduling messages on the server.
<!ELEMENT schedule-outbox-URL (DAV:href)>
A scheduling Inbox collection contains copies of incoming
scheduling messages. These can be requests sent by an
"Organizer", or replies sent by an "Attendee" in response to
a request. The scheduling Inbox collection is also used to manage scheduling privileges.
A scheduling Inbox collection MUST report the DAV:collection
and CALDAV:schedule-inbox XML elements in the value of the
DAV:resourcetype property. The element type declaration for
CALDAV:schedule-inbox is
<!ELEMENT schedule-inbox EMPTY>
Example:
<D:resourcetype xmlns:D="DAV:">
<D:collection/>
<C:schedule-inbox xmlns:C="urn:ietf:params:xml:ns:caldav"/>
</D:resourcetype>
Scheduling Inbox collections MUST only contain calendar object
resources that obey the restrictions specified in iTIP. Consequently,
scheduling Inbox collections MUST NOT contain any types of
collection resources. Restrictions defined in Section 4.1 of
CalDAV "calendar-access" on calendar
object resources contained in calendar collections (e.g.,
Unique Identifier ("UID")
uniqueness) do not apply to calendar object resources contained in
a scheduling Inbox collection. Thus, multiple calendar object resources
contained in a scheduling Inbox collection can have the same "UID"
property value (i.e., multiple scheduling messages for the same
calendar component).
A scheduling Inbox collection MUST NOT be a child (at any depth)
of a calendar collection resource.
The following WebDAV properties specified in
CalDAV "calendar-access" MAY
also be defined on scheduling Inbox collections and apply to scheduling
messages delivered to the collection:
CALDAV:supported-calendar-component-set
CALDAV:supported-calendar-data
CALDAV:max-resource-size
CALDAV:min-date-time
CALDAV:max-date-time
CALDAV:max-instances
CALDAV:max-attendees-per-instance
CALDAV:calendar-timezone
The following WebDAV property is defined on principal resources and used to locate the corresponding Inbox collection for the associated principal.schedule-inbox-URLurn:ietf:params:xml:ns:caldavIdentify the URL of the scheduling Inbox collection owned by the associated principal resource.This property MAY be protected.This property SHOULD NOT be returned by a PROPFIND DAV:allprop request (as defined in Section 14.2 of ).This property value SHOULD be preserved in COPY and MOVE operations.This property allows a client to determine where the scheduling Inbox collection of the current user is located so that processing of scheduling messages can occur. If not present, then the associated calendar user is not enabled for reception of scheduling messages on the server.
<!ELEMENT schedule-inbox-URL (DAV:href)>
This specification extends the CALDAV:calendar-query and
CALDAV:calendar-multiget REPORTs to return results for calendar
object resources in scheduling Inbox collections.
When a CALDAV:calendar-query REPORT includes a time-range query
and targets a scheduling Inbox collection, if any calendar
object resources contain "VEVENT" calendar components that do
not include a "DTSTART" iCalendar property (as allowed by iTIP) then such components
MUST always match the time-range query test.
Note that the CALDAV:free-busy-query REPORT is not supported on
scheduling Inbox collections.
This section defines new properties for WebDAV principal resources as defined in . These properties are likely to be protected, but the server MAY allow them to be written by appropriate users.calendar-user-address-seturn:ietf:params:xml:ns:caldavIdentify the calendar addresses of the associated principal resource.This property MAY be protected.This property SHOULD NOT be returned by a PROPFIND DAV:allprop request (as defined in Section 14.2 of ).This property value SHOULD be preserved in COPY and MOVE operations.Support for this property is
REQUIRED. This property is needed to map calendar user addresses in iCalendar
data to principal resources and their associated scheduling Inbox and Outbox
collections. In the event that a user has no well-defined identifier
for his calendar user address, the URI of his principal resource can be
used. This property SHOULD be searchable using the
DAV:principal-property-search REPORT. The DAV:principal-search-property-set
REPORT SHOULD identify this property as such. If not present, then the
associated calendar user is not enabled for scheduling on the server.
<!ELEMENT calendar-user-address-set (DAV:href*)>
<C:calendar-user-address-set xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:caldav">
<D:href>mailto:bernard@example.com</D:href>
<D:href>mailto:bernard.desruisseaux@example.com</D:href>
</C:calendar-user-address-set>
calendar-user-typeurn:ietf:params:xml:ns:caldavIdentifies the calendar user type of the associated principal resource.Same values allowed for the iCalendar "CUTYPE" property parameter defined in Section 3.2.3 of .This property MAY be protected.This property SHOULD NOT be returned by a PROPFIND DAV:allprop request (as defined in Section 14.2 of ).This property value SHOULD be preserved in COPY and MOVE operations.Clients can query principal resources
in order to look up "Attendees" available on the server. When doing this, it is useful to know, or restrict the query to, certain types of calendar users (e.g., only search for "people", or only search for "rooms"). This property MAY be defined on principal resources to indicate the type of calendar user associated with the principal resource. Its value is the same as the iCalendar "CUTYPE" property parameter that can be used on "ATTENDEE" properties. This property SHOULD be searchable using the DAV:principal-property-search REPORT. The DAV:principal-search-property-set REPORT SHOULD identify this property as such.
<!ELEMENT calendar-user-type (#PCDATA)>
<C:calendar-user-type
xmlns:C="urn:ietf:params:xml:ns:caldav">INDIVIDUAL<
/C:calendar-user-type>
When a calendar object resource is created, modified, or removed
from a calendar collection, the server examines the calendar data and
checks to see whether the data represents a scheduling object
resource. If it does, the server will automatically attempt to
deliver a scheduling message to the appropriate calendar users.
Several types of scheduling operations can occur in this case,
equivalent to iTIP "REQUEST", "REPLY", "CANCEL", and "ADD"
operations.
Calendar object resources on which the server performs
scheduling operations are referred to as scheduling object
resources. There are two types of scheduling object resources:
organizer scheduling object resources, and attendee scheduling
object resources.
A calendar object resource is considered to be a valid
organizer scheduling object resource if the "ORGANIZER"
iCalendar property is present and set in all the calendar
components to a value that matches one of the calendar user
addresses of the owner of the calendar collection.
A calendar object resource is considered to be a valid attendee
scheduling object resource if the "ORGANIZER" iCalendar
property is present and set in all the calendar components
to the same value and doesn't match one of the calendar user
addresses of the owner of the calendar collection, and if
at least one of the "ATTENDEE" iCalendar property values
matches one of the calendar user addresses of the owner of the
calendar collection.
The creation of attendee scheduling object resources is
typically done by the server, with the resource being
created in an appropriate calendar collection (see ).
The server's behavior when processing a scheduling object
resource depends on whether it is owned by the "Organizer" or
an "Attendee" specified in the calendar data.
An "Organizer" can create, modify, or remove a scheduling object resource, subject to access privileges, preconditions, and the restrictions defined in Section 4.1 of . These operations are each described next, and how they are invoked via HTTP requests is described in .
The "Organizer" of a calendar component can also be an "Attendee" of
that calendar component. In such cases, the server MUST NOT send a
scheduling message to the "Attendee" that matches the "Organizer".
The server SHOULD reject any attempt to set the
"PARTSTAT" iCalendar property parameter value of
the "ATTENDEE" iCalendar property of other users in
the calendar object resource to a value other than
"NEEDS-ACTION" if the "SCHEDULE-AGENT" property
parameter value is not present or set to the value
"SERVER".
The server MAY reject attempts to create a scheduling
object resource that specifies a "UID" property value
already specified in a scheduling object resource
contained in another calendar collection of the
"Organizer".
When an "Organizer" creates a scheduling object resource, the server MUST inspect each "ATTENDEE" property to determine whether to send a scheduling message. The table below indicates the appropriate iTIP method used by the server, taking into account any "SCHEDULE-AGENT" property parameter (see ) specified on each "ATTENDEE" property.
SCHEDULE-AGENTiTIP METHODSERVER (default)REQUESTCLIENT--NONE--
"SCHEDULE-STATUS" iCalendar property parameters are added or changed on "ATTENDEE" iCalendar properties in the scheduling object resource being created as described in , with the value set as described in . This will result in the created calendar object resource differing from the calendar data sent in the HTTP request. As a result, clients MAY reload the calendar data from the server in order to update to the new server-generated state information.
The server MUST add a
"SCHEDULE-STATUS" iCalendar property parameter (see ) to the
"ATTENDEE" iCalendar property in the scheduling object
resource being created, and set its value as described in
. This will result
in the created calendar object resource differing from
the calendar data sent in the HTTP request. As a result,
clients MAY reload the calendar data from the server
in order to
update to the new server-generated state information.
Servers MUST NOT set the "SCHEDULE-STATUS" property
parameter on the "ATTENDEE" property of "Attendees"
for which it did not attempt to deliver a scheduling
message.
The server MUST return an error with the CALDAV:allowed-organizer-scheduling-object-change precondition code () when the "Organizer" attempts to change the iCalendar data in a manner that is forbidden.
When an "Organizer" modifies a scheduling object resource, the server MUST inspect each "ATTENDEE" property in both the original and modified iCalendar data on a per-instance basis to determine whether to send a scheduling message. The table below indicates the appropriate iTIP method used by the server, taking into account any "SCHEDULE-AGENT" property parameter (see ) specified on each "ATTENDEE" property. The values "SERVER", "CLIENT", and "NONE" in the top and left titles of the table refer to the "SCHEDULE-AGENT" parameter value of the "ATTENDEE" property, and the values "<Absent>" and "<Removed>" are used to cover the cases where the "ATTENDEE" property is not present (Original) or is being removed (Modified).
+---------------+-----------------------------------------------+
| | Modified |
| +-----------+-----------+-----------+-----------+
| | <Removed> | SERVER | CLIENT | NONE |
| | | (default) | | |
+===+===========+===========+===========+===========+===========+
| | <Absent> | -- | REQUEST / | -- | -- |
| O | | | ADD | | |
| r +-----------+-----------+-----------+-----------+-----------+
| i | SERVER | CANCEL | REQUEST | CANCEL | CANCEL |
| g | (default) | | | | |
| i +-----------+-----------+-----------+-----------+-----------+
| n | CLIENT | -- | REQUEST / | -- | -- |
| a | | | ADD | | |
| l +-----------+-----------+-----------+-----------+-----------+
| | NONE | -- | REQUEST / | -- | -- |
| | | | ADD | | |
+---+-----------+-----------+-----------+-----------+-----------+
"SCHEDULE-STATUS" iCalendar property parameters are added or changed on "ATTENDEE" iCalendar properties in the scheduling object resource being modified as described in , with the value set as described in . This will result in the created calendar object resource differing from the calendar data sent in the HTTP request. As a result, clients MAY reload the calendar data from the server in order to update to the new server-generated state information.The server MUST return an error with the CALDAV:allowed-organizer-scheduling-object-change precondition code () when the "Organizer" attempts to change the iCalendar data in a manner that is forbidden.
When an "Organizer" removes a scheduling object resource, the server
MUST inspect each "ATTENDEE" property to determine whether to send a scheduling
message. The table below indicates the appropriate iTIP method used by the
server, taking into account any "SCHEDULE-AGENT" property parameter (see ) specified on each "ATTENDEE" property.SCHEDULE-AGENTiTIP METHODSERVER (default)CANCELCLIENT--NONE--An "Attendee" can create, modify, or remove a scheduling object resource. These operations are each described next, and how they are invoked via HTTP requests is described in .
"Attendees" are allowed to make some changes to a scheduling
object resource, though key properties such as start time,
end time, location, and summary are typically under the
control of the "Organizer".
Servers MUST allow "Attendees" to make the following iCalendar data changes, subject to other restrictions, such as access privileges and preconditions:
change their own "PARTSTAT" iCalendar property parameter value.add, modify, or remove any "TRANSP" iCalendar properties.add, modify, or remove any "PERCENT-COMPLETE" iCalendar properties.add, modify, or remove any "COMPLETED" iCalendar properties.add, modify, or remove any "VALARM" iCalendar components.add, modify, or remove the "CALSCALE" iCalendar property within the top-level "VCALENDAR" component.modify the "PRODID" iCalendar property within the top-level "VCALENDAR" component.add "EXDATE" iCalendar properties and possibly remove components for overridden recurrence instances.add, modify, or remove any "CREATED", "DTSTAMP", and "LAST-MODIFIED" iCalendar properties.add, modify, or remove "SCHEDULE-STATUS" iCalendar property parameters on "ATTENDEE" properties that have a "SCHEDULE-AGENT" parameter set to "CLIENT".add new components to represent overridden recurrence instances, provided the only changes to the recurrence instance follow the rules above.The server MUST return an error with the CALDAV:allowed-attendee-scheduling-object-change precondition code () when the "Attendee" attempts to change the iCalendar data in a manner forbidden by the server.Typically, an "Attendee" does not create scheduling object
resources, as scheduling messages delivered to him on the server are
automatically processed by the server and placed on one of his calendars (see
). However, in some cases, a scheduling
message can get delivered directly to the client (e.g., via email ), and the "Attendee" might wish to store that on the
server. In that case, the client creates a scheduling object resource in a
calendar belonging to the "Attendee". It can then set the "SCHEDULE-AGENT"
iCalendar property parameter on all "ORGANIZER" iCalendar properties in the
resource to determine how the server treats the resource. The value of the
"SCHEDULE-AGENT" iCalendar property parameter on all "ORGANIZER" iCalendar
properties MUST be the same.SCHEDULE-AGENTActionSERVER (default)The server will attempt to process changes to the resource using the normal rules for attendee scheduling object resources.CLIENTThe server does no special processing of the resource. The client is assumed to be handling "Attendee" replies, etc.NONEThe server does no special processing of the resource."SCHEDULE-STATUS" iCalendar property parameters are added or changed on "ORGANIZER" iCalendar properties in the scheduling object resource being created as described in , with the value set as described in .When a scheduling object resource is modified by an "Attendee",
the server's behavior depends on the value of the "SCHEDULE-AGENT" iCalendar
property parameter on the "ORGANIZER" iCalendar properties:SCHEDULE-AGENTActionSERVER (default)The server will attempt to process the update using the behavior listed below.CLIENTThe server does no special processing of the resource. The client is assumed to be handling any "Attendee" replies, etc.NONEThe server does no special processing of the resource.The server will inspect the changes by comparing the new scheduling object resource with the existing scheduling object resource.If the "Attendee" changes one or more "PARTSTAT" iCalendar property values on any component, or adds an overridden component with a changed "PARTSTAT" property, then the server MUST deliver an iTIP "REPLY" scheduling message to the "Organizer" to indicate the new participation status of the "Attendee".If the "Attendee" adds an "EXDATE" property value to effectively remove a recurrence instance, the server MUST deliver an iTIP "REPLY" scheduling message to the "Organizer" to indicate that the "Attendee" has declined the instance."SCHEDULE-STATUS" iCalendar property parameters are added or changed on "ORGANIZER" iCalendar properties in the scheduling object resource being modified as described in , with the value set as described in . This will result in the updated calendar object resource differing from the calendar data sent in the HTTP request. As a result, clients MAY reload the calendar data from the server in order to update to the new server-generated state information.When a scheduling object resource is removed by an "Attendee", the
server's behavior depends on the value of the "SCHEDULE-AGENT" iCalendar
property parameter on the "ORGANIZER" iCalendar properties:SCHEDULE-AGENTActionSERVER (default)The server will attempt to process the removal, taking into account any "Schedule-Reply" request header as per .CLIENTThe server does no special processing of the resource. The client is assumed to be handling any "Attendee" replies, etc.NONEThe server does no special processing of the resource.This section describes how the use of various HTTP and WebDAV methods
on a scheduling object resource will cause a create, modify, or remove
operation on that resource as described above. The use of these methods is
subject to the restrictions in , in addition to what is
described below.When the server receives a PUT method request, it MUST execute the
following operations, provided all appropriate preconditions are met:Existing Destination ResourceResulting Destination ResourceServer OperationNoneCalendar object resourceNoneNoneScheduling object resourceCreateCalendar object resourceCalendar object resourceNoneCalendar object resourceScheduling object resourceCreateScheduling object resourceCalendar object resourceRemoveScheduling object resourceScheduling object resourceModify
When the server receives a DELETE method request targeted at a scheduling object resource, it MUST execute the Remove operation.
When the server receives a DELETE method request targeted at a calendar collection, it MUST execute the Remove operation on all scheduling object resources contained in the calendar collection.
When the server receives a COPY method request, it MUST execute the
following operations based on the source and destination collections in the
request:Source CollectionDestination CollectionServer OperationNon-calendar collectionNon-calendar collectionNoneNon-calendar collectionCalendar collection(1)Calendar collectionNon-calendar collectionNoneCalendar collectionCalendar collection(2)The rules in are applied for the destination of the COPY request.The server MAY reject this as per ; otherwise, None.The behavior of a COPY method request on a calendar collection is undefined.
When the server receives a MOVE method request, it MUST
execute the following operations based on the source and
destination collections in the request:
Source CollectionDestination CollectionServer OperationNon-calendar collectionNon-calendar collectionNoneNon-calendar collectionCalendar collection(1)Calendar collectionNon-calendar collection(2)Calendar collectionCalendar collectionNoneThe rules in are applied for the destination of the MOVE request.The rules in are applied for the source of the MOVE request.The behavior of a MOVE method request on a calendar collection is undefined.
This specification defines method preconditions
(see Section 16 of WebDAV), in addition to those in ,
to provide machine-parseable information in error responses.
unique-scheduling-object-resourceurn:ietf:params:xml:ns:caldavPUT, COPY, and MOVE403 Forbidden
(precondition) --
Servers MAY reject requests to create a scheduling
object resource with an iCalendar "UID" property value
already in use by another scheduling object resource
owned by the same user in other calendar collections.
Servers SHOULD report the URL of the scheduling object
resource that is already making use of the same "UID"
property value in the DAV:href element.
<!ELEMENT unique-scheduling-object-resource (DAV:href?)>
<C:unique-scheduling-object-resource xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:caldav">
<D:href>/home/bernard/calendars/personal/abc123.ics</D:href>
</C:unique-scheduling-object-resource>
same-organizer-in-all-componentsurn:ietf:params:xml:ns:caldavPUT, COPY, and MOVE403 Forbidden
(precondition) -- All the calendar components in a
scheduling object resource MUST contain the same "ORGANIZER"
property value when present.
<!ELEMENT same-organizer-in-all-components EMPTY>
allowed-organizer-scheduling-object-changeurn:ietf:params:xml:ns:caldavPUT, COPY, and MOVE403 Forbidden
(precondition) --
Servers MAY impose restrictions on modifications allowed by an
"Organizer". For instance, servers MAY prevent the "Organizer"
from setting the "PARTSTAT" property parameter to a value other
than "NEEDS-ACTION" if the corresponding "ATTENDEE" property
has the "SCHEDULE-AGENT" property parameter set to "SERVER",
or does not have the "SCHEDULE-AGENT" property parameter.
See .
<!ELEMENT allowed-organizer-scheduling-object-change EMPTY>
allowed-attendee-scheduling-object-changeurn:ietf:params:xml:ns:caldavPUT, COPY, and MOVE403 Forbidden
(precondition) --
Servers MAY impose restrictions on modifications allowed
by an "Attendee", subject to the allowed changes specified in .
<!ELEMENT allowed-attendee-scheduling-object-change EMPTY>
The server MUST ensure that a
"DTSTAMP" iCalendar property is present and set
the value to the UTC time that the scheduling message
was generated (as required by iCalendar).
The server MUST ensure
that for each type of scheduling operation, the "SEQUENCE"
iCalendar property value is updated as per iTIP.
Servers MUST ensure that "Attendees"
only get information about recurrence instances that
explicitly include them as an "Attendee", when delivering scheduling messages for recurring calendar components.
For example, if an "Attendee" is invited to only a single
instance of a recurring event, the organizer scheduling
object resource will contain an overridden instance in the form
of a separate calendar component. That separate calendar
component will include the "ATTENDEE" property referencing
the "one-off" "Attendee". That "Attendee" will not be listed
in any other calendar components in the scheduling object
resource. Any scheduling messages delivered
to the "Attendee" will only contain information about this
overridden instance.
As another example, an "Attendee" could be excluded from one
instance of a recurring event. In that case, the organizer scheduling
object resource will include an overridden instance with an
"ATTENDEE" list that does not include the "Attendee" being
excluded. Any scheduling messages delivered to
the "Attendee" will not specify the overridden instance but
rather will include an "EXDATE" property in the "master"
component that defines the recurrence set.
The iCalendar property parameter "SCHEDULE-FORCE-SEND", defined
in , can be used
by a calendar user to force the server to send a scheduling
message to an "Attendee" or the "Organizer" in a situation where
the server would not normally send a scheduling message.
For instance, an "Organizer" could use this property parameter
to request an "Attendee" that previously declined an invitation
to reconsider his participation status without being forced to
modify the event.
This section specifies additional requirements on the handling
of the "PARTSTAT" property parameter when the "SCHEDULE-AGENT"
property parameter on the corresponding "ATTENDEE" property is
set to the value "SERVER" or is not present.
A reschedule occurs when any "DTSTART", "DTEND", "DURATION", "DUE", "RRULE", "RDATE", or "EXDATE" property changes in a calendar component such that existing recurrence instances are impacted by the changes, as shown in the table below. Servers MUST reset the "PARTSTAT" property parameter value of all "ATTENDEE" properties, except the one that corresponds to the "Organizer", to "NEEDS-ACTION" for each calendar component change that causes any instance to be rescheduled.
PropertyServer ActionDTSTART, DTEND, DURATION, DUEAny change to these properties results in "PARTSTAT" being set to "NEEDS-ACTION".RRULEA change to or addition of this property that results in the
addition of new recurring instances or a change in time for existing recurring
instances results in "PARTSTAT" being reset to "NEEDS-ACTION" on each affected
component.RDATEA change to or addition of this property that results in the
addition of new recurring instances or a change in time for existing recurring
instances results in "PARTSTAT" being reset to "NEEDS-ACTION" on each affected
component.EXDATEA change to or removal of this property that results in the
reinstatement of recurring instances results in "PARTSTAT" being set to
"NEEDS-ACTION" on each affected component.
The server MAY allow the "Organizer's" client to change an
"Attendee's" "PARTSTAT" property parameter value to "NEEDS-ACTION"
at any other time (e.g., when the "LOCATION" property value
changes, an "Organizer" might wish to re-invite "Attendees" who
might be impacted by the change).
When scheduling with an "Attendee", there are two types of status
information that can be returned during the operation. The first type of status
information is a "delivery" status that indicates whether the scheduling
message from the "Organizer" to the "Attendee" was delivered or not, or what the
current status of delivery is. The second type of status information is a
"reply" status corresponding to the "Attendee's" own "REQUEST-STATUS" information
from the scheduling message reply that is sent back to the "Organizer".Similarly, when an "Attendee" sends a reply back to the "Organizer", there will be "delivery" status information for the scheduling message sent to the "Organizer". However, there is no "REQUEST-STATUS" sent back by the "Organizer", so there is no equivalent of the "reply" status as per scheduling messages to "Attendees".The "delivery" status information on an "ORGANIZER" or "ATTENDEE"
iCalendar property is conveyed in the "SCHEDULE-STATUS" property parameter
value (). The status code value for "delivery"
status can be one of the following:Delivery Status CodeDescription1.0The scheduling message is pending. That is, the server is still
in the process of sending the message. The status code value can be expected to change once the server has completed its sending and delivery attempts.1.1The scheduling message has been successfully sent. However, the server does not have explicit information about whether the scheduling message was successfully delivered to the recipient. This state can occur with "store and forward" style scheduling protocols such as iMIP (iTIP using email).1.2The scheduling message has been successfully delivered.3.7The scheduling message was not delivered because the server did not recognize the calendar user address as a valid calendar user. Note that this code applies to both "Organizer" and "Attendee" calendar user addresses.3.8The scheduling message was not delivered due to insufficient privileges. Note that this code applies to privileges granted by both the "Organizer" and "Attendee" calendar users.5.1The scheduling message was not delivered because the server could not complete delivery of the message. This is likely due to a temporary failure, and the originator can try to send the message again at a later time.5.2The scheduling message was not delivered because the server was not able to find a way to deliver the message. This is likely a permanent failure, and the originator ought not try to send the message again, at least without verifying/correcting the calendar user address of the recipient.5.3The scheduling message was not delivered and was rejected because scheduling with that recipient is not allowed. This is likely a permanent failure, and the originator ought not try to send the message again.The status code for "reply" status can be any of the valid iTIP "REQUEST-STATUS" values.
The 1.xx "REQUEST-STATUS" codes are new. This specification modifies item (2) of Section 3.6 of by adding the following restriction:
For a 1.xx code, all components MUST have exactly the same code.
Definition of the new 1.xx codes is as follows:
1.0Pending.None.Delivery of the iTIP message is pending.1.1Sent.None.The iTIP message has been sent, though no information about successful delivery is known.1.2Delivered.None.The iTIP message has been sent and delivered.
Scheduling object resources on the server might change frequently as
"Attendees" change their participation status, triggering updates to the
"Organizer", and refreshes of other "Attendees'" copies of the scheduling
object resource. This can lead to an "inconsequential" change to a
calendar user's data -- one that does not directly impact the user's own
participation status. When this occurs, clients have to reload calendar
data and reconcile with changes being made by calendar
users. To avoid the need for this, the server can instead merge
calendar data changes from a client with changes made as a result
of a scheduling operation carried out by some other calendar user.
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 (one that simply
updates the status information of "Attendees" due to a reply
from another "Attendee").
Servers MUST automatically resolve conflicts with
"inconsequential" changes done to scheduling object resources when
the "If-Schedule-Tag-Match" request header is specified. The If-Schedule-Tag-Match request header applies only to the
Request-URI, and not to the destination of a COPY or MOVE.
A response to any successful GET or PUT request targeting a scheduling object resource MUST include a Schedule-Tag response header with the value set to the same value as the CALDAV:schedule-tag WebDAV property of the resource.
A response to any successful COPY or MOVE request that specifies a Destination request header targeting a scheduling object resource MUST include a Schedule-Tag response header with the value set to the same value as the CALDAV:schedule-tag WebDAV property of the destination resource.
Clients SHOULD use the If-Schedule-Tag-Match header on requests that update scheduling object resources, instead of HTTP ETag-based precondition tests (e.g., If-Match). Normal ETag-based precondition tests are used in all other cases, e.g., for synchronization.
The value of the CALDAV:schedule-tag property changes according
to these rules:
For an "Organizer's" copy of a scheduling object resource:
The server MUST NOT change the CALDAV:schedule-tag
property value when the scheduling object resource
is updated as the result of automatically processing
a scheduling message reply from an "Attendee". For
instance, when an "Attendee" replies to the "Organizer",
the CALDAV:schedule-tag property is unchanged after
the "Organizer's" scheduling object resource has been
automatically updated by the server with the "Attendee's"
new participation status.
The server MUST change the CALDAV:schedule-tag property
value when the scheduling object resource is changed
directly via an HTTP request (e.g., PUT, COPY, or MOVE).
For an "Attendee's" copy of a scheduling object resource:
The server MUST change the CALDAV:schedule-tag
property value when the scheduling object resource
is changed as the result of processing a
scheduling message update from an "Organizer"
that contains changes other than just the participation
status of "Attendees".
The server MUST NOT change the CALDAV:schedule-tag
property value when the scheduling object resource
is changed as the result of processing a scheduling
message update from an "Organizer" that only specifies
changes in the participation status of "Attendees".
For instance, when "Attendee" "A" replies to "Organizer"
"O", and "Attendee" "B" receives a scheduling message
update from "Organizer" "O" with the new participation
status of "Attendee" "A", the CALDAV:schedule-tag
property of "Attendee" "B"'s scheduling object resource
would remain the same.
The server MUST change the CALDAV:schedule-tag property
value when the scheduling object resource is changed
directly via an HTTP request (e.g., PUT, COPY, or MOVE).
Clients MAY use the If-Schedule-Tag-Match request header to do
a PUT request that ensures that "inconsequential"
changes on the server do not result in a precondition
error. The value of the request header is set to the last
Schedule-Tag value received for the resource being modified.
If the value of the If-Schedule-Tag-Match header matches the
current value of the CALDAV:schedule-tag property, the server
MUST take any "ATTENDEE" property changes for all "Attendees"
other than the owner of the scheduling object resource and
apply those to the new resource being stored.
Otherwise, the server MUST fail the request with a 412
Precondition Failed status code.
Clients MAY use the If-Schedule-Tag-Match request header to do
a DELETE, COPY, or MOVE request that ensures that "inconsequential"
changes on the server do not result in a precondition error. The
value of the request header is set to the last Schedule-Tag
value received for the resource being deleted.
If the value of the If-Schedule-Tag-Match header matches the
current value of the CALDAV:schedule-tag property, the server
performs the normal DELETE, COPY, or MOVE request processing for the resource.
Otherwise, the server MUST fail the request with a 412
Precondition Failed status code.
Scheduling operations can cause the delivery of a scheduling message
into an "Organizer's" or "Attendee's" scheduling Inbox collection. Servers
MUST automatically process incoming scheduling messages using the
rules defined by , by creating or updating the
corresponding scheduling object resources on calendars owned by the
owner of the scheduling Inbox collection. In addition, the scheduling
message is stored in the scheduling Inbox collection as an indicator
to the client that a scheduling operation has taken place. Scheduling messages are typically removed from the scheduling Inbox collection by the client once the calendar user has acknowledged the change.
The server MUST take into account privileges
on the scheduling Inbox collection when processing incoming
scheduling messages, to determine whether delivery of the
scheduling message is allowed. Privileges on
calendars containing any matching scheduling object resource are
not considered in this case (i.e., a schedule message from another user can cause modifications to resources in calendar collections that the other user would not normally have read or write access to). Additionally, servers MUST take
into account any scheduling Inbox collection preconditions
(see ) when delivering the
scheduling message, and MUST take into account the similar
preconditions on any calendar collection that contains, or
would contain, the corresponding scheduling object resource.
For a scheduling message sent by an "Organizer", the server first
tries to locate a corresponding scheduling object resource
belonging to the "Attendee". If no matching scheduling object
resource exists, the server treats the scheduling message as
a new message; otherwise, it is treated as an update.
In the case of a new message, the server processes the
scheduling message and creates a new scheduling object resource
as per .
In the case of an update, the server processes the
scheduling message and updates the matching scheduling
object resource belonging to the "Attendee" to reflect
the changes sent by the "Organizer".
In each case, the scheduling message MUST only appear
in the "Attendee's" scheduling Inbox collection once all
automatic processing has been done.
For a scheduling message reply sent by an "Attendee", the
server first locates the corresponding scheduling object
resource belonging to the "Organizer". If the corresponding scheduling object resource cannot be found, the server SHOULD ignore the scheduling message.
The server MUST then update the "PARTSTAT" iCalendar property parameter
value of each "ATTENDEE" iCalendar property in the scheduling
object resource to match the changes indicated in the reply
(taking into account the fact that an "Attendee" could have
created a new overridden iCalendar component to indicate
different participation status on one or more
instances of a recurring event).
The server MUST also update or add the "SCHEDULE-STATUS"
property parameter on each matching "ATTENDEE" iCalendar
property and set its value to that of the "REQUEST-STATUS"
property in the reply, or to "2.0" if "REQUEST-STATUS" is not
present (also taking into account recurrence instances). If
there are multiple "REQUEST-STATUS" properties in the
reply, the "SCHEDULE-STATUS" property parameter value is
set to a comma-separated list of status codes, one from each
"REQUEST-STATUS" property.
The server SHOULD send scheduling messages to all the other
"Attendees" indicating the change in participation status of
the "Attendee" replying, subject to the recurrence requirements
of .
The scheduling message MUST only appear in the
"Organizer's" scheduling Inbox collection once all automatic
processing has been done.
The server processes scheduling messages received for an "Attendee" by creating a new scheduling object
resource in a calendar collection belonging to the "Attendee", when one does not already exist. A calendar user
that is an "Attendee" in a scheduling operation
MUST have at least one valid calendar collection available. If there is no valid
calendar collection, then the server MUST reject the attempt to
deliver the scheduling message to the "Attendee".
Servers MAY provide support for a default calendar collection -- that is,
the calendar collection in which new scheduling object resources will be
created. The CALDAV:schedule-default-calendar-URL
WebDAV property, which can be present on the scheduling Inbox
collection of a calendar user, specifies whether this calendar user has a
default calendar collection. See
.
Servers SHOULD create new scheduling object resources in the default calendar collection, if the CALDAV:schedule-default-calendar-URL WebDAV property is set.
Servers MAY allow clients to change the default
calendar collection by changing the value of the
CALDAV:schedule-default-calendar-URL WebDAV property on the
scheduling Inbox collection. However, the server MUST ensure that
any new value for that property refers to a valid
calendar collection belonging to the owner of the scheduling
Inbox collection.
Servers MUST reject any attempt to delete the default calendar
collection.
This specification defines additional method preconditions
(see Section 16 of WebDAV)
to provide machine-parseable information in error responses.
default-calendar-neededurn:ietf:params:xml:ns:caldavDELETE403 Forbidden
(precondition) --
The client attempted to delete the calendar collection
currently referenced by the
CALDAV:schedule-default-calendar-URL property, or attempted
to remove the CALDAV:schedule-default-calendar-URL property
on the scheduling Inbox collection on a server that doesn't
allow such operations.
<!ELEMENT default-calendar-needed EMPTY>
valid-schedule-default-calendar-URLurn:ietf:params:xml:ns:caldavPROPPATCH403 Forbidden
(precondition) --
The client attempted to set the
CALDAV:schedule-default-calendar-URL property to a DAV:href
element that doesn't reference a valid calendar collection.
Note: Servers that do not allow clients to change the
CALDAV:schedule-default-calendar-URL property would simply
return the DAV:cannot-modify-protected-property precondition
defined in Section 16 of WebDAV.
<!ELEMENT valid-schedule-default-calendar-URL EMPTY>
Busy time information of one or more calendar users can be determined by submitting a POST request targeted at the scheduling Outbox collection of the calendar user requesting the information (the "Organizer"). To accomplish this, the request body MUST contain a "VFREEBUSY" calendar component with the "METHOD" iCalendar property set to the value "REQUEST" as specified in Section 3.3.2 of iTIP. The resource identified by the Request-URI MUST be a resource collection of type CALDAV:schedule-outbox. The "ORGANIZER" property value in the "VFREEBUSY" component MUST match one of the calendar user addresses of the owner of the Outbox collection.
A response to a busy time request that indicates status for one or more
calendar users MUST be an XML document with a CALDAV:schedule-response XML
element as its root element. This element MUST contain one CALDAV:response
element for each calendar user, with each such element in turn
containing elements that
indicate which calendar user they correspond to, the scheduling status for that
calendar user, any error codes, and an optional description. For a successful
busy time request, a CALDAV:calendar-data element is also present for each
calendar user, containing the actual busy time information (i.e., an iCalendar
"VFREEBUSY" component). See for
details on the child elements. See for an
example busy time request and response.
The list below summarizes the most common status codes used
for this method. However, clients need to be prepared to handle other
2/3/4/5xx series status codes as well.
200 (OK) -
The command succeeded.
204 (No Content) -
The command succeeded.
400 (Bad Request) -
The client has provided an invalid scheduling message.
403 (Forbidden) -
The client cannot submit a scheduling message to the
specified Request-URI.
404 (Not Found) -
The URL in the Request-URI was not present.
423 (Locked) - The specified resource is locked, and
the client either is not a lock owner or the lock type
requires a lock token to be submitted and the client did
not submit it.
The following are existing preconditions that are reused for the
POST method on an Outbox collection.
DAV:need-privilegesCALDAV:supported-calendar-dataCALDAV:valid-calendar-dataCALDAV:max-resource-size
The following are new method preconditions
for the POST method on an Outbox collection.
valid-scheduling-messageurn:ietf:params:xml:ns:caldavPOST400 Bad Request
(precondition) -- The resource submitted in the POST request MUST obey all the restrictions specified in Section 3.3.2 of iTIP.
<!ELEMENT valid-scheduling-message EMPTY>
valid-organizerurn:ietf:params:xml:ns:caldavPOST403 Forbidden
(precondition) -- The "ORGANIZER" property value in the POST request's scheduling message MUST match one of the calendar user addresses of the owner of the scheduling Outbox collection being targeted by the request.
<!ELEMENT valid-organizer EMPTY>
New scheduling privileges are defined in this section. All the scheduling privileges MUST be non-abstract and MUST appear in the DAV:supported-privilege-set property of scheduling Outbox and Inbox collections on which they are defined.The tables specified in clarify which scheduling methods (e.g., "REQUEST", "REPLY", etc.) are controlled by each scheduling privilege defined in this section.This section defines new WebDAV
Access Control List (ACL) privileges that are defined for use on scheduling Inbox collections. These
privileges determine whether delivery of scheduling messages from a calendar
user is allowed by the calendar user who "owns" the scheduling Inbox
collection. This allows calendar users to choose which other calendar users can
schedule with them.Note that when a scheduling message is delivered to a calendar user, in addition to a scheduling object resource being created in the calendar user's scheduling Inbox collection, a new scheduling object resource might be created or an existing one updated in a calendar belonging to the calendar user. In that case, the ability to create or update the scheduling object resource in the calendar is controlled by the privileges assigned to the scheduling Inbox collection.The privileges defined in this section are ignored if applied to a resource other than a scheduling Inbox collection.CALDAV:schedule-deliver is an aggregate privilege as per .
<!ELEMENT schedule-deliver EMPTY>
The CALDAV:schedule-deliver-invite privilege controls the processing and delivery of scheduling messages coming from an "Organizer".
<!ELEMENT schedule-deliver-invite EMPTY>
The CALDAV:schedule-deliver-reply privilege controls the processing and delivery of scheduling messages coming from an "Attendee".
<!ELEMENT schedule-deliver-reply EMPTY>
The CALDAV:schedule-query-freebusy privilege controls freebusy requests targeted at the owner of the scheduling Inbox collection.
<!ELEMENT schedule-query-freebusy EMPTY>
This section defines new WebDAV
ACL privileges that are defined for use on scheduling Outbox
collections. These privileges determine which calendar users are allowed to
send scheduling messages on behalf of the calendar user who "owns" the
scheduling Outbox collection. This allows calendar users to choose other
calendar users who can act on their behalf (e.g., assistants working on behalf
of their boss).The privileges defined in this section are ignored if applied to
a resource other than a scheduling Outbox collection.CALDAV:schedule-send is an aggregate privilege as per .
<!ELEMENT schedule-send EMPTY>
The CALDAV:schedule-send-invite privilege controls the sending of scheduling messages by "Organizers".Users granted the DAV:bind privilege on a calendar collection, or
the DAV:write privilege on scheduling object resources, will also need the CALDAV:schedule-send-invite privilege granted on the scheduling Outbox collection of the owner of the calendar collection or scheduling object resource in order to be allowed to create, modify, or delete scheduling object resources in a way that will trigger the CalDAV server to deliver scheduling messages to "Attendees".
<!ELEMENT schedule-send-invite EMPTY>
The CALDAV:schedule-send-reply privilege controls the sending of scheduling messages by "Attendees".Users granted the DAV:bind privilege on a calendar collection, or
the DAV:write privilege on scheduling object resources, will also need the CALDAV:schedule-send-reply privilege granted on the scheduling Outbox collection of the owner of the calendar collection or scheduling object resource in order to be allowed to create, modify, or delete scheduling object resources in a way that will trigger the CalDAV server to deliver scheduling message replies to the "Organizer".
<!ELEMENT schedule-send-reply EMPTY>
The CALDAV:schedule-send-freebusy privilege controls the use of the POST method to submit scheduling messages that specify the scheduling method "REQUEST" with a "VFREEBUSY" calendar component.
<!ELEMENT schedule-send-freebusy EMPTY>
Server implementations MUST aggregate the scheduling privileges as follows:
DAV:all contains CALDAV:schedule-deliver and CALDAV:schedule-send;CALDAV:schedule-deliver contains
CALDAV:schedule-deliver-invite, CALDAV:schedule-deliver-reply, and
CALDAV:schedule-query-freebusy;CALDAV:schedule-send contains CALDAV:schedule-send-invite,
CALDAV:schedule-send-reply, and CALDAV:schedule-send-freebusy.The following diagram illustrates how scheduling privileges are aggregated according to the above requirements.
[DAV:all] (aggregate)
|
+-- [CALDAV:schedule-deliver] (aggregate)
| |
| +-- [CALDAV:schedule-deliver-invite]
| +-- [CALDAV:schedule-deliver-reply]
| +-- [CALDAV:schedule-query-freebusy]
|
+-- [CALDAV:schedule-send] (aggregate)
|
+-- [CALDAV:schedule-send-invite]
+-- [CALDAV:schedule-send-reply]
+-- [CALDAV:schedule-send-freebusy]
This specification defines additional iCalendar property
parameters to support the CalDAV scheduling extensions.
SCHEDULE-AGENT
To specify the agent expected to deliver scheduling
messages to the corresponding "Organizer" or "Attendee".
This property parameter is defined by the following notation:
scheduleagentparam = "SCHEDULE-AGENT" "="
("SERVER" ; The server handles scheduling
/ "CLIENT" ; The client handles scheduling
/ "NONE" ; No scheduling
/ x-name ; Experimental type
/ iana-token) ; Other IANA-registered type
;
; If the parameter is not present, its value defaults to SERVER.
; "x-name" and "iana-token" are defined in Section 3.1 of
; [RFC5545].
This property parameter MAY be specified on "ORGANIZER" or "ATTENDEE"
iCalendar properties. In the absence of this parameter, the
value "SERVER" MUST be used for the default behavior.
The value determines whether or not a scheduling
operation on a server will cause a scheduling message
to be sent to the corresponding calendar user identified
by the "ORGANIZER" or "ATTENDEE" property value. When the value "SERVER"
is specified, or the parameter is absent, then it is the
server's responsibility to send a scheduling message as
part of a scheduling operation. When the value
"CLIENT" is specified, that indicates that the client
is handling scheduling messages with the calendar user
itself. When "NONE" is specified, no scheduling messages
are being sent to the calendar user.
Servers MUST NOT include this parameter in any scheduling
messages sent as the result of a scheduling
operation.
Clients MUST NOT include this parameter in any scheduling
messages that they themselves send.
The parameter value MUST be the same on every "ORGANIZER" property in a scheduling object resource.
The parameter value MUST be the same on each "ATTENDEE" property whose values match in a scheduling object resource.
Servers and clients MUST treat x-name and iana-token
values they do not recognize the same way as they would
the "NONE" value.
ORGANIZER;SCHEDULE-AGENT=SERVER:mailto:bernard@example.com
ATTENDEE;SCHEDULE-AGENT=NONE:mailto:cyrus@example.com
SCHEDULE-FORCE-SEND
To force a scheduling message to be sent to the calendar
user specified by the property.
This property parameter is defined by the following notation:
scheduleforcesendparam = "SCHEDULE-FORCE-SEND" "="
("REQUEST" ; Force a "REQUEST"
/ "REPLY" ; Force a "REPLY"
/ iana-token)
;
; "iana-token" is defined in Section 3.1 of [RFC5545]. Its value
; MUST be an IANA-registered iCalendar "METHOD" property value.
This property parameter MAY be specified on "ATTENDEE"
and "ORGANIZER" properties on which the "SCHEDULE-AGENT"
property parameter is set to the value "SERVER" or is
not specified.
This property parameter is used to force a server to send
a scheduling message to a specific calendar user in
situations where the server would not send a scheduling
message otherwise (e.g., when no change that warrants the
delivery of a new scheduling message was performed on
the scheduling object resource).
An "Organizer" MAY specify this parameter on an "ATTENDEE"
property with the value "REQUEST" to force a "REQUEST"
scheduling message to be sent to this "Attendee".
An "Attendee" MAY specify this parameter on the "ORGANIZER"
with the value "REPLY" to force a "REPLY" scheduling
message to be sent to the "Organizer".
Servers MUST NOT preserve this property parameter in
scheduling object resources, nor include it in any
scheduling messages sent as the result of a scheduling operation.
Clients MUST NOT include this parameter in any scheduling
messages that they themselves send.
Servers MUST set the "SCHEDULE-STATUS" parameter of the
"ATTENDEE" or "ORGANIZER" to 2.3 (i.e., "Success; invalid
property parameter ignored"; see Section 3.6 of
)
when the "SCHEDULE-FORCE-SEND" parameter is set to
an iana-token value they do not recognize.
ORGANIZER;SCHEDULE-FORCE-SEND=REPLY:mailto:cyrus@example.com
ATTENDEE;SCHEDULE-FORCE-SEND=REQUEST:mailto:bernard@example.com
SCHEDULE-STATUS
To specify the status codes returned from processing of the
most recent scheduling message sent to the corresponding
"Attendee", or received from the corresponding "Organizer".
This property parameter is defined by the following notation:
schedulestatusparam = "SCHEDULE-STATUS" "="
( statcode
/ DQUOTE statcode *("," statcode) DQUOTE)
;
; "statcode" is defined in Section 3.8.8.3 of [RFC5545]. The
; value is a single "statcode" or a comma-separated list of
; "statcode" values.
This property parameter MAY be specified on the "ATTENDEE"
and "ORGANIZER" properties.
Servers MUST only add or change this property parameter on any "ATTENDEE" properties corresponding to calendar users who were sent a scheduling message via a scheduling operation. Clients SHOULD NOT change or remove this parameter if it was provided by the server. In the case where the client is handling the scheduling, the client MAY add, change, or remove this parameter to indicate the last scheduling message status it received.
Servers MUST add this parameter to any "ORGANIZER"
properties corresponding to calendar users who were sent
a scheduling message reply by an "Attendee" via a scheduling operation. Clients SHOULD NOT change or remove
this parameter if it was provided by the server. In the
case where the client is handling the scheduling, the client
MAY add, change, or remove this parameter to indicate the
last scheduling message status it received.
Servers MUST NOT include this parameter in any scheduling messages sent as the result of a scheduling operation.Clients MUST NOT include this parameter in any scheduling messages that they themselves send.Values for this property parameter are described in .
ATTENDEE;SCHEDULE-STATUS="2.0":mailto:bernard@example.com
ATTENDEE;SCHEDULE-STATUS="2.0,2.4":mailto:cyrus@example.com
This specification defines additional HTTP request and response
headers for use with CalDAV.
Schedule-Reply = "Schedule-Reply" ":" ("T" | "F")
Schedule-Reply: F
When an "Attendee" removes a scheduling
object resource as per , and
the Schedule-Reply header is set to the value "T" (true) or
is not present, the server MUST send an
appropriate reply scheduling message with the "Attendee's"
"PARTSTAT" iCalendar property parameter value set to "DECLINED"
as part of its normal scheduling operation
processing.
When the Schedule-Reply header is set to the value "F" (false), the
server MUST NOT send a scheduling message as part of its
normal scheduling operation processing.
The Schedule-Reply request header is used by a client to
indicate to a server whether or not a scheduling
operation ought to occur when an "Attendee" deletes a scheduling
object resource. In particular, it controls whether a reply
scheduling message is sent to the "Organizer" as a result of the
removal. There are situations in which unsolicited scheduling
messages need to be silently removed (or ignored) for security
or privacy reasons. This request header allows the scheduling
object resource to be removed if such a need arises.
The Schedule-Tag response header provides the current value of
the CALDAV:schedule-tag property value. The behavior of this
response header is described in .
All scheduling object resources MUST support the Schedule-Tag
header.
Schedule-Tag = "Schedule-Tag" ":" opaque-tag
; "opaque-tag" is defined in Section 3.11 of [RFC2616].
Schedule-Tag: "12ab34-cd56ef"
The If-Schedule-Tag-Match request header field is used with a
method to make it conditional. Clients can set this header to
the value returned in the Schedule-Tag response header, or the
CALDAV:schedule-tag property, of a scheduling object resource
previously retrieved from the server to avoid overwriting
"consequential" changes to the scheduling object resource.
All scheduling object resources MUST support the
If-Schedule-Tag-Match header.
If-Schedule-Tag-Match = "If-Schedule-Tag-Match" ":" opaque-tag
; "opaque-tag" is defined in Section 3.11 of [RFC2616].
If-Schedule-Tag-Match: "12ab34-cd56ef"
This specification defines the following new WebDAV
properties for use with CalDAV.
schedule-calendar-transpurn:ietf:params:xml:ns:caldavDetermines whether the calendar object resources in a calendar collection will affect the owner's busy time information.This property MAY be protected and SHOULD NOT be returned by a PROPFIND DAV:allprop request (as defined in Section 14.2 of ).This property value SHOULD be kept during a MOVE operation, and SHOULD be copied and preserved in a COPY.This property SHOULD be defined on all
calendar collections. If present, it contains one of two XML elements that
indicate whether the calendar object resources in the calendar collection ought
to contribute to the owner's busy time. When the CALDAV:opaque element is used,
all calendar object resources in the corresponding calendar collection MUST
contribute to busy time, assuming that access privileges and other iCalendar properties allow it to. When the CALDAV:transparent XML element is used, the calendar object resources in the corresponding calendar collection MUST NOT contribute to busy time.If this property is not present on a calendar collection, then the default value CALDAV:opaque MUST be assumed.
<!ELEMENT schedule-calendar-transp (opaque | transparent)>
<!ELEMENT opaque EMPTY>
<!-- Affects busy time searches -->
<!ELEMENT transparent EMPTY>
<!-- Invisible to busy time searches -->
<C:schedule-calendar-transp
xmlns:C="urn:ietf:params:xml:ns:caldav">
<C:opaque/>
</C:schedule-calendar-transp>
schedule-default-calendar-URLurn:ietf:params:xml:ns:caldavSpecifies a default calendar for an "Attendee" where new scheduling object resources are created.This property MAY be protected in the case where a server does not support changing the default calendar, or does not support a default calendar.This property is only defined on a scheduling Inbox collection that cannot be moved or copied.This property MAY be defined on a
scheduling Inbox collection. If present, it contains zero or one DAV:href XML
elements. When a DAV:href element is present, its value indicates a URL to a
calendar collection that is used as the default calendar. When no DAV:href
element is present, it indicates that there is no default calendar. In the
absence of this property, there is no default calendar. When there is no default
calendar, the server is free to choose the calendar in which a new scheduling
object resource is created. See .
<!ELEMENT schedule-default-calendar-URL (DAV:href?)>
<C:schedule-default-calendar-URL xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:caldav">
<D:href>/home/cyrus/calendars/work/</D:href>
</C:schedule-default-calendar-URL>
schedule-tagurn:ietf:params:xml:ns:caldavIndicates whether a scheduling object resource has had a "consequential" change made to it.opaque-tag (defined in Section 3.11 of )This property MUST be protected, as only the server can update the value.This property value is determined
by the server and MAY be different from the value on the source resource.The CALDAV:schedule-tag property MUST be defined on all scheduling object resources. This property is described in .
<!ELEMENT schedule-tag (#PCDATA)>
<C:schedule-tag xmlns:C="urn:ietf:params:xml:ns:caldav"
>"12345-67890"</C:schedule-tag>
schedule-responseurn:ietf:params:xml:ns:caldavContains the set of responses for a POST method request.See .
<!ELEMENT schedule-response (response*)>
responseurn:ietf:params:xml:ns:caldavContains a single response for a POST method request.See .
<!ELEMENT response (recipient,
request-status,
calendar-data?,
DAV:error?,
DAV:responsedescription?)>
<!-- CALDAV:calendar-data is defined in Section 9.6 of
RFC 4791 and when used here uses the definition with
content (#PCDATA) only. -->
recipienturn:ietf:params:xml:ns:caldavThe calendar user address that the enclosing response for a POST method request is for.See .
<!ELEMENT recipient (DAV:href)>
request-statusurn:ietf:params:xml:ns:caldavThe iTIP "REQUEST-STATUS" property value for this response.See .
<!ELEMENT request-status (#PCDATA)>
The process of scheduling involves the sending and receiving of
scheduling messages. As a result, the security problems related to
messaging in general are relevant here. In particular, the authenticity
of the scheduling messages needs to be verified. Servers and clients
MUST use an HTTP connection protected with Transport Layer Security (TLS)
as defined in for all scheduling operations. Clients MUST use the
procedures detailed in Section 6 of to verify the
authenticity of the server. Servers MUST make use of HTTP authentication to verify the authenticity
of the calendar user for whom the client is sending requests.
Servers MUST ensure that clients cannot consume excessive server resources by carrying out "large" scheduling operations. In particular, servers SHOULD enforce CALDAV:max-resource-size, CALDAV:max-instances, and CALDAV:max-attendees-per-instance preconditions as applicable for scheduling Inbox and Outbox collections.
When handling a scheduling operation:
Servers MUST verify that the principal associated with
the DAV:owner of the calendar collection in which a
scheduling object resource is being manipulated contains a
CALDAV:schedule-outbox-URL property value.
Servers MUST verify that the currently authenticated user
has the CALDAV:schedule-send privilege, or a sub-privilege aggregated under this privilege, on the scheduling Outbox collection of the DAV:owner of the calendar collection in which a scheduling
object resource is being manipulated.
Servers MUST only deliver scheduling messages to recipients
when the CALDAV:schedule-deliver privilege, or a sub-privilege aggregated under this privilege, is granted on the recipient's scheduling Inbox collection for the principal associated with the DAV:owner of the calendar collection in which a scheduling
object resource is being manipulated.
To prevent impersonation of calendar users, the server MUST
verify that the "ORGANIZER" property in an organizer scheduling
object resource matches one of the calendar user addresses
of the DAV:owner of the calendar collection in which the
resource is stored.
To prevent spoofing of an existing scheduling object resource,
servers MUST verify that the "UID" iCalendar property value
in a new scheduling object resource does not match that
of an existing scheduling object resource with a different
"ORGANIZER" property value.
When handling a POST request on a scheduling Outbox collection:
Servers MUST verify that the principal associated with the
calendar user address specified in the "ORGANIZER" property
of the scheduling message data in the request contains a
CALDAV:schedule-outbox-URL property value that matches the
scheduling Outbox collection targeted by the request.
Servers MUST verify that the currently authenticated user
has the CALDAV:schedule-send privilege, or a sub-privilege aggregated under this privilege, on the scheduling Outbox collection targeted by the request.
Servers MUST only return valid freebusy information for recipients
when the CALDAV:schedule-deliver privilege, or a sub-privilege aggregated under this privilege, is granted on the recipient's scheduling Inbox collection for the principal associated with the DAV:owner of the scheduling Outbox collection targeted by the request.
This specification only defines how calendar users on the same server
are able to schedule with each other -- unauthenticated users have no way to
carry out scheduling operations. Access control privileges (as per ) can control which of those users can schedule with
others. Calendar users not wishing to expose their calendar information to
other users can do so by denying privileges to specific users, or all users,
for all scheduling operations, or perhaps only freebusy."Attendees" can also use the Schedule-Reply request header with the value set to "F" to prevent notification to an "Organizer" that a scheduling object resource was deleted. This allows "Attendees" to remove unwanted scheduling messages without any response to the "Organizer".
Servers MUST NOT expose any private iCalendar data, or WebDAV resource state information (URLs, WebDAV properties, etc.) for one calendar user to another via scheduling messages or error responses to scheduling operations. In particular, as per Section 8.1 of , authorization errors MUST take preference over other errors.
Section 6.1 of iTIP defines a set of
potential threats in a scheduling system, and Section 6.2 of
defines
recommendations on how those can be addressed in protocols using iTIP. This
specification addresses the iTIP threats in the following manner:
Addressed by item 4 in .Addressed by and item 2 in .Addressed by item 5 in .Addressed by requiring TLS.Addressed by requirements in .This specification does not support the REFRESH method.
The message header fields below have been added to the Permanent
Message Header Field Registry (see ).
Header field name: Schedule-ReplyApplicable protocol: httpStatus: standardAuthor/Change controller: IETFSpecification document(s): this specification ()Related information: noneHeader field name: Schedule-TagApplicable protocol: httpStatus: standardAuthor/Change controller: IETFSpecification document(s): this specification ()Related information: noneHeader field name: If-Schedule-Tag-MatchApplicable protocol: httpStatus: standardAuthor/Change controller: IETFSpecification document(s): this specification ()Related information: none
The following iCalendar property parameter names have been added to
the iCalendar Parameters Registry defined in Section
8.3.3 of .
ParameterStatusReferenceSCHEDULE-AGENTCurrentRFC 6638, SCHEDULE-STATUSCurrentRFC 6638, SCHEDULE-FORCE-SENDCurrentRFC 6638,
The following iCalendar "REQUEST-STATUS" values have been added to
the iCalendar REQUEST-STATUS Value Registry defined in Section
7.3 of .
Status CodeStatusReference1.0CurrentRFC 6638, 1.1CurrentRFC 6638, 1.2CurrentRFC 6638,
Per this specification, two new IANA registries for iCalendar
elements have been added. Additional codes MAY be used, provided the process described in Section 8.2.1 of is used to register them.
The following table has been used to initialize the
Schedule Agent Values Registry.
Schedule AgentStatusReferenceSERVERCurrentRFC 6638, CLIENTCurrentRFC 6638, NONECurrentRFC 6638,
The following table has been used to initialize the
Schedule Force Send Values Registry.
Schedule Force SendStatusReferenceREQUESTCurrentRFC 6638, REPLYCurrentRFC 6638,
The authors would like to thank the following individuals
for contributing their ideas and support for writing this
specification:
Mike Douglass,
Lisa Dusseault,
Red Dutta,
Jacob Farkas,
Jeffrey Harris,
Helge Hess,
Eliot Lear,
Andrew McMillan,
Alexey Melnikov,
Arnaud Quillaud,
Julian F. Reschke,
Wilfredo Sanchez Vega, and
Simon Vaillancourt.
The authors would also like to thank the Calendaring and Scheduling
Consortium for advice with this specification, and for organizing
interoperability testing events to help refine it.
Key words for use in RFCs to Indicate Requirement LevelsHarvard University1350 Mass. Ave.CambridgeMA 02138- +1 617 495 3864sob@harvard.edu
General
keyword
In many standards track documents several words are used to signify
the requirements in the specification. These words are often
capitalized. This document defines these words as they should be
interpreted in IETF documents. Authors who follow these guidelines
should incorporate this phrase near the beginning of their document:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119.
Note that the force of these words is modified by the requirement
level of the document in which they are used.
Hypertext Transfer Protocol -- HTTP/1.1Department of Information and Computer ScienceUniversity of California, IrvineIrvineCA92697-3425+1(949)824-1715fielding@ics.uci.eduWorld Wide Web ConsortiumMIT Laboratory for Computer Science, NE43-356545 Technology SquareCambridgeMA02139+1(617)258-8682jg@w3.orgCompaq Computer CorporationWestern Research Laboratory250 University AvenuePalo AltoCA94305mogul@wrl.dec.comWorld Wide Web ConsortiumMIT Laboratory for Computer Science, NE43-356545 Technology SquareCambridgeMA02139+1(617)258-8682frystyk@w3.orgXerox CorporationMIT Laboratory for Computer Science, NE43-3563333 Coyote Hill RoadPalo AltoCA94034masinter@parc.xerox.comMicrosoft Corporation1 Microsoft WayRedmondWA98052paulle@microsoft.comWorld Wide Web ConsortiumMIT Laboratory for Computer Science, NE43-356545 Technology SquareCambridgeMA02139+1(617)258-8682timbl@w3.org
The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information
systems. It is a generic, stateless, protocol which can be used for
many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its
request methods, error codes and headers . A feature of HTTP is
the typing and negotiation of data representation, allowing systems
to be built independently of the data being transferred.
HTTP has been in use by the World-Wide Web global information
initiative since 1990. This specification defines the protocol
referred to as "HTTP/1.1", and is an update to RFC 2068 .
HTTP Authentication: Basic and Digest Access AuthenticationNorthwestern University, Department of MathematicsNorthwestern UniversityEvanstonIL60208-2730USAjohn@math.nwu.eduVerisign Inc.301 Edgewater PlaceSuite 210WakefieldMA01880USApbaker@verisign.comAbiSource, Inc.6 Dunlap CourtSavoyIL61874USAjeff@AbiSource.comAgranat Systems, Inc.5 Clocktower PlaceSuite 400MaynardMA01754USAlawrence@agranat.comMicrosoft Corporation1 Microsoft WayRedmondWA98052USApaulle@microsoft.comNetscape Communications Corporation501 East Middlefield RoadMountain ViewCA94043USAOpen Market, Inc.215 First StreetCambridgeMA02142USAstewart@OpenMarket.com
"HTTP/1.0", includes the specification for a Basic Access
Authentication scheme. This scheme is not considered to be a secure
method of user authentication (unless used in conjunction with some
external secure system such as SSL ), as the user name and
password are passed over the network as cleartext.
This document also provides the specification for HTTP's
authentication framework, the original Basic authentication scheme
and a scheme based on cryptographic hashes, referred to as "Digest
Access Authentication". It is therefore also intended to serve as a
replacement for RFC 2069 . Some optional elements specified by
RFC 2069 have been removed from this specification due to problems
found since its publication; other new elements have been added for
compatibility, those new elements have been made optional, but are
strongly recommended.
Like Basic, Digest access authentication verifies that both parties
to a communication know a shared secret (a password); unlike Basic,
this verification can be done without sending the password in the
clear, which is Basic's biggest weakness. As with most other
authentication protocols, the greatest sources of risks are usually
found not in the core protocol itself but in policies and procedures
surrounding its use.
HTTP Over TLSThis memo describes how to use Transport Layer Security (TLS) to secure Hypertext Transfer Protocol (HTTP) connections over the Internet. This memo provides information for the Internet community.Web Distributed Authoring and Versioning (WebDAV) Access Control ProtocolIBM20 Maguire RoadLexingtonMA02421geoffrey.clemm@us.ibm.comgreenbytes GmbHSalzmannstrasse 152MuensterNW48159Germanyjulian.reschke@greenbytes.deOracle Corporation500 Oracle ParkwayRedwood ShoresCA94065eric.sedlar@oracle.comU.C. Santa Cruz, Dept. of Computer Science1156 High StreetSanta CruzCA95064ejw@cse.ucsc.edu
This document specifies a set of methods, headers, message bodies,
properties, and reports that define Access Control extensions to the
WebDAV Distributed Authoring Protocol. This protocol permits a client to
read and modify access control lists that instruct a server whether to
allow or deny operations upon a resource (such as HyperText Transfer
Protocol (HTTP) method invocations) by a given principal. A lightweight
representation of principals as Web resources supports integration of a
wide range of user management repositories. Search operations allow
discovery and manipulation of principals using human names.
Registration Procedures for Message Header FieldsThis specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Calendaring Extensions to WebDAV (CalDAV)Apple Inc.1 Infinite LoopCupertinoCA95014USAcyrus@daboo.namehttp://www.apple.com/Oracle Corporation600 Blvd. de Maisonneuve WestSuite 1900MontrealQCH3A 3J2CANADAbernard.desruisseaux@oracle.comhttp://www.oracle.com/CommerceNet169 University Ave.Palo AltoCA94301USAldusseault@commerce.nethttp://commerce.net/
Applications
calschedcalschcaldavcalendarcalendaringschedulingwebdaviCaliCalendariTIPtext/calendarHTTP
This document defines extensions to the Web Distributed Authoring
and Versioning (WebDAV) protocol to specify a standard way of
accessing, managing, and sharing calendaring and scheduling
information based on the iCalendar format. This document
defines the "calendar-access" feature of CalDAV.
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Augmented BNF for Syntax Specifications: ABNFInternet Calendaring and Scheduling Core Object Specification (iCalendar)iCalendar Transport-Independent Interoperability Protocol (iTIP)Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)Many application technologies enable secure communication between two entities by means of Internet Public Key Infrastructure Using X.509 (PKIX) certificates in the context of Transport Layer Security (TLS). This document specifies procedures for representing and verifying the identity of application services in such interactions. [STANDARDS-TRACK]Extensible Markup Language (XML) 1.0 (Fifth Edition)iCalendar Message-Based Interoperability Protocol (iMIP)
The following tables specify which scheduling privileges
grant the right to a calendar user to deliver a scheduling
message to the scheduling Inbox collection of another
calendar user. The appropriate behavior depends on the
calendar component type as well as the scheduling "METHOD"
specified in the scheduling message.
+--------------------------------+
| METHOD for VEVENT and VTODO |
+-----------------------------+---------+-------+-----+--------+
| Scheduling Inbox Privilege | REQUEST | REPLY | ADD | CANCEL |
+-----------------------------+---------+-------+-----+--------+
| schedule-deliver | * | * | * | * |
| schedule-deliver-invite | * | | * | * |
| schedule-deliver-reply | | * | | |
| schedule-query-freebusy | | | | |
+-----------------------------+---------+-------+-----+--------+
+----------------------+
| METHOD for VFREEBUSY |
+-----------------------------+----------------------+
| Scheduling Inbox Privilege | REQUEST |
+-----------------------------+----------------------+
| schedule-deliver | * |
| schedule-deliver-invite | |
| schedule-deliver-reply | |
| schedule-query-freebusy | * |
+-----------------------------+----------------------+
The following tables specify which scheduling privileges
grant the right to a calendar user to perform busy time
information requests and to submit scheduling messages
to other calendar users as the result of a scheduling
operation. The appropriate behavior depends on the
calendar component type as well as the scheduling "METHOD"
specified in the scheduling message.
+--------------------------------+
| METHOD for VEVENT and VTODO |
+-----------------------------+---------+-------+-----+--------+
| Scheduling Outbox Privilege | REQUEST | REPLY | ADD | CANCEL |
+-----------------------------+---------+-------+-----+--------+
| schedule-send | * | * | * | * |
| schedule-send-invite | * | | * | * |
| schedule-send-reply | | * | | |
| schedule-send-freebusy | | | | |
+-----------------------------+---------+-------+-----+--------+
+----------------------+
| METHOD for VFREEBUSY |
+-----------------------------+----------------------+
| Scheduling Outbox Privilege | REQUEST |
+-----------------------------+----------------------+
| schedule-send | * |
| schedule-send-invite | |
| schedule-send-reply | |
| schedule-send-freebusy | * |
+-----------------------------+----------------------+
This section describes some example scheduling operations that give
a general idea of how scheduling is carried out between CalDAV clients
and servers from the perspective of meeting "Organizers" and "Attendees".
The server is assumed to be hosted in the "example.com" domain, and users whose email addresses are at the "example.com" domain are assumed to be hosted by the server. In addition, the email addresses in the "example.net" domain are also valid email addresses for calendar users hosted by the server. Calendar users with an email address at the "example.org" domain are assumed to not be hosted by the server.
In the following examples, the requests and responses are incomplete and are only for illustrative purposes. In particular, HTTP authentication headers and behaviors are not shown, even though they are required in normal operation.
In the following example, Cyrus invites Wilfredo, Bernard, and Mike
to a single instance event by simply creating a new scheduling object
resource in one of his calendar collections by using the PUT method.
>> Request <<
PUT /home/cyrus/calendars/work/9263504FD3AD.ics HTTP/1.1
Host: cal.example.com
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
If-None-Match: *
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185254Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:wilfredo@
example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@ex
ample.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE:mailto:mike@example.org
END:VEVENT
END:VCALENDAR
>> Response <<
HTTP/1.1 201 Created
Content-Length: 0
Date: Tue, 02 Jun 2009 18:52:54 GMT
Last-Modified: Tue, 02 Jun 2009 18:52:54 GMT
ETag: "d85561cfe74a4e785eb4639451b434fb"
Schedule-Tag: "488177c8-2ea7-4176-a6cb-fab8cfccdea2"
Once the event creation has been completed, Cyrus's client will retrieve the event back from the server to get the schedule status of each "Attendee", as well as record the Schedule-Tag value for future use. In this example, the server reports that a scheduling message was delivered to Wilfredo, a scheduling message is still pending for Bernard, and the server was unable to deliver a scheduling message to Mike.
>> Request <<
GET /home/cyrus/calendars/work/9263504FD3AD.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 18:52:58 GMT
Last-Modified: Tue, 02 Jun 2009 18:52:58 GMT
ETag: "eb897deabc8939589da116714bc99265"
Schedule-Tag: "488177c8-2ea7-4176-a6cb-fab8cfccdea2"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185300Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE;SCHEDULE-STATUS=
1.2:mailto:wilfredo@e
xample.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE;SCHEDULE-STATUS=
1.0:mailto:bernard@example.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE;SCHEDULE-STATUS=3.7:mailto:mike@example.org
END:VEVENT
END:VCALENDAR
In the following example, Wilfredo's client retrieves and deletes
the new scheduling message that appeared in his scheduling
Inbox collection after the server automatically processed it and
created a new scheduling object resource in his default calendar
collection.
>> Request <<
GET /home/wilfredo/calendars/inbox/27d93fc0a58c.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 18:59:58 GMT
Last-Modified: Tue, 02 Jun 2009 18:59:58 GMT
ETag: "da116714bc9926c89395895eb897deab"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
METHOD:REQUEST
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185254Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:wilfredo@
example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@ex
ample.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE:mailto:mike@example.org
END:VEVENT
END:VCALENDAR
>> Request <<
DELETE /home/wilfredo/calendars/inbox/27d93fc0a58c.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 204 No Content
Date: Tue, 02 Jun 2009 20:40:36 GMT
In the following example, Wilfredo accepts Cyrus's invitation and sets an alarm reminder on the event. It uses the If-Schedule-Tag-Match precondition behavior to ensure it does not overwrite any significant changes from the "Organizer" that might have occurred after it retrieved the initial resource data.
>> Request <<
PUT /home/wilfredo/calendars/work/BB64861C2228.ics HTTP/1.1
Host: cal.example.com
If-Schedule-Tag-Match: "e78f23ed-0188-4bab-938d-2aeb3324c7e8"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185254Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=ACCEPTED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:wilfredo@exam
ple.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@ex
ample.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE:mailto:mike@example.org
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
>> Response <<
HTTP/1.1 200 OK
Content-Length: 0
Date: Tue, 02 Jun 2009 18:57:54 GMT
Last-Modified: Tue, 02 Jun 2009 18:57:54 GMT
ETag: "eb4639451b434fbd85561cfe74a4e785"
Schedule-Tag: "8893ee45-eb9d-428f-b53c-c777daf19e41"
Once the event modification has been completed, Wilfredo's client
will retrieve the event back from the server to get the schedule
status of the "Organizer".
>> Request <<
GET /home/wilfredo/calendars/work/BB64861C2228.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 19:03:03 GMT
Last-Modified: Tue, 02 Jun 2009 19:02:21 GMT
ETag: "5eb897deabda116714bc9926c8939589"
Schedule-Tag: "8893ee45-eb9d-428f-b53c-c777daf19e41"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T190221Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo";SCHEDULE-STATUS=1.2:mailto:cyrus@ex
ample.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=ACCEPTED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:wilfredo@exam
ple.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@ex
ample.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE:mailto:mike@example.org
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
On reception of Wilfredo's reply, Cyrus's server will
automatically update Cyrus's scheduling object resource, make
Wilfredo's scheduling message available in Cyrus's scheduling Inbox
collection, and deliver an updated scheduling message to Bernard to
share Wilfredo's updated participation status. In this example,
Cyrus's client retrieves and deletes this scheduling message in his
scheduling Inbox collection.
>> Request <<
GET /home/cyrus/calendars/inbox/c0a58c27d93f.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 19:05:02 GMT
Last-Modified: Tue, 02 Jun 2009 19:04:20 GMT
ETag: "9265eb897deabc8939589da116714bc9"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
METHOD:REPLY
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185754Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";PARTSTAT=ACCEPTED:mailto:w
ilfredo@example.com
REQUEST-STATUS:2.0;Success
END:VEVENT
END:VCALENDAR
>> Request <<
DELETE /home/cyrus/calendars/inbox/c0a58c27d93f.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 204 No Content
Date: Tue, 02 Jun 2009 19:05:05 GMT
Cyrus's client then retrieves the event back from the server
with Wilfredo's updated participation status.
>> Request <<
GET /home/cyrus/calendars/work/9263504FD3AD.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 19:05:02 GMT
Last-Modified: Tue, 02 Jun 2009 19:04:20 GMT
ETag: "eb897deabc8939589da116714bc99265"
Schedule-Tag: "132cab27-1fe3-67ab-de13-abd348d1dee3"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T190420Z
DTSTART:20090602T160000Z
DTEND:20090602T170000Z
TRANSP:OPAQUE
SUMMARY:Lunch
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT
=ACCEPTED;ROLE=REQ-PARTICIPANT;RSVP=TRUE;SCHEDULE-STATUS=2.0:
mailto:wilfredo@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE;SCHEDULE-STATUS=1
.0:mailto:bernard@example.net
ATTENDEE;CN="Mike Douglass";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-A
CTION;RSVP=TRUE;SCHEDULE-STATUS=3.7:mailto:mike@example.org
END:VEVENT
END:VCALENDAR
In this example, Cyrus requests the busy time information
of Wilfredo, Bernard, and Mike.
>> Request <<
POST /home/cyrus/calendars/outbox/ HTTP/1.1
Host: cal.example.com
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
METHOD:REQUEST
BEGIN:VFREEBUSY
UID:4FD3AD926350
DTSTAMP:20090602T190420Z
DTSTART:20090602T000000Z
DTEND:20090604T000000Z
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega":mailto:wilfredo@example.com
ATTENDEE;CN="Bernard Desruisseaux":mailto:bernard@example.net
ATTENDEE;CN="Mike Douglass":mailto:mike@example.org
END:VFREEBUSY
END:VCALENDAR
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 20:07:34 GMT
Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<C:schedule-response xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:caldav">
<C:response>
<C:recipient>
<D:href>mailto:wilfredo@example.com</D:href>
</C:recipient>
<C:request-status>2.0;Success</C:request-status>
<C:calendar-data>BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
METHOD:REPLY
BEGIN:VFREEBUSY
UID:4FD3AD926350
DTSTAMP:20090602T200733Z
DTSTART:20090602T000000Z
DTEND:20090604T000000Z
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega":mailto:wilfredo@example.com
FREEBUSY;FBTYPE=BUSY:20090602T110000Z/20090602T120000Z
FREEBUSY;FBTYPE=BUSY:20090603T170000Z/20090603T180000Z
END:VFREEBUSY
END:VCALENDAR
</C:calendar-data>
</C:response>
<C:response>
<C:recipient>
<D:href>mailto:bernard@example.net</D:href>
</C:recipient>
<C:request-status>2.0;Success</C:request-status>
<C:calendar-data>BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Server//EN
METHOD:REPLY
BEGIN:VFREEBUSY
UID:4FD3AD926350
DTSTAMP:20090602T200733Z
DTSTART:20090602T000000Z
DTEND:20090604T000000Z
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux":mailto:bernard@example.net
FREEBUSY;FBTYPE=BUSY:20090602T150000Z/20090602T160000Z
FREEBUSY;FBTYPE=BUSY:20090603T090000Z/20090603T100000Z
FREEBUSY;FBTYPE=BUSY:20090603T180000Z/20090603T190000Z
END:VFREEBUSY
END:VCALENDAR
</C:calendar-data>
</C:response>
<C:response>
<C:recipient>
<D:href>mailto:mike@example.org</D:href>
</C:recipient>
<C:request-status>3.7;Invalid calendar user</C:request-status>
</C:response>
</C:schedule-response>
In the following example, Cyrus attempts to create,
on behalf of Wilfredo, an event with Bernard specified
as an "Attendee". The request fails, since Wilfredo didn't
grant Cyrus the right to invite other calendar users
on his behalf.
>> Request <<
PUT /home/wilfredo/calendars/work/def456.ics HTTP/1.1
Host: cal.example.com
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
If-None-Match: *
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VEVENT
UID:3504F926D3AD
SEQUENCE:0
DTSTAMP:20090602T190221Z
DTSTART:20090602T230000Z
DTEND:20090603T000000Z
TRANSP:OPAQUE
SUMMARY:Dinner
ORGANIZER;CN="Wilfredo Sanchez Vega":mailto:wilfredo@example.com
ATTENDEE;CN="Wilfredo Sanchez Vega";CUTYPE=INDIVIDUAL;PARTSTAT=A
CCEPTED:mailto:wilfredo@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=NE
EDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@exampl
e.net
END:VEVENT
END:VCALENDAR
>> Response <<
HTTP/1.1 403 Forbidden
Content-Type: application/xml; charset="utf-8"
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
<D:need-privileges>
<D:resource>
<D:href>/home/wilfredo/calendars/outbox/</D:href>
<D:privilege><C:schedule-send-invite/></D:privilege>
</D:resource>
</D:need-privileges>
</D:error>
In the following example, Bernard declines the second recurrence
instance of a daily recurring event he's been invited to by Cyrus.
>> Request <<
PUT /home/bernard/calendars/work/4FD3AD926350.ics HTTP/1.1
Host: cal.example.com
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
If-Schedule-Tag-Match: "7775FB30-7534-489E-A79A-0EA147B933EB"
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VTIMEZONE
TZID:America/Montreal
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185254Z
DTSTART;TZID=America/Montreal:20090601T150000
DTEND;TZID=America/Montreal:20090601T160000
RRULE:FREQ=DAILY;INTERVAL=1;COUNT=5
TRANSP:OPAQUE
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
ACCEPTED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@exampl
e.net
END:VEVENT
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090603T183823Z
RECURRENCE-ID;TZID=America/Montreal:20090602T150000
DTSTART;TZID=America/Montreal:20090602T150000
DTEND;TZID=America/Montreal:20090602T160000
TRANSP:TRANSPARENT
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
DECLINED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@exampl
e.net
END:VEVENT
END:VCALENDAR
>> Response <<
HTTP/1.1 200 OK
Content-Length: 0
Date: Tue, 02 Jun 2009 18:52:54 GMT
Last-Modified: Tue, 02 Jun 2009 18:52:54 GMT
ETag: "d85561cfe74a4e785eb4639451b434fb"
Schedule-Tag: "488177c8-2ea7-4176-a6cb-fab8cfccdea2"
Bernard's participation status update will cause his
server to deliver a scheduling message to Cyrus.
Cyrus's client will find the following reply message
from Bernard in Cyrus's scheduling Inbox collection:
>> Request <<
GET /home/cyrus/calendars/inbox/9263504FD3AD.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 18:52:58 GMT
Last-Modified: Tue, 02 Jun 2009 18:52:58 GMT
ETag: "eb897deabc8939589da116714bc99265"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
METHOD:REPLY
BEGIN:VTIMEZONE
TZID:America/Montreal
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090603T183823Z
RECURRENCE-ID;TZID=America/Montreal:20090602T150000
DTSTART;TZID=America/Montreal:20090602T150000
DTEND;TZID=America/Montreal:20090602T160000
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";PARTSTAT=DECLINED:
mailto:bernard@example.net
REQUEST-STATUS:2.0;Success
END:VEVENT
END:VCALENDAR
In the following example, Bernard removes from his calendar the
third recurrence instance of a daily recurring event he's been
invited to by Cyrus. This is accomplished by the addition of an "EXDATE" property to the scheduling object resource stored by Bernard.
>> Request <<
PUT /home/bernard/calendars/work/4FD3AD926350.ics HTTP/1.1
Host: cal.example.com
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
If-Schedule-Tag-Match: "488177c8-2ea7-4176-a6cb-fab8cfccdea2"
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
BEGIN:VTIMEZONE
TZID:America/Montreal
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090602T185254Z
DTSTART;TZID=America/Montreal:20090601T150000
DTEND;TZID=America/Montreal:20090601T160000
RRULE:FREQ=DAILY;INTERVAL=1;COUNT=5
EXDATE;TZID=America/Montreal:20090603T150000
TRANSP:OPAQUE
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
ACCEPTED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@exampl
e.net
END:VEVENT
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090603T183823Z
RECURRENCE-ID;TZID=America/Montreal:20090602T150000
DTSTART;TZID=America/Montreal:20090602T150000
DTEND;TZID=America/Montreal:20090602T160000
TRANSP:TRANSPARENT
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Cyrus Daboo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:
mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";CUTYPE=INDIVIDUAL;PARTSTAT=
DECLINED;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:bernard@exampl
e.net
END:VEVENT
END:VCALENDAR
Bernard's deletion of a recurrence instance will cause his
server to deliver a scheduling message to Cyrus.
Cyrus's client will find the following reply message
from Bernard in Cyrus's scheduling Inbox collection:
>> Request <<
GET /home/cyrus/calendars/inbox/6504923FD3AD.ics HTTP/1.1
Host: cal.example.com
>> Response <<
HTTP/1.1 200 OK
Date: Tue, 02 Jun 2009 18:52:58 GMT
Last-Modified: Tue, 02 Jun 2009 18:52:58 GMT
ETag: "eb897deabc8939589da116714bc99265"
Content-Type: text/calendar; charset="utf-8"
Content-Length: xxxx
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Corp.//CalDAV Client//EN
METHOD:REPLY
BEGIN:VTIMEZONE
TZID:America/Montreal
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9263504FD3AD
SEQUENCE:0
DTSTAMP:20090603T183823Z
RECURRENCE-ID;TZID=America/Montreal:20090603T150000
DTSTART;TZID=America/Montreal:20090603T150000
DTEND;TZID=America/Montreal:20090603T160000
SUMMARY:Review Internet-Draft
ORGANIZER;CN="Cyrus Daboo":mailto:cyrus@example.com
ATTENDEE;CN="Bernard Desruisseaux";PARTSTAT=DECLINED:
mailto:bernard@example.net
REQUEST-STATUS:2.0;Success
END:VEVENT
END:VCALENDAR