Try out our new RRULE tool for creating RRULE compatible strings.

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 Section 4). However, in some cases, a scheduling message can get delivered directly to the client (e.g., via email [RFC6047]), 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-AGENT | Action                                           |
+----------------+--------------------------------------------------+
| SERVER         | The server will attempt to process changes to    |
| (default)      | the resource using the normal rules for attendee |
|                | scheduling object resources.                     |
|                |                                                  |
| CLIENT         | The server does no special processing of the     |
|                | resource.  The client is assumed to be handling  |
|                | "Attendee" replies, etc.                         |
|                |                                                  |
| NONE           | The 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 Section 7.3, with the value set as described in Section 3.2.9.

This document was automatically converted to XHTML using an RFC to HTML converter with the original text document at the Internet Engineering Task Force web site at ietf.org .  The original text document should be referred to if there are any errors or discrepancies found in this document.

Need to test your iCalendar feeds? The iCalendar Validator provides developers and testers a method to validate their iCalendar feeds, which can take data from either a URL, file or text snippet and compare it against the RFC 5545 specification.  We believe we have one of the best iCalendar validation tools available on the internet. More information about the validator can be found here.