draft-ietf-calsch-itip-06.txt   rfc2446.txt 
Network Working Group Steve Silverberg, Microsoft Network Working Group S. Silverberg
INTERNET-DRAFT Steve Mansour, Netscape Request for Comments: 2446 Microsoft
Calendaring and Scheduling Working Group Frank Dawson, Lotus Category: Standards Track S. Mansour
<draft-ietf-calsch-itip-06.txt> Ross Hopson, ON Technologies Netscape
Expires six months after: September 15, 1998 F. Dawson
Lotus
R. Hopson
ON Technologies
November 1998
iCalendar Transport-Independent Interoperability Protocol iCalendar Transport-Independent Interoperability Protocol
(iTIP) (iTIP)
Scheduling Events, BusyTime, To-dos and Journal Entries Scheduling Events, BusyTime, To-dos and Journal Entries
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months.
Internet-Drafts may be updated, replaced, or made obsolete by other
documents at any time. It is not appropriate to use Internet-Drafts as
reference material or to cite them other than as a "working draft" or
"work in progress".
To view the entire list of current Internet-Drafts, please check the This document specifies an Internet standards track protocol for the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Internet community, and requests discussion and suggestions for
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), improvements. Please refer to the current edition of the "Internet
ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), Official Protocol Standards" (STD 1) for the standardization state
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). and status of this protocol. Distribution of this memo is unlimited.
Distribution of this document is unlimited. Copyright Notice
Copyright (C) The Internet Society 1998. All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This document specifies how calendaring systems use iCalendar objects to
interoperate with other calendar systems. It does so in a general way so
as to allow multiple methods of communication between systems.
Subsequent documents specify interoperable methods of communications
between systems that use this protocol.
The document outlines a model for calendar exchange that defines both
static and dynamic event, to-do, journal and free/busy objects. Static
objects are used to transmit information from one entity to another
without the expectation of continuity or referential integrity with the
original item. Dynamic objects are a superset of static objects and will
gracefully degrade to their static counterparts for clients that only
support static objects.
This document specifies an Internet protocol based on the iCalendar
object specification that provides scheduling interoperability between
different calendar systems. The Internet protocol is called the
"iCalendar Transport-Independent Interoperability Protocol (iTIP)".
iTIP complements the iCalendar object specification by adding semantics
for group scheduling methods commonly available in current calendar
systems. These scheduling methods permit two or more calendar systems to
perform transactions such as publish, schedule, reschedule, respond to
scheduling requests, negotiation of changes or cancel iCalendar-based
calendar components.
iTIP is defined independent of the particular transport used to transmit
the scheduling information. Companion memos to iTIP provide bindings of
the interoperability protocol to a number of Internet protocols.
Table of Contents
1 INTRODUCTION.........................................................5
1.1 FORMATTING CONVENTIONS ...........................................5
1.2 RELATED DOCUMENTS ................................................6
1.3 ITIP ROLES AND TRANSACTIONS ......................................6
2 INTEROPERABILITY MODELS..............................................8
2.1 APPLICATION PROTOCOL .............................................8
2.1.1 Calendar Entry State .........................................9
2.1.2 Delegation ...................................................9
2.1.3 Acting on Behalf of other Calendar Users .....................9
2.1.4 Component Revisions ..........................................9
2.1.5 Message Sequencing ..........................................10
3 APPLICATION PROTOCOL ELEMENTS.......................................11 This document specifies how calendaring systems use iCalendar objects
to interoperate with other calendar systems. It does so in a general
3.1 COMMON COMPONENT RESTRICTION TABLES .............................12 way so as to allow multiple methods of communication between systems.
3.2 METHODS FOR VEVENT CALENDAR COMPONENTS ..........................13 Subsequent documents specify interoperable methods of communications
3.2.1 PUBLISH .....................................................14 between systems that use this protocol.
3.2.2 REQUEST .....................................................15
3.2.2.1 Rescheduling an Event....................................17
3.2.2.2 Updating or Reconfirmation of an Event...................17
3.2.2.3 Delegating an Event to another CU........................17
3.2.2.4 Changing the Organizer...................................18
3.2.2.5 Sending on Behalf of the Organizer.......................18
3.2.2.6 Forwarding to An Uninvited CU............................18
3.2.2.7 Updating Attendee Status.................................19
3.2.3 REPLY .......................................................19
3.2.4 ADD .........................................................21
3.2.5 CANCEL ......................................................22
3.2.6 REFRESH .....................................................24
3.2.7 COUNTER .....................................................25
3.2.8 DECLINECOUNTER ..............................................26
3.3 METHODS FOR VFREEBUSY COMPONENTS ................................27
3.3.1 PUBLISH .....................................................28
3.3.2 REQUEST .....................................................29
3.3.3 REPLY .......................................................30
3.4 METHODS FOR VTODO COMPONENTS ....................................31
3.4.1 PUBLISH .....................................................32
3.4.2 REQUEST .....................................................33
3.4.2.1 REQUEST for Rescheduling a VTODO.........................35
3.4.2.2 REQUEST for Update or Reconfirmation of a VTODO..........35
3.4.2.3 REQUEST for Delegating a VTODO...........................36
3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User..........36
3.4.2.5 REQUEST Updated Attendee Status..........................37
3.4.3 REPLY .......................................................37
3.4.4 ADD .........................................................38
3.4.5 CANCEL ......................................................40
3.4.6 REFRESH .....................................................41
3.4.7 COUNTER .....................................................43
3.4.8 DECLINECOUNTER ..............................................44
3.5 METHODS FOR VJOURNAL COMPONENTS .................................45
3.5.1 PUBLISH .....................................................46
3.5.2 ADD .........................................................47
3.5.3 CANCEL ......................................................48
3.6 STATUS REPLIES ..................................................49
3.7 IMPLEMENTATION CONSIDERATIONS ...................................51
3.7.1 Working With Recurrence Instances ...........................51
3.7.2 Attendee Property Considerations ............................52
3.7.3 X-Tokens ....................................................53
4 EXAMPLES............................................................53
4.1 PUBLISHED EVENT EXAMPLES ........................................53
4.1.1 A Minimal Published Event ...................................54
4.1.2 Changing A Published Event ..................................54
4.1.3 Canceling A Published Event .................................55
4.1.4 A Rich Published Event ......................................55
4.1.5 Anniversaries or Events attached to entire days .............56
4.2 GROUP EVENT EXAMPLES ............................................57
4.2.1 A Group Event Request .......................................57
4.2.2 Reply To A Group Event Request ..............................58
4.2.3 Update An Event .............................................59
4.2.4 Countering an Event Proposal ................................59
4.2.5 Delegating an Event .........................................61
4.2.6 Delegate Accepts the Meeting ................................63
4.2.7 Delegate Declines the Meeting ...............................64
4.2.8 Forwarding an Event Request .................................65
4.2.9 Cancel A Group Event ........................................65
4.2.10 Removing Attendees .........................................66
4.2.11 Replacing the Organizer ....................................67
4.3 BUSY TIME EXAMPLES ..............................................68
4.3.1 Request Busy Time ...........................................69
4.3.2 Reply To A Busy Time Request ................................69
4.4 RECURRING EVENT AND TIME ZONE EXAMPLES ..........................69
4.4.1 A Recurring Event Spanning Time Zones .......................69
4.4.2 Modify A Recurring Instance .................................71
4.4.3 Cancel an Instance ..........................................72
4.4.4 Cancel Recurring Event ......................................73
4.4.5 Change All Future Instances .................................73
4.4.6 Add A New Instance To A Recurring Event .....................74
4.4.7 Add A New Series of Instances To A Recurring Event ..........74
4.4.8 Counter An Instance Of A Recurring Event ....................78
4.4.9 Error Reply To A Request ....................................78
4.5 GROUP TO-DO EXAMPLES ............................................79
4.5.1 A VTODO Request .............................................80
4.5.2 A VTODO Reply ...............................................81
4.5.3 A VTODO Request for Updated Status ..........................81
4.5.4 A Reply: Percent-Complete ...................................82
4.5.5 A Reply: Completed ..........................................82
4.5.6 An Updated VTODO Request ....................................82
4.5.7 Recurring VTODOs ............................................83
4.5.7.1 Request for a Recurring VTODO............................83
4.5.7.2 Calculating due dates in recurring VTODOs................84
4.5.7.3 Replying to an instance of a recurring VTODO.............84
4.6 JOURNAL EXAMPLES ................................................84
4.7 OTHER EXAMPLES ..................................................85
4.7.1 Event Refresh ...............................................85
4.7.2 Bad RECURRENCE-ID ...........................................85
5 APPLICATION PROTOCOL FALLBACKS......................................87
5.1 PARTIAL IMPLEMENTATION ..........................................87 The document outlines a model for calendar exchange that defines both
5.1.1 Event-Related Fallbacks .....................................87 static and dynamic event, to-do, journal and free/busy objects.
5.1.2 Free/Busy-Related Fallbacks .................................89 Static objects are used to transmit information from one entity to
5.1.3 To-Do-Related Fallbacks .....................................89 another without the expectation of continuity or referential
5.1.4 Journal-Related Fallbacks ...................................91 integrity with the original item. Dynamic objects are a superset of
5.2 LATENCY ISSUES ..................................................92 static objects and will gracefully degrade to their static
5.2.1 Cancellation of an Unknown Calendar Component. ..............92 counterparts for clients that only support static objects.
5.2.2 Unexpected Reply from an Unknown Delegate ...................92
5.3 SEQUENCE NUMBER .................................................92
6 SECURITY CONSIDERATIONS.............................................93 This document specifies an Internet protocol based on the iCalendar
object specification that provides scheduling interoperability
between different calendar systems. The Internet protocol is called
the "iCalendar Transport-Independent Interoperability Protocol
(iTIP)".
6.1 SECURITY THREATS ................................................93 iTIP complements the iCalendar object specification by adding
6.1.1 Spoofing the "Organizer" ....................................93 semantics for group scheduling methods commonly available in current
6.1.2 Spoofing the "Attendee" .....................................93 calendar systems. These scheduling methods permit two or more
6.1.3 Unauthorized Replacement of the Organizer ...................93 calendar systems to perform transactions such as publish, schedule,
6.1.4 Eavesdropping ...............................................93 reschedule, respond to scheduling requests, negotiation of changes or
6.1.5 Flooding a Calendar .........................................94 cancel iCalendar-based calendar components.
6.1.6 Procedural Alarms ...........................................94
6.1.7 Unauthorized REFRESH Requests ...............................94
6.2 RECOMMENDATIONS .................................................94
6.2.1 Use of [RFC-1847] to secure iTIP transactions ...............94
6.2.2 Implementation Controls .....................................95
7 ACKNOWLEDGMENTS.....................................................95 iTIP is defined independent of the particular transport used to
transmit the scheduling information. Companion memos to iTIP provide
bindings of the interoperability protocol to a number of Internet
protocols.
8 BIBLIOGRAPHY........................................................95 Table of Contents
9 AUTHORS ADDRESSES...................................................96 1 INTRODUCTION...................................................5
1.1 FORMATTING CONVENTIONS .....................................5
1.2 RELATED DOCUMENTS ..........................................6
1.3 ITIP ROLES AND TRANSACTIONS ................................6
2 INTEROPERABILITY MODELS........................................8
2.1 APPLICATION PROTOCOL .......................................9
2.1.1 Calendar Entry State ...................................9
2.1.2 Delegation .............................................9
2.1.3 Acting on Behalf of other Calendar Users ..............10
2.1.4 Component Revisions ...................................10
2.1.5 Message Sequencing ....................................11
3 APPLICATION PROTOCOL ELEMENTS.................................12
3.1 COMMON COMPONENT RESTRICTION TABLES .......................13
3.2 METHODS FOR VEVENT CALENDAR COMPONENTS ....................14
3.2.1 PUBLISH ...............................................15
3.2.2 REQUEST ...............................................17
3.2.2.1 Rescheduling an Event..............................19
3.2.2.2 Updating or Reconfirmation of an Event.............19
3.2.2.3 Delegating an Event to another CU..................19
3.2.2.4 Changing the Organizer.............................20
3.2.2.5 Sending on Behalf of the Organizer.................20
3.2.2.6 Forwarding to An Uninvited CU......................20
3.2.2.7 Updating Attendee Status...........................21
3.2.3 REPLY .................................................21
3.2.4 ADD ...................................................23
3.2.5 CANCEL ................................................25
3.2.6 REFRESH ...............................................26
3.2.7 COUNTER ...............................................28
3.2.8 DECLINECOUNTER ........................................29
3.3 METHODS FOR VFREEBUSY COMPONENTS ..........................31
3.3.1 PUBLISH ...............................................32
3.3.2 REQUEST ...............................................33
3.3.3 REPLY .................................................34
3.4 METHODS FOR VTODO COMPONENTS ..............................35
3.4.1 PUBLISH ...............................................35
3.4.2 REQUEST ...............................................37
3.4.2.1 REQUEST for Rescheduling a VTODO...................39
3.4.2.2 REQUEST for Update or Reconfirmation of a VTODO....39
3.4.2.3 REQUEST for Delegating a VTODO.....................40
3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User....40
3.4.2.5 REQUEST Updated Attendee Status....................41
3.4.3 REPLY .................................................41
3.4.4 ADD ...................................................43
3.4.5 CANCEL ................................................44
3.4.6 REFRESH ...............................................46
3.4.7 COUNTER ...............................................48
3.4.8 DECLINECOUNTER ........................................49
3.5 METHODS FOR VJOURNAL COMPONENTS ...........................50
3.5.1 PUBLISH ...............................................51
3.5.2 ADD ...................................................52
3.5.3 CANCEL ................................................53
3.6 STATUS REPLIES ............................................55
3.7 IMPLEMENTATION CONSIDERATIONS .............................57
3.7.1 Working With Recurrence Instances .....................57
3.7.2 Attendee Property Considerations ......................58
3.7.3 X-Tokens ..............................................59
4 EXAMPLES......................................................59
4.1 PUBLISHED EVENT EXAMPLES ..................................59
4.1.1 A Minimal Published Event .............................60
4.1.2 Changing A Published Event ............................60
4.1.3 Canceling A Published Event ...........................61
4.1.4 A Rich Published Event ................................62
4.1.5 Anniversaries or Events attached to entire days .......63
4.2 GROUP EVENT EXAMPLES ......................................63
4.2.1 A Group Event Request .................................64
4.2.2 Reply To A Group Event Request ........................65
4.2.3 Update An Event .......................................65
4.2.4 Countering an Event Proposal ..........................66
4.2.5 Delegating an Event ...................................68
4.2.6 Delegate Accepts the Meeting ..........................70
4.2.7 Delegate Declines the Meeting .........................71
4.2.8 Forwarding an Event Request ...........................72
4.2.9 Cancel A Group Event ..................................72
4.2.10 Removing Attendees ...................................74
4.2.11 Replacing the Organizer ..............................75
4.3 BUSY TIME EXAMPLES ........................................76
4.3.1 Request Busy Time .....................................77
4.3.2 Reply To A Busy Time Request ..........................77
4.4 RECURRING EVENT AND TIME ZONE EXAMPLES ....................78
4.4.1 A Recurring Event Spanning Time Zones .................78
4.4.2 Modify A Recurring Instance ...........................79
4.4.3 Cancel an Instance ....................................81
4.4.4 Cancel Recurring Event ................................81
4.4.5 Change All Future Instances ...........................82
4.4.6 Add A New Instance To A Recurring Event ...............82
4.4.7 Add A New Series of Instances To A Recurring Event ....83
4.4.8 Counter An Instance Of A Recurring Event ..............87
4.4.9 Error Reply To A Request ..............................88
4.5 GROUP TO-DO EXAMPLES ......................................89
4.5.1 A VTODO Request .......................................90
4.5.2 A VTODO Reply .........................................90
4.5.3 A VTODO Request for Updated Status ....................91
4.5.4 A Reply: Percent-Complete .............................91
4.5.5 A Reply: Completed ....................................92
4.5.6 An Updated VTODO Request ..............................92
4.5.7 Recurring VTODOs ......................................92
4.5.7.1 Request for a Recurring VTODO......................93
4.5.7.2 Calculating due dates in recurring VTODOs..........93
4.5.7.3 Replying to an instance of a recurring VTODO.......93
4.6 JOURNAL EXAMPLES ..........................................94
4.7 OTHER EXAMPLES ............................................94
4.7.1 Event Refresh .........................................94
4.7.2 Bad RECURRENCE-ID .....................................95
5 APPLICATION PROTOCOL FALLBACKS................................97
5.1 PARTIAL IMPLEMENTATION ....................................97
5.1.1 Event-Related Fallbacks ...............................97
5.1.2 Free/Busy-Related Fallbacks ...........................99
5.1.3 To-Do-Related Fallbacks ...............................99
5.1.4 Journal-Related Fallbacks ............................101
5.2 LATENCY ISSUES ...........................................102
5.2.1 Cancellation of an Unknown Calendar Component. .......102
5.2.2 Unexpected Reply from an Unknown Delegate ............103
5.3 SEQUENCE NUMBER ..........................................103
6 SECURITY CONSIDERATIONS......................................103
6.1 SECURITY THREATS .........................................103
6.1.1 Spoofing the "Organizer" .............................103
6.1.2 Spoofing the "Attendee" ..............................103
6.1.3 Unauthorized Replacement of the Organizer ............104
6.1.4 Eavesdropping ........................................104
6.1.5 Flooding a Calendar ..................................104
6.1.6 Procedural Alarms ....................................104
6.1.7 Unauthorized REFRESH Requests ........................104
6.2 RECOMMENDATIONS ..........................................104
6.2.1 Use of [RFC-1847] to secure iTIP transactions ........105
6.2.2 Implementation Controls ..............................105
7 ACKNOWLEDGMENTS..............................................106
8 BIBLIOGRAPHY.................................................106
9 AUTHORS' ADDRESSES...........................................107
10 FULL COPYRIGHT STATEMENT....................................109
10 FULL COPYRIGHT STATEMENT...........................................98 1 Introduction
1 Introduction
This document specifies how calendaring systems use iCalendar objects to This document specifies how calendaring systems use iCalendar objects
interoperate with other calendar systems. In particular, it specifies to interoperate with other calendar systems. In particular, it
how to schedule events, to-dos, or daily journal entries. It further specifies how to schedule events, to-dos, or daily journal entries.
specifies how to search for available busy time information. It does so It further specifies how to search for available busy time
in a general way so as to allow multiple methods of communication information. It does so in a general way so as to allow multiple
between systems. Subsequent documents specify transport bindings between methods of communication between systems. Subsequent documents
systems that use this protocol. specify transport bindings between systems that use this protocol.
This protocol is based on messages sent from an originator to one or This protocol is based on messages sent from an originator to one or
more recipients. For certain types of messages, a recipient may reply, more recipients. For certain types of messages, a recipient may
in order to update their status and may also return transaction/request reply, in order to update their status and may also return
status information. The protocol supports the ability for the message transaction/request status information. The protocol supports the
originator to modify or cancel the original message. The protocol also ability for the message originator to modify or cancel the original
supports the ability for recipients to suggest changes to the originator message. The protocol also supports the ability for recipients to
of a message. The elements of the protocol also define the user roles suggest changes to the originator of a message. The elements of the
for its transactions. protocol also define the user roles for its transactions.
1.1 Formatting Conventions 1.1 Formatting Conventions
In order to refer to elements of the calendaring and scheduling model, In order to refer to elements of the calendaring and scheduling
core object or interoperability protocol defined in [ICMS], [iCAL] and model, core object or interoperability protocol defined in [iCAL] and
[iTIP] several formatting conventions have been utilized. [iTIP] several formatting conventions have been utilized.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in [RFC-2119]. document are to be interpreted as described in [RFC-2119].
Calendaring and scheduling roles described by [ICMS] are referred to in Calendaring and scheduling roles are referred to in quoted-strings of
quoted-strings of text with the first character of each word in upper text with the first character of each word in upper case. For
case. For example, "Organizer" refers to a role of a "Calendar User" example, "Organizer" refers to a role of a "Calendar User" (CU)
(CU) within the scheduling protocol defined by [iTIP]. Calendar within the scheduling protocol defined by [iTIP]. Calendar components
components defined by [iCAL] are referred to with capitalized, quoted- defined by [iCAL] are referred to with capitalized, quoted-strings of
strings of text. All calendar components start with the letter "V". For text. All calendar components start with the letter "V". For example,
example, "VEVENT" refers to the event calendar component, "VTODO" refers "VEVENT" refers to the event calendar component, "VTODO" refers to
to the to-do calendar component and "VJOURNAL" refers to the daily the to-do calendar component and "VJOURNAL" refers to the daily
journal calendar component. Scheduling methods defined by [iTIP] are journal calendar component. Scheduling methods defined by [iTIP] are
referred to with capitalized, quoted-strings of text. For example, referred to with capitalized, quoted-strings of text. For example,
"REQUEST" refers to the method for requesting a scheduling calendar "REQUEST" refers to the method for requesting a scheduling calendar
component be created or modified, "REPLY" refers to the method a component be created or modified, "REPLY" refers to the method a
recipient of a request uses to update their status with the "Organizer" recipient of a request uses to update their status with the
of the calendar component. "Organizer" of the calendar component.
Properties defined by [iCAL] are referred to with capitalized, quoted- Properties defined by [iCAL] are referred to with capitalized,
strings of text, followed by the word "property". For example, quoted-strings of text, followed by the word "property". For example,
"ATTENDEE" property refers to the iCalendar property used to convey the "ATTENDEE" property refers to the iCalendar property used to convey
calendar address of a "Calendar User". Property parameters defined by the calendar address of a "Calendar User". Property parameters
this memo are referred to with lower case, quoted-strings of text, defined by this memo are referred to with lower case, quoted-strings
followed by the word "parameter". For example, "value" parameter refers of text, followed by the word "parameter". For example, "value"
to the iCalendar property parameter used to override the default data parameter refers to the iCalendar property parameter used to override
type for a property value. Enumerated values defined by this memo are the default data type for a property value. Enumerated values defined
referred to with capitalized text, either alone or followed by the word by this memo are referred to with capitalized text, either alone or
"value". followed by the word "value".
In tables, the quoted-string text is specified without quotes in order In tables, the quoted-string text is specified without quotes in
to minimize the table length. order to minimize the table length.
1.2 Related Documents 1.2 Related Documents
Implementers will need to be familiar with several other memos that, Implementers will need to be familiar with several other memos that,
along with this one, describe the Internet calendaring and scheduling along with this one, describe the Internet calendaring and scheduling
standards. This document, [iTIP], specifies an interoperability protocol standards. This document, [iTIP], specifies an interoperability
for scheduling between different implementations. The related documents protocol for scheduling between different implementations. The
are: related documents are:
[ICMS] - describes the abstract model and defines common terms and
concepts;
[iCAL] - specifies the objects, data types, properties and property [iCAL] - specifies the objects, data types, properties and
parameters used in the protocols, along with the methods for property parameters used in the protocols, along with the
representing and encoding them; methods for representing and encoding them;
[iMIP] specifies an Internet email binding for [iTIP]. [iMIP] specifies an Internet email binding for [iTIP].
This memo does not attempt to repeat the specification of concepts or This memo does not attempt to repeat the specification of concepts or
definitions from these other memos. Where possible, references are made definitions from these other memos. Where possible, references are
to the memo that provides for the specification of these concepts or made to the memo that provides for the specification of these
definitions. concepts or definitions.
1.3 ITIP Roles and Transactions 1.3 ITIP Roles and Transactions
ITIP defines methods for exchanging [iCAL] objects for the purposes of ITIP defines methods for exchanging [iCAL] objects for the purposes
group calendaring and scheduling between "Calendar Users" (CUs). CUs of group calendaring and scheduling between "Calendar Users" (CUs).
take on one of two roles in iTIP. The CU who initiates an exchange takes CUs take on one of two roles in iTIP. The CU who initiates an
on the role of "Organizer". For example, the CU who proposes a group exchange takes on the role of "Organizer". For example, the CU who
meeting is the "Organizer". The CUs asked to participate in the group proposes a group meeting is the "Organizer". The CUs asked to
meeting by the "Organizer" take on the role of "Attendee". Note that participate in the group meeting by the "Organizer" take on the role
"role" is also a descriptive parameter to the _ATTENDEE_ property. Its of "Attendee". Note that "role" is also a descriptive parameter to
use is to convey descriptive context to an "Attendee" such as "chair", the _ATTENDEE_ property. Its use is to convey descriptive context to
"req-participant" or "non-participant" and has nothing to do with the an "Attendee" such as "chair", "req-participant" or "non-participant"
calendaring workflow. and has nothing to do with the calendaring workflow.
The ITIP methods are listed below and their usage and semantics are
defined in section 3 of this document.
+================+==================================================+ The ITIP methods are listed below and their usage and semantics are
| Method | Description | defined in section 3 of this document.
|================+==================================================|
| PUBLISH | Used to publish a calendar entry to one or more |
| | Calendar Users. There is no interactivity |
| | between the publisher and any other calendar |
| | user. An example might include a baseball team |
| | publishing its schedule to the public. |
| | |
| REQUEST | Used to schedule a calendar entry with other |
| | Calendar Users. Requests are interactive in that |
| | they require the receiver to respond using |
| | the Reply methods. Meeting Requests, Busy |
| | Time requests and the assignment of VTODOs to |
| | other Calendar Users are all examples. |
| | Requests are also used by the "Organizer" to |
| | update the status of a calendar entry. |
| | |
| REPLY | A Reply is used in response to a Request to |
| | convey "Attendee" status to the "Organizer". |
| | Replies are commonly used to respond to meeting |
| | and task requests. |
| | |
| ADD | Add one or more instances to an existing |
| | VEVENT, VTODO, or VJOURNAL. |
| | |
| CANCEL | Cancel one or more instances of an existing |
| | VEVENT, VTODO, or VJOURNAL. |
| | |
| REFRESH | The Refresh method is used by an "Attendee" to |
| | request the latest version of a calendar entry. |
| | |
| COUNTER | The Counter method is used by an "Attendee" to |
| | negotiate a change in the calendar entry. |
| | Examples include the request to change a |
| | proposed Event time or change the due date for a |
| | VTODO. |
| | |
| DECLINE- | Used by the "Organizer" to decline the proposed |
| COUNTER | counter-proprosal. |
+================+==================================================+
Group scheduling in iTIP is accomplished using the set of "request" and +================+==================================================+
"response" methods described above. The following table shows the | Method | Description |
methods broken down by who can send them. |================+==================================================|
| PUBLISH | Used to publish a calendar entry to one or more |
| | Calendar Users. There is no interactivity |
| | between the publisher and any other calendar |
| | user. An example might include a baseball team |
| | publishing its schedule to the public. |
| | |
| REQUEST | Used to schedule a calendar entry with other |
| | Calendar Users. Requests are interactive in that |
| | they require the receiver to respond using |
| | the Reply methods. Meeting Requests, Busy |
| | Time requests and the assignment of VTODOs to |
| | other Calendar Users are all examples. |
| | Requests are also used by the "Organizer" to |
| | update the status of a calendar entry. |
| | |
| REPLY | A Reply is used in response to a Request to |
| | convey "Attendee" status to the "Organizer". |
| | Replies are commonly used to respond to meeting |
| | and task requests. |
| | |
| ADD | Add one or more instances to an existing |
| | VEVENT, VTODO, or VJOURNAL. |
| | |
| CANCEL | Cancel one or more instances of an existing |
| | VEVENT, VTODO, or VJOURNAL. |
| | |
| REFRESH | The Refresh method is used by an "Attendee" to |
| | request the latest version of a calendar entry. |
| | |
| COUNTER | The Counter method is used by an "Attendee" to |
| | negotiate a change in the calendar entry. |
| | Examples include the request to change a |
| | proposed Event time or change the due date for a |
| | VTODO. |
| | |
| DECLINE- | Used by the "Organizer" to decline the proposed |
| COUNTER | counter-proprosal. |
+================+==================================================+
Group scheduling in iTIP is accomplished using the set of "request"
and "response" methods described above. The following table shows the
methods broken down by who can send them.
+================+==================================================+ +================+==================================================+
| Originator | Methods | | Originator | Methods |
|================+==================================================| |================+==================================================|
| Organizer | PUBLISH, REQUEST, ADD, CANCEL, DECLINECOUNTER | | Organizer | PUBLISH, REQUEST, ADD, CANCEL, DECLINECOUNTER |
| | | | | |
| Attendee | REPLY, REFRESH, COUNTER | | Attendee | REPLY, REFRESH, COUNTER |
| | REQUEST only when delegating | | | REQUEST only when delegating |
+================+==================================================+ +================+==================================================+
Note that for some calendar component types, the allowable methods are a Note that for some calendar component types, the allowable methods
subset of the above set. are a subset of the above set.
2 Interoperability Models 2 Interoperability Models
There are two distinct protocols relevant to interoperability: an There are two distinct protocols relevant to interoperability: an
"Application Protocol" and a "Transport Protocol". The Application "Application Protocol" and a "Transport Protocol". The Application
Protocol defines the content of the iCalendar objects sent between Protocol defines the content of the iCalendar objects sent between
sender and receiver to accomplish the scheduling transactions listed sender and receiver to accomplish the scheduling transactions listed
above. The Transport Protocol defines how the iCalendar objects are sent above. The Transport Protocol defines how the iCalendar objects are
between the sender and receiver. This document focuses on the sent between the sender and receiver. This document focuses on the
Application Protocol. Binding documents such as [iMIP] focus on the Application Protocol. Binding documents such as [iMIP] focus on the
Transport Protocol. Transport Protocol.
The connection between Sender and Receiver in the diagram below refers The connection between Sender and Receiver in the diagram below
to the Application Protocol. The iCalendar objects passed from the refers to the Application Protocol. The iCalendar objects passed from
Sender to the Receiver are presented in Section 3, Application Protocol the Sender to the Receiver are presented in Section 3, Application
Elements. Protocol Elements.
+----------+ +----------+ +----------+ +----------+
| | iTIP | | | | iTIP | |
| Sender |<-------------------->| Receiver | | Sender |<-------------------->| Receiver |
| | | | | | | |
+----------+ +----------+ +----------+ +----------+
There are several variations of this diagram in which the Sender and There are several variations of this diagram in which the Sender and
Receiver take on various roles of a "Calendar User Agent" (CUA) or a Receiver take on various roles of a "Calendar User Agent" (CUA) or a
"Calendar Service" (CS). These variants are detailed in the Model "Calendar Service" (CS).
document [ICMS].
The architecture of iTIP is depicted in the diagram below. An The architecture of iTIP is depicted in the diagram below. An
application written to this specification may work with bindings for the application written to this specification may work with bindings for
store-and-forward transport, the real time transport, or both. Also note the store-and-forward transport, the real time transport, or both.
that iTIP could be bound to other transports. Also note that iTIP could be bound to other transports.
+------------------------------------------+ +------------------------------------------+
| iTIP | | iTIP |
+------------------------------------------+ +------------------------------------------+
|Real-time | Store-and-Fwd | Other | |Real-time | Store-and-Fwd | Other |
|Transport | Transport | Transports... | |Transport | Transport | Transports... |
+------------------------------------------+ +------------------------------------------+
2.1 Application Protocol 2.1 Application Protocol
In the iTIP model, a calendar entry is created and managed by an In the iTIP model, a calendar entry is created and managed by an
"Organizer". The "Organizer" interacts with other CUs by sending one or "Organizer". The "Organizer" interacts with other CUs by sending one
more of the iTIP messages listed above. "Attendees" use the "REPLY" or more of the iTIP messages listed above. "Attendees" use the
method to communicate their status. "Attendees" do not make direct "REPLY" method to communicate their status. "Attendees" do not make
changes to the master calendar entry. They can, however, use the direct changes to the master calendar entry. They can, however, use
"COUNTER" method to suggest changes to the "Organizer". In any case, the the "COUNTER" method to suggest changes to the "Organizer". In any
"Organizer" has complete control over the master calendar entry. case, the "Organizer" has complete control over the master calendar
entry.
2.1.1 Calendar Entry State 2.1.1 Calendar Entry State
There are two distinct states relevant to calendar entries: the overall There are two distinct states relevant to calendar entries: the
state of the entry and the state associated with an "Attendee" to that overall state of the entry and the state associated with an
entry. "Attendee" to that entry.
The state of an entry is defined by the "STATUS" property and is The state of an entry is defined by the "STATUS" property and is
controlled by the "Organizer." There is no default value for the controlled by the "Organizer." There is no default value for the
"STATUS" property. The "Organizer" sets the "STATUS" property to the "STATUS" property. The "Organizer" sets the "STATUS" property to the
appropriate value for each calendar entry. appropriate value for each calendar entry.
The state of a particular "Attendee" relative to an entry is defined by The state of a particular "Attendee" relative to an entry is defined
the "partstat" parameter in the "ATTENDEE" property for each "Attendee". by the "partstat" parameter in the "ATTENDEE" property for each
When an "Organizer" issues the initial entry, "Attendee" status is "Attendee". When an "Organizer" issues the initial entry, "Attendee"
unknown. The "Organizer" specifies this by setting the "partstat" status is unknown. The "Organizer" specifies this by setting the
parameter to "NEEDS-ACTION". Each "Attendee" modifies their "ATTENDEE" "partstat" parameter to "NEEDS-ACTION". Each "Attendee" modifies
property "partstat" parameter to an appropriate value as part of a their "ATTENDEE" property "partstat" parameter to an appropriate
"REPLY" message sent back to the "Organizer". value as part of a "REPLY" message sent back to the "Organizer".
2.1.2 Delegation 2.1.2 Delegation
Delegation is defined as the process by which an "Attendee" grants Delegation is defined as the process by which an "Attendee" grants
another CU (or several CUs) the right to attend on their behalf. The another CU (or several CUs) the right to attend on their behalf. The
"Organizer" is made aware of this change because the delegating "Organizer" is made aware of this change because the delegating
"Attendee" informs the "Organizer". These steps are detailed in the "Attendee" informs the "Organizer". These steps are detailed in the
REQUEST method section. REQUEST method section.
2.1.3 Acting on Behalf of other Calendar Users 2.1.3 Acting on Behalf of other Calendar Users
In many organizations one user will act on behalf of another to organize In many organizations one user will act on behalf of another to
and/or respond to meeting requests. ITIP provides two mechanisms that organize and/or respond to meeting requests. ITIP provides two
support these activities. mechanisms that support these activities.
First, the "Organizer" is treated as a special entity, separate from First, the "Organizer" is treated as a special entity, separate from
"Attendees". All responses from "Attendees" flow to the "Organizer", "Attendees". All responses from "Attendees" flow to the "Organizer",
making it easy to separate a calendar user organizing a meeting from making it easy to separate a calendar user organizing a meeting from
calendar users attending the meeting. Additionally, iCalendar provides calendar users attending the meeting. Additionally, iCalendar
descriptive roles for each "Attendee". For instance, a role of "chair" provides descriptive roles for each "Attendee". For instance, a role
may be ascribed to one or more "Attendees". The "chair" and the of "chair" may be ascribed to one or more "Attendees". The "chair"
"Organizer" may or may not be the same calendar user. This maps well to and the "Organizer" may or may not be the same calendar user. This
scenarios where an assistant may manage meeting logistics for another maps well to scenarios where an assistant may manage meeting
individual who chairs a meeting. logistics for another individual who chairs a meeting.
Second, a "sent-by" parameter may be specified in either the "Organizer" Second, a "sent-by" parameter may be specified in either the
or "Attendee" properties. When specified, the "sent-by" parameter "Organizer" or "Attendee" properties. When specified, the "sent-by"
indicates that the responding CU acted on behalf of the specified parameter indicates that the responding CU acted on behalf of the
"Attendee" or "Organizer". specified "Attendee" or "Organizer".
2.1.4 Component Revisions 2.1.4 Component Revisions
The "SEQUENCE" property is used by the "Organizer" to indicate revisions The "SEQUENCE" property is used by the "Organizer" to indicate
to the calendar component. The rules for incrementing the "SEQUENCE" revisions to the calendar component. The rules for incrementing the
number are defined in [iCAL]. For clarity, these rules are paraphrased "SEQUENCE" number are defined in [iCAL]. For clarity, these rules are
here in terms of how they are applied in [iTIP]. For a given "UID" in a paraphrased here in terms of how they are applied in [iTIP]. For a
calendar component: given "UID" in a calendar component:
. For the "PUBLISH" and "REQUEST" methods, the "SEQUENCE" property . For the "PUBLISH" and "REQUEST" methods, the "SEQUENCE" property
value is incremented according to the rules defined in [iCAL]. value is incremented according to the rules defined in [iCAL].
. The "SEQUENCE" property value MUST be incremented each time the . The "SEQUENCE" property value MUST be incremented each time the
"Organizer" uses the "ADD" or "CANCEL" methods. "Organizer" uses the "ADD" or "CANCEL" methods.
. The "SEQUENCE" property value MUST NOT be incremented when using . The "SEQUENCE" property value MUST NOT be incremented when using
"REPLY", "REFRESH", "COUNTER", "DECLINECOUNTER", or when sending a "REPLY", "REFRESH", "COUNTER", "DECLINECOUNTER", or when sending a
delegation "REQUEST". delegation "REQUEST".
In some circumstances the "Organizer" may not have received responses to In some circumstances the "Organizer" may not have received responses
the final revision sent out. In this situation, the "Organizer" may wish to the final revision sent out. In this situation, the "Organizer"
to send an update "REQUEST", and set "RSVP=TRUE" for all "Attendees", so may wish to send an update "REQUEST", and set "RSVP=TRUE" for all
that current responses can be collected. "Attendees", so that current responses can be collected.
The value of the "SEQUENCE" property contained in a response from an The value of the "SEQUENCE" property contained in a response from an
"Attendee" may not always match the "Organizer's" revision. "Attendee" may not always match the "Organizer's" revision.
Implementations may choose to have the CUA indicate to the CU that the Implementations may choose to have the CUA indicate to the CU that
response is to an entry that has been revised and allow the CU to decide the response is to an entry that has been revised and allow the CU to
whether or not to accept the response. decide whether or not to accept the response.
2.1.5 Message Sequencing 2.1.5 Message Sequencing
CUAs that handle the [iTIP] application protocol must often correlate a CUAs that handle the [iTIP] application protocol must often correlate
component in a calendar store with a component received in the [iTIP] a component in a calendar store with a component received in the
message. For example, an event may be updated with a later revision of [iTIP] message. For example, an event may be updated with a later
the same event. To accomplish this, a CUA must correlate the version of revision of the same event. To accomplish this, a CUA must correlate
the event already in its calendar store with the version sent in the the version of the event already in its calendar store with the
[iTIP] message. In addition to this correlation, there are several version sent in the [iTIP] message. In addition to this correlation,
factors that can cause [iTIP] messages to arrive in an unexpected order. there are several factors that can cause [iTIP] messages to arrive in
That is, an "Organizer" could receive a reply to an earlier revision of an unexpected order. That is, an "Organizer" could receive a reply
a component AFTER receiving a reply to a later revision. to an earlier revision of a component AFTER receiving a reply to a
later revision.
To maximize interoperability and to handle messages that arrive in an To maximize interoperability and to handle messages that arrive in an
unexpected order, use the following rules: unexpected order, use the following rules:
1. The primary key for referencing a particular iCalendar component is 1. The primary key for referencing a particular iCalendar component
the "UID" property value. To reference an instance of a recurring is the "UID" property value. To reference an instance of a
component, the primary key is composed of the "UID" and the recurring component, the primary key is composed of the "UID" and
"RECURRENCE-ID" properties. the "RECURRENCE-ID" properties.
2. The secondary key for referencing a component is the "SEQUENCE" 2. The secondary key for referencing a component is the "SEQUENCE"
property value. For components where the "UID" is the same, the property value. For components where the "UID" is the same, the
component with the highest numeric value for the "SEQUENCE" property component with the highest numeric value for the "SEQUENCE"
obsoletes all other revisions of the component with lower values. property obsoletes all other revisions of the component with
lower values.
3. "Attendees" send "REPLY" messages to the "Organizer". For replies 3. "Attendees" send "REPLY" messages to the "Organizer". For
where the "UID" property value is the same, the value of the replies where the "UID" property value is the same, the value of
"SEQUENCE" property indicates the revision of the component to which the "SEQUENCE" property indicates the revision of the component
the "Attendee" is replying. The reply with the highest numeric value to which the "Attendee" is replying. The reply with the highest
for the "SEQUENCE" property obsoletes all other replies with lower numeric value for the "SEQUENCE" property obsoletes all other
values. replies with lower values.
4. In situations where the "UID" and "SEQUENCE" properties match, the 4. In situations where the "UID" and "SEQUENCE" properties match,
"DTSTAMP" property is used as the tie-breaker. The component with the the "DTSTAMP" property is used as the tie-breaker. The component
latest "DTSTAMP" overrides all others. Similarly, for "Attendee" with the latest "DTSTAMP" overrides all others. Similarly, for
responses where the "UID" property values match and the "SEQUENCE" "Attendee" responses where the "UID" property values match and
property values match, the response with the latest "DTSTAMP" the "SEQUENCE" property values match, the response with the
overrides all others. latest "DTSTAMP" overrides all others.
Hence, CUAs must persist the following component properties: "UID", Hence, CUAs must persist the following component properties: "UID",
"RECURRENCE-ID", "SEQUENCE", and "DTSTAMP". Furthermore, for each "RECURRENCE-ID", "SEQUENCE", and "DTSTAMP". Furthermore, for each
"ATTENDEE" property of a component CUAs must persist the "SEQUENCE" and "ATTENDEE" property of a component CUAs must persist the "SEQUENCE"
"DTSTAMP" property values associated with the "Attendee's" response. and "DTSTAMP" property values associated with the "Attendee's"
response.
3 Application Protocol Elements 3 Application Protocol Elements
ITIP messages are "text/calendar" MIME entities that contain calendaring ITIP messages are "text/calendar" MIME entities that contain
and scheduling information. The particular type of [iCAL] message is calendaring and scheduling information. The particular type of [iCAL]
referred to as the "method type". Each method type is identified by a message is referred to as the "method type". Each method type is
"METHOD" property specified as part of the "text/calendar" content type. identified by a "METHOD" property specified as part of the
The table below shows various combinations of calendar components and "text/calendar" content type. The table below shows various
the method types that this memo supports. combinations of calendar components and the method types that this
memo supports.
+=================================================+ +=================================================+
| | VEVENT | VTODO | VJOURNAL | VFREEBUSY | | | VEVENT | VTODO | VJOURNAL | VFREEBUSY |
|=================================================| |=================================================|
|Publish | Yes | Yes | Yes | Yes | |Publish | Yes | Yes | Yes | Yes |
|Request | Yes | Yes | No | Yes | |Request | Yes | Yes | No | Yes |
|Refresh | Yes | Yes | No | No | |Refresh | Yes | Yes | No | No |
|Cancel | Yes | Yes | Yes | No | |Cancel | Yes | Yes | Yes | No |
|Add | Yes | Yes | Yes | No | |Add | Yes | Yes | Yes | No |
|Reply | Yes | Yes | No | Yes | |Reply | Yes | Yes | No | Yes |
|Counter | Yes | Yes | No | No | |Counter | Yes | Yes | No | No |
|Decline- | | | | | |Decline- | | | | |
|Counter | Yes | Yes | No | No | |Counter | Yes | Yes | No | No |
+=================================================+ +=================================================+
Each method type is defined in terms of its associated components and Each method type is defined in terms of its associated components and
properties. Some components and properties are required, some are properties. Some components and properties are required, some are
optional and others are excluded. The restrictions are expressed in this optional and others are excluded. The restrictions are expressed in
document using a simple "restriction table". The first column indicates this document using a simple "restriction table". The first column
the name of a component or property. Properties of the iCalendar object indicates the name of a component or property. Properties of the
are not indented. Properties of a component are indented. The second iCalendar object are not indented. Properties of a component are
column contains "MUST" if the component or property must be present, indented. The second column contains "MUST" if the component or
"MAY" if the component or property is optional, and "NOT" if the property must be present, "MAY" if the component or property is
component or property must not be present. Entries in the second column optional, and "NOT" if the component or property must not be present.
sometimes contain comments for further clarification. Entries in the second column sometimes contain comments for further
clarification.
3.1 Common Component Restriction Tables 3.1 Common Component Restriction Tables
The restriction table below applies to properties of the iCalendar The restriction table below applies to properties of the iCalendar
object. That is, the properties at the outermost scope. The presence object. That is, the properties at the outermost scope. The presence
column uses the following values to assert whether a property is column uses the following values to assert whether a property is
required, is optional and the number of times it may appear in the required, is optional and the number of times it may appear in the
iCalendar object. iCalendar object.
Presence Value Description Presence Value Description
1 One instance MUST be present --------------------------------------------------------------
1+ At least one instance MUST be present 1 One instance MUST be present
0 Instances of this property Must NOT be present 1+ At least one instance MUST be present
0+ Multiple instances MAY be present 0 Instances of this property Must NOT be present
0 or 1 Up to 1 instance of this property MAY be present 0+ Multiple instances MAY be present
0 or 1 Up to 1 instance of this property MAY be present
---------------------------------------------------------------
The tables also call out "X-PROPERTY" and "X-COMPONENT" to show where The tables also call out "X-PROPERTY" and "X-COMPONENT" to show
vendor-specific properties and components can appear. The tables do not where vendor-specific properties and components can appear. The
lay out the restrictions of property parameters. Those restrictions are tables do not lay out the restrictions of property parameters. Those
defined in [iCAL]. restrictions are defined in [iCAL].
Component/Property Presence Component/Property Presence
CALSCALE 0 or 1 ------------------- ----------------------------------------------
PRODID 1 CALSCALE 0 or 1
VERSION 1 Value MUST be "2.0" PRODID 1
X-PROPERTY 0+ VERSION 1 Value MUST be "2.0"
X-PROPERTY 0+
DateTime values MAY refer to a "VTIMEZONE" component. The property DateTime values MAY refer to a "VTIMEZONE" component. The property
restrictions in the table below apply to any "VTIMEZONE" component in an restrictions in the table below apply to any "VTIMEZONE" component in
ITIP message. an ITIP message.
Component/Property Presence Component/Property Presence
VTIMEZONE 0+ MUST be present if any date/time refers to ------------------- ----------------------------------------------
timezone VTIMEZONE 0+ MUST be present if any date/time refers
DAYLIGHT 0+ MUST be one or more of either STANDARD or to timezone
DAYLIGHT DAYLIGHT 0+ MUST be one or more of either STANDARD or
COMMENT 0 or 1 DAYLIGHT
DTSTART 1 MUST be local time format COMMENT 0 or 1
RDATE 0+ if present RRULE MUST NOT be present DTSTART 1 MUST be local time format
RRULE 0+ if present RDATE MUST NOT be present RDATE 0+ if present RRULE MUST NOT be present
TZNAME 0 or 1 RRULE 0+ if present RDATE MUST NOT be present
TZOFFSET 1 TZNAME 0 or 1
TZOFFSETFROM 1 TZOFFSET 1
TZOFFSETTO 1 TZOFFSETFROM 1
X-PROPERTY 0+ TZOFFSETTO 1
LAST-MODIFIED 0 or 1 X-PROPERTY 0+
STANDARD 0+ MUST be one or more of either STANDARD or LAST-MODIFIED 0 or 1
DAYLIGHT STANDARD 0+ MUST be one or more of either STANDARD or
COMMENT 0 or 1 DAYLIGHT
DTSTART 1 MUST be local time format COMMENT 0 or 1
RDATE 0+ if present RRULE MUST NOT be present DTSTART 1 MUST be local time format
RRULE 0+ if present RDATE MUST NOT be present RDATE 0+ if present RRULE MUST NOT be present
TZNAME 0 or 1 RRULE 0+ if present RDATE MUST NOT be present
TZOFFSETFROM 1 TZNAME 0 or 1
TZOFFSETTO 1 TZOFFSETFROM 1
X-PROPERTY 0+ TZOFFSETTO 1
TZID 1 X-PROPERTY 0+
TZURL 0 or 1 TZID 1
X-PROPERTY 0+ TZURL 0 or 1
X-PROPERTY 0+
The property restrictions in the table below apply to any "VALARM" The property restrictions in the table below apply to any "VALARM"
component in an ITIP message. component in an ITIP message.
Component/Property Presence Component/Property Presence
VALARM 0+ ------------------- ----------------------------------------------
ACTION 1 VALARM 0+
ATTACH 0+ ACTION 1
DESCRIPTION 0 or 1 ATTACH 0+
DURATION 0 or 1 if present REPEAT MUST be present DESCRIPTION 0 or 1
REPEAT 0 or 1 if present DURATION MUST be present DURATION 0 or 1 if present REPEAT MUST be present
SUMMARY 0 or 1 REPEAT 0 or 1 if present DURATION MUST be present
TRIGGER 1 SUMMARY 0 or 1
X-PROPERTY 0+ TRIGGER 1
X-PROPERTY 0+
3.2 Methods for VEVENT Calendar Components 3.2 Methods for VEVENT Calendar Components
This section defines the property set restrictions for the method types This section defines the property set restrictions for the method
that are applicable to the "VEVENT" calendar component. Each method is types that are applicable to the "VEVENT" calendar component. Each
defined using a table that clarifies the property constraints that method is defined using a table that clarifies the property
define the particular method. constraints that define the particular method.
The following summarizes the methods that are defined for the "VEVENT" The following summarizes the methods that are defined for the
calendar component. "VEVENT" calendar component.
+================+==================================================+ +================+==================================================+
| Method | Description | | Method | Description |
|================+==================================================| |================+==================================================|
| PUBLISH | Post notification of an event. Used primarily as | | PUBLISH | Post notification of an event. Used primarily as |
| | a method of advertising the existence of an | | | a method of advertising the existence of an |
| | event. | | | event. |
| | | | | |
| REQUEST | Make a request for an event. This is an explicit | | REQUEST | Make a request for an event. This is an explicit |
| | invitation to one or more "Attendees". Event | | | invitation to one or more "Attendees". Event |
| | Requests are also used to update or change an | | | Requests are also used to update or change an |
| | existing event. Clients that cannot handle | | | existing event. Clients that cannot handle |
| | REQUEST may degrade the event to view it as an | | | REQUEST may degrade the event to view it as an |
| | PUBLISH. | | | PUBLISH. |
| | | | | |
| REPLY | Reply to an event request. Clients may set their | | REPLY | Reply to an event request. Clients may set their |
| | status ("partstat") to ACCEPTED, DECLINED, | | | status ("partstat") to ACCEPTED, DECLINED, |
| | TENTATIVE, or DELEGATED. | | | TENTATIVE, or DELEGATED. |
| | | | | |
| ADD | Add one or more instances to an existing event. | | ADD | Add one or more instances to an existing event. |
| | | | | |
| CANCEL | Cancel one or more instances of an existing | | CANCEL | Cancel one or more instances of an existing |
| | event. | | | event. |
| | | | | |
| REFRESH | A request is sent to an "Organizer" by an | | REFRESH | A request is sent to an "Organizer" by an |
| | "Attendee" asking for the latest version of an | | | "Attendee" asking for the latest version of an |
| | event to be resent to the requester. | | | event to be resent to the requester. |
| | | | | |
| COUNTER | Counter a REQUEST with an alternative proposal, | | COUNTER | Counter a REQUEST with an alternative proposal, |
| | Sent by an "Attendee" to the "Organizer". | | | Sent by an "Attendee" to the "Organizer". |
| | | | | |
| DECLINECOUNTER | Decline a counter proposal. Sent to an | | DECLINECOUNTER | Decline a counter proposal. Sent to an |
| | "Attendee" by the "Organizer". | | | "Attendee" by the "Organizer". |
+================+==================================================+ +================+==================================================+
3.2.1 PUBLISH 3.2.1 PUBLISH
The "PUBLISH" method in a "VEVENT" calendar component is an unsolicited The "PUBLISH" method in a "VEVENT" calendar component is an
posting of an iCalendar object. Any CU may add published components to unsolicited posting of an iCalendar object. Any CU may add published
their calendar. The "Organizer" MUST be present in a published iCalendar components to their calendar. The "Organizer" MUST be present in a
component. "Attendees" MUST NOT be present. Its expected usage is for published iCalendar component. "Attendees" MUST NOT be present. Its
encapsulating an arbitrary event as an iCalendar object. The "Organizer" expected usage is for encapsulating an arbitrary event as an
may subsequently update (with another "PUBLISH" method), add instances iCalendar object. The "Organizer" may subsequently update (with
to (with an "ADD" method), or cancel (with a "CANCEL" method) a another "PUBLISH" method), add instances to (with an "ADD" method),
previously published "VEVENT" calendar component. or cancel (with a "CANCEL" method) a previously published "VEVENT"
calendar component.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST equal "PUBLISH" METHOD 1 MUST equal "PUBLISH"
VEVENT 1+ VEVENT 1+
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
SUMMARY 1 Can be null. SUMMARY 1 Can be null.
UID 1 UID 1
RECURRENCE-ID 0 or 1 only if referring to an instance of a RECURRENCE-ID 0 or 1 only if referring to an instance of a
recurring calendar component. Otherwise it recurring calendar component. Otherwise
MUST NOT be present. it MUST NOT be present.
SEQUENCE 0 or 1 MUST be present if value is greater than 0, SEQUENCE 0 or 1 MUST be present if value is greater than
MAY be present if 0 0, MAY be present if 0
ATTACH 0+ ATTACH 0+
CATEGORIES 0 or 1 This property may contain a list of values CATEGORIES 0 or 1 This property may contain a list of
values
CLASS 0 or 1 CLASS 0 or 1
COMMENT 0 or 1 COMMENT 0 or 1
CONTACT 0+ CONTACT 0+
CREATED 0 or 1 CREATED 0 or 1
DESCRIPTION 0 or 1 Can be null DESCRIPTION 0 or 1 Can be null
DTEND 0 or 1 if present DURATION MUST NOT be present DTEND 0 or 1 if present DURATION MUST NOT be present
DURATION 0 or 1 if present DTEND MUST NOT be present DURATION 0 or 1 if present DTEND MUST NOT be present
EXDATE 0+ EXDATE 0+
EXRULE 0+ EXRULE 0+
GEO 0 or 1 GEO 0 or 1
skipping to change at line 750 skipping to change at page 17, line 5
URL 0 or 1 URL 0 or 1
X-PROPERTY 0+ X-PROPERTY 0+
ATTENDEE 0 ATTENDEE 0
REQUEST-STATUS 0 REQUEST-STATUS 0
VALARM 0+ VALARM 0+
VFREEBUSY 0 VFREEBUSY 0
VJOURNAL 0 VJOURNAL 0
VTODO 0 VTODO 0
VTIMEZONE 0+ MUST be present if any date/time refers to a VTIMEZONE 0+ MUST be present if any date/time refers to
timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
3.2.2 REQUEST 3.2.2 REQUEST
The "REQUEST" method in a "VEVENT" component provides the following The "REQUEST" method in a "VEVENT" component provides the following
scheduling functions: scheduling functions:
. Invite "Attendees" to an event; . Invite "Attendees" to an event;
. Reschedule an existing event; . Reschedule an existing event;
. Response to a REFRESH request; . Response to a REFRESH request;
. Update the details of an existing event, without rescheduling it; . Update the details of an existing event, without rescheduling it;
. Update the status of "Attendees" of an existing event, without . Update the status of "Attendees" of an existing event, without
rescheduling it; rescheduling it;
. Reconfirm an existing event, without rescheduling it; . Reconfirm an existing event, without rescheduling it;
. Forward a "VEVENT" to another uninvited CU. . Forward a "VEVENT" to another uninvited CU.
. For an existing "VEVENT" calendar component, delegate the role of . For an existing "VEVENT" calendar component, delegate the role of
"Attendee" to another CU; "Attendee" to another CU;
. For an existing "VEVENT" calendar component, changing the role of . For an existing "VEVENT" calendar component, changing the role of
"Organizer" to another CU. "Organizer" to another CU.
The "Organizer" originates the "REQUEST". The recipients of the The "Organizer" originates the "REQUEST". The recipients of the
"REQUEST" method are the CUs invited to the event, the "Attendees". "REQUEST" method are the CUs invited to the event, the "Attendees".
"Attendees" use the "REPLY" method to convey attendance status to the "Attendees" use the "REPLY" method to convey attendance status to the
"Organizer". "Organizer".
The "UID" and "SEQUENCE" properties are used to distinguish the various The "UID" and "SEQUENCE" properties are used to distinguish the
uses of the "REQUEST" method. If the "UID" property value in the various uses of the "REQUEST" method. If the "UID" property value in
"REQUEST" is not found on the recipient's calendar, then the "REQUEST" the "REQUEST" is not found on the recipient's calendar, then the
is for a new "VEVENT" calendar component. If the "UID" property value is "REQUEST" is for a new "VEVENT" calendar component. If the "UID"
found on the recipient's calendar, then the "REQUEST" is for a property value is found on the recipient's calendar, then the
rescheduling, an update, or a reconfirm of the "VEVENT" calendar "REQUEST" is for a rescheduling, an update, or a reconfirm of the
component. "VEVENT" calendar component.
For the "REQUEST" method, multiple "VEVENT" components in a single For the "REQUEST" method, multiple "VEVENT" components in a single
iCalendar object are only permitted when for components with the same iCalendar object are only permitted when for components with the same
"UID" property. That is, a series of recurring events may have "UID" property. That is, a series of recurring events may have
instance-specific information. In this case, multiple "VEVENT" instance-specific information. In this case, multiple "VEVENT"
components are needed to express the entire series. components are needed to express the entire series.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
----------------------------------------------------------------- -----------------------------------------------------------------
METHOD 1 MUST be "REQUEST" METHOD 1 MUST be "REQUEST"
VEVENT 1+ All components MUST have the same UID VEVENT 1+ All components MUST have the same UID
ATTENDEE 1+ ATTENDEE 1+
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
SEQUENCE 0 or 1 MUST be present if value is greater than 0, SEQUENCE 0 or 1 MUST be present if value is greater than 0,
skipping to change at line 839 skipping to change at page 19, line 4
RRULE 0+ RRULE 0+
STATUS 0 or 1 MAY be one of TENTATIVE/CONFIRMED STATUS 0 or 1 MAY be one of TENTATIVE/CONFIRMED
TRANSP 0 or 1 TRANSP 0 or 1
URL 0 or 1 URL 0 or 1
X-PROPERTY 0+ X-PROPERTY 0+
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VFREEBUSY 0 VFREEBUSY 0
VJOURNAL 0 VJOURNAL 0
VTODO 0 VTODO 0
3.2.2.1 Rescheduling an Event 3.2.2.1 Rescheduling an Event
The "REQUEST" method may be used to reschedule an event. A rescheduled The "REQUEST" method may be used to reschedule an event. A
event involves a change to the existing event in terms of its time or rescheduled event involves a change to the existing event in terms of
recurrence intervals and possibly the location or description. If the its time or recurrence intervals and possibly the location or
recipient CUA of a "REQUEST" method finds that the "UID" property value description. If the recipient CUA of a "REQUEST" method finds that
already exists on the calendar, but that the "SEQUENCE" (or "DTSTAMP") the "UID" property value already exists on the calendar, but that the
property value in the "REQUEST" method is greater than the value for the "SEQUENCE" (or "DTSTAMP") property value in the "REQUEST" method is
existing event, then the "REQUEST" method describes a rescheduling of greater than the value for the existing event, then the "REQUEST"
the event. method describes a rescheduling of the event.
3.2.2.2 Updating or Reconfirmation of an Event 3.2.2.2 Updating or Reconfirmation of an Event
The "REQUEST" method may be used to update or reconfirm an event. An The "REQUEST" method may be used to update or reconfirm an event. An
update to an existing event does not involve changes to the time or update to an existing event does not involve changes to the time or
recurrence intervals, and might not involve a change to the location or recurrence intervals, and might not involve a change to the location
description for the event. If the recipient CUA of a "REQUEST" method or description for the event. If the recipient CUA of a "REQUEST"
finds that the "UID" property value already exists on the calendar and method finds that the "UID" property value already exists on the
that the "SEQUENCE" property value in the "REQUEST" is the same as the calendar and that the "SEQUENCE" property value in the "REQUEST" is
value for the existing event, then the "REQUEST" method describes an the same as the value for the existing event, then the "REQUEST"
update of the event details, but no rescheduling of the event. method describes an update of the event details, but no rescheduling
of the event.
The update "REQUEST" method is the appropriate response to a "REFRESH" The update "REQUEST" method is the appropriate response to a
method sent from an "Attendee" to the "Organizer" of an event. "REFRESH" method sent from an "Attendee" to the "Organizer" of an
event.
The "Organizer" of an event may also send unsolicited "REQUEST" methods. The "Organizer" of an event may also send unsolicited "REQUEST"
The unsolicited "REQUEST" methods may be used to update the details of methods. The unsolicited "REQUEST" methods may be used to update the
the event without rescheduling it, to update the "partstat" parameter of details of the event without rescheduling it, to update the
"Attendees", or to reconfirm the event. "partstat" parameter of "Attendees", or to reconfirm the event.
3.2.2.3 Delegating an Event to another CU 3.2.2.3 Delegating an Event to another CU
Some calendar and scheduling systems allow "Attendees" to delegate their Some calendar and scheduling systems allow "Attendees" to delegate
presence at an event to another calendar user. ITIP supports this their presence at an event to another calendar user. ITIP supports
concept using the following workflow. Any "Attendee" may delegate their this concept using the following workflow. Any "Attendee" may
right to participate in a calendar VEVENT to another CU. The implication delegate their right to participate in a calendar VEVENT to another
is that the delegate participates in lieu of the original "Attendee"; CU. The implication is that the delegate participates in lieu of the
NOT in addition to the "Attendee". The delegator MUST notify the original "Attendee"; NOT in addition to the "Attendee". The delegator
"Organizer" of this action using the steps outlined below. MUST notify the "Organizer" of this action using the steps outlined
Implementations may support or restrict delegation as they see fit. For below. Implementations may support or restrict delegation as they
instance, some implementations may restrict a delegate from delegating a see fit. For instance, some implementations may restrict a delegate
"REQUEST" to another CU. from delegating a "REQUEST" to another CU.
The "Delegator" of an event forwards the existing "REQUEST" to the The "Delegator" of an event forwards the existing "REQUEST" to the
"Delegate". The "REQUEST" method MUST include an "ATTENDEE" property "Delegate". The "REQUEST" method MUST include an "ATTENDEE" property
with the calendar address of the "Delegate". The "Delegator" MUST also with the calendar address of the "Delegate". The "Delegator" MUST
send a "REPLY" method to the "Organizer" with the "Delegator's" also send a "REPLY" method to the "Organizer" with the "Delegator's"
"ATTENDEE" property "partstat" parameter value set to "delegated". In "ATTENDEE" property "partstat" parameter value set to "delegated". In
addition, the "delegated-to" parameter MUST be included with the addition, the "delegated-to" parameter MUST be included with the
calendar address of the "Delegate". calendar address of the "Delegate".
In response to the request, the "Delegate" MUST send a "REPLY" method to In response to the request, the "Delegate" MUST send a "REPLY" method
the "Organizer" and optionally, to the "Delegator". The "REPLY" method " to the "Organizer" and optionally, to the "Delegator". The "REPLY"
SHOULD include the "ATTENDEE" property with the "delegated-from" method " SHOULD include the "ATTENDEE" property with the "delegated-
parameter value of the "Delegator's" calendar address. from" parameter value of the "Delegator's" calendar address.
The "Delegator" may continue to receive updates to the event even though The "Delegator" may continue to receive updates to the event even
they will not be attending. This is accomplished by the "Delegator" though they will not be attending. This is accomplished by the
setting their "role" attribute to " NON-PARTICIPANT" in the "REPLY" to "Delegator" setting their "role" attribute to " NON-PARTICIPANT" in
the "Organizer" the "REPLY" to the "Organizer"
3.2.2.4 Changing the Organizer 3.2.2.4 Changing the Organizer
The situation may arise where the "Organizer" of a VEVENT is no longer The situation may arise where the "Organizer" of a VEVENT is no
able to perform the "Organizer" role and abdicates without passing on longer able to perform the "Organizer" role and abdicates without
the "Organizer" role to someone else. When this occurs the "Attendees" passing on the "Organizer" role to someone else. When this occurs the
of the VEVENT may use out-of-band mechanisms to communicate the "Attendees" of the VEVENT may use out-of-band mechanisms to
situation and agree upon a new "Organizer". The new "Organizer" should communicate the situation and agree upon a new "Organizer". The new
then send out a new "REQUEST" with a modified version of the VEVENT in "Organizer" should then send out a new "REQUEST" with a modified
which the "SEQUENCE" number has been incremented and value of the version of the VEVENT in which the "SEQUENCE" number has been
"ORGANIZER" property has been changed to the calendar address of the new incremented and value of the "ORGANIZER" property has been changed to
"Organizer". the calendar address of the new "Organizer".
3.2.2.5 Sending on Behalf of the Organizer 3.2.2.5 Sending on Behalf of the Organizer
There are a number of scenarios that support the need for a calendar There are a number of scenarios that support the need for a calendar
user to act on behalf of the "Organizer" without explicit role changing. user to act on behalf of the "Organizer" without explicit role
This might be the case if the CU designated as "Organizer" was sick or changing. This might be the case if the CU designated as "Organizer"
unable to perform duties associated with that function. In these cases was sick or unable to perform duties associated with that function.
iTIP supports the notion of one CU acting on behalf of another. Using In these cases iTIP supports the notion of one CU acting on behalf of
the "sent-by" parameter, a calendar user could send an updated "VEVENT" another. Using the "sent-by" parameter, a calendar user could send an
REQUEST. In the case where one CU sends on behalf of another CU, the updated "VEVENT" REQUEST. In the case where one CU sends on behalf of
"Attendee" responses are still directed back towards the CU designated another CU, the "Attendee" responses are still directed back towards
as "Organizer". the CU designated as "Organizer".
3.2.2.6 Forwarding to An Uninvited CU 3.2.2.6 Forwarding to An Uninvited CU
An "Attendee" invited to an event may invite another uninvited CU to the An "Attendee" invited to an event may invite another uninvited CU to
event. The invited "Attendee" accomplishes this by forwarding the the event. The invited "Attendee" accomplishes this by forwarding the
original "REQUEST" method to the uninvited CU. The "Organizer" decides original "REQUEST" method to the uninvited CU. The "Organizer"
whether or not the uninvited CU is added to the attendee list. If the decides whether or not the uninvited CU is added to the attendee
"Organizer" decides not to add the uninvited CU no further action is list. If the "Organizer" decides not to add the uninvited CU no
required, however the "Organizer" MAY send the uninvited CU a "CANCEL" further action is required, however the "Organizer" MAY send the
message. If the "Organizer" decides to add an uninvited CU, a new uninvited CU a "CANCEL" message. If the "Organizer" decides to add
"ATTENDEE" property is added for the uninvited CU with its property an uninvited CU, a new "ATTENDEE" property is added for the uninvited
parameters set as the "Organizer" deems appropriate. When forwarding a CU with its property parameters set as the "Organizer" deems
"REQUEST" to another CU, the forwarding "Attendee" MUST NOT make changes appropriate. When forwarding a "REQUEST" to another CU, the
to the VEVENT property set. forwarding "Attendee" MUST NOT make changes to the VEVENT property
set.
3.2.2.7 Updating Attendee Status 3.2.2.7 Updating Attendee Status
The "Organizer" of an event may also request updated status from one or The "Organizer" of an event may also request updated status from one
more "Attendees. The "Organizer" sends a "REQUEST" method to the or more "Attendees. The "Organizer" sends a "REQUEST" method to the
"Attendee" and sets the "ATTENDEE;RSVP=TRUE" property parameter. The "Attendee" and sets the "ATTENDEE;RSVP=TRUE" property parameter. The
"SEQUENCE" property for the event is not changed from its previous "SEQUENCE" property for the event is not changed from its previous
value. A recipient will determine that the only change in the "REQUEST" value. A recipient will determine that the only change in the
is that their "RSVP" property parameter indicates a request for updated "REQUEST" is that their "RSVP" property parameter indicates a request
status. The recipient SHOULD respond with a "REPLY" method indicating for updated status. The recipient SHOULD respond with a "REPLY"
their current status with respect to the "REQUEST". method indicating their current status with respect to the "REQUEST".
3.2.3 REPLY 3.2.3 REPLY
The "REPLY" method in a "VEVENT" calendar component is used to respond The "REPLY" method in a "VEVENT" calendar component is used to
(e.g., accept or decline) to a "REQUEST" or to reply to a delegation respond (e.g., accept or decline) to a "REQUEST" or to reply to a
"REQUEST". When used to provide a delegation response, the "Delegator" delegation "REQUEST". When used to provide a delegation response, the
SHOULD include the calendar address of the "Delegate" on the "delegated- "Delegator" SHOULD include the calendar address of the "Delegate" on
to" property parameter of the "Delegator's" "ATTENDEE" property. The the "delegated-to" property parameter of the "Delegator's" "ATTENDEE"
"Delegate" SHOULD include the calendar address of the "Delegator" on the property. The "Delegate" SHOULD include the calendar address of the
"delegated-from" property parameter of the "Delegate's" "ATTENDEE" "Delegator" on the "delegated-from" property parameter of the
property. "Delegate's" "ATTENDEE" property.
The "REPLY" method may also be used to respond to an unsuccessful The "REPLY" method may also be used to respond to an unsuccessful
"REQUEST" method. Depending on the value of the "REQUEST-STATUS" "REQUEST" method. Depending on the value of the "REQUEST-STATUS"
property no scheduling action may have been performed. property no scheduling action may have been performed.
The "Organizer" of an event may receive the "REPLY" method from a CU not The "Organizer" of an event may receive the "REPLY" method from a CU
in the original "REQUEST". For example, a "REPLY" may be received from a not in the original "REQUEST". For example, a "REPLY" may be received
"Delegate" to an event. In addition, the "REPLY" method may be received from a "Delegate" to an event. In addition, the "REPLY" method may be
from an unknown CU (a "Party Crasher"). This uninvited "Attendee" may be received from an unknown CU (a "Party Crasher"). This uninvited
accepted, or the "Organizer" may cancel the event for the uninvited "Attendee" may be accepted, or the "Organizer" may cancel the event
"Attendee" by sending a "CANCEL" method to the uninvited "Attendee". for the uninvited "Attendee" by sending a "CANCEL" method to the
uninvited "Attendee".
An "Attendee" can include a message to the "Organizer" using the An "Attendee" can include a message to the "Organizer" using the
"COMMENT" property. For example, if the user indicates tentative "COMMENT" property. For example, if the user indicates tentative
acceptance and wants to let the "Organizer" know why, the reason can be acceptance and wants to let the "Organizer" know why, the reason can
expressed in the "COMMENT" property value. be expressed in the "COMMENT" property value.
The "Organizer" may also receive a "REPLY" from one CU on behalf of The "Organizer" may also receive a "REPLY" from one CU on behalf of
another. Like the scenario enumerated above for the "Organizer", another. Like the scenario enumerated above for the "Organizer",
"Attendees" may have another CU respond on their behalf. This is done "Attendees" may have another CU respond on their behalf. This is done
using the "sent-by" parameter. using the "sent-by" parameter.
The optional properties listed in the table below (those listed as "0+" The optional properties listed in the table below (those listed as
or "0 or 1") MUST NOT be changed from those of the original request. If "0+" or "0 or 1") MUST NOT be changed from those of the original
property changes are desired the COUNTER message must be used. request. If property changes are desired the COUNTER message must be
used.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "REPLY" METHOD 1 MUST be "REPLY"
VEVENT 1+ All components MUST have the same UID VEVENT 1+ All components MUST have the same UID
ATTENDEE 1 MUST be the address of the Attendee ATTENDEE 1 MUST be the address of the Attendee
replying. replying.
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
RECURRENCE-ID 0 or 1 only if referring to an instance of a RECURRENCE-ID 0 or 1 only if referring to an instance of a
recurring calendar component. Otherwise it recurring calendar component. Otherwise
must NOT be present. it must NOT be present.
UID 1 MUST be the UID of the original REQUEST UID 1 MUST be the UID of the original REQUEST
SEQUENCE 0 or 1 MUST if non-zero, MUST be the sequence SEQUENCE 0 or 1 MUST if non-zero, MUST be the sequence
number of the original REQUEST. MAY be number of the original REQUEST. MAY be
present if 0. present if 0.
ATTACH 0+ ATTACH 0+
CATEGORIES 0 or 1 This property may contain a list of values CATEGORIES 0 or 1 This property may contain a list of values
CLASS 0 or 1 CLASS 0 or 1
COMMENT 0 or 1 COMMENT 0 or 1
skipping to change at line 1038 skipping to change at page 23, line 13
RELATED-TO 0+ RELATED-TO 0+
RESOURCES 0 or 1 This property MAY contain a list of values RESOURCES 0 or 1 This property MAY contain a list of values
REQUEST-STATUS 0+ REQUEST-STATUS 0+
RRULE 0+ RRULE 0+
STATUS 0 or 1 STATUS 0 or 1
SUMMARY 0 or 1 SUMMARY 0 or 1
TRANSP 0 or 1 TRANSP 0 or 1
URL 0 or 1 URL 0 or 1
X-PROPERTY 0+ X-PROPERTY 0+
VTIMEZONE 0 or 1 MUST be present if any date/time refers to a VTIMEZONE 0 or 1 MUST be present if any date/time refers
timezone to a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VFREEBUSY 0 VFREEBUSY 0
VJOURNAL 0 VJOURNAL 0
VTODO 0 VTODO 0
3.2.4 ADD 3.2.4 ADD
The "ADD" method in a "VEVENT" calendar component is used to add one or The "ADD" method in a "VEVENT" calendar component is used to add one
more instances to an existing "VEVENT". Unlike the "REQUEST" method, or more instances to an existing "VEVENT". Unlike the "REQUEST"
when using issuing an "ADD" method, the "Organizer" does not send the method, when using issuing an "ADD" method, the "Organizer" does not
full "VEVENT" description; only the new instance(s). The "ADD" method is send the full "VEVENT" description; only the new instance(s). The
especially useful if there are instance-specific properties to be "ADD" method is especially useful if there are instance-specific
preserved in a recurring "VEVENT". For instance, an "Organizer" may have properties to be preserved in a recurring "VEVENT". For instance, an
originally scheduled a weekly Thursday meeting. At some point, several "Organizer" may have originally scheduled a weekly Thursday meeting.
instances changed. Location or start time may have changed, or some At some point, several instances changed. Location or start time may
instances may have unique "DESCRIPTION" properties. The "ADD" method have changed, or some instances may have unique "DESCRIPTION"
allows the "Organizer" to add new instances to an existing event using a properties. The "ADD" method allows the "Organizer" to add new
single ITIP message without redefining the entire recurring pattern. instances to an existing event using a single ITIP message without
redefining the entire recurring pattern.
The "UID" must be that of the existing event. If the "UID" property The "UID" must be that of the existing event. If the "UID" property
value in the "ADD" is not found on the recipient's calendar, then the value in the "ADD" is not found on the recipient's calendar, then the
recipient SHOULD send a "REFRESH" to the "Organizer" in order to be recipient SHOULD send a "REFRESH" to the "Organizer" in order to be
updated with the latest version of the "VEVENT". If an "Attendee" updated with the latest version of the "VEVENT". If an "Attendee"
implementation does not support the "ADD" method it should respond with implementation does not support the "ADD" method it should respond
a "REQUEST-STATUS" value of 3.14 and ask for a "REFRESH". with a "REQUEST-STATUS" value of 3.14 and ask for a "REFRESH".
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "ADD" METHOD 1 MUST be "ADD"
VEVENT 1 VEVENT 1
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
SEQUENCE 1 MUST be greater than 0 SEQUENCE 1 MUST be greater than 0
SUMMARY 1 Can be null SUMMARY 1 Can be null
skipping to change at line 1118 skipping to change at page 25, line 4
REQUEST-STATUS 0 REQUEST-STATUS 0
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VFREEBUSY 0 VFREEBUSY 0
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
3.2.5 CANCEL
3.2.5 CANCEL The "CANCEL" method in a "VEVENT" calendar component is used to send
a cancellation notice of an existing event request to the
The "CANCEL" method in a "VEVENT" calendar component is used to send a "Attendees". The message is sent by the "Organizer" of the event. For
cancellation notice of an existing event request to the "Attendees". The a recurring event, either the whole event or instances of an event
message is sent by the "Organizer" of the event. For a recurring event, may be cancelled. To cancel the complete range of recurring event,
either the whole event or instances of an event may be cancelled. To the "UID" property value for the event MUST be specified and a
cancel the complete range of recurring event, the "UID" property value "RECURRENCE-ID" MUST NOT be specified in the "CANCEL" method. In
for the event MUST be specified and a "RECURRENCE-ID" MUST NOT be order to cancel an individual instance of the event, the
specified in the "CANCEL" method. In order to cancel an individual "RECURRENCE-ID" property value for the event MUST be specified in the
instance of the event, the "RECURRENCE-ID" property value for the event "CANCEL" method.
MUST be specified in the "CANCEL" method.
There are two options for canceling a sequence of instances of a There are two options for canceling a sequence of instances of a
recurring "VEVENT" calendar component: recurring "VEVENT" calendar component:
(a) the "RECURRENCE-ID" property for an instance in the sequence MUST be (a) the "RECURRENCE-ID" property for an instance in the sequence MUST
specified with the "RANGE" property parameter value of THISANDPRIOR be specified with the "RANGE" property parameter value of
(or THISANDFUTURE) to indicate cancellation of the specified THISANDPRIOR (or THISANDFUTURE) to indicate cancellation of the
"VEVENT" calendar component and all instances before (or after); or specified "VEVENT" calendar component and all instances before
(or after); or
(b) individual recurrence instances may be cancelled by specifying (b) individual recurrence instances may be cancelled by specifying
multiple "RECURRENCE-ID" properties corresponding to the instances to multiple "RECURRENCE-ID" properties corresponding to the
be cancelled. instances to be cancelled.
When a "VEVENT" is cancelled, the "SEQUENCE" property value MUST be When a "VEVENT" is cancelled, the "SEQUENCE" property value MUST be
incremented. incremented.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "CANCEL" METHOD 1 MUST be "CANCEL"
VEVENT 1+ All must have the same UID VEVENT 1+ All must have the same UID
ATTENDEE 0+ MUST include all "Attendees" being removed ATTENDEE 0+ MUST include all "Attendees" being removed
the event. MUST include all "Attendees" if the event. MUST include all "Attendees" if
the entire event is cancelled. the entire event is cancelled.
DTSTAMP 1 DTSTAMP 1
skipping to change at line 1179 skipping to change at page 26, line 18
DTEND 0 or 1 if present DURATION MUST NOT be present DTEND 0 or 1 if present DURATION MUST NOT be present
DTSTART 0 or 1 DTSTART 0 or 1
DURATION 0 or 1 if present DTEND MUST NOT be present DURATION 0 or 1 if present DTEND MUST NOT be present
EXDATE 0+ EXDATE 0+
EXRULE 0+ EXRULE 0+
GEO 0 or 1 GEO 0 or 1
LAST-MODIFIED 0 or 1 LAST-MODIFIED 0 or 1
LOCATION 0 or 1 LOCATION 0 or 1
PRIORITY 0 or 1 PRIORITY 0 or 1
RDATE 0+ RDATE 0+
RECURRENCE-ID 0 or 1 MUST be present if referring to one or more RECURRENCE-ID 0 or 1 MUST be present if referring to one or
or more recurring instances. Otherwise it more or more recurring instances.
MUST NOT be present Otherwise it MUST NOT be present
RELATED-TO 0+ RELATED-TO 0+
RESOURCES 0 or 1 RESOURCES 0 or 1
RRULE 0+ RRULE 0+
STATUS 0 or 1 MUST be set to CANCELLED. If uninviting STATUS 0 or 1 MUST be set to CANCELLED. If uninviting
specific "Attendees" then MUST NOT be specific "Attendees" then MUST NOT be
included. included.
SUMMARY 0 or 1 SUMMARY 0 or 1
TRANSP 0 or 1 TRANSP 0 or 1
URL 0 or 1 URL 0 or 1
X-PROPERTY 0+ X-PROPERTY 0+
skipping to change at line 1203 skipping to change at page 26, line 42
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VFREEBUSY 0 VFREEBUSY 0
VALARM 0 VALARM 0
3.2.6 REFRESH 3.2.6 REFRESH
The "REFRESH" method in a "VEVENT" calendar component is used by The "REFRESH" method in a "VEVENT" calendar component is used by
"Attendees" of an existing event to request an updated description from "Attendees" of an existing event to request an updated description
the event "Organizer". The "REFRESH" method must specify the "UID" from the event "Organizer". The "REFRESH" method must specify the
property of the event to update. A recurrence instance of an event may "UID" property of the event to update. A recurrence instance of an
be requested by specifying the "RECURRENCE-ID" property corresponding to event may be requested by specifying the "RECURRENCE-ID" property
the associated event. The "Organizer" responds with the latest corresponding to the associated event. The "Organizer" responds with
description and version of the event. the latest description and version of the event.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "REFRESH" METHOD 1 MUST be "REFRESH"
VEVENT 1 VEVENT 1
ATTENDEE 1 MUST be the address of requestor ATTENDEE 1 MUST be the address of requestor
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
UID 1 MUST be the UID associated with original UID 1 MUST be the UID associated with original
REQUEST REQUEST
COMMENT 0 or 1 COMMENT 0 or 1
RECURRENCE-ID 0 or 1 MUST only if referring to an instance of a RECURRENCE-ID 0 or 1 MUST only if referring to an instance of a
recurring calendar component. Otherwise it recurring calendar component. Otherwise
must NOT be present. it must NOT be present.
X-PROPERTY 0+ X-PROPERTY 0+
ATTACH 0 ATTACH 0
CATEGORIES 0 CATEGORIES 0
CLASS 0 CLASS 0
CONTACT 0 CONTACT 0
CREATED 0 CREATED 0
DESCRIPTION 0 DESCRIPTION 0
DTEND 0 DTEND 0
DTSTART 0 DTSTART 0
skipping to change at line 1266 skipping to change at page 28, line 9
URL 0 URL 0
X-COMPONENT 0+ X-COMPONENT 0+
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VFREEBUSY 0 VFREEBUSY 0
VTIMEZONE 0 VTIMEZONE 0
VALARM 0 VALARM 0
3.2.7 COUNTER 3.2.7 COUNTER
The "COUNTER" method for a "VEVENT" calendar component is used by an The "COUNTER" method for a "VEVENT" calendar component is used by an
"Attendee" of an existing event to submit to the "Organizer" a counter "Attendee" of an existing event to submit to the "Organizer" a
proposal to the event description. The "Attendee" sends this message to counter proposal to the event description. The "Attendee" sends this
the "Organizer" of the event. message to the "Organizer" of the event.
The counter proposal is an iCalendar object consisting of a VEVENT The counter proposal is an iCalendar object consisting of a VEVENT
calendar component describing the complete description of the alternate calendar component describing the complete description of the
event. alternate event.
The "Organizer" rejects the counter proposal by sending the "Attendee" a The "Organizer" rejects the counter proposal by sending the
VEVENT "DECLINECOUNTER" method. The "Organizer" accepts the counter "Attendee" a VEVENT "DECLINECOUNTER" method. The "Organizer" accepts
proposal by rescheduling the event as described in section 3.2.2.1 the counter proposal by rescheduling the event as described in
Rescheduling an Event. section 3.2.2.1 Rescheduling an Event.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "COUNTER" METHOD 1 MUST be "COUNTER"
VEVENT 1 VEVENT 1
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 MUST be the "Organizer" of the original ORGANIZER 1 MUST be the "Organizer" of the original
event event
skipping to change at line 1340 skipping to change at page 29, line 35
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VFREEBUSY 0 VFREEBUSY 0
3.2.8 DECLINECOUNTER 3.2.8 DECLINECOUNTER
The "DECLINECOUNTER" method in a "VEVENT" calendar component is used by The "DECLINECOUNTER" method in a "VEVENT" calendar component is used
the "Organizer" of an event to reject a counter proposal submitted by an by the "Organizer" of an event to reject a counter proposal submitted
"Attendee". The "Organizer" must send the "DECLINECOUNTER" message to by an "Attendee". The "Organizer" must send the "DECLINECOUNTER"
the "Attendee" that sent the "COUNTER" method to the "Organizer". message to the "Attendee" that sent the "COUNTER" method to the
"Organizer".
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "DECLINECOUNTER" METHOD 1 MUST be "DECLINECOUNTER"
VEVENT 1 VEVENT 1
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
UID 1 MUST, same UID specified in original UID 1 MUST, same UID specified in original
REQUEST and subsequent COUNTER REQUEST and subsequent COUNTER
skipping to change at line 1399 skipping to change at page 31, line 4
SUMMARY 0 SUMMARY 0
TRANSP 0 TRANSP 0
URL 0 URL 0
X-COMPONENT 0+ X-COMPONENT 0+
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VFREEBUSY 0 VFREEBUSY 0
VTIMEZONE 0 VTIMEZONE 0
VALARM 0 VALARM 0
3.3 Methods For VFREEBUSY Components 3.3 Methods For VFREEBUSY Components
This section defines the property set for the methods that are This section defines the property set for the methods that are
applicable to the "VFREEBUSY" calendar component. Each of the methods is applicable to the "VFREEBUSY" calendar component. Each of the methods
defined using a restriction table. is defined using a restriction table.
This document only addresses the transfer of busy time information. This document only addresses the transfer of busy time information.
Applications desiring free time information MUST infer this from Applications desiring free time information MUST infer this from
available busy time information. available busy time information.
The busy time information within the iCalendar object MAY be grouped The busy time information within the iCalendar object MAY be grouped
into more than one "VFREEBUSY" calendar component. This capability into more than one "VFREEBUSY" calendar component. This capability
allows busy time periods to be grouped according to some common allows busy time periods to be grouped according to some common
periodicity, such as a calendar week, month, or year. In this case, each periodicity, such as a calendar week, month, or year. In this case,
"VFREEBUSY" calendar component MUST include the "ATTENDEE", "DTSTART" each "VFREEBUSY" calendar component MUST include the "ATTENDEE",
and "DTEND" properties in order to specify the source of the busy time "DTSTART" and "DTEND" properties in order to specify the source of
information and the date and time interval over which the busy time the busy time information and the date and time interval over which
information covers. the busy time information covers.
The "FREEBUSY" property value MAY include a list of values, separated by The "FREEBUSY" property value MAY include a list of values, separated
the COMMA character (ASCII decimal 44). Alternately, multiple busy time by the COMMA character ([US-ASCII] decimal 44). Alternately, multiple
periods MAY be specified with multiple instances of the "FREEBUSY" busy time periods MAY be specified with multiple instances of the
property. Both forms MUST be supported by implementations conforming to "FREEBUSY" property. Both forms MUST be supported by implementations
this document. Duplicate busy time periods SHOULD NOT be specified in an conforming to this document. Duplicate busy time periods SHOULD NOT
iCalendar object. However, two different busy time periods MAY overlap. be specified in an iCalendar object. However, two different busy time
periods MAY overlap.
"FREEBUSY" properties should be sorted such that their values are in "FREEBUSY" properties should be sorted such that their values are in
ascending order, based on the start time, and then the end time, with ascending order, based on the start time, and then the end time, with
the earliest periods first. For example, today's busy time information the earliest periods first. For example, today's busy time
should appear after yesterday's busy time information. And the busy time information should appear after yesterday's busy time information.
for this half-hour should appear after the busy time for earlier today. And the busy time for this half-hour should appear after the busy
time for earlier today.
Since events may span a day boundary, free busy time period may also Since events may span a day boundary, free busy time period may also
span a day boundary. Individual "A" requests busy time from individuals span a day boundary. Individual "A" requests busy time from
"B", "C" and "D". Individual "B" and "C" replies with busy time data to individuals "B", "C" and "D". Individual "B" and "C" replies with
individual "A". Individual "D" does not support busy time requests and busy time data to individual "A". Individual "D" does not support
does not reply with any data. If the transport binding supports busy time requests and does not reply with any data. If the transport
exception messages, then individual "D" returns an "unsupported binding supports exception messages, then individual "D" returns an
capability" message to individual "A". "unsupported capability" message to individual "A4.34.3".
The following summarizes the methods that are defined for the The following summarizes the methods that are defined for the
"VFREEBUSY" calendar component. "VFREEBUSY" calendar component.
|================|==================================================| |================|==================================================|
| Method | Description | | Method | Description |
|================|==================================================| |================|==================================================|
| PUBLISH | Publish unsolicited busy time data. | | PUBLISH | Publish unsolicited busy time data. |
| REQUEST | Request busy time data. | | REQUEST | Request busy time data. |
| REPLY | Reply to a busy time request. | | REPLY | Reply to a busy time request. |
|================|==================================================| |================|==================================================|
3.3.1 PUBLISH 3.3.1 PUBLISH
The "PUBLISH" method in a "VFREEBUSY" calendar component is used to The "PUBLISH" method in a "VFREEBUSY" calendar component is used to
publish busy time data. The method may be sent from one CU to any other. publish busy time data. The method may be sent from one CU to any
The purpose of the method is to provide a message for sending other. The purpose of the method is to provide a message for sending
unsolicited busy time data. That is, the busy time data is not being unsolicited busy time data. That is, the busy time data is not being
sent as a "REPLY" to the receipt of a "REQUEST" method. sent as a "REPLY" to the receipt of a "REQUEST" method.
The "ATTENDEE" property must be specified in the busy time information. The "ATTENDEE" property must be specified in the busy time
The value is the CU address of the originator of the busy time information. The value is the CU address of the originator of the
information. busy time information.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "PUBLISH" METHOD 1 MUST be "PUBLISH"
VFREEBUSY 1+ VFREEBUSY 1+
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DateTime values must be in UTC DTSTART 1 DateTime values must be in UTC
DTEND 1 DateTime values must be in UTC DTEND 1 DateTime values must be in UTC
FREEBUSY 1+ MUST be BUSYTIME. Multiple instances are FREEBUSY 1+ MUST be BUSYTIME. Multiple instances are
skipping to change at line 1491 skipping to change at page 33, line 4
CONTACT 0+ CONTACT 0+
X-PROPERTY 0+ X-PROPERTY 0+
URL 0 or 1 Specifies busy time URL URL 0 or 1 Specifies busy time URL
ATTENDEE 0 ATTENDEE 0
DURATION 0 DURATION 0
REQUEST-STATUS 0 REQUEST-STATUS 0
UID 0 UID 0
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VTIMEZONE 0 VTIMEZONE 0
VALARM 0 VALARM 0
3.3.2 REQUEST 3.3.2 REQUEST
The "REQUEST" method in a "VFREEBUSY" calendar component is used to ask The "REQUEST" method in a "VFREEBUSY" calendar component is used to
a "Calendar User" for their busy time information. The request may be ask a "Calendar User" for their busy time information. The request
for a busy time information bounded by a specific date and time may be for a busy time information bounded by a specific date and
interval. time interval.
This message only permits requests for busy time information. The This message only permits requests for busy time information. The
message is sent from a "Calendar User" requesting the busy time message is sent from a "Calendar User" requesting the busy time
information to one or more intended recipients. information to one or more intended recipients.
If the originator of the "REQUEST" method is not authorized to make a If the originator of the "REQUEST" method is not authorized to make a
busy time request on the recipient's calendar system, then an exception busy time request on the recipient's calendar system, then an
message SHOULD be returned in a "REPLY" method, but no busy time data exception message SHOULD be returned in a "REPLY" method, but no busy
need be returned. time data need be returned.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "REQUEST" METHOD 1 MUST be "REQUEST"
VFREEBUSY 1 VFREEBUSY 1
ATTENDEE 1+ contain the address of the calendar store ATTENDEE 1+ contain the address of the calendar store
for which busy time is being requested.
DTEND 1 DateTime values must be in UTC DTEND 1 DateTime values must be in UTC
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DateTime values must be in UTC DTSTART 1 DateTime values must be in UTC
ORGANIZER 1 MUST be the request originator's address ORGANIZER 1 MUST be the request originator's address
UID 1 UID 1
COMMENT 0 or 1 COMMENT 0 or 1
CONTACT 0+ CONTACT 0+
X-PROPERTY 0+ X-PROPERTY 0+
FREEBUSY 0 FREEBUSY 0
skipping to change at line 1545 skipping to change at page 34, line 8
REQUEST-STATUS 0 REQUEST-STATUS 0
URL 0 URL 0
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VTIMEZONE 0 VTIMEZONE 0
3.3.3 REPLY 3.3.3 REPLY
The "REPLY" method in a "VFREEBUSY" calendar component is used to The "REPLY" method in a "VFREEBUSY" calendar component is used to
respond to a busy time request. The method is sent by the recipient of a respond to a busy time request. The method is sent by the recipient
busy time request to the originator of the request. of a busy time request to the originator of the request.
The "REPLY" method may also be used to respond to an unsuccessful The "REPLY" method may also be used to respond to an unsuccessful
"REQUEST" method. Depending on the "REQUEST-STATUS" value, no busy time "REQUEST" method. Depending on the "REQUEST-STATUS" value, no busy
information may be returned. time information may be returned.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "REPLY" METHOD 1 MUST be "REPLY"
VFREEBUSY 1 VFREEBUSY 1
ATTENDEE 1 (address of recipient replying) ATTENDEE 1 (address of recipient replying)
DTSTAMP 1 DTSTAMP 1
DTEND 1 DateTime values must be in UTC DTEND 1 DateTime values must be in UTC
DTSTART 1 DateTime values must be in UTC DTSTART 1 DateTime values must be in UTC
skipping to change at line 1588 skipping to change at page 35, line 4
X-PROPERTY 0+ X-PROPERTY 0+
DURATION 0 DURATION 0
SEQUENCE 0 SEQUENCE 0
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VTODO 0 VTODO 0
VJOURNAL 0 VJOURNAL 0
VTIMEZONE 0 VTIMEZONE 0
3.4 Methods For VTODO Components 3.4 Methods For VTODO Components
This section defines the property set for the methods that are This section defines the property set for the methods that are
applicable to the "VTODO" calendar component. Each of the methods is applicable to the "VTODO" calendar component. Each of the methods is
defined using a restriction table that specifies the property defined using a restriction table that specifies the property
constraints that define the particular method. constraints that define the particular method.
The following summarizes the methods that are defined for the "VTODO" The following summarizes the methods that are defined for the "VTODO"
calendar component. calendar component.
+================+==================================================+ +================+==================================================+
| Method | Description | | Method | Description |
|================+==================================================| |================+==================================================|
| PUBLISH | Post notification of a VTODO. Used primarily as | | PUBLISH | Post notification of a VTODO. Used primarily as |
| | a method of advertising the existence of a VTODO.| | | a method of advertising the existence of a VTODO.|
| | | | | |
| REQUEST | Assign a VTODO. This is an explicit assignment to| | REQUEST | Assign a VTODO. This is an explicit assignment to|
| | one or more Calendar Users. The REQUEST method | | | one or more Calendar Users. The REQUEST method |
| | is also used to update or change an existing | | | is also used to update or change an existing |
| | VTODO. Clients that cannot handle REQUEST MAY | | | VTODO. Clients that cannot handle REQUEST MAY |
| | degrade the method to treat it as a PUBLISH. | | | degrade the method to treat it as a PUBLISH. |
| | | | | |
| REPLY | Reply to a VTODO request. Attendees MAY set | | REPLY | Reply to a VTODO request. Attendees MAY set |
| | PARTSTAT to ACCEPTED, DECLINED, TENTATIVE, | | | PARTSTAT to ACCEPTED, DECLINED, TENTATIVE, |
| | DELEGATED, PARTIAL, and COMPLETED. | | | DELEGATED, PARTIAL, and COMPLETED. |
| | | | | |
| ADD | Add one or more instances to an existing to-do. | | ADD | Add one or more instances to an existing to-do. |
| | | | | |
| CANCEL | Cancel one or more instances of an existing | | CANCEL | Cancel one or more instances of an existing |
| | to-do. | | | to-do. |
| | | | | |
| REFRESH | A request sent to a VTODO Organizer asking for | | REFRESH | A request sent to a VTODO Organizer asking for |
| | the latest version of a VTODO. | | | the latest version of a VTODO. |
| | | | | |
| COUNTER | Counter a REQUEST with an alternative proposal. | | COUNTER | Counter a REQUEST with an alternative proposal. |
| | | | | |
| DECLINECOUNTER | Decline a counter proposal by an Attendee. | | DECLINECOUNTER | Decline a counter proposal by an Attendee. |
+================+==================================================+ +================+==================================================+
3.4.1 PUBLISH 3.4.1 PUBLISH
The "PUBLISH" method in a "VTODO" calendar component has no associated The "PUBLISH" method in a "VTODO" calendar component has no
response. It is simply a posting of an iCalendar object that maybe added associated response. It is simply a posting of an iCalendar object
to a calendar. It MUST have an "Organizer". It MUST NOT have that maybe added to a calendar. It MUST have an "Organizer". It MUST
"Attendees". Its expected usage is for encapsulating an arbitrary NOT have "Attendees". Its expected usage is for encapsulating an
"VTODO" calendar component as an iCalendar object. The "Organizer" MAY arbitrary "VTODO" calendar component as an iCalendar object. The
subsequently update (with another "PUBLISH" method), add instances to "Organizer" MAY subsequently update (with another "PUBLISH" method),
(with an "ADD" method), or cancel (with a "CANCEL" method) a previously add instances to (with an "ADD" method), or cancel (with a "CANCEL"
published "VTODO" calendar component. method) a previously published "VTODO" calendar component.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "PUBLISH" METHOD 1 MUST be "PUBLISH"
VTODO 1+ VTODO 1+
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
PRIORITY 1 PRIORITY 1
SEQUENCE 0 or 1 MUST be present if value is greater than SEQUENCE 0 or 1 MUST be present if value is greater than
skipping to change at line 1695 skipping to change at page 37, line 14
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
VALARM 0+ VALARM 0+
X-COMPONENT 0+ X-COMPONENT 0+
VFREEBUSY 0 VFREEBUSY 0
VEVENT 0 VEVENT 0
VJOURNAL 0 VJOURNAL 0
3.4.2 REQUEST 3.4.2 REQUEST
The "REQUEST" method in a "VTODO" calendar component provides the The "REQUEST" method in a "VTODO" calendar component provides the
following scheduling functions: following scheduling functions:
. Assign a to-do to one or more "Calendar Users"; . Assign a to-do to one or more "Calendar Users";
. Reschedule an existing to-do; . Reschedule an existing to-do;
. Update the details of an existing to-do, without rescheduling it; . Update the details of an existing to-do, without rescheduling
. Update the completion status of "Attendees" of an existing to-do, it;
without rescheduling it; . Update the completion status of "Attendees" of an existing
. Reconfirm an existing to-do, without rescheduling it; to-do, without rescheduling it;
. Delegate/reassign an existing to-do to another "Calendar User". . Reconfirm an existing to-do, without rescheduling it;
. Delegate/reassign an existing to-do to another "Calendar User".
The assigned "Calendar Users" are identified in the "VTODO" calendar The assigned "Calendar Users" are identified in the "VTODO" calendar
component by individual "ATTENDEE;ROLE=REQ-PARTICIPANT" property value component by individual "ATTENDEE;ROLE=REQ-PARTICIPANT" property
sequences. value sequences.
The originator of a "REQUEST" is the "Organizer" of the to-do. The The originator of a "REQUEST" is the "Organizer" of the to-do. The
recipient of a "REQUEST" is the "Calendar User" assigned the to-do. The recipient of a "REQUEST" is the "Calendar User" assigned the to-do.
"Attendee" uses the "REPLY" method to convey their acceptance and The "Attendee" uses the "REPLY" method to convey their acceptance and
completion status to the "Organizer" of the "REQUEST". completion status to the "Organizer" of the "REQUEST".
The "UID", "SEQUENCE", and "DTSTAMP" properties are used to distinguish The "UID", "SEQUENCE", and "DTSTAMP" properties are used to
the various uses of the "REQUEST" method. If the "UID" property value in distinguish the various uses of the "REQUEST" method. If the "UID"
the "REQUEST" is not found on the recipient's calendar, then the property value in the "REQUEST" is not found on the recipient's
"REQUEST" is for a new to-do. If the "UID" property value is found on calendar, then the "REQUEST" is for a new to-do. If the "UID"
the recipient's calendar, then the "REQUEST" is a rescheduling, an property value is found on the recipient's calendar, then the
update, or a reconfirm of the "VTODO" calendar object. "REQUEST" is a rescheduling, an update, or a reconfirm of the "VTODO"
calendar object.
If the "Organizer" of the "REQUEST" method is not authorized to make a If the "Organizer" of the "REQUEST" method is not authorized to make
to-do request on the "Attendee's" calendar system, then an exception is a to-do request on the "Attendee's" calendar system, then an
returned in the "REQUEST-STATUS" property of a subsequent "REPLY" exception is returned in the "REQUEST-STATUS" property of a
method, but no scheduling action is performed. subsequent "REPLY" method, but no scheduling action is performed.
For the "REQUEST" method, multiple "VTODO" components in a single For the "REQUEST" method, multiple "VTODO" components in a single
iCalendar object are only permitted when for components with the same iCalendar object are only permitted when for components with the same
"UID" property. That is, a series of recurring events may have "UID" property. That is, a series of recurring events may have
instance-specific information. In this case, multiple "VTODO" instance-specific information. In this case, multiple "VTODO"
components are needed to express the entire series. components are needed to express the entire series.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "REQUEST" METHOD 1 MUST be "REQUEST"
VTODO 1+ All components must have the same UID VTODO 1+ All components must have the same UID
ATTENDEE 1+ ATTENDEE 1+
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
PRIORITY 1 PRIORITY 1
skipping to change at line 1780 skipping to change at page 39, line 4
recurring calendar component. Otherwise recurring calendar component. Otherwise
it MUST NOT be present. it MUST NOT be present.
RELATED-TO 0+ RELATED-TO 0+
RESOURCES 0 or 1 This property may contain a list of RESOURCES 0 or 1 This property may contain a list of
values values
RRULE 0+ RRULE 0+
STATUS 0 or 1 MAY be one of COMPLETED/NEEDS ACTION/IN- STATUS 0 or 1 MAY be one of COMPLETED/NEEDS ACTION/IN-
PROCESS PROCESS
URL 0 or 1 URL 0 or 1
X-PROPERTY 0+ X-PROPERTY 0+
REQUEST-STATUS 0 REQUEST-STATUS 0
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers VTIMEZONE 0+ MUST be present if any date/time refers
to a timezone to a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
VJOURNAL 0 VJOURNAL 0
3.4.2.1 REQUEST for Rescheduling a VTODO 3.4.2.1 REQUEST for Rescheduling a VTODO
The "REQUEST" method may be used to reschedule a "VTODO" calendar The "REQUEST" method may be used to reschedule a "VTODO" calendar
component. component.
Rescheduling a "VTODO" calendar component involves a change to the Rescheduling a "VTODO" calendar component involves a change to the
existing "VTODO" calendar component in terms of its start or due time or existing "VTODO" calendar component in terms of its start or due time
recurrence intervals and possibly the description. If the recipient CUA or recurrence intervals and possibly the description. If the
of a "REQUEST" method finds that the "UID" property value already exists recipient CUA of a "REQUEST" method finds that the "UID" property
on the calendar, but that the "SEQUENCE" property value in the "REQUEST" value already exists on the calendar, but that the "SEQUENCE"
is greater than the value for the existing VTODO, then the "REQUEST" property value in the "REQUEST" is greater than the value for the
method describes a rescheduling of the "VTODO" calendar component. existing VTODO, then the "REQUEST" method describes a rescheduling of
the "VTODO" calendar component.
3.4.2.2 REQUEST for Update or Reconfirmation of a VTODO 3.4.2.2 REQUEST for Update or Reconfirmation of a VTODO
The "REQUEST" method may be used to update or reconfirm a "VTODO" The "REQUEST" method may be used to update or reconfirm a "VTODO"
calendar component. Reconfirmation is merely an update of "Attendee" calendar component. Reconfirmation is merely an update of "Attendee"
completion status or overall "VTODO" calendar component status. completion status or overall "VTODO" calendar component status.
An update to an existing "VTODO" calendar component does not involve An update to an existing "VTODO" calendar component does not involve
changes to the start or due time or recurrence intervals, nor generally changes to the start or due time or recurrence intervals, nor
to the description for the "VTODO" calendar component. If the recipient generally to the description for the "VTODO" calendar component. If
CUA of a "REQUEST" method finds that the "UID" property value already the recipient CUA of a "REQUEST" method finds that the "UID" property
exists on the calendar and that the "SEQUENCE" property value in the value already exists on the calendar and that the "SEQUENCE" property
"REQUEST" is the same as the value for the existing event, then the value in the "REQUEST" is the same as the value for the existing
"REQUEST" method describes an update of the "VTODO" calendar component event, then the "REQUEST" method describes an update of the "VTODO"
details, but not a rescheduling of the "VTODO" calendar component. calendar component details, but not a rescheduling of the "VTODO"
calendar component.
The update "REQUEST" is the appropriate response to a "REFRESH" method The update "REQUEST" is the appropriate response to a "REFRESH"
sent from an "Attendee" to the "Organizer" of a "VTODO" calendar method sent from an "Attendee" to the "Organizer" of a "VTODO"
component. calendar component.
Unsolicited "REQUEST" methods MAY be sent by the "Organizer" of a Unsolicited "REQUEST" methods MAY be sent by the "Organizer" of a
"VTODO" calendar component. The unsolicited "REQUEST" methods are used "VTODO" calendar component. The unsolicited "REQUEST" methods are
to update the details of the "VTODO" (without rescheduling it or used to update the details of the "VTODO" (without rescheduling it or
updating the completion status of "Attendees") or the "VTODO" calendar updating the completion status of "Attendees") or the "VTODO"
component itself (i.e., reconfirm the "VTODO"). calendar component itself (i.e., reconfirm the "VTODO").
3.4.2.3 REQUEST for Delegating a VTODO 3.4.2.3 REQUEST for Delegating a VTODO
The "REQUEST" method is also used to delegate or reassign ownership of a The "REQUEST" method is also used to delegate or reassign ownership
"VTODO" calendar component to another "Calendar User". For example, it of a "VTODO" calendar component to another "Calendar User". For
may be used to delegate an "Attendee's" role (i.e. "chair", or example, it may be used to delegate an "Attendee's" role (i.e.
"participant") for a "VTODO" calendar component. The "REQUEST" method is "chair", or "participant") for a "VTODO" calendar component. The
sent by one of the "Attendees" of an existing "VTODO" calendar component "REQUEST" method is sent by one of the "Attendees" of an existing
to some other individual. An "Attendee" of a "VTODO" calendar component
MUST NOT delegate to the "Organizer" of the event.
For the purposes of this description, the "Attendee" delegating the "VTODO" calendar component to some other individual. An "Attendee" of
"VTODO" calendar component is referred to as the "Delegator". The a "VTODO" calendar component MUST NOT delegate to the "Organizer" of
"Attendee" receiving the delegation request is referred to as the the event.
"Delegate".
The "Delegator" of a "VTODO" calendar component MUST forward the For the purposes of this description, the "Attendee" delegating the
existing "REQUEST" method for a "VTODO" calendar component to the "VTODO" calendar component is referred to as the "Delegator". The
"Delegate". The "VTODO" calendar component description MUST include the "Attendee" receiving the delegation request is referred to as the
"Delegator's" up-to-date "VTODO" calendar component definition. The "Delegate".
"REQUEST" method MUST also include an "ATTENDEE" property with the
calendar address of the "Delegate". The "Delegator" MUST also send a
"REPLY" method back to the "Organizer" with the "Delegator's" "Attendee"
property "partstat" parameter value set to "DELEGATED". In addition, the
"delegated-to" parameter MUST be included with the calendar address of
the "Delegate". A response to the delegation "REQUEST" is sent from the
"Delegate" to the "Organizer" and optionally, to the "Delegator". The
"REPLY" method from the "Delegate" SHOULD include the "ATTENDEE"
property with their calendar address and the "delegated-from" parameter
with the value of the "Delegator's" calendar address.
The delegation "REQUEST" method MUST assign a value for the "RSVP" The "Delegator" of a "VTODO" calendar component MUST forward the
property parameter associated with the "Delegator's" "Attendee" property existing "REQUEST" method for a "VTODO" calendar component to the
to that of the "Delegate's" "ATTENDEE" property. For example if the "Delegate". The "VTODO" calendar component description MUST include
"Delegator's" "ATTENDEE" property specifies "RSVP=TRUE", then the the "Delegator's" up-to-date "VTODO" calendar component definition.
"Delegate's" "ATTENDEE" property MUST specify "RSVP=TRUE". The "REQUEST" method MUST also include an "ATTENDEE" property with
the calendar address of the "Delegate". The "Delegator" MUST also
send a "REPLY" method back to the "Organizer" with the "Delegator's"
"Attendee" property "partstat" parameter value set to "DELEGATED". In
addition, the "delegated-to" parameter MUST be included with the
calendar address of the "Delegate". A response to the delegation
"REQUEST" is sent from the "Delegate" to the "Organizer" and
optionally, to the "Delegator". The "REPLY" method from the
"Delegate" SHOULD include the "ATTENDEE" property with their calendar
address and the "delegated-from" parameter with the value of the
"Delegator's" calendar address.
3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User The delegation "REQUEST" method MUST assign a value for the "RSVP"
property parameter associated with the "Delegator's" "Attendee"
property to that of the "Delegate's" "ATTENDEE" property. For example
if the "Delegator's" "ATTENDEE" property specifies "RSVP=TRUE", then
the "Delegate's" "ATTENDEE" property MUST specify "RSVP=TRUE".
An "Attendee" assigned a "VTODO" calendar component may send the "VTODO" 3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User
calendar component to another new CU, not previously associated with the
"VTODO" calendar component. The current "Attendee" assigned the "VTODO"
calendar component does this by forwarding the original "REQUEST" method
to the new CU. The new CU can send a "REPLY" to the "Organizer" of the
"VTODO" calendar component. The reply contains an "ATTENDEE" property
for the new CU.
The "Organizer" ultimately decides whether or not the new CU becomes An "Attendee" assigned a "VTODO" calendar component may send the
part of the to-do and is not obligated to do anything with a "REPLY" "VTODO" calendar component to another new CU, not previously
from a new (uninvited) CU. If the "Organizer" does not want the new CU associated with the "VTODO" calendar component. The current
to be part of the to-do, the new "ATTENDEE" property is not added to the "Attendee" assigned the "VTODO" calendar component does this by
"VTODO" calendar component. The "Organizer" MAY send the CU a "CANCEL" forwarding the original "REQUEST" method to the new CU. The new CU
message to indicate that they will not be added to the to-do. If the can send a "REPLY" to the "Organizer" of the "VTODO" calendar
"Organizer" decides to add the new CU, the new "ATTENDEE" property is component. The reply contains an "ATTENDEE" property for the new CU.
added to the "VTODO" calendar component. Furthermore, the "Organizer" is
free to change any "ATTENDEE" property parameter from the values
supplied by the new CU to something the "Organizer" considers
appropriate.
3.4.2.5 REQUEST Updated Attendee Status The "Organizer" ultimately decides whether or not the new CU becomes
part of the to-do and is not obligated to do anything with a "REPLY"
from a new (uninvited) CU. If the "Organizer" does not want the new
CU to be part of the to-do, the new "ATTENDEE" property is not added
to the "VTODO" calendar component. The "Organizer" MAY send the CU a
"CANCEL" message to indicate that they will not be added to the to-
do. If the "Organizer" decides to add the new CU, the new "ATTENDEE"
property is added to the "VTODO" calendar component. Furthermore, the
"Organizer" is free to change any "ATTENDEE" property parameter from
the values supplied by the new CU to something the "Organizer"
considers appropriate.
An "Organizer" of a "VTODO" may request an updated status from one or 3.4.2.5 REQUEST Updated Attendee Status
more "Attendees". The "Organizer" sends a "REQUEST" method to the
"Attendee" with the "ATTENDEE;RSVP=TRUE" property sequence. The
"SEQUENCE" property for the "VTODO" is not changed from its previous
value. A recipient determines that the only change in the "REQUEST" is
that their "RSVP" property parameter indicates a request for an updated
status. The recipient SHOULD respond with a "REPLY" method indicating
their current status with respect to the "REQUEST".
3.4.3 REPLY An "Organizer" of a "VTODO" may request an updated status from one or
more "Attendees". The "Organizer" sends a "REQUEST" method to the
"Attendee" with the "ATTENDEE;RSVP=TRUE" property sequence. The
"SEQUENCE" property for the "VTODO" is not changed from its previous
value. A recipient determines that the only change in the "REQUEST"
is that their "RSVP" property parameter indicates a request for an
updated status. The recipient SHOULD respond with a "REPLY" method
indicating their current status with respect to the "REQUEST".
The "REPLY" method in a "VTODO" calendar component is used to respond 3.4.3 REPLY
(e.g., accept or decline) to a request or to reply to a delegation
request. It is also used by an "Attendee" to update their completion
status. When used to provide a delegation response, the "Delegator" MUST
include the calendar address of the "Delegate" in the "delegated-to"
parameter of the "Delegator's" "ATTENDEE" property. The "Delegate" MUST
include the calendar address of the "Delegator" on the "delegated-from"
parameter of the "Delegate's" "ATTENDEE" property.
The "REPLY" method MAY also be used to respond to an unsuccessful The "REPLY" method in a "VTODO" calendar component is used to respond
"VTODO" calendar component "REQUEST" method. Depending on the "REQUEST- (e.g., accept or decline) to a request or to reply to a delegation
STATUS" value, no scheduling action may have been performed. request. It is also used by an "Attendee" to update their completion
status. When used to provide a delegation response, the "Delegator"
MUST include the calendar address of the "Delegate" in the
"delegated-to" parameter of the "Delegator's" "ATTENDEE" property.
The "Delegate" MUST include the calendar address of the "Delegator"
on the "delegated-from" parameter of the "Delegate's" "ATTENDEE"
property.
The "Organizer" of a "VTODO" calendar component MAY receive a "REPLY" The "REPLY" method MAY also be used to respond to an unsuccessful
method from a "Calendar User" not in the original "REQUEST". For "VTODO" calendar component "REQUEST" method. Depending on the
example, a "REPLY" method MAY be received from a "Delegate" of a "VTODO" "REQUEST-STATUS" value, no scheduling action may have been performed.
calendar component. In addition, the "REPLY" method MAY be received from
an unknown "Calendar User", having been forwarded the "REQUEST" by an
original "Attendee" of the "VTODO" calendar component. This uninvited
"Attendee" MAY be accepted, or the "Organizer" MAY cancel the "VTODO"
calendar component for the uninvited "Attendee" by sending them a
"CANCEL" method.
This method type is an iCalendar object that conforms to the following The "Organizer" of a "VTODO" calendar component MAY receive a "REPLY"
property constraints: method from a "Calendar User" not in the original "REQUEST". For
example, a "REPLY" method MAY be received from a "Delegate" of a
"VTODO" calendar component. In addition, the "REPLY" method MAY be
received from an unknown "Calendar User", having been forwarded the
"REQUEST" by an original "Attendee" of the "VTODO" calendar
component. This uninvited "Attendee" MAY be accepted, or the
"Organizer" MAY cancel the "VTODO" calendar component for the
uninvited "Attendee" by sending them a "CANCEL" method.
This method type is an iCalendar object that conforms to the
following property constraints:
Component/Property Presence Component/Property Presence
------------------- --------------------------------------------- ------------------- ---------------------------------------------
METHOD 1 MUST be "REPLY" METHOD 1 MUST be "REPLY"
VTODO 1+ All component MUST have the same UID VTODO 1+ All component MUST have the same UID
ATTENDEE 1+ ATTENDEE 1+
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
REQUEST-STATUS 1+ REQUEST-STATUS 1+
UID 1 MUST must be the address of the replying UID 1 MUST must be the address of the replying
skipping to change at line 1978 skipping to change at page 43, line 16
X-PROPERTY 0+ X-PROPERTY 0+
VTIMEZONE 0 or 1 MUST be present if any date/time refers to VTIMEZONE 0 or 1 MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
3.4.4 ADD 3.4.4 ADD
The "ADD" method in a "VTODO" calendar component is used to add one or The "ADD" method in a "VTODO" calendar component is used to add one
more instances to an existing to-do. or more instances to an existing to-do.
If the "UID" property value in the "ADD" is not found on the recipient's If the "UID" property value in the "ADD" is not found on the
calendar, then the recipient SHOULD send a "REFRESH" to the "Organizer" recipient's calendar, then the recipient SHOULD send a "REFRESH" to
in order to be updated with the latest version of the "VTODO". If an the "Organizer" in order to be updated with the latest version of the
"Attendee" implementation does not support the "ADD" method it should "VTODO". If an "Attendee" implementation does not support the "ADD"
respond with a "REQUEST-STATUS" value of 5.3 and ask for a "REFRESH". method it should respond with a "REQUEST-STATUS" value of 5.3 and ask
for a "REFRESH".
The "SEQUENCE" property value is incremented as the sequence of to-dos The "SEQUENCE" property value is incremented as the sequence of to-
has changed. dos has changed.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "ADD" METHOD 1 MUST be "ADD"
VTODO 1 VTODO 1
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
PRIORITY 1 PRIORITY 1
SEQUENCE 1 MUST be greater than 0 SEQUENCE 1 MUST be greater than 0
SUMMARY 1 Can be null. SUMMARY 1 Can be null.
skipping to change at line 2046 skipping to change at page 44, line 37
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers VTIMEZONE 0+ MUST be present if any date/time refers
to a timezone to a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VJOURNAL 0 VJOURNAL 0
VFREEBUSY 0 VFREEBUSY 0
3.4.5 CANCEL 3.4.5 CANCEL
The "CANCEL" method in a "VTODO" calendar component is used to send a The "CANCEL" method in a "VTODO" calendar component is used to send a
cancellation notice of an existing "VTODO" calendar request to the cancellation notice of an existing "VTODO" calendar request to the
"Attendees". The message is sent by the "Organizer" of a "VTODO" "Attendees". The message is sent by the "Organizer" of a "VTODO"
calendar component to the "Attendees" of the "VTODO" calendar component. calendar component to the "Attendees" of the "VTODO" calendar
For a recurring "VTODO" calendar component, either the whole "VTODO" component. For a recurring "VTODO" calendar component, either the
calendar component or instances of a "VTODO" calendar component may be whole "VTODO" calendar component or instances of a "VTODO" calendar
cancelled. To cancel the complete range of a recurring "VTODO" calendar component may be cancelled. To cancel the complete range of a
component, the "UID" property value for the "VTODO" calendar component recurring "VTODO" calendar component, the "UID" property value for
MUST be specified and a "RECURRENCE-ID" MUST NOT be specified in the the "VTODO" calendar component MUST be specified and a "RECURRENCE-
"CANCEL" method. In order to cancel an individual instance of a ID" MUST NOT be specified in the "CANCEL" method. In order to cancel
recurring "VTODO" calendar component, the "RECURRENCE-ID" property value an individual instance of a recurring "VTODO" calendar component, the
for the "VTODO" calendar component MUST be specified in the "CANCEL" "RECURRENCE-ID" property value for the "VTODO" calendar component
method. MUST be specified in the "CANCEL" method.
There are two options for canceling a sequence of instances of a There are two options for canceling a sequence of instances of a
recurring "VTODO" calendar component: recurring "VTODO" calendar component:
(a) the "RECURRENCE-ID" property for an instance in the sequence MUST be (a) the "RECURRENCE-ID" property for an instance in the sequence MUST
specified with the "RANGE" property parameter value of THISANDPRIOR be specified with the "RANGE" property parameter value of
(or THISANDFUTURE) to indicate cancellation of the specified "VTODO" THISANDPRIOR (or THISANDFUTURE) to indicate cancellation of the
calendar component and all instances before (or after); or specified "VTODO" calendar component and all instances before (or
after); or
(b) individual recurrence instances may be cancelled by specifying (b) individual recurrence instances may be cancelled by specifying
multiple "RECURRENCE-ID" properties corresponding to the instances to multiple "RECURRENCE-ID" properties corresponding to the
be cancelled. instances to be cancelled.
When a "VTODO" is cancelled, the "SEQUENCE" property value MUST be When a "VTODO" is cancelled, the "SEQUENCE" property value MUST be
incremented. incremented.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- --------------------------------------------- ------------------- ---------------------------------------------
METHOD 1 MUST be "CANCEL" METHOD 1 MUST be "CANCEL"
VTODO 1 VTODO 1
ATTENDEE 0+ include all "Attendees" being removed from ATTENDEE 0+ include all "Attendees" being removed from
the todo. MUST include all "Attendees" if the todo. MUST include all "Attendees" if
the entire todo is cancelled. the entire todo is cancelled.
UID 1 MUST echo original UID UID 1 MUST echo original UID
DTSTAMP 1 DTSTAMP 1
skipping to change at line 2134 skipping to change at page 46, line 29
REQUEST-STATUS 0 REQUEST-STATUS 0
VTIMEZONE 0 or 1 MUST be present if any date/time refers to VTIMEZONE 0 or 1 MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
3.4.6 REFRESH 3.4.6 REFRESH
The "REFRESH" method in a "VTODO" calendar component is used by The "REFRESH" method in a "VTODO" calendar component is used by
"Attendees" of an existing "VTODO" calendar component to request an "Attendees" of an existing "VTODO" calendar component to request an
updated description from the "Organizer" of the "VTODO" calendar updated description from the "Organizer" of the "VTODO" calendar
component. The "Organizer" of the "VTODO" calendar component MAY use component. The "Organizer" of the "VTODO" calendar component MAY use
this method to request an updated status from the "Attendees". The this method to request an updated status from the "Attendees". The
"REFRESH" method MUST specify the "UID" property corresponding to the "REFRESH" method MUST specify the "UID" property corresponding to the
"VTODO" calendar component needing update. "VTODO" calendar component needing update.
A refresh of a recurrence instance of a "VTODO" calendar component may A refresh of a recurrence instance of a "VTODO" calendar component
be requested by specifying the "RECURRENCE-ID" property corresponding to may be requested by specifying the "RECURRENCE-ID" property
the associated "VTODO" calendar component. The "Organizer" responds with corresponding to the associated "VTODO" calendar component. The
the latest description and rendition of the "VTODO" calendar component. "Organizer" responds with the latest description and rendition of the
In most cases this will be a REQUEST unless the "VTODO" has been "VTODO" calendar component. In most cases this will be a REQUEST
cancelled, in which case the ORGANIZER MUST send a "CANCEL". This method unless the "VTODO" has been cancelled, in which case the ORGANIZER
is intended to facilitate machine processing of requests for updates to MUST send a "CANCEL". This method is intended to facilitate machine
a "VTODO" calendar component. processing of requests for updates to a "VTODO" calendar component.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- --------------------------------------------- ------------------- ---------------------------------------------
METHOD 1 MUST be "REFRESH" METHOD 1 MUST be "REFRESH"
VTODO 1 VTODO 1
ATTENDEE 1 ATTENDEE 1
DTSTAMP 1 DTSTAMP 1
UID 1 MUST echo original UID UID 1 MUST echo original UID
RECURRENCE-ID 0 or 1 MUST only if referring to an instance of a RECURRENCE-ID 0 or 1 MUST only if referring to an instance of a
skipping to change at line 2202 skipping to change at page 48, line 4
SEQUENCE 0 SEQUENCE 0
STATUS 0 STATUS 0
URL 0 URL 0
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
VTIMEZONE 0 VTIMEZONE 0
3.4.7 COUNTER 3.4.7 COUNTER
The "COUNTER" method in a "VTODO" calendar component is used by an The "COUNTER" method in a "VTODO" calendar component is used by an
"Attendee" of an existing "VTODO" calendar component to submit to the "Attendee" of an existing "VTODO" calendar component to submit to the
"Organizer" a counter proposal for the "VTODO" calendar component. The "Organizer" a counter proposal for the "VTODO" calendar component.
"Attendee" sends the message to the "Organizer" of the "VTODO" calendar The "Attendee" sends the message to the "Organizer" of the "VTODO"
component. calendar component.
The counter proposal is an iCalendar object consisting of a "VTODO" The counter proposal is an iCalendar object consisting of a "VTODO"
calendar component describing the complete description of the alternate calendar component describing the complete description of the
"VTODO" calendar component. alternate "VTODO" calendar component.
The "Organizer" rejects the counter proposal by sending the "Attendee" a The "Organizer" rejects the counter proposal by sending the
"DECLINECOUNTER" method. The "Organizer" accepts the counter proposal by "Attendee" a "DECLINECOUNTER" method. The "Organizer" accepts the
sending all of the "Attendees" of the "VTODO" calendar component a counter proposal by sending all of the "Attendees" of the "VTODO"
"REQUEST" method rescheduling the "VTODO" calendar component. In the calendar component a "REQUEST" method rescheduling the "VTODO"
latter case, the "Organizer" SHOULD reset the individual "RSVP" property calendar component. In the latter case, the "Organizer" SHOULD reset
parameter values to TRUE on each "ATTENDEE" property; in order to force the individual "RSVP" property parameter values to TRUE on each
a response by the "Attendees". "ATTENDEE" property; in order to force a response by the "Attendees".
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "COUNTER" METHOD 1 MUST be "COUNTER"
VTODO 1 VTODO 1
ATTENDEE 1+ ATTENDEE 1+
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
PRIORITY 1 PRIORITY 1
SUMMARY 1 Can be null SUMMARY 1 Can be null
skipping to change at line 2253 skipping to change at page 49, line 7
DTSTART 0 or 1 DTSTART 0 or 1
DUE 0 or 1 If present DURATION MUST NOT be present DUE 0 or 1 If present DURATION MUST NOT be present
DURATION 0 or 1 If present DUE MUST NOT be present DURATION 0 or 1 If present DUE MUST NOT be present
EXDATE 0+ EXDATE 0+
EXRULE 0+ EXRULE 0+
GEO 0 or 1 GEO 0 or 1
LAST-MODIFIED 0 or 1 LAST-MODIFIED 0 or 1
LOCATION 0 or 1 LOCATION 0 or 1
PERCENT-COMPLETE 0 or 1 PERCENT-COMPLETE 0 or 1
RDATE 0+ RDATE 0+
RECURRENCE-ID 0 or 1 MUST only if referring to an instance of a RECURRENCE-ID 0 or 1 MUST only 3.5if referring to an instance of a
recurring calendar component. Otherwise it recurring calendar component. Otherwise it
MUST NOT be present. MUST NOT be present.
RELATED-TO 0+ RELATED-TO 0+
REQUEST-STATUS 0+ REQUEST-STATUS 0+
RESOURCES 0 or 1 This property MAY contain a list of values RESOURCES 0 or 1 This property MAY contain a list of values
RRULE 0 or 1 RRULE 0 or 1
SEQUENCE 0 or 1 MUST echo the original SEQUENCE number. SEQUENCE 0 or 1 MUST echo the original SEQUENCE number.
MUST be present if non-zero. MAY be present MUST be present if non-zero. MAY be present
if zero. if zero.
STATUS 0 or 1 MAY be one of COMPLETED/NEEDS ACTION/IN- STATUS 0 or 1 MAY be one of COMPLETED/NEEDS ACTION/IN-
skipping to change at line 2276 skipping to change at page 49, line 30
X-PROPERTY 0+ X-PROPERTY 0+
VALARM 0+ VALARM 0+
VTIMEZONE 0 or 1 MUST be present if any date/time refers to VTIMEZONE 0 or 1 MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
3.4.8 DECLINECOUNTER 3.4.8 DECLINECOUNTER
The "DECLINECOUNTER" method in a "VTODO" calendar component is used by The "DECLINECOUNTER" method in a "VTODO" calendar component is used
an "Organizer" of "VTODO" calendar component to reject a counter by an "Organizer" of "VTODO" calendar component to reject a counter
proposal offered by one of the "Attendees". The "Organizer" sends the proposal offered by one of the "Attendees". The "Organizer" sends the
message to the "Attendee" that sent the "COUNTER" method to the message to the "Attendee" that sent the "COUNTER" method to the
"Organizer". "Organizer".
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- --------------------------------------------- ------------------- ---------------------------------------------
METHOD 1 MUST be "DECLINECOUNTER" METHOD 1 MUST be "DECLINECOUNTER"
VTODO 1 VTODO 1
ATTENDEE 1+ MUST for all attendees ATTENDEE 1+ MUST for all attendees
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
SEQUENCE 1 MUST echo the original SEQUENCE number SEQUENCE 1 MUST echo the original SEQUENCE number
skipping to change at line 2338 skipping to change at page 50, line 44
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
3.5 Methods For VJOURNAL Components 3.5 Methods For VJOURNAL Components
This section defines the property set for the methods that are This section defines the property set for the methods that are
applicable to the "VJOURNAL" calendar component. applicable to the "VJOURNAL" calendar component.
The following summarizes the methods that are defined for the "VJOURNAL" The following summarizes the methods that are defined for the
calendar component. "VJOURNAL" calendar component.
+================+==================================================+ +================+==================================================+
| Method | Description | | Method | Description |
|================+==================================================| |================+==================================================|
| PUBLISH | Post a journal entry. Used primarily as a method | | PUBLISH | Post a journal entry. Used primarily as a method |
| | of advertising the existence of a journal entry. | | | of advertising the existence of a journal entry. |
| | | | | |
| ADD | Add one or more instances to an existing journal | | ADD | Add one or more instances to an existing journal |
| | entry. | | | entry. |
| | | | | |
| CANCEL | Cancel one or more instances of an existing | | CANCEL | Cancel one or more instances of an existing |
| | journal entry. | | | journal entry. |
+================+==================================================+ +================+==================================================+
3.5.1 PUBLISH
The "PUBLISH" method in a "VJOURNAL" calendar component has no 3.5.1 PUBLISH
associated response. It is simply a posting of an iCalendar object that
may be added to a calendar. It MUST have an "Organizer". It MUST NOT
have "Attendees". The expected usage is for encapsulating an arbitrary
journal entry as an iCalendar object. The "Organizer" MAY subsequently
update (with another "PUBLISH" method) or cancel (with a "CANCEL"
method) a previously published journal entry.
This method type is an iCalendar object that conforms to the following The "PUBLISH" method in a "VJOURNAL" calendar component has no
property constraints: associated response. It is simply a posting of an iCalendar object
that may be added to a calendar. It MUST have an "Organizer". It MUST
NOT have "Attendees". The expected usage is for encapsulating an
arbitrary journal entry as an iCalendar object. The "Organizer" MAY
subsequently update (with another "PUBLISH" method) or cancel (with a
"CANCEL" method) a previously published journal entry.
This method type is an iCalendar object that conforms to the
following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "PUBLISH" METHOD 1 MUST be "PUBLISH"
VJOURNAL 1+ VJOURNAL 1+
DESCRIPTION 1 Can be null. DESCRIPTION 1 Can be null.
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
UID 1 UID 1
skipping to change at line 2413 skipping to change at page 52, line 27
VALARM 0+ VALARM 0+
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
VTODO 0 VTODO 0
3.5.2 ADD 3.5.2 ADD
The "ADD" method in a "VJOURNAL" calendar component is used to add one The "ADD" method in a "VJOURNAL" calendar component is used to add
or more instances to an existing "VJOURNAL" entry. There is no response one or more instances to an existing "VJOURNAL" entry. There is no
to the "Organizer". response to the "Organizer".
If the "UID" property value in the "ADD" is not found on the recipient's If the "UID" property value in the "ADD" is not found on the
calendar, then the recipient MAY treat the "ADD" as a "PUBLISH". recipient's calendar, then the recipient MAY treat the "ADD" as a
"PUBLISH".
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- ---------------------------------------------- ------------------- ----------------------------------------------
METHOD 1 MUST be "ADD" METHOD 1 MUST be "ADD"
VJOURNAL 1 VJOURNAL 1
DESCRIPTION 1 Can be null. DESCRIPTION 1 Can be null.
DTSTAMP 1 DTSTAMP 1
DTSTART 1 DTSTART 1
ORGANIZER 1 ORGANIZER 1
SEQUENCE 1 MUST be greater than 0 SEQUENCE 1 MUST be greater than 0
skipping to change at line 2465 skipping to change at page 53, line 32
VALARM 0+ VALARM 0+
VTIMEZONE 0 or 1 MUST be present if any date/time refers to VTIMEZONE 0 or 1 MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
VTODO 0 VTODO 0
3.5.3 CANCEL 3.5.3 CANCEL
The "CANCEL" method in a "VJOURNAL" calendar component is used to send a The "CANCEL" method in a "VJOURNAL" calendar component is used to
cancellation notice of an existing journal entry. The message is sent by send a cancellation notice of an existing journal entry. The message
the "Organizer" of a journal entry. For a recurring journal entry, is sent by the "Organizer" of a journal entry. For a recurring
either the whole journal entry or instances of a journal entry may be journal entry, either the whole journal entry or instances of a
cancelled. To cancel the complete range of a recurring journal entry, journal entry may be cancelled. To cancel the complete range of a
the "UID" property value for the journal entry MUST be specified and a recurring journal entry, the "UID" property value for the journal
"RECURRENCE-ID" property MUST NOT be specified in the "CANCEL" method. entry MUST be specified and a "RECURRENCE-ID" property MUST NOT be
In order to cancel an individual instance of the journal entry, the specified in the "CANCEL" method. In order to cancel an individual
"RECURRENCE-ID" property value for the journal entry MUST be specified instance of the journal entry, the "RECURRENCE-ID" property value for
in the "CANCEL" method. the journal entry MUST be specified in the "CANCEL" method.
There are two options for canceling a sequence of instances of a There are two options for canceling a sequence of instances of a
recurring "VJOURNAL" calendar component: recurring "VJOURNAL" calendar component:
(a) the "RECURRENCE-ID" property for an instance in the sequence MUST be (a) the "RECURRENCE-ID" property for an instance in the sequence MUST
specified with the "RANGE" property parameter value of THISANDPRIOR be specified with the "RANGE" property parameter value of
(or THISANDFUTURE) to indicate cancellation of the specified "VTODO" THISANDPRIOR (or THISANDFUTURE) to indicate cancellation of the
calendar component and all instances before (or after); or specified "VTODO" calendar component and all instances before (or
after); or
(b) individual recurrence instances may be cancelled by specifying (b) individual recurrence instances may be cancelled by specifying
multiple "RECURRENCE-ID" properties corresponding to the instances to multiple "RECURRENCE-ID" properties corresponding to the
be cancelled. instances to be cancelled.
When a "VJOURNAL" is cancelled, the "SEQUENCE" property value MUST be When a "VJOURNAL" is cancelled, the "SEQUENCE" property value MUST be
incremented. incremented.
This method type is an iCalendar object that conforms to the following This method type is an iCalendar object that conforms to the
property constraints: following property constraints:
Component/Property Presence Component/Property Presence
------------------- --------------------------------------------- ------------------- ---------------------------------------------
METHOD 1 MUST be "CANCEL" METHOD 1 MUST be "CANCEL"
VJOURNAL 1+ All MUST have the same UID VJOURNAL 1+ All MUST have the same UID
DTSTAMP 1 DTSTAMP 1
ORGANIZER 1 ORGANIZER 1
SEQUENCE 1 SEQUENCE 1
UID 1 MUST be the UID of the original REQUEST UID 1 MUST be the UID of the original REQUEST
skipping to change at line 2541 skipping to change at page 55, line 16
VTIMEZONE 0+ MUST be present if any date/time refers to VTIMEZONE 0+ MUST be present if any date/time refers to
a timezone a timezone
X-COMPONENT 0+ X-COMPONENT 0+
VALARM 0 VALARM 0
VEVENT 0 VEVENT 0
VFREEBUSY 0 VFREEBUSY 0
VTODO 0 VTODO 0
3.6 Status Replies 3.6 Status Replies
The "REQUEST-STATUS" property may include the following values: The "REQUEST-STATUS" property may include the following values:
|==============+============================+=========================| |==============+============================+=========================|
| Short Return | Longer Return Status | Offending Data | | Short Return | Longer Return Status | Offending Data |
| Status Code | Description | | | Status Code | Description | |
|==============+============================+=========================| |==============+============================+=========================|
| 2.0 | Success. | None. | | 2.0 | Success. | None. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.1 | Success but fallback taken | Property name and value | | 2.1 | Success but fallback taken | Property name and value |
| | on one or more property | MAY be specified. | | | on one or more property | MAY be specified. |
| | values. | | | | values. | |
skipping to change at line 2661 skipping to change at page 57, line 41
|==============+============================+=========================| |==============+============================+=========================|
| 5.2 | Invalid calendar service. | ATTENDEE property value | | 5.2 | Invalid calendar service. | ATTENDEE property value |
| | | MAY be specified. | | | | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 5.3 | No scheduling support for | ATTENDEE property value | | 5.3 | No scheduling support for | ATTENDEE property value |
| | user. | MAY be specified. | | | user. | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
3.7 Implementation Considerations 3.7 Implementation Considerations
3.7.1 Working With Recurrence Instances 3.7.1 Working With Recurrence Instances
iCalendar includes a recurrence grammar to represent recurring events.
The benefit of such a grammar is the ability to represent a number of
events in a single object. However, while this simplifies creation of a
recurring event, meeting instances still need to be referenced. For
instance, an "Attendee" may decline the third instance of a recurring
Friday event. Similarly, the "Organizer" may change the time or location
to a single instance of the recurring event.
Since implementations may elect to store recurring events as either a iCalendar includes a recurrence grammar to represent recurring
single event object or a collection of discreet, related event objects, events. The benefit of such a grammar is the ability to represent a
the protocol is designed so that each recurring instance may be both number of events in a single object. However, while this simplifies
referenced and versioned. Hence, implementations that choose to maintain creation of a recurring event, meeting instances still need to be
per-instance properties (such as "ATTENDEE" property "partstat" referenced. For instance, an "Attendee" may decline the third
parameter) may do so. However, the protocol does not require per- instance of a recurring Friday event. Similarly, the "Organizer" may
instance recognition unless the instance itself must be renegotiated. change the time or location to a single instance of the recurring
event.
The scenarios for recurrence instance referencing are listed below. For Since implementations may elect to store recurring events as either a
purposes of simplification a change to an event refers to a "trigger single event object or a collection of discreet, related event
property." That is, a property that has a substantive effect on the objects, the protocol is designed so that each recurring instance may
meeting itself such as start time, location, due date (for "VTODO" be both referenced and versioned. Hence, implementations that choose
calendar component components) and possibly description. to maintain per-instance properties (such as "ATTENDEE" property
"partstat" parameter) may do so. However, the protocol does not
require per-instance recognition unless the instance itself must be
renegotiated.
"Organizer" initiated actions: The scenarios for recurrence instance referencing are listed below.
For purposes of simplification a change to an event refers to a
"trigger property." That is, a property that has a substantive
effect on the meeting itself such as start time, location, due date
(for "VTODO" calendar component components) and possibly description.
. "Organizer" deletes or changes a single instance of a recurring "Organizer" initiated actions:
event
. "Organizer" makes changes that affect all future instances
. "Organizer" makes changes that affect all previous instances
. "Organizer" deletes or modifies a previously changed instance
"Attendee" initiated actions: . "Organizer" deletes or changes a single instance of a recurring
event
. "Organizer" makes changes that affect all future instances
. "Organizer" makes changes that affect all previous instances
. "Organizer" deletes or modifies a previously changed instance
. "Attendee" changes status for a particular recurrence instance "Attendee" initiated actions:
. "Attendee" sends Event-Counter for a particular recurrence instance
An instance of a recurring event is assigned a unique identification, . "Attendee" changes status for a particular recurrence instance
"RECURRENCE-ID" property, when that instance is renegotiated. . "Attendee" sends Event-Counter for a particular recurrence
Negotiation may be necessary when a substantive change to the event or instance
to-do has be made (such as changing the start time, end time, due date
or location). The "Organizer" can identify a specific recurrence
instance using the "RECURRENCE-ID" property. The property value is equal
to the date/time of the instance. If the "Organizer" wishes to change
the "DTSTART", the original "DTSTART" value is used for "RECURRENCE-ID"
property and the new "DTSTART" and "DTEND" values reflect the change.
Note that after the change has occurred, the "RECURRENCE-ID" has changed
to the new "DTSTART" value.
3.7.2 Attendee Property Considerations An instance of a recurring event is assigned a unique identification,
"RECURRENCE-ID" property, when that instance is renegotiated.
Negotiation may be necessary when a substantive change to the event
or to-do has be made (such as changing the start time, end time, due
date or location). The "Organizer" can identify a specific recurrence
instance using the "RECURRENCE-ID" property. The property value is
equal to the date/time of the instance. If the "Organizer" wishes to
change the "DTSTART", the original "DTSTART" value is used for
"RECURRENCE-ID" property and the new "DTSTART" and "DTEND" values
reflect the change. Note that after the change has occurred, the
"RECURRENCE-ID" has changed to the new "DTSTART" value.
The "ORGANIZER" property is required on published events, to-dos, and 3.7.2 Attendee Property Considerations
journal entries for two reasons. First, only the "Organizer" is allowed
to update and redistribute an event or to-do component. It follows that
the "ORGANIZER" property MUST be present in the event, to-do, or journal
entry component so that the CUA has a basis for authorizing an update.
Second, it is prudent to provide a point of contact for anyone who
receives a published component in case of problems.
There are valid [RFC-822] addresses that represent groups. Sending email The "ORGANIZER" property is required on published events, to-dos, and
to such an address results in mail being sent to multiple recipients. journal entries for two reasons. First, only the "Organizer" is
Such an address may be used as the value of an "ATTENDEE" property. allowed to update and redistribute an event or to-do component. It
follows that the "ORGANIZER" property MUST be present in the event,
to-do, or journal entry component so that the CUA has a basis for
authorizing an update. Second, it is prudent to provide a point of
contact for anyone who receives a published component in case of
problems.
Thus, it is possible that the recipient of a "REQUEST" does not appear There are valid [RFC-822] addresses that represent groups. Sending
explicitly in the list. email to such an address results in mail being sent to multiple
recipients. Such an address may be used as the value of an
"ATTENDEE" property. Thus, it is possible that the recipient of a
"REQUEST" does not appear explicitly in the list.
It is recommended that the general approach to finding a "Calendar User" It is recommended that the general approach to finding a "Calendar
in an attendee list be as follows: User" in an attendee list be as follows:
1. Search for the "Calendar User" in the attendee list where 1. Search for the "Calendar User" in the attendee list where
"TYPE=INDIVIDUAL" "TYPE=INDIVIDUAL"
2. Failing (1) look for attendees where "TYPE=GROUP" or 'TYPE=UNKNOWN". 2. Failing (1) look for attendees where "TYPE=GROUP" or
The CUA then determines if the "Calendar User" is a member of one of 'TYPE=UNKNOWN". The CUA then determines if the "Calendar User"
these groups. If so, the "REPLY" method sent to the "Organizer" MUST is a member of one of these groups. If so, the "REPLY" method
contain a new "ATTENDEE" property in which: sent to the "Organizer" MUST contain a new "ATTENDEE" property in
. the "type" property parameter is set to INDIVIDUAL which:
. the "member" property parameter is set to the name of the group . the "type" property parameter is set to INDIVIDUAL
. the "member" property parameter is set to the name of the
group
3. Failing (2) the CUA MAY ignore or accept the request as the "Calendar 3. Failing (2) the CUA MAY ignore or accept the request as the
User" wishes. "Calendar User" wishes.
3.7.3 X-Tokens 3.7.3 X-Tokens
To make iCalendar objects extensible, new property types MAY be inserted To make iCalendar objects extensible, new property types MAY be
into components. These properties are called X-Tokens as they are inserted into components. These properties are called X-Tokens as
prefixed with "X-". A client is not required to make sense of X-Tokens. they are prefixed with "X-". A client is not required to make sense
Clients are not required to save X-Tokens or use them in replies. of X-Tokens. Clients are not required to save X-Tokens or use them
in replies.
4 Examples 4 Examples
4.1 Published Event Examples 4.1 Published Event Examples
In the calendaring and scheduling context, publication refers to the one In the calendaring and scheduling context, publication refers to the
way transfer of event information. Consumers of published events simply one way transfer of event information. Consumers of published events
incorporate the event into a calendar. No reply is expected. Individual simply incorporate the event into a calendar. No reply is expected.
"A" publishes an event. Individual "B" reads the event and incorporates Individual "A" publishes an event. Individual "B" reads the event and
it into their calendar. Events are published in several ways including: incorporates it into their calendar. Events are published in several
embedding the event as an object in a web page, e-mailing the event to a ways including: embedding the event as an object in a web page, e-
distribution list, and posting the event to a newsgroup. mailing the event to a distribution list, and posting the event to a
newsgroup.
The table below illustrates the sequence of events between the publisher The table below illustrates the sequence of events between the
and the consumers of a published event. publisher and the consumers of a published event.
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
| Action | "Organizer" | | Action | "Organizer" |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| Publish an event | "A" sends or posts a PUBLISH | | Publish an event | "A" sends or posts a PUBLISH |
| | message | | | message |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| "B" reads a published event | | | "B" reads a published event | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| Publish an updated event | "A" sends or posts a PUBLISH | | Publish an updated event | "A" sends or posts a PUBLISH |
| | message | | | message |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| "B" reads the updated event | | | "B" reads the updated event | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| Cancel a published event | "A" sends or posts a CANCEL | | Cancel a published event | "A" sends or posts a CANCEL |
| | message | | | message |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| "B" reads the canceled event | | | "B" reads the canceled event | |
| publication | | | publication | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
4.1.1 A Minimal Published Event 4.1.1 A Minimal Published Event
The iCalendar object below describes a single event that begins on July The iCalendar object below describes a single event that begins on
1, 1997 at 20:00 UTC. This event contains the minimum set of properties July 1, 1997 at 20:00 UTC. This event contains the minimum set of
for a "PUBLISH" for a "VEVENT" calendar component. properties for a "PUBLISH" for a "VEVENT" calendar component.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:PUBLISH METHOD:PUBLISH
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:mailto:a@example.com ORGANIZER:mailto:a@example.com
DTSTART:19970701T200000Z DTSTART:19970701T200000Z
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
UID:0981234-1234234-23@example.com UID:0981234-1234234-23@example.com
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.1.2 Changing A Published Event 4.1.2 Changing A Published Event
The iCalendar object below describes an update to the event described in The iCalendar object below describes an update to the event described
4.1.1, the time has been changed, an end time has been added, and the in 4.1.1, the time has been changed, an end time has been added, and
sequence number has been adjusted. the sequence number has been adjusted.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:PUBLISH METHOD:PUBLISH
VERSION:2.0 VERSION:2.0
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:mailto:a@example.com ORGANIZER:mailto:a@example.com
DTSTAMP:19970612T190000Z DTSTAMP:19970612T190000Z
DTSTART:19970701T210000Z DTSTART:19970701T210000Z
DTEND:19970701T230000Z DTEND:19970701T230000Z
SEQUENCE:1 SEQUENCE:1
UID:0981234-1234234-23@example.com UID:0981234-1234234-23@example.com
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The "UID" property is used by the client to identify the event. The
"SEQUENCE" property indicates that this is a change to the event. The
event with a matching UID and sequence number 0 is superseded by this
event.
The "SEQUENCE" property provides a reliable way to distinguish different The "UID" property is used by the client to identify the event. The
versions of the same event. Each time an event is published, its "SEQUENCE" property indicates that this is a change to the event. The
sequence number is incremented. If a client receives an event with a event with a matching UID and sequence number 0 is superseded by this
sequence number 5 and finds it has the same event with sequence number event.
2, the event SHOULD be updated. However, if the client received an event
with sequence number 2 and finds it already has sequence number 5 of the
same event, the event MUST NOT be updated.
4.1.3 Canceling A Published Event The "SEQUENCE" property provides a reliable way to distinguish
different versions of the same event. Each time an event is
published, its sequence number is incremented. If a client receives
an event with a sequence number 5 and finds it has the same event
with sequence number 2, the event SHOULD be updated. However, if the
client received an event with sequence number 2 and finds it already
has sequence number 5 of the same event, the event MUST NOT be
updated.
The iCalendar object below cancels the event described in 4.1.1. This 4.1.3 Canceling A Published Event
cancels the event with "SEQUENCE" property of 0, 1, and 2.
BEGIN:VCALENDAR The iCalendar object below cancels the event described in 4.1.1. This
METHOD:CANCEL cancels the event with "SEQUENCE" property of 0, 1, and 2.
VERSION:2.0
PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT
ORGANIZER:mailto:a@example.com
COMMENT:DUKES forfeit the game
SEQUENCE:2
UID:0981234-1234234-23@example.com
DTSTAMP:19970613T190000Z
END:VEVENT
END:VCALENDAR
4.1.4 A Rich Published Event BEGIN:VCALENDAR
METHOD:CANCEL
VERSION:2.0
PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT
ORGANIZER:mailto:a@example.com
COMMENT:DUKES forfeit the game
SEQUENCE:2
UID:0981234-1234234-23@example.com
DTSTAMP:19970613T190000Z
END:VEVENT
END:VCALENDAR
This example describes the same event as in 4.1.1, but in much greater 4.1.4 A Rich Published Event
detail.
BEGIN:VCALENDAR This example describes the same event as in 4.1.1, but in much
PRODID:-//ACME/DesktopCalendar//EN greater detail.
METHOD:PUBLISH
SCALE:GREGORIAN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America-Chicago
TZURL:http://zones.stds_r_us.net/tz/America-Chicago
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER:mailto:a@example.com
ATTACH:http://www.dukes.com/
CATEGORIES:SPORTS EVENT,ENTERTAINMENT
CLASS:PRIVATE
DESCRIPTION:MIDWAY STADIUM\n
Big time game. MUST see.\n
Expected duration:2 hours\n
DTEND;TZID=America-Chicago:19970701T180000
DTSTART;TZID=America-Chicago:19970702T160000
DTSTAMP:19970614T190000Z
STATUS:CONFIRMED
LOCATION;VALUE=URI:http://www.midwaystadium.com/
PRIORITY:2
RESOURCES:SCOREBOARD
SEQUENCE:3
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
UID:0981234-1234234-23@example.com
RELATED-TO:0981234-1234234-14@example.com
BEGIN:VALARM
TRIGGER:-PT2H
ACTION:DISPLAY
DESCRIPTION:You should be leaving for the game now.
END:VALARM
BEGIN:VALARM
TRIGGER:-PT30M
ACTION:AUDIO
END:VALARM
END:VEVENT
END:VCALENDAR
The "RELATED-TO" field contains the "UID" property of a related calendar BEGIN:VCALENDAR
event. The "SEQUENCE" property 3 indicates that this event supersedes PRODID:-//ACME/DesktopCalendar//EN
versions 0, 1, and 2. METHOD:PUBLISH
SCALE:GREGORIAN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America-Chicago
TZURL:http://zones.stds_r_us.net/tz/America-Chicago
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER:mailto:a@example.com
ATTACH:http://www.dukes.com/
CATEGORIES:SPORTS EVENT,ENTERTAINMENT
CLASS:PRIVATE
DESCRIPTION:MIDWAY STADIUM\n
Big time game. MUST see.\n
Expected duration:2 hours\n
DTEND;TZID=America-Chicago:19970701T180000
DTSTART;TZID=America-Chicago:19970702T160000
DTSTAMP:19970614T190000Z
STATUS:CONFIRMED
LOCATION;VALUE=URI:http://www.midwaystadium.com/
PRIORITY:2
RESOURCES:SCOREBOARD
SEQUENCE:3
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
UID:0981234-1234234-23@example.com
RELATED-TO:0981234-1234234-14@example.com
BEGIN:VALARM
TRIGGER:-PT2H
ACTION:DISPLAY
DESCRIPTION:You should be leaving for the game now.
END:VALARM
BEGIN:VALARM
TRIGGER:-PT30M
ACTION:AUDIO
END:VALARM
END:VEVENT
END:VCALENDAR
4.1.5 Anniversaries or Events attached to entire days The "RELATED-TO" field contains the "UID" property of a related
calendar event. The "SEQUENCE" property 3 indicates that this event
supersedes versions 0, 1, and 2.
This example demonstrates the use of the "value" parameter to tie a 4.1.5 Anniversaries or Events attached to entire days
"VEVENT" to day rather than a specific time.
BEGIN:VCALENDAR This example demonstrates the use of the "value" parameter to tie a
PRODID:-//ACME/DesktopCalendar//EN "VEVENT" to day rather than a specific time.
METHOD:PUBLISH
VERSION:2.0 BEGIN:VCALENDAR
BEGIN:VEVENT PRODID:-//ACME/DesktopCalendar//EN
ORGANIZER:mailto:a@example.com METHOD:PUBLISH
DTSTAMP:19970614T190000Z VERSION:2.0
UID:0981234-1234234-23@example.com BEGIN:VEVENT
DTSTART;VALUE=DATE:19970714 ORGANIZER:mailto:a@example.com
RRULE:FREQ=YEARLY;INTERVAL=1 DTSTAMP:19970614T190000Z
SUMMARY: Bastille Day UID:0981234-1234234-23@example.com
END:VEVENT DTSTART;VALUE=DATE:19970714
END:VCALENDAR RRULE:FREQ=YEARLY;INTERVAL=1
SUMMARY: Bastille Day
END:VEVENT
END:VCALENDAR
4.2 Group Event Examples 4.2 Group Event Examples
Group events are distinguished from published events in that they have Group events are distinguished from published events in that they
"Attendees" and that there is interaction between the "Attendees" and have "Attendees" and that there is interaction between the
the "Organizer" with respect to the event. Individual "A" requests a "Attendees" and the "Organizer" with respect to the event. Individual
meeting between individuals "A", "B", "C" and "D". Individual "B" "A" requests a meeting between individuals "A", "B", "C" and "D".
confirms attendance to the meeting. Individual "C" declines attendance. Individual "B" confirms attendance to the meeting. Individual "C"
Individual "D" tentatively confirms attendance. The following table declines attendance. Individual "D" tentatively confirms attendance.
illustrates the the message flow between these individuals. A, the CU The following table illustrates the the message flow between these
scheduling the meeting, is referenced as the "Organizer". individuals. A, the CU scheduling the meeting, is referenced as the
"Organizer".
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Initiate a meeting | "A" sends a REQUEST | | | Initiate a meeting | "A" sends a REQUEST | |
| request | message to "B", "C",| | | request | message to "B", "C",| |
| | and "D" | | | | and "D" | |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Accept the meeting | | "B" sends a REPLY | | Accept the meeting | | "B" sends a REPLY |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | ATTENDEE "partstat" para-| | | | ATTENDEE "partstat" para-|
| | | set to "accepted" | | | | set to "accepted" |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Decline the meeting| | "C" sends a REPLY | | Decline the meeting| | "C" sends a REPLY |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | ATTENDEE "partstat" para-| | | | ATTENDEE "partstat" para-|
| | | set to "declined" | | | | set to "declined" |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Tentatively accept | | "D" sends a REPLY | | Tentatively accept | | "D" sends a REPLY |
| the meeting request| | message to "A" with its | | the meeting request| | message to "A" with its |
| | | ATTENDEE "partstat" para-| | | | ATTENDEE "partstat" para-|
| | | set to "tentative" | | | | set to "tentative" |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Confirm meeting | "A" sends a REQUEST | | | Confirm meeting | "A" sends a REQUEST | |
| status with | message to "B" and | | | status with | message to "B" and | |
| attendees | "D" with updated | | | attendees | "D" with updated | |
| | information. | | | | information. | |
+--------------------------------------------------------------------+ +---------------------------------------------------------------------+
4.2.1 A Group Event Request 4.2.1 A Group Event Request
A sample meeting request is sent from "A" to "B", "C", and "D". _E_ is A sample meeting request is sent from "A" to "B", "C", and "D". _E_
also sent a copy of the request but is not expected to attend and need is also sent a copy of the request but is not expected to attend and
not reply. "E" illustrates how CUAs might implement an "FYI" type need not reply. "E" illustrates how CUAs might implement an "FYI"
feature. Note the use of the "role" parameter. The default value for the type feature. Note the use of the "role" parameter. The default value
"role" parameter is "req-participant" and it need not be enumerated. In for the "role" parameter is "req-participant" and it need not be
this case we are using the value "non-participant" to indicate "E" is a enumerated. In this case we are using the value "non-participant" to
non-attending CU. The parameter is not needed on other "Attendees" since indicate "E" is a non-attending CU. The parameter is not needed on
"participant" is the default value. other "Attendees" since "participant" is the default value.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN=BIG A:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN=BIG A:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=B:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=B:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=C:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=C:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com
ATTENDEE;RSVP=FALSE;TYPE=ROOM:conf_Big@example.com ATTENDEE;RSVP=FALSE;TYPE=ROOM:conf_Big@example.com
ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T200000Z DTSTART:19970701T200000Z
DTEND:19970701T2000000Z DTEND:19970701T2000000Z
SUMMARY:Conference SUMMARY:Conference
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.2.2 Reply To A Group Event Request 4.2.2 Reply To A Group Event Request
Attendee "B" accepts the meeting. Attendee "B" accepts the meeting.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;PARTSTAT=ACCEPTED:Mailto:B@example.com ATTENDEE;PARTSTAT=ACCEPTED:Mailto:B@example.com
ORGANIZER:MAILTO:A@example.com ORGANIZER:MAILTO:A@example.com
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
DTSTAMP:19970612T190000Z DTSTAMP:19970612T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"B" could have declined the meeting or indicated tentative acceptance by "B" could have declined the meeting or indicated tentative acceptance
setting the "ATTENDEE" "partstat" parameter to "declined" or by setting the "ATTENDEE" "partstat" parameter to "declined" or
"tentative", respectively. Also, "REQUEST-STATUS" is not required in "tentative", respectively. Also, "REQUEST-STATUS" is not required in
successful transactions. successful transactions.
4.2.3 Update An Event 4.2.3 Update An Event
The event is moved to a different time. The combination of the "UID" The event is moved to a different time. The combination of the "UID"
property (unchanged) and the "SEQUENCE" (bumped to 1) properties property (unchanged) and the "SEQUENCE" (bumped to 1) properties
indicate the update. indicate the update.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com
ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE; ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE;
CUTYPE=ROOM:Mailto:Conf@example.com CUTYPE=ROOM:Mailto:Conf@example.com
ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com
DTSTART:19970701T180000Z DTSTART:19970701T180000Z
DTEND:19970701T190000Z DTEND:19970701T190000Z
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:1 SEQUENCE:1
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.2.4 Countering an Event Proposal 4.2.4 Countering an Event Proposal
"A" sends a "REQUEST" to "B" and "C". "B" makes a counter-proposal to "A" sends a "REQUEST" to "B" and "C". "B" makes a counter-proposal to
"A" to change the time and location. "A" to change the time and location.
"A" sends the following "REQUEST": "A" sends the following "REQUEST":
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
DTSTART:19970701T190000Z DTSTART:19970701T190000Z
DTEND:19970701T200000Z DTEND:19970701T200000Z
SUMMARY:Discuss the Merits of the election results SUMMARY:Discuss the Merits of the election results
LOCATION:Green Conference Room LOCATION:Green Conference Room
UID:calsrv.example.com-873970198738777a@example.com UID:calsrv.example.com-873970198738777a@example.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"B" sends "COUNTER" to "A", requesting changes to time and place. "B" "B" sends "COUNTER" to "A", requesting changes to time and place. "B"
uses the "COMMENT" property to communicate a rationale for the change. uses the "COMMENT" property to communicate a rationale for the
Note that the "SEQUENCE" property is NOT incremented on a "COUNTER". change. Note that the "SEQUENCE" property is NOT incremented on a
"COUNTER".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:COUNTER METHOD:COUNTER
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
DTSTART:19970701T160000Z DTSTART:19970701T160000Z
DTEND:19970701T190000Z DTEND:19970701T190000Z
DTSTAMP:19970612T190000Z DTSTAMP:19970612T190000Z
SUMMARY:Discuss the Merits of the election results SUMMARY:Discuss the Merits of the election results
LOCATION:Green Conference Room LOCATION:Green Conference Room
COMMENT:This time works much better and I think the big conference COMMENT:This time works much better and I think the big conference
room is too big room is too big
UID:calsrv.example.com-873970198738777a@example.com UID:calsrv.example.com-873970198738777a@example.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"A" accepts the changes from "B". To accept a counter-proposal, the "A" accepts the changes from "B". To accept a counter-proposal, the
"Organizer" sends a new event "REQUEST" with an incremented sequence "Organizer" sends a new event "REQUEST" with an incremented sequence
number. number.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
DTSTART:19970701T160000Z DTSTART:19970701T160000Z
DTEND:19970701T190000Z DTEND:19970701T190000Z
SUMMARY:Discuss the Merits of the election results - changed to SUMMARY:Discuss the Merits of the election results - changed to
meet B's schedule meet B's schedule
LOCATION:Green Conference Room LOCATION:Green Conference Room
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:1 SEQUENCE:1
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Instead, "A" rejects "B's" counter proposal Instead, "A" rejects "B's" counter proposal
BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:DECLINECOUNTER
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
COMMENT:Sorry, I cannot change this meeting time
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
DTSTAMP:19970614T190000Z
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.2.5 Delegating an Event
PRODID:-//ACME/DesktopCalendar//EN
METHOD:DECLINECOUNTER
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
COMMENT:Sorry, I cannot change this meeting time
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
DTSTAMP:19970614T190000Z
END:VEVENT
END:VCALENDAR
4.2.5 Delegating an Event When delegating an event request to another "Calendar User", the
"Delegator" must both update the "Organizer" with a "REPLY" and send
a request to the "Delegate". There is currently no protocol
limitation to delegation depth. It is possible for the original
When delegating an event request to another "Calendar User", the delegate to delegate the meeting to someone else, and so on. When a
"Delegator" must both update the "Organizer" with a "REPLY" and send a request is delegated from one CUA to another there are a number of
request to the "Delegate". There is currently no protocol limitation to responsibilities required of the "Delegator". The "Delegator" MUST:
delegation depth. It is possible for the original delegate to delegate
the meeting to someone else, and so on. When a request is delegated from
one CUA to another there are a number of responsibilities required of
the "Delegator". The "Delegator" MUST:
. Send a "REPLY" to the "Organizer" with the following updates: . Send a "REPLY" to the "Organizer" with the following updates:
. The "Delegator's" "ATTENDEE" property "partstat" parameter set to . The "Delegator's" "ATTENDEE" property "partstat" parameter set
"delegated" and the "delegated-to" parameter is set to the address to "delegated" and the "delegated-to" parameter is set to the
of the "Delegate" address of the "Delegate"
. Add an additional "ATTENDEE" property for the "Delegate" with the . Add an additional "ATTENDEE" property for the "Delegate" with
"delegated-from" property parameter set to the "Delegator" the "delegated-from" property parameter set to the "Delegator"
. Indicate whether they want to continue to receive updates when the . Indicate whether they want to continue to receive updates when
"Organizer" sends out updated versions of the event. Setting the the "Organizer" sends out updated versions of the event.
"rsvp" property parameter to "TRUE" will cause the updates to be Setting the "rsvp" property parameter to "TRUE" will cause the
sent, setting it to "FALSE" causes no further updates to be sent. updates to be sent, setting it to "FALSE" causes no further
Note that in either case, if the "Delegate" declines the invitation updates to be sent. Note that in either case, if the "Delegate"
the "Delegator" will be notified. declines the invitation the "Delegator" will be notified.
. The "Delegator" MUST also send a copy of the original "REQUEST" . The "Delegator" MUST also send a copy of the original "REQUEST"
method to the "Delegate". method to the "Delegate".
It is not required that the "Delegate" include the "Delegator" in their It is not required that the "Delegate" include the "Delegator" in
"REPLY" method. However, it is strongly advised since this will inform their "REPLY" method. However, it is strongly advised since this will
the "Delegator" whether the "Delegate" plans to attend the meeting. inform the "Delegator" whether the "Delegate" plans to attend the
[Editors note: How so?] If the "Delegate" declines the meeting, the meeting. [Editors note: How so?] If the "Delegate" declines the
"Delegator" may elect to delegate the "REQUEST" to another CUA. The meeting, the "Delegator" may elect to delegate the "REQUEST" to
process is the same. another CUA. The process is the same.
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Initiate a meeting | "A" sends a REQUEST | | | Initiate a meeting | "A" sends a REQUEST | |
| request | message to "B" and | | | request | message to "B" and | |
| | "C" | | | | "C" | |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Delegate: | | "C" sends a REPLY to "A" | | Delegate: | | "C" sends a REPLY to "A" |
| "C" delegates to | | with the ATTENDEE. | | "C" delegates to | | with the ATTENDEE. |
| "E" | | "partstat" parameter set | | "E" | | "partstat" parameter set |
| | | to "delegated" and with a| | | | to "delegated" and with a|
| | | new "ATTENDEE" property | | | | new "ATTENDEE" property |
| | | for "E". "E's" ATTENDEE | | | | for "E". "E's" ATTENDEE |
| | | "delegated-from" param | | | | "delegated-from" param |
| | | is set to "C". "C's" | | | | is set to "C". "C's" |
| | | ATTENDEE "delegated-to" | | | | ATTENDEE "delegated-to" |
| | | param is set to "E". | | | | param is set to "E". |
| | | "C" sends REQUEST message| | | | "C" sends REQUEST message|
| | | to "E" with the original | | | | to "E" with the original |
| | | meeting request | | | | meeting request |
| | | information. The | | | | information. The |
| | | "partstat" property | | | | "partstat" property |
| | | parameter for "C" is set | | | | parameter for "C" is set |
| | | to "delegated" and the | | | | to "delegated" and the |
| | | "delegated-to" | | | | "delegated-to" |
| | | parameter is set to | | | | parameter is set to |
| | | the address of "E". An | | | | the address of "E". An |
| | | "ATTENDEE" property is | | | | "ATTENDEE" property is |
| | | added for "E" and the | | | | added for "E" and the |
| | | "delegated-from" | | | | "delegated-from" |
| | | parameter is set to | | | | parameter is set to |
| | | the address of "C". | | | | the address of "C". |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Confirm meeting | | "E" sends REPLY message | | Confirm meeting | | "E" sends REPLY message |
| attendance | | to "A" and optionally "C"| | attendance | | to "A" and optionally "C"|
| | | with its "partstat" | | | | with its "partstat" |
| | | property parameter set | | | | property parameter set |
| | | to "ACCEPTED" | | | | to "ACCEPTED" |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Optional: | "A" sends REQUEST | | | Optional: | "A" sends REQUEST | |
| Redistribute | message to "B", "C" | | | Redistribute | message to "B", "C" | |
| meeting to | and "E". | | | meeting to | and "E". | |
| attendees | | | | attendees | | |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
"C" responds to the "Organizer".
"C" responds to the "Organizer". BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=DELEGATED;DELEGATED-
TO="Mailto:E@example.com":Mailto:C@example.com
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
REQUEST-STATUS:2.0;Success
DTSTAMP:19970611T190000Z
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR Attendee "C" delegates presence at the meeting to "E".
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=DELEGATED;DELEGATED-
TO="Mailto:E@example.com":Mailto:C@example.com
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
REQUEST-STATUS:2.0;Success
DTSTAMP:19970611T190000Z
END:VEVENT
END:VCALENDAR
Attendee "C" delegates presence at the meeting to "E". BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;PARTSTAT=DELEGATED;DELEGATED-
TO="Mailto:E@example.com":Mailto:C@example.com
ATTENDEE;RSVP=TRUE;
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
DTSTART:19970701T180000Z
DTEND:19970701T200000Z
SUMMARY:Phone Conference
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
STATUS:CONFIRMED
DTSTAMP:19970611T190000Z
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.2.6 Delegate Accepts the Meeting
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;PARTSTAT=DELEGATED;DELEGATED-
TO="Mailto:E@example.com":Mailto:C@example.com
ATTENDEE;RSVP=TRUE;
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
DTSTART:19970701T180000Z
DTEND:19970701T200000Z
SUMMARY:Phone Conference
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
STATUS:CONFIRMED
DTSTAMP:19970611T190000Z
END:VEVENT
END:VCALENDAR
4.2.6 Delegate Accepts the Meeting To accept a delegated meeting, the delegate, "E", sends the following
message to "A" and "C":
To accept a delegated meeting, the delegate, "E", sends the following BEGIN:VCALENDAR
message to "A" and "C": PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=ACCEPTED;DELEGATED-
FROM="Mailto:C@example.com":Mailto:E@example.com
ATTENDEE;PARTSTAT=DELEGATED;
DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
REQUEST-STATUS:2.0;Success
DTSTAMP:19970614T190000Z
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.2.7 Delegate Declines the Meeting
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=ACCEPTED;DELEGATED-
FROM="Mailto:C@example.com":Mailto:E@example.com
ATTENDEE;PARTSTAT=DELEGATED;
DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0
REQUEST-STATUS:2.0;Success
DTSTAMP:19970614T190000Z
END:VEVENT
END:VCALENDAR
4.2.7 Delegate Declines the Meeting
In this example the "Delegate" declines the meeting request and sets the In this example the "Delegate" declines the meeting request and sets
"ATTENDEE" property "partstat" parameter to "DECLINED". The "Organizer" the "ATTENDEE" property "partstat" parameter to "DECLINED". The
SHOULD resend the "REQUEST" to "C" with the "partstat" parameter of the "Organizer" SHOULD resend the "REQUEST" to "C" with the "partstat"
"Delegate" set to "declined". This lets the "Delegator" know that the parameter of the "Delegate" set to "declined". This lets the
"Delegate" has declined and provides an opportunity to the "Delegator" "Delegator" know that the "Delegate" has declined and provides an
to either accept the request or delegate it to another CU. opportunity to the "Delegator" to either accept the request or
delegate it to another CU.
Response from "E" to "A" and "C". Note the use of the "COMMENT" property Response from "E" to "A" and "C". Note the use of the "COMMENT"
"E" uses to indicate why the delegation was declined. property "E" uses to indicate why the delegation was declined.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=DELEGATED; ATTENDEE;PARTSTAT=DELEGATED;
DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com
ATTENDEE;PARTSTAT=DECLINED; ATTENDEE;PARTSTAT=DECLINED;
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
COMMENT:Sorry, I will be out of town at that time. COMMENT:Sorry, I will be out of town at that time.
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"A" resends the "REQUEST" method to "C". "A" may also wish to express "A" resends the "REQUEST" method to "C". "A" may also wish to express
the fact that the item was delegated in the "COMMENT" property. the fact that the item was delegated in the "COMMENT" property.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:MAILTO:A@Example.com ORGANIZER:MAILTO:A@Example.com
ATTENDEE;PARTSTAT=DECLINED; ATTENDEE;PARTSTAT=DECLINED;
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com ATTENDEE;RSVP=TRUE:Mailto:C@example.com
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
SUMMARY:Phone Conference SUMMARY:Phone Conference
DTSTART:19970701T180000Z DTSTART:19970701T180000Z
DTEND:19970701T200000Z DTEND:19970701T200000Z
DTSTAMP:19970614T200000Z DTSTAMP:19970614T200000Z
COMMENT:DELEGATE (ATTENDEE Mailto:E@example.com) DECLINED YOUR COMMENT:DELEGATE (ATTENDEE Mailto:E@example.com) DECLINED YOUR
INVITATION INVITATION
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.2.8 Forwarding an Event Request
The protocol does not prevent an "Attendee" from "forwarding" an 4.2.8 Forwarding an Event Request
"VEVENT" calendar component to other "Calendar Users". Forwarding
differs from delegation in that the forwarded "Calendar User" (often
referred to as a "Party Crasher") does not replace the forwarding
"Calendar User". Implementations are not required to add the "Party
Crasher" to the "Attendee" list and hence there is no guarantee that a
"Party Crasher" will receive additional updates to the Event. The
forwarding "Calendar User" SHOULD NOT add the "Party Crasher" to the
attendee list. The "Organizer" MAY add the forwarded "Calendar User" to
the attendee list.
4.2.9 Cancel A Group Event The protocol does not prevent an "Attendee" from "forwarding" an
"VEVENT" calendar component to other "Calendar Users". Forwarding
differs from delegation in that the forwarded "Calendar User" (often
referred to as a "Party Crasher") does not replace the forwarding
"Calendar User". Implementations are not required to add the "Party
Crasher" to the "Attendee" list and hence there is no guarantee that
a "Party Crasher" will receive additional updates to the Event. The
forwarding "Calendar User" SHOULD NOT add the "Party Crasher" to the
attendee list. The "Organizer" MAY add the forwarded "Calendar User"
to the attendee list.
Individual "A" requests a meeting between individuals "A", "B", "C", and 4.2.9 Cancel A Group Event
"D". Individual "B" declines attendance to the meeting. Individual "A"
decides to cancel the meeting. The following table illustrates the
sequence of messages that would be exchanged between these individuals.
Messages related to a previously canceled event ("SEQUENCE" property Individual "A" requests a meeting between individuals "A", "B", "C",
value is less than the "SEQUENCE" property value of the "CANCEL" and "D". Individual "B" declines attendance to the meeting.
message) MUST be ignored. Individual "A" decides to cancel the meeting. The following table
illustrates the sequence of messages that would be exchanged between
these individuals.
+--------------------------------------------------------------------+ Messages related to a previously canceled event ("SEQUENCE" property
| Action | "Organizer" | "Attendee" | value is less than the "SEQUENCE" property value of the "CANCEL"
+--------------------------------------------------------------------+ message) MUST be ignored.
| Initiate a meeting | "A" sends a REQUEST | |
| request | message to "B", "C",| |
| | and "D" | |
+--------------------------------------------------------------------+
| Decline the meeting| | "B" sends a "REPLY" |
| request | | message to "A" with its |
| | | "partstat" para- |
| | | set to "declined". |
+--------------------------------------------------------------------+
| Cancel the meeting | "A" sends a CANCEL | |
| | message to "B", "C" | |
| | and "D" | |
+--------------------------------------------------------------------+
The example shows how "A" cancels the event. +--------------------------------------------------------------------+
| Action | "Organizer" | "Attendee" |
+--------------------------------------------------------------------+
| Initiate a meeting | "A" sends a REQUEST | |
| request | message to "B", "C",| |
| | and "D" | |
+--------------------------------------------------------------------+
| Decline the meeting| | "B" sends a "REPLY" |
| request | | message to "A" with its |
| | | "partstat" para- |
| | | set to "declined". |
+--------------------------------------------------------------------+
| Cancel the meeting | "A" sends a CANCEL | |
| | message to "B", "C" | |
| | and "D" | |
+--------------------------------------------------------------------+
BEGIN:VCALENDAR The example shows how "A" cancels the event.
PRODID:-//ACME/DesktopCalendar//EN
METHOD:CANCEL
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL;Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com
COMMENT:Mr. B cannot attend. It's raining. Lets cancel.
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:1
STATUS:CANCELLED
DTSTAMP:19970613T190000Z
END:VEVENT
END:VCALENDAR
4.2.10 Removing Attendees BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:CANCEL
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL;Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com
COMMENT:Mr. B cannot attend. It's raining. Lets cancel.
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:1
STATUS:CANCELLED
DTSTAMP:19970613T190000Z
END:VEVENT
END:VCALENDAR
"A" wants to remove "B" from a meeting. This is done by sending a 4.2.10 Removing Attendees
"CANCEL" to "B" and removing "B" from the attendee list in the master
copy of the event.
+--------------------------------------------------------------------+ "A" wants to remove "B" from a meeting. This is done by sending a
| Action | "Organizer" | "Attendee" | "CANCEL" to "B" and removing "B" from the attendee list in the master
+--------------------------------------------------------------------+ copy of the event.
| Remove an "B" | "A" sends a CANCEL | |
| as an "Attendee" | message to "B" | |
+--------------------------------------------------------------------+
| Update the master | "A" sends the | |
| copy of the event | updated event to | |
| | the remaining | |
| | "Attendees" | |
+--------------------------------------------------------------------+
The original meeting includes "A", "B", "C", and "D". The example below +--------------------------------------------------------------------+
shows the "CANCEL" that "A" sends to "B". Note that in the example below | Action | "Organizer" | "Attendee" |
the "STATUS" property is omitted. This is used when the meeting itself +--------------------------------------------------------------------+
is cancelled and not when the intent is to remove an "Attendee" from the | Remove an "B" | "A" sends a CANCEL | |
Event. | as an "Attendee" | message to "B" | |
+--------------------------------------------------------------------+
| Update the master | "A" sends the | |
| copy of the event | updated event to | |
| | the remaining | |
| | "Attendees" | |
+--------------------------------------------------------------------+
BEGIN:VCALENDAR The original meeting includes "A", "B", "C", and "D". The example
PRODID:-//ACME/DesktopCalendar//EN below shows the "CANCEL" that "A" sends to "B". Note that in the
METHOD:CANCEL example below the "STATUS" property is omitted. This is used when the
VERSION:2.0 meeting itself is cancelled and not when the intent is to remove an
BEGIN:VEVENT "Attendee" from the Event.
ORGANIZER:Mailto:A@example.com
ATTENDEE:mailto:B@example.com
COMMENT:You're off the hook for this meeting
UID:calsrv.example.com-873970198738777@example.com
DTSTAMP:19970613T193000Z
SEQUENCE:1
END:VEVENT
END:VCALENDAR
The updated master copy of the event is shown below. The "Organizer" MAY BEGIN:VCALENDAR
resend the updated event to the remaining "Attendees". Note that "B" has PRODID:-//ACME/DesktopCalendar//EN
been removed. METHOD:CANCEL
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE:mailto:B@example.com
COMMENT:You're off the hook for this meeting
UID:calsrv.example.com-873970198738777@example.com
DTSTAMP:19970613T193000Z
SEQUENCE:1
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR The updated master copy of the event is shown below. The "Organizer"
PRODID:-//ACME/DesktopCalendar//EN MAY resend the updated event to the remaining "Attendees". Note that
METHOD:REQUEST "B" has been removed.
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com
ATTENDEE;TYPE=ROOM:CR_Big@example.com
ATTENDEE;ROLE=NON-PARTICIPANT;
RSVP=FALSE:Mailto:E@example.com
DTSTAMP:19970611T190000Z
DTSTART:19970701T200000Z
DTEND:19970701T203000Z
SUMMARY:Phone Conference
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:2
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
4.2.11 Replacing the Organizer BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com
ATTENDEE;TYPE=ROOM:CR_Big@example.com
ATTENDEE;ROLE=NON-PARTICIPANT;
RSVP=FALSE:Mailto:E@example.com
DTSTAMP:19970611T190000Z
DTSTART:19970701T200000Z
DTEND:19970701T203000Z
SUMMARY:Phone Conference
UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:2
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
The scenario for this example begins with "A" as the "Organizer" for a 4.2.11 Replacing the Organizer
recurring meeting with "B", "C", and "D". "A" receives a new job offer
in another country and drops out of touch. "A" left no forwarding
address or way to be reached. Using out-of-band communication, the
other "Attendees" eventually learn what has happened and reach an
agreement that "B" should become the new "Organizer" for the meeting. To
do this, "B" sends out a new version of the event and the other
"Attendees" agree to accept "B" as the new "Organizer". "B" also removes
"A" from the event.
When the "Organizer" is replaced, the "SEQUENCE" property value MUST be The scenario for this example begins with "A" as the "Organizer" for
incremented. a recurring meeting with "B", "C", and "D". "A" receives a new job
offer in another country and drops out of touch. "A" left no
forwarding address or way to be reached. Using out-of-band
communication, the other "Attendees" eventually learn what has
happened and reach an agreement that "B" should become the new
"Organizer" for the meeting. To do this, "B" sends out a new version
of the event and the other "Attendees" agree to accept "B" as the new
"Organizer". "B" also removes "A" from the event.
This is the message "B" sends to "C" and "D" When the "Organizer" is replaced, the "SEQUENCE" property value MUST
be incremented.
BEGIN:VCALENDAR This is the message "B" sends to "C" and "D"
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST BEGIN:VCALENDAR
VERSION:2.0 PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT METHOD:REQUEST
ORGANIZER:Mailto:B@example.com VERSION:2.0
ATTENDEE;ROLE=CHAIR;STATUS=ACCEPTED:Mailto:B@example.com BEGIN:VEVENT
ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com ORGANIZER:Mailto:B@example.com
ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com ATTENDEE;ROLE=CHAIR;STATUS=ACCEPTED:Mailto:B@example.com
DTSTAMP:19970611T190000Z ATTENDEE;TYPE=INDIVIDUAL:Mailto:C@example.com
DTSTART:19970701T200000Z ATTENDEE;TYPE=INDIVIDUAL:Mailto:D@example.com
DTEND:19970701T203000Z DTSTAMP:19970611T190000Z
RRULE:FREQ=WEEKLY DTSTART:19970701T200000Z
SUMMARY:Phone Conference DTEND:19970701T203000Z
UID:123456@example.com RRULE:FREQ=WEEKLY
SEQUENCE:1 SUMMARY:Phone Conference
STATUS:CONFIRMED UID:123456@example.com
END:VEVENT SEQUENCE:1
END:VCALENDAR STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
4.3 Busy Time Examples 4.3 Busy Time Examples
Busy time objects can be used in several ways. First, a CU may request Busy time objects can be used in several ways. First, a CU may
busy time from another CU for a specific range of time. That request can request busy time from another CU for a specific range of time. That
be answered with a busy time Reply. Additionally, a CU may simply request can be answered with a busy time Reply. Additionally, a CU
publish their busy time for a given interval and point other CUs to the may simply publish their busy time for a given interval and point
published location. The following examples outline both scenarios. other CUs to the published location. The following examples outline
both scenarios.
Individual "A" publishes busy time for one week. Individual "A" publishes busy time for one week.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
VERSION:2.0 VERSION:2.0
METHOD:PUBLISH METHOD:PUBLISH
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
DTSTAMP:19980101T124100Z DTSTAMP:19980101T124100Z
ORGANIZER:MAILTO:A@Example.com ORGANIZER:MAILTO:A@Example.com
DTSTART:19980101T124200Z DTSTART:19980101T124200Z
DTEND:19980107T124200Z DTEND:19980107T124200Z
FREEBUSY:19980101T180000Z/19980101T190000Z FREEBUSY:19980101T180000Z/19980101T190000Z
FREEBUSY:19980103T020000Z/19980103T050000Z FREEBUSY:19980103T020000Z/19980103T050000Z
FREEBUSY:19980107T020000Z/19980107T050000Z FREEBUSY:19980107T020000Z/19980107T050000Z
FREEBUSY:19980113T000000Z/19980113T010000Z FREEBUSY:19980113T000000Z/19980113T010000Z
FREEBUSY:19980115T190000Z/19980115T200000Z FREEBUSY:19980115T190000Z/19980115T200000Z
FREEBUSY:19980115T220000Z/19980115T230000Z FREEBUSY:19980115T220000Z/19980115T230000Z
FREEBUSY:19980116T013000Z/19980116T043000Z FREEBUSY:19980116T013000Z/19980116T043000Z
END:VFREEBUSY END:VFREEBUSY
END:VCALENDAR END:VCALENDAR
Individual "A" requests busy time from individuals "B", "C". Individual Individual "A" requests busy time from individuals "B", "C".
"B" and "C" replies with busy time data to individual "A". The following Individual "B" and "C" replies with busy time data to individual "A".
table illustrates the sequence of messages that would be exchanged The following table illustrates the sequence of messages that would
between these individuals. be exchanged between these individuals.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Initiate a busy | "A" sends "REQUEST" | | | Initiate a busy | "A" sends "REQUEST" | |
| time request | message to "B" and | | | time request | message to "B" and | |
| | and "C" | | | | and "C" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Reply to the "BUSY"| | "B" sends a "REPLY" | | Reply to the "BUSY"| | "B" sends a "REPLY" |
| request with "BUSY"| | message to "A" with | | request with "BUSY"| | message to "A" with |
| time data | | busy time data | | time data | | busy time data |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4.3.1 Request Busy Time
"A" sends a "BUSY-REQUEST" to "B" and "C" for busy time 4.3.1 Request Busy Time
BEGIN:VCALENDAR "A" sends a "BUSY-REQUEST" to "B" and "C" for busy time
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VFREEBUSY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
DTSTAMP:19970613T190000Z
DTSTART:19970701T080000Z
DTEND:19970701T200000
UID:calsrv.example.com-873970198738777@example.com
END:VFREEBUSY
END:VCALENDAR
4.3.2 Reply To A Busy Time Request BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST
VERSION:2.0
BEGIN:VFREEBUSY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
DTSTAMP:19970613T190000Z
DTSTART:19970701T080000Z
DTEND:19970701T200000
UID:calsrv.example.com-873970198738777@example.com
END:VFREEBUSY
END:VCALENDAR
"B" sends a "REPLY" method type of a "VFREEBUSY" calendar component to 4.3.2 Reply To A Busy Time Request
"A"
BEGIN:VCALENDAR "B" sends a "REPLY" method type of a "VFREEBUSY" calendar component
PRODID:-//ACME/DesktopCalendar//EN to "A"
METHOD:REPLY
VERSION:2.0
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:A@example.com
ATTENDEE:Mailto:B@example.com
DTSTART:19970701T080000Z
DTEND:19970701T200000Z
UID:calsrv.example.com-873970198738777@example.com
FREEBUSY:19970701T090000Z/PT1H,19970701T140000Z/PT30M
DTSTAMP:19970613T190030Z
END:VFREEBUSY
END:VCALENDAR
"B" is busy from 09:00 to 10:00 and from 14:00 to 14:30. BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:A@example.com
ATTENDEE:Mailto:B@example.com
DTSTART:19970701T080000Z
DTEND:19970701T200000Z
UID:calsrv.example.com-873970198738777@example.com
FREEBUSY:19970701T090000Z/PT1H,19970701T140000Z/PT30M
DTSTAMP:19970613T190030Z
END:VFREEBUSY
END:VCALENDAR
"B" is busy from 09:00 to 10:00 and from 14:00 to 14:30.
4.4 Recurring Event and Time Zone Examples 4.4 Recurring Event and Time Zone Examples
4.4.1 A Recurring Event Spanning Time Zones 4.4.1 A Recurring Event Spanning Time Zones
This event describes a weekly phone conference. The "Attendees" are each This event describes a weekly phone conference. The "Attendees" are
in a different time zone. each in a different time zone.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America-SanJose TZID:America-SanJose
TZURL:http://zones.stds_r_us.net/tz/America-SanJose TZURL:http://zones.stds_r_us.net/tz/America-SanJose
BEGIN:STANDARD BEGIN:STANDARD
DTSTART:19671029T020000 DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0700 TZOFFSETFROM:-0700
TZOFFSETTO:-0800 TZOFFSETTO:-0800
TZNAME:PST TZNAME:PST
END:STANDARD END:STANDARD
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19870405T020000 DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZOFFSETFROM:-0800 TZOFFSETFROM:-0800
TZOFFSETTO:-0700 TZOFFSETTO:-0700
TZNAME:PDT TZNAME:PDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;TYPE=INDIVIDUAL:A@example.COM ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;TYPE=INDIVIDUAL:A@example.COM
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:B@example.fr ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:B@example.fr
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:c@example.jp ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:c@example.jp
DTSTAMP:19970613T190030Z DTSTAMP:19970613T190030Z
DTSTART;TZID=America-SanJose:19970701T140000 DTSTART;TZID=America-SanJose:19970701T140000
DTEND;TZID=America-SanJose:19970701T150000 DTEND;TZID=America-SanJose:19970701T150000
RRULE:FREQ=WEEKLY;INTERVAL=20;WKST=SU;BYDAY=TU RRULE:FREQ=WEEKLY;INTERVAL=20;WKST=SU;BYDAY=TU
RDATE;TZID=America-SanJose:19970910T140000 RDATE;TZID=America-SanJose:19970910T140000
EXDATE;TZID=America-SanJose:19970909T140000 EXDATE;TZID=America-SanJose:19970909T140000
EXDATE;TZID=America-SanJose:19971028T140000 EXDATE;TZID=America-SanJose:19971028T140000
SUMMARY:Weekly Phone Conference SUMMARY:Weekly Phone Conference
UID:calsrv.example.com-873970198738777@example.com UID:calsrv.example.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The first two components of this iCalendar object are the time zone The first two components of this iCalendar object are the time zone
components. The "DTSTART" date coincides with the first instance of the components. The "DTSTART" date coincides with the first instance of
RRULE property. the RRULE property.
The recurring meeting is defined in a particular time zone, presumably The recurring meeting is defined in a particular time zone,
that of the originator. The client for each "Attendee" has the presumably that of the originator. The client for each "Attendee" has
responsibility of determining the recurrence time in the "Attendee's" the responsibility of determining the recurrence time in the
time zone. "Attendee's" time zone.
The repeating event starts on Tuesday, July 1, 1997 at 2:00pm PDT. The repeating event starts on Tuesday, July 1, 1997 at 2:00pm PDT.
"Attendee" B@example.fr is in France where the local time on this date "Attendee" B@example.fr is in France where the local time on this
is 9 hours ahead of PDT or 23:00. "Attendee" C@example.jp is in Japan date is 9 hours ahead of PDT or 23:00. "Attendee" C@example.jp is in
where local time is 8 hours ahead of UTC or Wednesday, July 2 at 06:00. Japan where local time is 8 hours ahead of UTC or Wednesday, July 2
The event repeats weekly on Tuesdays (in PST/PDT). The "RRULE" property at 06:00. The event repeats weekly on Tuesdays (in PST/PDT). The
results in 20 instances. The last instance falls on Tuesday, November "RRULE" property results in 20 instances. The last instance falls on
11, 1997 2:00pm PDT. The "RDATE" property adds another instance: WED, Tuesday, November 11, 1997 2:00pm PDT. The "RDATE" property adds
10-SEP-1997 2:00 PM PST. another instance: WED, 10-SEP-1997 2:00 PM PST.
There are two exceptions to this recurring appointment. The first one There are two exceptions to this recurring appointment. The first one
is: is:
TUE, 09-SEP-1997 23:00 GMT TUE, 09-SEP-1997 23:00 GMT
TUE, 09-SEP-1997 14:00 PDT TUE, 09-SEP-1997 14:00 PDT
WED, 10-SEP-1997 06:00 JST WED, 10-SEP-1997 06:00 JST
and the second is: and the second is:
TUE, 28-OCT-1997 23:00 GMT TUE, 28-OCT-1997 23:00 GMT
TUE, 28-OCT-1997 14:00 PST TUE, 28-OCT-1997 14:00 PST
WED, 29-OCT-1997 06:00 JST WED, 29-OCT-1997 06:00 JST
4.4.2 Modify A Recurring Instance 4.4.2 Modify A Recurring Instance
In this example the "Organizer" issues a recurring meeting. Later the In this example the "Organizer" issues a recurring meeting. Later the
"Organizer" changes an instance of the event by changing the "DTSTART" "Organizer" changes an instance of the event by changing the
property. Note the use of "RECURRENCE-ID" property and "SEQUENCE" "DTSTART" property. Note the use of "RECURRENCE-ID" property and
property in the second request. "SEQUENCE" property in the second request.
Original Request: Original Request:
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:guid-1@host1.com UID:guid-1@host1.com
SEQUENCE:0 SEQUENCE:0
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com ATTENDEE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970601T210000Z DTSTART:19970601T210000Z
DTEND:19970601T220000Z DTEND:19970601T220000Z
LOCATION:Conference Call LOCATION:Conference Call
DTSTAMP:19970526T083000Z DTSTAMP:19970526T083000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The event request below is to change the time of a specific instance.
This changes the July 1st instance to July 3rd.
BEGIN:VCALENDAR The event request below is to change the time of a specific instance.
METHOD:REQUEST This changes the July 1st instance to July 3rd.
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1com
RECURRENCE-ID:19970701T210000Z
SEQUENCE:1
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970703T210000Z
DTEND:19970703T220000Z
LOCATION:Conference Call
DTSTAMP:19970626T093000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
4.4.3 Cancel an Instance BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1com
RECURRENCE-ID:19970701T210000Z
SEQUENCE:1
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970703T210000Z
DTEND:19970703T220000Z
LOCATION:Conference Call
DTSTAMP:19970626T093000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
In this example the "Organizer" of a recurring event deletes the August 4.4.3 Cancel an Instance
1st instance.
BEGIN:VCALENDAR In this example the "Organizer" of a recurring event deletes the
METHOD:CANCEL August 1st instance.
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
RECURRENCE-ID:19970801T210000Z
SEQUENCE:2
STATUS:CANCELLED
DTSTAMP:19970721T093000Z
END:VEVENT
END:VCALENDAR
4.4.4 Cancel Recurring Event
In this example the "Organizer" wishes to cancel the entire recurring BEGIN:VCALENDAR
event and any exceptions. METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
RECURRENCE-ID:19970801T210000Z
SEQUENCE:2
STATUS:CANCELLED
DTSTAMP:19970721T093000Z
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.4.4 Cancel Recurring Event
METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
DTSTAMP:19970721T103000Z
STATUS:CANCELLED
SEQUENCE:3
END:VEVENT
END:VCALENDAR
4.4.5 Change All Future Instances In this example the "Organizer" wishes to cancel the entire recurring
event and any exceptions.
This example changes the meeting location from a conference call to BEGIN:VCALENDAR
Seattle starting September 1 and extends to all future instances. METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
ATTENDEE:Mailto:D@example.com
DTSTAMP:19970721T103000Z
STATUS:CANCELLED
SEQUENCE:3
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.4.5 Change All Future Instances
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
RECURRENCE-ID;THISANDFUTURE:19970901T210000Z
SEQUENCE:3
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Discussion
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970901T210000Z
DTEND:19970901T220000Z
LOCATION:Building 32, Microsoft, Seattle, WA
DTSTAMP:19970526T083000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
4.4.6 Add A New Instance To A Recurring Event
This example adds a one-time additional instance to the recurring event. This example changes the meeting location from a conference call to
"Organizer" adds a second July meeting on the 15th. Seattle starting September 1 and extends to all future instances.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:ADD METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:123456789@host1.com UID:guid-1@host1.com
SEQUENCE:4 RECURRENCE-ID;THISANDFUTURE:19970901T210000Z
ORGANIZER:Mailto:A@example.com SEQUENCE:3
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com ATTENDEE;RSVP=TRUE:Mailto:C@example.com
DESCRIPTION:IETF-C&S Conference Call ATTENDEE;RSVP=TRUE:Mailto:D@example.com
CLASS:PUBLIC DESCRIPTION:IETF-C&S Discussion
SUMMARY:IETF Calendaring Working Group Meeting CLASS:PUBLIC
DTSTART:19970715T210000Z SUMMARY:IETF Calendaring Working Group Meeting
DTEND:19970715T220000Z DTSTART:19970901T210000Z
LOCATION:Conference Call DTEND:19970901T220000Z
DTSTAMP:19970629T093000Z LOCATION:Building 32, Microsoft, Seattle, WA
STATUS:CONFIRMED DTSTAMP:19970526T083000Z
END:VEVENT STATUS:CONFIRMED
END:VCALENDAR END:VEVENT
END:VCALENDAR
4.4.7 Add A New Series of Instances To A Recurring Event 4.4.6 Add A New Instance To A Recurring Event
The scenario for this example involves an ongoing meeting, originally This example adds a one-time additional instance to the recurring
set up to occur every Tuesday. The "Organizer" later decides that the event. "Organizer" adds a second July meeting on the 15th.
meetings need to be on Tuesdays and Thursdays, but does not want to
reschedule the entire meeting or lose any of the per-instance
information already collected.
The original event: BEGIN:VCALENDAR
METHOD:ADD
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:4
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970715T210000Z
DTEND:19970715T220000Z
LOCATION:Conference Call
DTSTAMP:19970629T093000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR 4.4.7 Add A New Series of Instances To A Recurring Event
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:0
RRULE:WKST=SU;BYDAY=TU;FREQ=WEEKLY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980303T210000Z
DTEND:19980303T220000Z
LOCATION:The White Room
DTSTAMP:19980301T093000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
Assume that many other updates happen to this event and that a lot of The scenario for this example involves an ongoing meeting, originally
instance-specific information exists in the recurring series. The set up to occur every Tuesday. The "Organizer" later decides that
"SEQUENCE" property value is 7 for the next update. Now the "Organizer" the meetings need to be on Tuesdays and Thursdays, but does not want
wants to add Thursdays to the event: to reschedule the entire meeting or lose any of the per-instance
information already collected.
BEGIN:VCALENDAR The original event:
METHOD:ADD
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:7
RRULE:WKST=SU;BYDAY=TH;FREQ=WEEKLY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980303T210000Z
DTEND:19980303T220000Z
DTSTAMP:19980303T193000Z
LOCATION:The Usual conference room
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
Alternatively, if the "Organizer" is not concerned with per-instance BEGIN:VCALENDAR
updates, the entire event can be rescheduled using a "REQUEST". This is METHOD:REQUEST
done by using the "UID" of the event to reschedule and including the PRODID:-//RDU Software//NONSGML HandCal//EN
modified "RRULE". Note, that since this is an entire rescheduling of the VERSION:2.0
event, any instance-specific information will be lost. BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:0
RRULE:WKST=SU;BYDAY=TU;FREQ=WEEKLY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980303T210000Z
DTEND:19980303T220000Z
LOCATION:The White Room
DTSTAMP:19980301T093000Z
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR Assume that many other updates happen to this event and that a lot of
METHOD:REQUEST instance-specific information exists in the recurring series. The
PRODID:-//RDU Software//NONSGML HandCal//EN "SEQUENCE" property value is 7 for the next update. Now the
VERSION:2.0 "Organizer" wants to add Thursdays to the event:
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:7
RRULE:WKST=SU;BYDAY=TU,TH;FREQ=WEEKLY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980303T210000Z
DTEND:19980303T220000Z
DTSTAMP:19980303T193000Z
LOCATION:The White Room
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
The next series of examples illustrate how an "Organizer" would respond BEGIN:VCALENDAR
to a "REFRESH" submitted by an "Attendee" after a series of instance- METHOD:ADD
specific modifications. To convey all instance-specific changes, the PRODID:-//RDU Software//NONSGML HandCal//EN
"Organizer" must provide the latest event description and the relevant VERSION:2.0
instances. The first three examples show the history including the BEGIN:VEVENT
initial "VEVENT" request and subsequent instance changes and finally the UID:123456789@host1.com
"REFRESH". SEQUENCE:7
RRULE:WKST=SU;BYDAY=TH;FREQ=WEEKLY
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980303T210000Z
DTEND:19980303T220000Z
DTSTAMP:19980303T193000Z
LOCATION:The Usual conference room
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
Original Request: Alternatively, if the "Organizer" is not concerned with per-instance
updates, the entire event can be rescheduled using a "REQUEST". This
is done by using the "UID" of the event to reschedule and including
the modified "RRULE". Note, that since this is an entire rescheduling
of the event, any instance-specific information will be lost.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:123456789@host1.com UID:123456789@host1.com
SEQUENCE:0 SEQUENCE:7
RDATE:19980304T180000Z RRULE:WKST=SU;BYDAY=TU,TH;FREQ=WEEKLY
RDATE:19980311T180000Z ORGANIZER:Mailto:A@example.com
RDATE:19980318T180000Z ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ORGANIZER:Mailto:A@example.com ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com SUMMARY:Review Accounts
ATTENDEE;RSVP=TRUE:Mailto:B@example.com DTSTART:19980303T210000Z
SUMMARY:Review Accounts DTEND:19980303T220000Z
DTSTART:19980304T180000Z DTSTAMP:19980303T193000Z
DTEND:19980304T200000Z LOCATION:The White Room
DTSTAMP:19980303T193000Z STATUS:CONFIRMED
LOCATION:Conference Room A END:VEVENT
STATUS:CONFIRMED END:VCALENDAR
END:VEVENT
END:VCALENDAR
Organizer changes 2nd instance Location and Time: The next series of examples illustrate how an "Organizer" would
respond to a "REFRESH" submitted by an "Attendee" after a series of
instance-specific modifications. To convey all instance-specific
changes, the "Organizer" must provide the latest event description
and the relevant instances. The first three examples show the history
including the initial "VEVENT" request and subsequent instance
changes and finally the "REFRESH".
BEGIN:VCALENDAR Original Request:
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:1
RECURRENCE-ID:19980311T180000Z
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980311T160000Z
DTEND:19980311T180000Z
DTSTAMP:19980306T193000Z
LOCATION:The Small conference room
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
Organizer adds a 4th instance of the meeting using the "ADD" method BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:0
RDATE:19980304T180000Z
RDATE:19980311T180000Z
RDATE:19980318T180000Z
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980304T180000Z
DTEND:19980304T200000Z
DTSTAMP:19980303T193000Z
LOCATION:Conference Room A
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR Organizer changes 2nd instance Location and Time:
METHOD:ADD
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:2
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980315T180000Z
DTEND:19980315T200000Z
DTSTAMP:19980307T193000Z
LOCATION:Conference Room A
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
If "B" requests a "REFRESH", "A" responds with the following to capture BEGIN:VCALENDAR
all instance-specific data. In this case both the initial request and an METHOD:REQUEST
additional "VEVENT" that specifies the instance-specific data are PRODID:-//RDU Software//NONSGML HandCal//EN
included. Because these are both of the same type (they are both VERSION:2.0
"VEVENTS"), they can be conveyed in the same iCalendar object. BEGIN:VEVENT
UID:123456789@host1.com
SEQUENCE:1
RECURRENCE-ID:19980311T180000Z
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980311T160000Z
DTEND:19980311T180000Z
DTSTAMP:19980306T193000Z
LOCATION:The Small conference room
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
Organizer adds a 4th instance of the meeting using the "ADD" method
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:ADD
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:123456789@host1.com UID:123456789@host1.com
SEQUENCE:2 SEQUENCE:2
RDATE:19980304T180000Z ORGANIZER:Mailto:A@example.com
RDATE:19980311T160000Z ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
RDATE:19980315T180000Z ATTENDEE;RSVP=TRUE:Mailto:B@example.com
Error! Bookmark not defined. SUMMARY:Review Accounts
ORGANIZER:Mailto:A@example.com DTSTART:19980315T180000Z
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com DTEND:19980315T200000Z
ATTENDEE;RSVP=TRUE:Mailto:B@example.com DTSTAMP:19980307T193000Z
SUMMARY:Review Accounts LOCATION:Conference Room A
DTSTART:19980304T180000Z STATUS:CONFIRMED
DTEND:19980304T200000Z END:VEVENT
DTSTAMP:19980303T193000Z END:VCALENDAR
LOCATION:Conference Room A
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT If "B" requests a "REFRESH", "A" responds with the following to
Error! Bookmark not defined. capture all instance-specific data. In this case both the initial
request and an additional "VEVENT" that specifies the instance-
specific data are included. Because these are both of the same type
(they are both "VEVENTS"), they can be conveyed in the same iCalendar
object.
SEQUENCE:2 BEGIN:VCALENDAR
RECURRENCE-ID:19980311T160000Z METHOD:REQUEST
Error! Bookmark not defined. PRODID:-//RDU Software//NONSGML HandCal//EN
ATTENDEE;ROLE=CHAIR;Error! Bookmark not defined. VERSION:2.0
ATTENDEE;Error! Bookmark not defined. BEGIN:VEVENT
SUMMARY:Review Accounts UID:123456789@host1.com
DTSTART:19980311T160000Z SEQUENCE:2
DTEND:19980304T180000Z RDATE:19980304T180000Z
DTSTAMP:19980306T193000Z RDATE:19980311T160000Z
LOCATION:The Small conference room RDATE:19980315T180000Z
STATUS:CONFIRMED Error! Bookmark not defined.
END:VEVENT ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SUMMARY:Review Accounts
DTSTART:19980304T180000Z
DTEND:19980304T200000Z
DTSTAMP:19980303T193000Z
LOCATION:Conference Room A
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR BEGIN:VEVENT
Error! Bookmark not defined.
SEQUENCE:2
RECURRENCE-ID:19980311T160000Z
Error! Bookmark not defined.
ATTENDEE;ROLE=CHAIR;Error! Bookmark not defined.
ATTENDEE;Error! Bookmark not defined.
SUMMARY:Review Accounts
DTSTART:19980311T160000Z
DTEND:19980304T180000Z
DTSTAMP:19980306T193000Z
LOCATION:The Small conference room
STATUS:CONFIRMED
END:VEVENT
4.4.8 Counter An Instance Of A Recurring Event END:VCALENDAR
In this example one of the "Attendees" counters the "DTSTART" property 4.4.8 Counter An Instance Of A Recurring Event
of the proposed second July meeting.
BEGIN:VCALENDAR In this example one of the "Attendees" counters the "DTSTART"
METHOD:COUNTER property of the proposed second July meeting.
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
RECURRENCE-ID:19970715T210000Z
SEQUENCE:4
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;RSVP=TRUE:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970715T220000Z
DTEND:19970715T230000Z
LOCATION:Conference Call
COMMENT:May we bump this by an hour? I have a conflict
DTSTAMP:19970629T094000Z
END:VEVENT
END:VCALENDAR
4.4.9 Error Reply To A Request BEGIN:VCALENDAR
METHOD:COUNTER
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
RECURRENCE-ID:19970715T210000Z
SEQUENCE:4
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;RSVP=TRUE:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970715T220000Z
DTEND:19970715T230000Z
LOCATION:Conference Call
COMMENT:May we bump this by an hour? I have a conflict
DTSTAMP:19970629T094000Z
END:VEVENT
END:VCALENDAR
The following example illustrates a scenario where a meeting is proposed 4.4.9 Error Reply To A Request
containing an unsupported property and a bad property.
Original Request The following example illustrates a scenario where a meeting is
BEGIN:VCALENDAR proposed containing an unsupported property and a bad property.
METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VEVENT
UID:guid-1@host1.com
SEQUENCE:0
RRULE:FREQ=MONTHLY;BYMONTHDAY=1
ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970601T210000Z
DTEND:19970601T220000Z
DTSTAMP:19970602T094000Z
LOCATION:Conference Call
STATUS:CONFIRMED
FOO:BAR
END:VEVENT
END:VCALENDAR
Response from "B" to indicate that RRULE is not supported and an Original Request
unrecognized property was encountered
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN METHOD:REQUEST
METHOD:REPLY PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com UID:guid-1@host1.com
ATTENDEE:Mailto:B@example.com SEQUENCE:0
REQUEST-STATUS:2.8;Repeating event ignored. Scheduled as a single RRULE:FREQ=MONTHLY;BYMONTHDAY=1
event;RRULE ORGANIZER:Mailto:A@example.com
REQUEST-STATUS:3.0;Invalid Property Name;FOO ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
UID:guid-1@host1.com ATTENDEE;RSVP=TRUE:Mailto:B@example.com
SEQUENCE:0 ATTENDEE;RSVP=TRUE:Mailto:C@example.com
DTSTAMP:19970603T094000Z ATTENDEE;RSVP=TRUE:Mailto:D@example.com
END:VEVENT DESCRIPTION:IETF-C&S Conference Call
END:VCALENDAR CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970601T210000Z
DTEND:19970601T220000Z
DTSTAMP:19970602T094000Z
LOCATION:Conference Call
STATUS:CONFIRMED
FOO:BAR
END:VEVENT
END:VCALENDAR
Response from "B" to indicate that RRULE is not supported and an
unrecognized property was encountered
BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN
METHOD:REPLY
VERSION:2.0
BEGIN:VEVENT
ORGANIZER:Mailto:A@example.com
ATTENDEE:Mailto:B@example.com
REQUEST-STATUS:2.8;Repeating event ignored. Scheduled as a single
event;RRULE
REQUEST-STATUS:3.0;Invalid Property Name;FOO
UID:guid-1@host1.com
SEQUENCE:0
DTSTAMP:19970603T094000Z
END:VEVENT
END:VCALENDAR
4.5 Group To-do Examples 4.5 Group To-do Examples
Individual "A" creates a group task in which individuals "A", "B", "C" Individual "A" creates a group task in which individuals "A", "B",
and "D" will participate. Individual "B" confirms acceptance of the "C" and "D" will participate. Individual "B" confirms acceptance of
task. Individual "C" declines the task. Individual "D" tentatively the task. Individual "C" declines the task. Individual "D"
accepts the task. The following table illustrates the sequence of tentatively accepts the task. The following table illustrates the
messages that would be exchanged between these individuals. Individual sequence of messages that would be exchanged between these
"A" then issues a "REQUEST" method to obtain the status of the to-do individuals. Individual "A" then issues a "REQUEST" method to obtain
from each participant. The response indicates the individual the status of the to-do from each participant. The response indicates
"Attendee's" completion status. The table below illustrates the message the individual "Attendee's" completion status. The table below
flow. illustrates the message flow.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Initiate a to-do | "A" sends a REQUEST | | | Initiate a to-do | "A" sends a REQUEST | |
| request | message to "B", "C",| | | request | message to "B", "C",| |
| | and "D" | | | | and "D" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Accept the to-do | | "B" sends a "REPLY" | | Accept the to-do | | "B" sends a "REPLY" |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | "partstat" paramater | | | | "partstat" paramater |
| | | set to "accepted". | | | | set to "accepted". |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Decline the to-do | | "C" sends a REPLY | | Decline the to-do | | "C" sends a REPLY |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | "partstat" parameter | | | | "partstat" parameter |
| | | set to "declined". | | | | set to "declined". |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Tentatively accept | | "D" sends a REPLY | | Tentatively accept | | "D" sends a REPLY |
| the to-do request | | message to "A" with its | | the to-do request | | message to "A" with its |
| | | "partstat" parameter | | | | "partstat" parameter |
| | | set to "tentative". | | | | set to "tentative". |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Check attendee | "A" sends a REQUEST | | | Check attendee | "A" sends a REQUEST | |
| completion status | message to "B" and | | | completion status | message to "B" and | |
| | "D" with current | | | | "D" with current | |
| | information. | | | | information. | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Attendee indicates | | "B" sends a "REPLY" | | Attendee indicates | | "B" sends a "REPLY" |
| percent complete | | message indicating | | percent complete | | message indicating |
| | | percent complete | | | | percent complete |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Attendee indicates | | "D" sends a "REPLY" | | Attendee indicates | | "D" sends a "REPLY" |
| completion | | message indicating | | completion | | message indicating |
| | | completion | | | | completion |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4.5.1 A VTODO Request 4.5.1 A VTODO Request
A sample "REQUEST" for a "VTODO" calendar component that "A" sends to A sample "REQUEST" for a "VTODO" calendar component that "A" sends to
"B", "C", and "D". "B", "C", and "D".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR:Mailto:A@example.com ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
ATTENDEE;RSVP=TRUE:Mailto:B@example.com ATTENDEE;RSVP=TRUE:Mailto:B@example.com
ATTENDEE;RSVP=TRUE:Mailto:C@example.com ATTENDEE;RSVP=TRUE:Mailto:C@example.com
ATTENDEE;RSVP=TRUE:Mailto:D@example.com ATTENDEE;RSVP=TRUE:Mailto:D@example.com
DTSTART:19970701T170000Z DTSTART:19970701T170000Z
DUE:19970722T170000Z DUE:19970722T170000Z
PRIORITY:1 PRIORITY:1
SUMMARY:Create the requirements document SUMMARY:Create the requirements document
UID:calsrv.example.com-873970198738777-00@example.com UID:calsrv.example.com-873970198738777-00@example.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970717T200000Z DTSTAMP:19970717T200000Z
STATUS:Needs Action STATUS:Needs Action
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.5.2 A VTODO Reply 4.5.2 A VTODO Reply
"B" accepts the to-do. "B" accepts the to-do.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;PARTSTAT=ACCEPTED:Mailto:B@example.com ATTENDEE;PARTSTAT=ACCEPTED:Mailto:B@example.com
UID:calsrv.example.com-873970198738777-00@example.com UID:calsrv.example.com-873970198738777-00@example.com
COMMENT:I'll send you my input by e-mail COMMENT:I'll send you my input by e-mail
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970717T203000Z DTSTAMP:19970717T203000Z
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
"B" could have declined the TODO or indicated tentative acceptance by "B" could have declined the TODO or indicated tentative acceptance by
setting the "partstat" property parameter sequence to "declined" or setting the "partstat" property parameter sequence to "declined" or
"tentative", respectively. "tentative", respectively.
4.5.3 A VTODO Request for Updated Status 4.5.3 A VTODO Request for Updated Status
"A" requests status from all "Attendees". "A" requests status from all "Attendees".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR:Mailto:A@example.com ATTENDEE;ROLE=CHAIR:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:D@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:D@example.com
UID:calsrv.example.com-873970198738777-00@example.com UID:calsrv.example.com-873970198738777-00@example.com
SUMMARY:Create the requirements document SUMMARY:Create the requirements document
PRIORITY:1 PRIORITY:1
SEQUENCE:0 SEQUENCE:0
STATUS:IN-PROCESS STATUS:IN-PROCESS
DTSTART:19970701T170000Z DTSTART:19970701T170000Z
DTSTAMP:19970717T230000Z DTSTAMP:19970717T230000Z
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.5.4 A Reply: Percent-Complete 4.5.4 A Reply: Percent-Complete
A reply indicating the task being worked on and that "B" is 75% complete A reply indicating the task being worked on and that "B" is 75%
with "B's" part of the assignment. complete with "B's" part of the assignment.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ORGANIZER:MAILTO:A@example.com ORGANIZER:MAILTO:A@example.com
ATTENDEE;PARTSTAT=IN-PROCESS:Mailto:B@example.