draft-ietf-calsch-itip-02.txt   draft-ietf-calsch-itip-03.txt 
Network Working Group Steve Silverberg, Microsoft Network Working Group Steve Silverberg, Microsoft
INTERNET-DRAFT Steve Mansour, Netscape INTERNET-DRAFT Steve Mansour, Netscape
Calendaring and Scheduling Working Group Frank Dawson, Lotus Calendaring and Scheduling Working Group Frank Dawson, Lotus
<ietf-draft-calsch-itip-02.txt> Ross Hopson, ON Technologies <ietf-draft-calsch-itip-03.txt Ross Hopson, ON Technologies
Expires in six months from November 21,1997 Expires in six months from March 13, 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 This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas, and
and its working groups. Note that other groups MAY also distribute its working groups. Note that other groups may also distribute working
working documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months.
months. Internet-Drafts MAY be updated, replaced, or made obsolete by Internet-Drafts may be updated, replaced, or made obsolete by other
other documents at any time. It is not appropriate to use Internet- documents at any time. It is not appropriate to use Internet-Drafts as
Drafts as reference material or to cite them other than as a "working reference material or to cite them other than as a "working draft" or
draft" or "work in progress". "work in progress".
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the 1id-
1id-abstracts.txt listing contained in the Internet-Drafts Shadow abstracts.txt listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Rim).
Distribution of this document is unlimited. Distribution of this document is unlimited.
Copyright (C) The Internet Society 1997. All Rights Reserved. Copyright (C) The Internet Society 1997. All Rights Reserved.
Abstract Abstract
This document specifies how calendaring systems use iCalendar objects to
This document specifies how calendaring systems use iCalendar objects interoperate with other calendar systems. It does so in a general way so
to interoperate with other calendar systems. It does so in a general as to allow multiple methods of communication between systems.
way so as to allow multiple methods of communication between systems.
Subsequent documents specify interoperable methods of communications Subsequent documents specify interoperable methods of communications
between systems that use this protocol. between systems that use this protocol.
The document outlines a model for calendar exchange that defines both The document outlines a model for calendar exchange that defines both
static and dynamic event, to-do, journal and free/busy objects. static and dynamic event, to-do, journal and free/busy objects. Static
Static objects are used to transmit information from one entity to objects are used to transmit information from one entity to another
another without the expectation of continuity or referential without the expectation of continuity or referential integrity with the
integrity with the original item. Dynamic objects are a superset of original item. Dynamic objects are a superset of static objects and will
static objects and will gracefully degrade to their static gracefully degrade to their static counterparts for clients that only
counterparts for clients that only support static objects. support static objects.
Silverberg/Mansour/Dawson/Hopson 1 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 1 Expires September 1998
Silverberg/Mansour/Dawson/Hopson 2 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 2 Expires September 1998
Silverberg/Mansour/Dawson/Hopson 3 Expires September 1998
Silverberg/Mansour/Dawson/Hopson 3 Expires MAY 1998
Table of Contents Table of Contents
1 8 1 INTRODUCTION.........................................................9
Introduction 9
1.1 Formatting Conventions 9
1.2 Related Documents 10
1.3 Calendar Roles 10
1.4 iTIP Transactions 11
2 Interoperability Models 12
2.1 Application Protocol 12
2.1.1 Calendar Entry State 13
3 Application Protocol Elements 13
3.1 Methods For "VEVENT" Calendar Component 15
3.1.1 PUBLISH 15
3.1.2 REQUEST 16
3.1.2.1 REQUEST for Rescheduling an Event 18
3.1.2.2 REQUEST for Update or Reconfirmation of an Event 18
3.1.2.3 REQUEST for Delegating an Event from an "Attendee" to
another CU 18
3.1.2.4 REQUEST for Delegating role of "Organizer" to another CU 19
3.1.2.5 REQUEST for Changing the "Organizer" from one CU to another
19
3.1.2.6 REQUEST for Changing the "Owner" 19
3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User 20
3.1.2.8 REQUEST Updated Attendee Status 20
3.1.3 REPLY 20
3.1.4 CANCEL 21
3.1.5 REFRESH 22
3.1.6 COUNTER 23
3.1.7 DECLINECOUNTER 24
3.2 Methods For VFREEBUSY Component 25
3.2.1 PUBLISH 26
3.2.2 REQUEST 27
3.2.3 REPLY 28
3.3 Methods For VTODO Component 29
3.3.1 PUBLISH 30
3.3.2 REQUEST 31
3.3.2.1 REQUEST for Rescheduling a VTODO 32
3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO 33
3.3.2.3 REQUEST for Delegating a VTODO 33
3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User 34
3.3.2.5 REQUEST Updated Attendee Status 34
3.3.3 REPLY 35
3.3.4 CANCEL 36
3.3.5 REFRESH 37
3.3.6 COUNTER 37
3.3.7 DECLINECOUNTER 38
3.4 Methods For VJOURNAL Component 39
3.4.1 PUBLISH 40
3.4.2 CANCEL 41
3.4.3 REFRESH 41
3.5 Status Replies 42
Silverberg/Mansour/Dawson/Hopson 4 Expires MAY 1998 1.1 FORMATTING CONVENTIONS ...........................................9
3.6 Implementation Considerations 44 1.2 RELATED DOCUMENTS ...............................................10
3.6.1 Working With Recurrence Instances 44 1.3 ITIP ROLES AND TRANSACTIONS .....................................10
3.6.2 Attendee Property Considerations 45
3.6.3 When To Refresh An Event 46
3.6.4 Timezones 46
3.6.5 Alarms 46
3.6.6 SUMMARY Property 46
3.6.7 X-Tokens 47
4 Examples 47
4.1 Published Event Examples 47
4.1.1 A Minimal Published Event 47
4.1.2 Changing A Published Event 48
4.1.3 Canceling A Published Event 49
4.1.4 A Rich Published Event 49
4.1.5 Anniversaries or Events attached to entire days 51
4.2 Group Event Examples 51
4.2.1 A Group Event Request 52
4.2.2 Reply To A Group Event Request 52
4.2.3 Update An Event 53
4.2.4 Countering an Event Proposal 53
4.2.5 Delegate An Event 55
4.2.6 Delegate Accepts the Meeting 58
4.2.7 Delegate Declines the Meeting 58
4.2.8 Forwarding an Event Request 59
4.2.9 Cancel A Group Event 59
4.3 Busy Time Examples 60
4.3.1 Request Busy Time 60
4.3.2 Reply To A Busy Time Request 61
4.4 Recurring Event and Time Zone Examples 61
4.4.1 A Recurring Event Spanning Time Zones 61
4.4.2 Modify A Recurring Instance 63
4.4.3 Cancel A Recurring Instance 64
4.4.4 Cancel An Exception 65
4.4.5 Cancel Recurring Event 65
4.4.6 Change All Future Instances 65
4.4.7 Add A New Instance To A Recurring Event 66
4.4.8 Counter An Instance Of A Recurring Event 67
4.4.9 Error Reply To A request 67
4.5 Group To-do Examples 68
4.5.1 A VTODO Request 69
4.5.2 A VTODO Reply 70
4.5.3 A VTODO Refresh 70
4.5.4 A Refresh Reply: Percent-Complete 71
4.5.5 A Refresh Reply: Completed 71
4.5.6 An Updated VTODO Request 71
4.5.7 A Recurring VTODOs 72
4.5.7.1 Request for a Recurring VTODO 72
4.5.7.2 Calculating due dates in recurring VTODOs 72
4.5.7.3 Replying to an instance of a recurring VTODO 73
4.6 Journal Examples 73
4.7 Other Examples 74
4.7.1 Event Refresh 74
4.7.2 Bad RECURRENCE-ID 74
5 Application Protocol Fallbacks 75
Silverberg/Mansour/Dawson/Hopson 5 Expires MAY 1998 2 INTEROPERABILITY MODELS.............................................11
5.1 Partial Implementation 75
5.1.1 Event-Related Fallbacks 76
5.1.2 To-Do-Related Fallbacks 77
5.1.3 Journal-Related Fallbacks 79
5.2 Latency Issues 80
5.2.1 Cancellation of an Unknown Calendar Component. 80
5.2.2 Unexpected Reply from an Unknown Delegate 80
5.3 Sequence Number 81
6 Security Considerations 81
6.1 Security Threats 81
6.1.1 Spoofing the "Organizer" 81
6.1.2 Spoofing the "Attendee" 82
6.1.3 Eavesdropping 82
6.1.4 Flooding a Calendar 82
6.1.5 Procedural Alarms 82
6.2 Recommendations 82
6.2.1 Use of [RFC1847] to secure iTIP transactions 82
6.2.2 Implementation Controls 83
7 Acknowledgments 83
8 Bibliography 83
9 Authors Addresses 84
10 Full Copyright Statement 85
1 2.1 APPLICATION PROTOCOL ............................................12
2.1.1 Calendar Entry State ........................................12
2.1.2 Delegation ..................................................13
2.1.3 Acting on Behalf of other Calendar Users ....................13
Silverberg/Mansour/Dawson/Hopson 6 Expires MAY 1998 3 APPLICATION PROTOCOL ELEMENTS.......................................13
Introduction
This document specifies how calendaring systems use iCalendar objects 3.1 COMMON COMPONENT RESTRICTION TABLES .............................14
to interoperate with other calendar systems. In particular, it 3.2 METHODS FOR VEVENT CALENDAR COMPONENTS ..........................15
specifies how to schedule events, to-dos, or daily journal entries. 3.2.1 PUBLISH .....................................................16
It further specifies how to search for available busy time 3.2.2 REQUEST .....................................................17
information. It does so in a general way so as to allow multiple 3.2.2.1 Rescheduling an Event....................................18
methods of communication between systems. Subsequent documents 3.2.2.2 Updating or Reconfirmation of an Event...................19
specify interoperable methods of communications between systems that 3.2.2.3 Delegating an Event to another CU........................19
use this protocol. 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.................................20
3.2.3 REPLY .......................................................20
3.2.4 ADD .........................................................22
3.2.5 CANCEL ......................................................23
3.2.6 REFRESH .....................................................25
3.2.7 COUNTER .....................................................26
3.2.8 DECLINECOUNTER ..............................................28
3.3 METHODS FOR VFREEBUSY COMPONENTS ................................29
3.3.1 PUBLISH .....................................................30
3.3.2 REQUEST .....................................................31
3.3.3 REPLY .......................................................32
3.4 METHODS FOR VTODO COMPONENTS ....................................34
3.4.1 PUBLISH .....................................................35
3.4.2 REQUEST .....................................................36
3.4.2.1 REQUEST for Rescheduling a VTODO.........................37
3.4.2.2 REQUEST for Update or Reconfirmation of a VTODO..........38
3.4.2.3 REQUEST for Delegating a VTODO...........................38
3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User..........39
3.4.2.5 REQUEST Updated Attendee Status..........................39
3.4.3 REPLY .......................................................39
3.4.4 ADD .........................................................41
3.4.5 CANCEL ......................................................42
3.4.6 REFRESH .....................................................43
3.4.7 COUNTER .....................................................45
3.4.8 DECLINECOUNTER ..............................................46
3.5 METHODS FOR VJOURNAL COMPONENTS .................................47
This protocol is based on requests sent from an originator and Silverberg/Mansour/Dawson/Hopson 4 Expires September 1998
conveyed to one or more recipients. A recipient of a request MAY 3.5.1 PUBLISH .....................................................47
reply, in order to update their status and MAY also return 3.5.2 ADD .........................................................49
transaction/request status information. The protocol also supports 3.5.3 CANCEL ......................................................50
the ability for the entry originator to modify or cancel the original 3.6 STATUS REPLIES ..................................................51
entry. The elements of the protocol also include the notion of user 3.7 IMPLEMENTATION CONSIDERATIONS ...................................53
roles. 3.7.1 Working With Recurrence Instances ...........................53
3.7.2 Attendee Property Considerations ............................54
3.7.3 X-Tokens ....................................................55
4 EXAMPLES............................................................55
4.1 PUBLISHED EVENT EXAMPLES ........................................55
4.1.1 A Minimal Published Event ...................................56
4.1.2 Changing A Published Event ..................................56
4.1.3 Canceling A Published Event .................................57
4.1.4 A Rich Published Event ......................................57
4.1.5 Anniversaries or Events attached to entire days .............58
4.2 GROUP EVENT EXAMPLES ............................................59
4.2.1 A Group Event Request .......................................60
4.2.2 Reply To A Group Event Request ..............................60
4.2.3 Update An Event .............................................61
4.2.4 Countering an Event Proposal ................................61
4.2.5 Delegating an Event .........................................63
4.2.6 Delegate Accepts the Meeting ................................65
4.2.7 Delegate Declines the Meeting ...............................66
4.2.8 Forwarding an Event Request .................................67
4.2.9 Cancel A Group Event ........................................67
4.2.10 Removing Attendees .........................................68
4.2.11 Replacing the Organizer ....................................69
4.3 BUSY TIME EXAMPLES ..............................................70
4.3.1 Request Busy Time ...........................................70
4.3.2 Reply To A Busy Time Request ................................71
4.4 RECURRING EVENT AND TIME ZONE EXAMPLES ..........................71
4.4.1 A Recurring Event Spanning Time Zones .......................71
4.4.2 Modify A Recurring Instance .................................73
4.4.3 Cancel an Instance ..........................................74
4.4.4 Cancel Recurring Event ......................................75
4.4.5 Change All Future Instances .................................75
4.4.6 Add A New Instance To A Recurring Event .....................75
4.4.7 Add A New Series of Instances To A Recurring Event ..........76
4.4.8 Counter An Instance Of A Recurring Event ....................80
4.4.9 Error Reply To A Request ....................................80
4.5 GROUP TO-DO EXAMPLES ............................................81
4.5.1 A VTODO Request .............................................82
4.5.2 A VTODO Reply ...............................................83
4.5.3 A VTODO Request for Updated Status ..........................83
4.5.4 A Reply: Percent-Complete ...................................84
4.5.5 A Reply: Completed ..........................................84
4.5.6 An Updated VTODO Request ....................................84
4.5.7 Recurring VTODOs ............................................85
4.5.7.1 Request for a Recurring VTODO............................85
4.5.7.2 Calculating due dates in recurring VTODOs................85
4.5.7.3 Replying to an instance of a recurring VTODO.............86
4.6 JOURNAL EXAMPLES ................................................86
Silverberg/Mansour/Dawson/Hopson 5 Expires September 1998
4.7 OTHER EXAMPLES ..................................................87
4.7.1 Event Refresh ...............................................87
4.7.2 Bad RECURRENCE-ID ...........................................87
5 APPLICATION PROTOCOL FALLBACKS......................................88
5.1 PARTIAL IMPLEMENTATION ..........................................88
5.1.1 Event-Related Fallbacks .....................................89
5.1.2 To-Do-Related Fallbacks .....................................90
5.1.3 Journal-Related Fallbacks ...................................92
5.2 LATENCY ISSUES ..................................................93
5.2.1 Cancellation of an Unknown Calendar Component. ..............93
5.2.2 Unexpected Reply from an Unknown Delegate ...................93
5.3 SEQUENCE NUMBER .................................................94
6 SECURITY CONSIDERATIONS.............................................94
6.1 SECURITY THREATS ................................................94
6.1.1 Spoofing the "Organizer" ....................................94
6.1.2 Spoofing the "Attendee" .....................................94
6.1.3 Unauthorized Replacement of the Organizer ...................95
6.1.4 Eavesdropping ...............................................95
6.1.5 Flooding a Calendar .........................................95
6.1.6 Procedural Alarms ...........................................95
6.1.7 Unauthorized REFRESH Requests ...............................95
6.2 RECOMMENDATIONS .................................................95
6.2.1 Use of [RFC1847] to secure iTIP transactions ................96
6.2.2 Implementation Controls .....................................96
7 ACKNOWLEDGMENTS.....................................................96
8 BIBLIOGRAPHY........................................................97
9 AUTHORS ADDRESSES...................................................98
10 FULL COPYRIGHT STATEMENT...........................................99
Silverberg/Mansour/Dawson/Hopson 6 Expires September 1998
1 Introduction
This document specifies how calendaring systems use iCalendar objects to
interoperate with other calendar systems. In particular, it specifies
how to schedule events, to-dos, or daily journal entries. It further
specifies how to search for available busy time information. It does so
in a general way so as to allow multiple methods of communication
between systems. Subsequent documents specify transport bindings between
systems that use this protocol.
This protocol is based on messages sent from an originator to one or
more recipients. For certain types of messages, a recipient may reply,
in order to update their status and may also return transaction/request
status information. The protocol supports the ability for the message
originator to modify or cancel the original message. The protocol also
supports the ability for recipients to suggest changes to the originator
of a message. The elements of the 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 In order to refer to elements of the calendaring and scheduling model,
model, core object or interoperability protocol defined in [ICMS], core object or interoperability protocol defined in [ICMS], [ICAL] and
[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 interopreted as described in [RFC 2119]. document are to be interpreted as described in [RFC 2119].
Calendaring and scheduling roles defined by [ICMS] are referred to in Calendaring and scheduling roles described by [ICMS] are referred to in
quoted-strings of text with the first character of each word in upper quoted-strings of text with the first character of each word in upper
case. For example, "Organizer" refers to a role of a "Calendar User" case. For example, "Organizer" refers to a role of a "Calendar User"
within the scheduling protocol defined by [ITIP] Calendar components (CU) within the scheduling protocol defined by [ITIP]. Calendar
defined by [ICAL] are referred to with capitalized, quoted-strings of components defined by [ICAL] are referred to with capitalized, quoted-
text. All calendar components start with the letter "V". For example, strings of text. All calendar components start with the letter "V". For
"VEVENT" refers to the event calendar component, "VTODO" refers to example, "VEVENT" refers to the event calendar component, "VTODO" refers
the to-do calendar component and "VJOURNAL" refers to the daily to 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 recipient of a request uses to update their status with the "Organizer"
"Organizer" of the calendar component. of the calendar component.
Properties defined by [ICAL] are referred to with capitalized, Properties defined by [ICAL] are referred to with capitalized, quoted-
quoted-strings of text, followed by the word "property". For example, strings of text, followed by the word "property". For example,
"ATTENDEE" property refers to the iCalendar property used to convey "ATTENDEE" property refers to the iCalendar property used to convey the
the calendar address of a "Calendar User". Property parameters calendar address of a "Calendar User". Property parameters defined by
defined by this memo are referred to with lower case, quoted-strings this memo are referred to with lower case, quoted-strings of text,
of text, followed by the word "parameter". For example, "value" followed by the word "parameter". For example, "value" parameter refers
parameter refers to the iCalendar property parameter used to override to the iCalendar property parameter used to override the default data
the default data type for a property value. Enumerated values defined
Silverberg/Mansour/Dawson/Hopson 7 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 7 Expires September 1998
by this memo are referred to with capitalized text, either alone or
followed by the word "value".
In tables, the quoted-string text is specified without quotes in type for a property value. Enumerated values defined by this memo are
order to minimize the table length. referred to with capitalized text, either alone or followed by the word
"value".
In tables, the quoted-string text is specified without quotes in 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 standards. This document, [ITIP], specifies an interoperability protocol
protocol for scheduling between different implementations; for scheduling between different implementations. The related documents
are:
[ICMS] - describes the abstract model and defines common terms and [ICMS] - describes the abstract model and defines common terms and
concepts; concepts;
[ICAL] - specifies the objects, data types, properties and property [ICAL] - specifies the objects, data types, properties and property
parameters used in the protocols, along with the methods for parameters used in the protocols, along with the methods for
representing and encoding them; representing and encoding them;
[IRIP] - specifies an Internet real time protocol binding for [IRIP] - specifies an Internet real time protocol binding for
[ITIP]. [ITIP];
[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 definitions from these other memos. Where possible, references are made
made to the memo that provides for the specification of these to the memo that provides for the specification of these concepts or
concepts or definitions. definitions.
1.3 Calendar Roles
Roles are a behavior or set of activities performed by particular
groups of users or agents at a given state of the calendar
transaction. This specification describes 4 roles that determine a
range of actions and responsibilities specific to each role.
+=====================================================================+
| Role Name | Description |
|=====================================================================|
| Owner | The calendar entry owner is the only Calendar User |
| | allowed to directly modify an entry using the iTIP |
| | protocol. However, the Owner MAY delegate or |
| | assign an Organizer to manage the entry on their |
| | behalf. Usually, a calendar entry Owner is also the |
| | Organizer. |
| | |
| Organizer | The Organizer controls manipulation of the calendar |
| | entry. In most cases, the Owner and the Organizer |
| | are the same Calendar User. |
| | |
| Attendee | An Attendee is a Calendar User associated with |
Silverberg/Mansour/Dawson/Hopson 8 Expires MAY 1998
| | a calendar entry via a Request method issued by an | 1.3 ITIP Roles and Transactions
| | Organizer or another Attendee. Attendees are not |
| | capable of directly manipulating calendar entries, |
| | but MUST act through the Organizer. |
| | |
| Delegate | A Delegate is a proxy that acts on behalf of another |
| | Calendar User. ITIP addresses two forms of |
| | delegation: |
| | 1) An Owner MAY delegate or re-assign an Organizer |
| | to manage a calendar entry |
| | 2) An Attendee MAY delegate a calendar entry request |
| | to another Calendar User. |
+=====================================================================+
1.4 iTIP Transactions ITIP defines seven methods for exchanging [ICAL] objects for the
purposes of group calendaring and scheduling between "Calendar Users"
(CUs). CUs take on one of two roles in iTIP. The CU who initiates an
exchange takes on the role of "Organizer". For example, the CU who
proposes a group meeting is the "Organizer". The CUs asked to
participate in the group meeting by the "Organizer" take on the role of
"Attendee". Note that "role" is also a descriptive parameter to the
_ATTENDEE_ property. Its use is to convey descriptive context to an
"Attendee" such as "chair", "req-participant" or "non-participant" and
has nothing to do with the calendaring workflow.
This protocol defines seven methods for exchanging [ICAL] objects for The ITIP methods are defined below and their usage and semantics are
the purposes of group calendaring and scheduling between "Calendar outlined in section 3 of this document.
Users". The methods are defined below and their usage and semantics
are outlined in section 3 of this document.
+================+==================================================+ +================+==================================================+
| Method | Description | | Method | Description |
|================+==================================================| |================+==================================================|
| PUBLISH | Used to publish a calendar entry to one or more | | PUBLISH | Used to publish a calendar entry to one or more |
Silverberg/Mansour/Dawson/Hopson 8 Expires September 1998
| | Calendar Users. There is no interactivity | | | Calendar Users. There is no interactivity |
| | between the publisher and any other calendar | | | between the publisher and any other calendar |
| | user. An example might include a baseball team | | | user. An example might include a baseball team |
| | publishing its schedule to the public. | | | publishing its schedule to the public. |
| | | | | |
| REQUEST | Used to schedule a calendar entry with other | | REQUEST | Used to schedule a calendar entry with other |
| | Calendar Users. Requests are interactive in that | | | Calendar Users. Requests are interactive in that |
| | they MAY require the receiver to respond using | | | they require the receiver to respond using |
| | the the Reply methods. Meeting Requests, Busy | | | the the Reply methods. Meeting Requests, Busy |
| | Time requests and the assignment of VTODOs to | | | Time requests and the assignment of VTODOs to |
| | other Calendar Users are all examples. | | | other Calendar Users are all examples. |
| | Requests are also used by the "Organizer" to | | | Requests are also used by the "Organizer" to |
| | update the status of a calendar entry. | | | update the status of a calendar entry. |
| | |
| REPLY | A Reply is used in response to a Request to | | REPLY | A Reply is used in response to a Request to |
| | convey "Attendee" status to the "Organizer". | | | convey "Attendee" status to the "Organizer". |
| | Replies are commonly used to respond to meeting | | | Replies are commonly used to respond to meeting |
| | and task requests. | | | and task requests. |
| | | | | |
| CANCEL | The Cancel method is used to cancel an existing | | ADD | Add one or more instances to an existing |
| | calendar entry such as a VEVENT or VTODO. | | | 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 | | REFRESH | The Refresh method is used by an "Attendee" to |
| | request the latest version of a calendar entry | | | request the latest version of a calendar entry. |
| | | | | |
| COUNTER | The Counter method is used by an "Attendee" to | | COUNTER | The Counter method is used by an "Attendee" to |
| | negotiate a change in the calendar entry. | | | negotiate a change in the calendar entry. |
| | Examples include the request to change a | | | Examples include the request to change a |
Silverberg/Mansour/Dawson/Hopson 9 Expires MAY 1998
| | proposed Event time or change the due date for a | | | proposed Event time or change the due date for a |
| | VTODO. | | | VTODO. |
| DECLINE- | | | | |
| COUNTER | Used by the "Organizer" to decline the proposed | | DECLINE- | Used by the "Organizer" to decline the proposed |
| | counter-proprosal by an "Attendee" | | COUNTER | counter-proprosal. |
+================+==================================================+ +================+==================================================+
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 described
in section 1.4. The Transport Protocol defines how the iCalendar above. The Transport Protocol defines how the iCalendar objects are sent
objects are sent between the sender and receiver. This document between the sender and receiver. This document focuses on the
focuses on the Application Protocol. Application Protocol. Binding documents such as [IMIP] and [IRIP] focus
on the Transport Protocol.
The connection between Sender and Receiver in the diagram below The connection between Sender and Receiver in the diagram below refers
refers to the Application Protocol. In particular, the iCalendar to the Application Protocol. The iCalendar objects passed from the
objects passed from the Sender to the Receiver which conform to those Sender to the Receiver are presented in Section 3, Application Protocol
presented in Section 3, Application Protocol Elements. Elements.
Silverberg/Mansour/Dawson/Hopson 9 Expires September 1998
+----------+ +----------+ +----------+ +----------+
| | 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 "CUA" or CS. These variants are Receiver take on various roles of a "Calendar User Agent" (CUA) or a
detailed in the Model document [ICMS] "Calendar Service" (CS). These variants are detailed in the Model
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 application written to this specification may work with bindings for the
the store-and-forward transport, the real time transport, or both. store-and-forward transport, the real time transport, or both. Also note
Also note that iTIP could be bound to other transports. If a that iTIP could be bound to other transports.
capability is not available on a particular transport binding, iTIP
provides a mechanism for indicating so.
+------------------------------------------+ +------------------------------------------+
| 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
The model for the application protocol is centered with the The iTIP model is in which a calendar entry is created and managed by an
"Organizer" of the calendar entry. That is, the "Organizer" of a "Organizer". The "Organizer" interacts with other CUs by sending one or
more of the iTIP messages described above. "Attendees" use the "REPLY"
Silverberg/Mansour/Dawson/Hopson 10 Expires MAY 1998 method to communicate their status. "Attendees" do not make direct
Calendar entry sends a request to one or more "Attendees". The changes to the master calendar entry. They can, however, use the
"Attendees" then reply to the "Organizer". The "Organizer" maintains "COUNTER" method to suggest changes to the "Organizer". The "Organizer"
the status of the event. has complete control over the master calendar entry.
The "Owner" is usually the "Organizer" of the calendar entry.
However, the "Owner" MAY delegate or assign an "Organizer" to manage
the calendar entry on their behalf. In cases where the "Owner" has
delegated to another "Organizer", the "Owner" must still be specified
in associated "REQUEST" and "COUNTER" methods.
The data sources for the application protocol are the "Calendar
Users". Examples of these users are the "Organizer" and "Attendees"
of an iCalendar event. The data objects are the iCalendar objects
that are exchanged between "Calendar Users".
2.1.1 Calendar Entry State 2.1.1 Calendar Entry State
There are two distinct states relevant to calendar entries: the There are two distinct states relevant to calendar entries: the overall
overall state of the entry and the state associated with an state of the entry and the state associated with an "Attendee" to that
"Attendee" to that entry. 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" MAY either set the "STATUS" "STATUS" property. The "Organizer" sets the "STATUS" property to the
property to TENTATIVE or CONFIRMED values. The "Organizer" MAY also appropriate value for each calendar entry.
set the "STATUS" property to CANCELLED value by sending a "CANCEL"
method to each "Attendee".
The state of a particular "Attendee" relative to an entry is defined The state of a particular "Attendee" relative to an entry is defined by
by the "STATUS" property parameter in the "ATTENDEE" property for the "attstat" parameter in the "ATTENDEE" property for each "Attendee".
that "Attendee". When an "Organizer" sends out an entry, the state When an "Organizer" issues the initial entry, "Attendee" status is
associated with each "Attendee" is NEEDS-ACTION. Each "Attendee" MAY unknown. The "Organizer" specifies this by setting the "attstat"
modify their "ATTENDEE" property "STATUS" parameter to an appropriate parameter to "needs-action". Each "Attendee" modifies their "ATTENDEE"
value and send it back to the "Organizer" in a "REPLY" message. property "attstat" parameter to an appropriate value as part of a
"REPLY" message sent back to the "Organizer".
Silverberg/Mansour/Dawson/Hopson 10 Expires September 1998
2.1.2 Delegation
Delegation is defined as the process by which an "Attendee" grants
another CU (or several CUs) the right to attend on their behalf. The
"Organizer" is made aware of this change because the delegating
"Attendee" informs the "Organizer" of this change. These steps are
detailed in the REQUEST method section.
2.1.3 Acting on Behalf of other Calendar Users
In many organizations one user will act on behalf of another to organize
and/or respond to meeting requests. ITIP provides two mechanisms that
support these activities.
First, the "Organizer" is treated as a special entity, separate from
"Attendees". All responses from "Attendees" flow to the "Organizer",
making it easy to separate a calendar user organizing a meeting from
calendar users attending the meeting. Additionally, iCalendar provides
descriptive roles for each "Attendee". For instance, a role of "chair"
may be ascribed to one or more "Attendees". The "chair and the
"Organizer" may or may not be the same calendar user. This maps well to
scenarios where an assistant may manage meeting logistics for another
individual who chairs a one-time or recurring meeting.
Second, a "sent-by" parameter may be specified in either the "Organizer"
or "Attendee" properties. When specified, the "sent-by" parameter
indicates that the responding CU acted on behalf of the specified
"Attendee" or "Organizer".
3 Application Protocol Elements 3 Application Protocol Elements
Messages are "text/calendar" MIME entities that contain calendaring ITIP messages are "text/calendar" MIME entities that contain calendaring
and scheduling information. The particular type of [ICAL] message is and scheduling information. The particular type of [ICAL] message is
referred to as the "method type". Each method type is identified by a referred to as the "method type". Each method type is identified by a
"METHOD" property specified as part of the "text/calendar" content "METHOD" property specified as part of the "text/calendar" content type.
type. The table below shows various combinations of calendar The table below shows various combinations of calendar components and
components and the method types that this memo supports. 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 | Yes | No | |Refresh | Yes | Yes | No | No |
|Cancel | Yes | Yes | Yes | No | |Cancel | 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 |
Silverberg/Mansour/Dawson/Hopson 11 Expires MAY 1998
|Decline- | | | | | |Decline- | | | | |
|Counter | Yes | Yes | No | No | |Counter | Yes | Yes | No | No |
+=================================================+ +=================================================+
Each method type is defined in terms of its associated properties. Silverberg/Mansour/Dawson/Hopson 11 Expires September 1998
Some properties are required, some are optional and others are
excluded. The property restrictions are expressed in this memo using
the following formal notation:
prop-restriction = "(" description component method
1*MUST-component *MAY-component *not-component ")"
description = "DESCRIPTION" *ws text
component = "COMPONENT" *ws ("CALPROPOS" / "VEVENT" /
"VTODO" / "VJOURNAL")
method = "METHOD" *ws <any of the methods defined in this
memo for the associated calendar component>
MUST-component = "MUST COMPONENT =" *ws ("VEVENT" / "VTODO" /
"VJOURNAL" / "VTIMEZONE" / "VALARM" /
"VFREEBUSY" / "X-TOKEN")
*ws "(" [ws] 1*MUST-props *ws
*MAY-props *ws *not-props *ws ")"
MAY-component = "MAY COMPONENT =" *ws ("VEVENT" / "VTODO" / Each method type is defined in terms of its associated components and
"VJOURNAL" / "VTIMEZONE" / "VALARM" / properties. Some components and properties are required, some are
"VFREEBUSY" / "X-TOKEN") optional and others are excluded. The restrictions are expressed in this
*ws "(" [ws] ((*MUST-props *ws document using a simple "restriction table". The first column indicates
*MAY-props *ws *not-props *ws) / any) ")" the name of a component or property. Properties of the iCalendar object
are not indented. Properties of a component are indented. The second
column contains "MUST" if the component or property must be present,
"MAY" if the component or property is optional, and "NOT" if the
component or property must not be present. Entries in the second column
sometimes contain comments for further clarification.
not-component = "NOT COMPONENT =" *ws ("VEVENT" / "VTODO" / 3.1 Common Component Restriction Tables
"VJOURNAL" / "VTIMEZONE" / "VALARM" /
"VFREEBUSY" /"X-TOKEN")
MUST-props = "MUST PROPERTY =" *ws restriction-list DateTime values MAY refer to a "VTIMEZONE" component. The property
MAY-props = "MAY PROPERTY =" *ws (restriction-list / any) restrictions in the table below apply to any "VTIMEZONE" component in an
not-props = "NOT PROPERTY =" *ws (restriction-list) ITIP message.
restriction-list = restriction Component/Property Presence
/ restriction *ws "," *ws restriction ------------------- ----------------------------------------------
restriction = property-name VTIMEZONE MUST be present if any date/time refers to a
[*ws "{" parm-or-val-restriction "}"] timezone
property-name = <any of the valid properties for the component> LAST-MODIFIED MAY
parm-or-val-restriction = <a text string description of a TZID MUST
constraint on the property parameters TZURL MAY
or values> STANDARD MUST
any = "ANY" -- Specifies that any permissible DTSTART MUST be present if RRULE is present
properties are allowed - - TZOFFSETFROM MUST
TZOFFSETTO MUST
COMMENT MAY
RDATE MAY be present, if present RRULE must not be
present
RRULE MAY be present, if present RDATE must not be
present
TZNAME MAY
DAYLIGHT MAY
DTSTART MUST
TZOFFSET MUST
COMMENT MAY
RDATE MAY be present, if present RRULE must not be
present
RRULE MAY be present, if present RDATE must not be
present
TZNAME MAY
ws = HTAB / SPACE The property restrictions in the table below apply to any "VALARM"
component in an ITIP message.
HTAB = <Horizontal TAB character> Component/Property Presence
SPACE = <Required Space character> ------------------- ----------------------------------------------
VALARM MAY
ALARM-TYPE MUST
DURATION MUST
Silverberg/Mansour/Dawson/Hopson 12 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 12 Expires September 1998
REPEAT MUST
TRIGGER MUST
ATTACH MAY
DESCRIPTION MAY
SUMMARY MAY
COMMENT NOT
CREATED NOT
LAST-MODIFIED NOT
RELATED-TO NOT
URL NOT
3.1 Methods For "VEVENT" Calendar Component 3.2 Methods for VEVENT Calendar Components
This section defines the property set restrictions for the method This section defines the property set restrictions for the method types
types that are applicable to the "VEVENT" calendar component. Each of that are applicable to the "VEVENT" calendar component. Each method is
the methods is defined using a grammar that clarifies the property defined using a table that clarifies the property constraints that
constraints that define the particular method. define the particular method.
The following summarizes the methods that are defined for the The following summarizes the methods that are defined for the "VEVENT"
"VEVENT" calendar component. 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 MAYdegrade 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 MAYset their | | | |
| | status to | | REPLY | Reply to an event request. Clients may set their |
| | ACCEPTED, DECLINED, TENTATIVE, DELEGATED. | | | status ("attstat") to ACCEPTED, DECLINED, |
| CANCEL | Cancel an existing event request. | | | TENTATIVE, or DELEGATED. |
| REFRESH | A request sent to an by an "Attendee" | | | |
| | "Organizer" asking | | ADD | Add one or more instances to an existing event. |
| | for the latest version of an event to be resent | | | |
| | to the requester. | | CANCEL | Cancel one or more instances of an existing |
| COUNTER | Counter a REQUEST with an alternative proposal. | | | event. |
| DECLINECOUNTER | Decline a counter proposal by an "Attendee". | | | |
| REFRESH | A request is sent to an "Organizer" by an |
| | "Attendee" asking for the latest version of an |
| | event to be resent to the requester. |
| | |
| COUNTER | Counter a REQUEST with an alternative proposal, |
| | Sent by an "Attendee" to the "Organizer". |
| | |
| DECLINECOUNTER | Decline a counter proposal. Sent to an |
Silverberg/Mansour/Dawson/Hopson 13 Expires September 1998
| | "Attendee" by the "Organizer". |
+================+==================================================+ +================+==================================================+
3.1.1 PUBLISH 3.2.1 PUBLISH
The "PUBLISH" method in a "VEVENT" calendar component provides an The "PUBLISH" method in a "VEVENT" calendar component is an unsolicited
unsolicited posting of an iCalendar object. Any "Calendar User" MAY posting of an iCalendar object. Any CU may add published components to
add the published components to their calendar. It requires and their calendar. The "Organizer" MUST be present in a published iCalendar
accepts no responses to the "Organizer". Its expected usage is for component. Other "Attendees" MAY be present. However, no replies are
encapsulating an arbitrary event or to-do as an iCalendar object. The expected. Its expected usage is for encapsulating an arbitrary event as
"Organizer" MAY subsequently update (with another "PUBLISH" method) an iCalendar object. The "Organizer" may subsequently update (with
or cancel (with a "CANCEL" method) a previously published "VEVENT" another "PUBLISH" method), add instances to (with an "ADD" method), or
calendar component. cancel (with a "CANCEL" method) a previously published "VEVENT" calendar
component.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "Event - Publish" COMPONENT "VEVENT" METHOD "PUBLISH Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "PUBLISH"
VEVENT MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
SEQUENCE MUST be present if not 0, may be present if 0
SUMMARY MUST; may be null.
UID MUST
Silverberg/Mansour/Dawson/Hopson 13 Expires MAY 1998 ATTENDEE MAY
MUST COMPONENT = CALPROPS ( ATTACH MAY
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) CATEGORIES MAY
MUST COMPONENT = VEVENT ( CLASS MAY
MUST PROPERTY = ATTENDEE{ROLE=OWNER and ORGANIZER if COMMENT MAY
different}, DESCRIPTION{MAY BE NULL},DTSTAMP, DTSTART, CONTACT MAY
SEQUENCE{IF NE 0}, UID CREATED MAY
MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER | DESCRIPTION MAY be present and MAY be NULL
ORGANIZER}, CATEGORIES, CLASS, COMMENT, DTEND MAY
CREATED, DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, EXDATE MAY
LOCATION,PRIORITY, RELATED-TO, RDATE, RECURRENCE-ID, EXRULE MAY
RESOURCES, RRULE, SEQUENCE{IF EQ 0}, GEO MAY
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, LAST-MODIFIED MAY
SUMMARY{MAYBE NULL}, URL LOCATION MAY
NOT PROPERTY = REQUEST-STATUS, TRANSP) PRIORITY MAY
MAY COMPONENT = VTIMEZONE ( RELATED-TO MAY
MUST PROPERTY = DTSTART, TZOFFSET RDATE MAY
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME, RESOURCES MAY
NOT PROPERTY = CREATED) RRULE MAY
MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
)
3.1.2 REQUEST Silverberg/Mansour/Dawson/Hopson 14 Expires September 1998
STATUS MAY be one of TENTATIVE/CONFIRMED/CANCELLED
TRANSP MAY
URL MAY
The "REQUEST" method in a "VEVENT" calendar component provides the DURATION NOT
following scheduling functions:
. Invite "Attendees" to an event; VTODO NOT
VJOURNAL NOT
. Reschedule an existing event; VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
. Update the details of an existing event, without rescheduling 3.2.2 REQUEST
it;
The "REQUEST" method in a "VEVENT" component provides the following
scheduling functions:
. Invite "Attendees" to an event;
. Reschedule an existing event;
. 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;
. To forward a VEVENT to another uninvited CU.
. For an existing "VEVENT" calendar component, delegate the role of
"Attendee" to another CU;
. For an existing "VEVENT" calendar component, changing the role of
"Organizer" to another CU.
. For an existing "VEVENT" calendar component, delegate the role The "Organizer" originates the "REQUEST". The recipients of the
of "Attendee" to another "Calendar User"; "REQUEST" method are the CUs invited to the event, the "Attendees".
"Attendees" use the "REPLY" method to convey attendance status to the
"Organizer".
. For an existing "VEVENT" calendar component, delegate the role The "UID" and "SEQUENCE" properties are used to distinguish the various
of "Organizer" to another "Calendar User". uses of the "REQUEST" method. If the "UID" property value in the
"REQUEST" is not found on the recipient's calendar, then the "REQUEST"
is for a new "VEVENT" calendar component. If the "UID" property value is
found on the recipient's calendar, then the "REQUEST" is for a
rescheduling, an update, or a reconfirm of the "VEVENT" calendar
component.
Silverberg/Mansour/Dawson/Hopson 14 Expires MAY 1998 This method type is an iCalendar object that conforms to the following
The originator of the "REQUEST" method is the "Organizer" of the property constraints:
event. Normally this is the "Owner" of the event. The recipient of
the "REQUEST" method is the "Calendar User" invited to the event,
called the "Attendee". The "Attendee" uses the "REPLY" method to
convey their attendance status to the "Organizer" of a VEVENT
"REQUEST".
The "UID" and "SEQUENCE" properties are used to distinguish the Component/Property Presence
various uses of the "REQUEST" method. If the "UID" property value in ------------------- ----------------------------------------------
the "REQUEST" is not found on the recipient's calendar, then the PRODID MUST
"REQUEST" is for a new "VEVENT" calendar component. If the "UID" VERSION MUST be "2.0"
property value is found on the recipient's calendar, then the METHOD MUST be "REQUEST"
"REQUEST"' is for either a rescheduling, an update, or a reconfirm of
the "VEVENT" calendar component.
If the "Organizer" of the "REQUEST" method is not authorized to make Silverberg/Mansour/Dawson/Hopson 15 Expires September 1998
an event request on the "Attendee's" calendar system, then an
exception is returned in the "REQUEST-STATUS" property of a
subsequent "REPLY" method, but no scheduling action is performed.
This method type is an iCalendar object that conforms to the VEVENT MUST
following property constraints: ATTENDEE MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
SEQUENCE MUST be present if non-zero, may be present if zero
SUMMARY MUST be present, may be NULL
UID MUST
(DESCRIPTION "Event - Request" COMPONENT "VEVENT" METHOD "REQUEST" ATTACH MAY
CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present and may be NULL
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PRIORITY MAY
RDATE MAY
RELATED-TO MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of TENTATIVE/CONFIRMED
TRANSP MAY
URL MAY
MUST COMPONENT = CALPROPS ( DURATION NOT
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) REQUEST-STATUS NOT
MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{ ROLE=OWNER and ORGANIZER if
different and "STATUS parameter absent or
STATUS=NEEDS-ACTION on Attendees}, DESCRIPTION{MAYBE
NULL}, DTSTAMP,DTSTART,SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT, CREATED,
DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,
PRIORITY, RDATE, RECURRENCE-ID, RELATED-TO, RESOURCES,
RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED
/CANCELLED}, SUMMARY {MAYBE NULL}, TRANSP, URL
NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
)
Silverberg/Mansour/Dawson/Hopson 15 Expires MAY 1998 VTODO NOT
VJOURNAL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
3.1.2.1 REQUEST for Rescheduling an Event 3.2.2.1 Rescheduling an Event
The "REQUEST" method MAY be used to reschedule an event. The "REQUEST" method may be used to reschedule an event. A rescheduled
event involves a change to the existing event in terms of its time or
recurrence intervals and possibly the location or description. If the
recipient CUA of a "REQUEST" method finds that the "UID" property value
already exists on the calendar, but that the "SEQUENCE" (or "DTSTAMP")
property value in the "REQUEST" method is greater than the value for the
A rescheduled event involves a change to the existing event in terms Silverberg/Mansour/Dawson/Hopson 16 Expires September 1998
of it's time or recurrence intervals and possibly the location or
description. If the recipient "CUA" of a "REQUEST" method finds that
the "UID" property value already exists on the calendar, but that the
"SEQUENCE" property value in the "REQUEST" method is greater than the
value for the existing event, then the "REQUEST" method describes a
rescheduling of the event.
3.1.2.2 REQUEST for Update or Reconfirmation of an Event existing event, then the "REQUEST" method describes a rescheduling of
the event.
The "REQUEST" method MAY be used to update or reconfirm an event. 3.2.2.2 Updating or Reconfirmation of an Event
An update to an existing event does not involve changes to the time The "REQUEST" method may be used to update or reconfirm an event. An
or recurrence intervals, and might not involve a change to the update to an existing event does not involve changes to the time or
location or description for the event. If the recipient "CUA" of a recurrence intervals, and might not involve a change to the location or
"REQUEST" method finds that the "UID" property value already exists description for the event. If the recipient CUA of a "REQUEST" method
on the calendar and that the "SEQUENCE" property value in the finds that the "UID" property value already exists on the calendar and
"REQUEST" is the same as the value for the existing event, then the that the "SEQUENCE" property value in the "REQUEST" is the same as the
"REQUEST" method describes an update of the event details, but no value for the existing event, then the "REQUEST" method describes an
rescheduling of the event. update of the event details, but no rescheduling of the event.
The update "REQUEST" method is the appropriate response to a The update "REQUEST" method is the appropriate response to a "REFRESH"
"REFRESH" method sent from an "Attendee" to the "Organizer" of an method sent from an "Attendee" to the "Organizer" of an event.
event.
Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of The "Organizer" of an event may also send unsolicited "REQUEST" methods.
an event. The unsolicited "REQUEST" methods MAY be used to either The unsolicited "REQUEST" methods may be used to update the details of
update the details of the event, without rescheduling it, to update the event without rescheduling it, to update the "attstat" parameter of
the "STATUS" property parameter of "Attendees", or to reconfirm the "Attendees", or to reconfirm the event.
event.
3.1.2.3 REQUEST for Delegating an Event from an "Attendee" to another 3.2.2.3 Delegating an Event to another CU
CU
The "REQUEST" method MAY be used to delegate an event to another Some calendar and scheduling systems allow "Attendees" to delegate their
"Calendar User". The method is used to delegate the "Attendee's" role presence at an event to another calendar user. ITIP supports this
(i.e., "Organizer" or "Attendee") for an event. The "REQUEST" method concept using the following workflow. Any "Attendee" may delegate their
for delegation is sent by one of the "Attendees" of an existing event right to participate in a calendar VEVENT to another CU. The implication
request to some other "Calendar User". In order to avoid scheduling is that the delegate participates in lieu of the original "Attendee";
loops, the method MUST NOT be sent from an "Attendee" back to the NOT in addition to the "Attendee". The delegator MUST notify the
"Organizer" of the event. An "Attendee" MAY NOT delegate to the "Organizer" of this action using the steps outlined below.
"Organizer" of the event. Implementations may support or restrict delegation as they see fit. For
instance, some implementations may restrict a delegate from delegating a
"REQUEST" to another CU.
For the purposes of this description, the "Attendee" delegating the The "Delegator" of an event forwards the existing "REQUEST" to the
event is referred to as the "delegator". The "Attendee" receiving the "Delegate". The "REQUEST" method MUST include an "ATTENDEE" property
delegation request is referred to as the "delegatee". with the calendar address of the "Delegate". The "Delegator" MUST also
send a "REPLY" method to the "Organizer" with the "Delegator's"
"ATTENDEE" property "attstat" parameter value set to "delegated". In
addition, the "delegated-to" parameter MUST be included with the
calendar address of the "Delegate".
Silverberg/Mansour/Dawson/Hopson 16 Expires MAY 1998 In response to the request, the "Delegate" MUST send a "REPLY" method to
The "delegator" of an event MUST forward the existing "REQUEST" the "Organizer" and optionally, to the "Delegator". The "REPLY" method "
method for an event to the "delegatee". The event description MUST SHOULD include the "ATTENDEE" property with the "delegated-from"
include the "delegator's" up-to-date event definition. The "REQUEST" parameter value of the "Delegator's" calendar address.
method MUST also include an "ATTENDEE" property with the calendar
address of the "delegatee". The "delegator" MUST also send a "REPLY"
method back to the "Organizer" with the "delegator's" "Attendee"
property "STATUS" parameter value set to DELEGATED. In addition, the
"DELEGATED-TO" parameter SHOULD be included with the calendar address
of the "delegatee". A response to the delegation "REQUEST" is sent
from the "delegatee" to the "Organizer" and optionally, to the
"delegator". The "REPLY" method from the "delegatee" SHOULD include
their "ATTENDEE" property with the "DELEGATED-FROM" parameter value
of the "delegator's"calendar address.
The delegation "REQUEST" method MUST assign the values of the "RSVP" Silverberg/Mansour/Dawson/Hopson 17 Expires September 1998
and "EXPECT" property parameters associated with the "delegator's"
"ATTENDEE" property to that of the "delegatee's" "ATTENDEE" property.
For example if the "delegator's" "ATTENDEE" property specifies
"RSVP=TRUE;EXPECT=REQUEST", then the "delegatee's" "ATTENDEE"
property MUST specify "RSVP=TRUE;EXPECT=REQUEST".
3.1.2.4 REQUEST for Delegating role of "Organizer" to another CU 3.2.2.4 Changing the Organizer
If the "Owner" of an existing "VEVENT" calendar component wishes to The situation may arise where the "Organizer" of a VEVENT is no longer
delegate the role of "Organizer" to another CU, they MAY issue able to perform the "Organizer" role and abdicates without passing on
another "REQUEST" method that notifies all "Attendees" and the new the "Organizer" role to someone else. When this occurs the "Attendees"
"Organizer" of this change. The "Owner MUST modify several property of the VEVENT may use out-of-band mechanisms to communicate the
parameters of the "ATTENDEE" property including the "ROLE", where the situation and agree upon a new "Organizer". The new "Organizer" should
role of "Owner" and "Organizer" MUST be specified. Additionally, the then send out a new "REQUEST" with a modified version of the VEVENT in
"DELEGATED-TO" and "DELEGATED-FROM" parameters MUST specify the which the "SEQUENCE" number has been incremented and value of the
"Organizer" and "Owner" calendar addresses. The "Owner" MAY request "ORGANIZER" property has been changed to the calendar address of the new
reconfirmation by incrementing the "SEQUENCE" property and setting "Organizer".
the "RSVP" property parameter to TRUE. This will cause a
reconfirmation to be sent to the new organizer.
3.1.2.5 REQUEST for Changing the "Organizer" from one CU to another 3.2.2.5 Sending on Behalf of the Organizer
An "Owner" of an existing "VEVENT" calendar component MAY change the There are a number of scenarios that support the need for a calendar
"Organizer" from one "CU" to another by sending a "REQUEST" method. user to act on behalf of the "Organizer" without explicit role changing.
The "ROLE" property parameter value of ORGANIZER MUST be assigned to This might be the case if the CU designated as "Organizer" was sick or
the new "Organizer". If the old "Organizer" is still an "Attendee" unable to perform duties associated with that function. In these cases
then "ROLE" property parameter for that "CU" MUST be set to ATTENDEE. iTIP supports the notion of one CU acting on behalf of another. Using
the "sent-by" parameter, a calendar user could send an updated "VEVENT"
REQUEST. In the case where one CU sends on behalf of another CU, the
"Attendee" responses are still directed back towards the CU designated
as "Organizer".
3.1.2.6 REQUEST for Changing the "Owner" 3.2.2.6 Forwarding to An Uninvited CU
This memo does not support the notion of changing ownership of a An "Attendee" invited to an event may invite another uninvited CU to the
"VEVENT" calendar component. event. The invited "Attendee" accomplishes this by forwarding the
original "REQUEST" method to the uninvited CU. Whether the uninvited CU
is added to the attendee list, and thus informed of changes to the
"VEVENT" calendar component, is an issue left to individual
implementations. It is not required. It is important to note that when
forwarding a "REQUEST" to another CU, the forwarding "Attendee" MUST NOT
make changes to the VEVENT property set.
Silverberg/Mansour/Dawson/Hopson 17 Expires MAY 1998 3.2.2.7 Updating Attendee Status
3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User The "Organizer" of an event may also request updated status from one or
more "Attendees. The "Organizer" sends a "REQUEST" method to the
"Attendee" and sets the "ATTENDEE;RSVP=TRUE" property parameter. The
"SEQUENCE" property for the event is not changed from its previous
value. A recipient will determine that the only change in the "REQUEST"
is that their "RSVP" property parameter indicates a request for updated
status. The recipient SHOULD respond with a "REPLY" method indicating
their current status with respect to the "REQUEST".
An "Attendee" invited to an event MAY invite another uninvited 3.2.3 REPLY
"Calendar User" to the event. The invited "Attendee" accomplishes
this scheduling action by forwarding the original "REQUEST" method to
the uninvited "Calendar User". The forwarded "REQUEST" method need
not include a new "ATTENDEE" property for the uninvited "Attendee".
Whether the uninvited "Calendar User" is added to the attendee list,
and thus informed of changes to the "VEVENT" calendar component is an
implementation issue.
3.1.2.8 REQUEST Updated Attendee Status The "REPLY" method in a "VEVENT" calendar component is used to respond
(e.g., accept or decline) to a "REQUEST" or to reply to a delegation
An "Organizer" of an event MAY also request an updated status from Silverberg/Mansour/Dawson/Hopson 18 Expires September 1998
one of the "Attendees". This is achieved by the "Organizer" sending a
"REQUEST" method to the "Attendee" with the "ATTENDEE;RSVP=TRUE"
property sequence. The "SEQUENCE" property for the event is not
changed from its previous value. A recipient will determine 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".
This capability MAY also be achieved by the "Organizer" sending the "REQUEST". When used to provide a delegation response, the "Delegator"
"REFRESH" method to the "Attendees". SHOULD include the calendar address of the "Delegate" on the "delegated-
to" property parameter of the "Delegator's" "ATTENDEE" property. The
"Delegate" SHOULD include the calendar address of the "Delegator" on the
"delegated-from" property parameter of the "Delegate's" "ATTENDEE"
property.
3.1.3 REPLY The "REPLY" method may also be used to respond to an unsuccessful
"REQUEST" method. Depending on the value of the "REQUEST-STATUS"
property no scheduling action may have been performed.
The "REPLY" method in a "VEVENT" calendar component is used to The "Organizer" of an event may receive the "REPLY" method from a CU not
respond (e.g., accept or decline) to a request or to reply to a in the original "REQUEST". For example, a "REPLY" may be received from a
delegation request. When used in to provide a delegation response, "Delegate" to an event. In addition, the "REPLY" method may be received
the "delegator" SHOULD include the calendar address of the from an unknown CU (a "Party Crasher"). This uninvited "Attendee" may be
"delegatee" on the "DELEGATED-TO" property parameter of the accepted, or the "Organizer" may cancel the event for the uninvited
"delegator's" "ATTENDEE" property. The "delegatee" SHOULD include the "Attendee" by sending a "CANCEL" method to the uninvited "Attendee".
calendar address of the "delegator" on the "DELEGATED-FROM" property
parameter of the "delegatee's" "ATTENDEE" property.
The "REPLY" method MAY also be used to respond to an unsuccessful The "Organizer" may also receive a "REPLY" from one CU on behalf of
"REQUEST" method. Depending on the value of the "REQUEST-STATUS" another. Like the scenario enumerated above for the "Organizer",
property no scheduling action MAY have been performed. "Attendees" may have another CU respond on their behalf. This is done
using the "sent-by" parameter.
The "Organizer" of an event MAY receive the "REPLY" method from a The optional properties listed in the table below (those listed as
"Calendar User" not in the original "REQUEST". For example, a "REPLY" "MAY") MUST NOT be changed from those of the original request. If
method MAY be received from a "delegatee" to an event. In addition, property changes are desired the COUNTER message must be used.
the "REPLY" method MAY be received from an unknown "Calendar User",
forwarded the "REQUEST" from an invited "Attendee". This uninvited
"Attendee" MAY be accepted, or the "Organizer" MAY cancel the event
for the uninvited "Attendee" by sending them a "CANCEL" method to the
univited "Attendee".
Silverberg/Mansour/Dawson/Hopson 18 Expires MAY 1998 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:
(DESCRIPTION "Event - Reply" COMPONENT "VEVENT" METHOD "REPLY" Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REPLY"
MUST COMPONENT = CALPROPS ( VEVENT MUST
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"}) ATTENDEE MUST be the address of the Attendee replying.
MUST COMPONENT = VEVENT ( DTSTAMP MUST
MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE ORGANIZER MUST
replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID RECURRENCE-ID MUST only if referring to an instance of a
associated with original REQUEST} recurring calendar component. Otherwise it
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to must NOT be present.
"Organizer"}, EXDATE, EXRULE, RECURRENCE-ID, REQUEST- SEQUENCE MUST if non-zero
STATUS, SEQUENCE{IF EQ 0}, SUMMARY {MAYBE NULL}, URL UID MUST be the UID of the original REQUEST
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, GEO, LAST-MODIFIED,
PRIORITY, RELATED-TO, RESOURCES, RDATE, RRULE, STATUS,
SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.1.4 CANCEL ATTACH MAY
COMMENT MAY
CONTACT MAY
EXDATE MAY
EXRULE MAY
REQUEST-STATUS MAY
The "CANCEL" method in a "VEVENT" calendar component is used to send CATEGORIES MAY
a cancellation notice of an existing event request to the
"Attendees". The message is sent by the "Organizer" of an event to Silverberg/Mansour/Dawson/Hopson 19 Expires September 1998
the "Attendees" of the event. For a recurring event, either the whole CLASS MAY
event or instances of an event MAY be cancelled. To cancel the CREATED MAY
complete range of recurring event, the "UID" property value for the DESCRIPTION MAY
event MUST be specified in the "CANCEL" method. In order to cancel an DTSTART MAY
individual instance of the event, the "RECURRENCE-ID" property value DTEND MAY
for the event MUST be specified in the "CANCEL" method. In order to DURATION MAY
cancel a sequence of recurring events, either the"RECURRENCE-ID" GEO MAY
property for the first event instance in the sequence MUST be LAST-MODIFIED MAY
PRIORITY MAY
RELATED-TO MAY
RESOURCES MAY
RDATE MAY
RRULE MAY
STATUS MAY
SUMMARY MAY
TRANSP MAY
URL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
X-TOKENS NOT
VTODO NOT
VJOURNAL NOT
VFREEBUSY NOT
VALARM NOT
3.2.4 ADD
The "ADD" method in a "VEVENT" calendar component is used to add one or
more instances to an existing "VEVENT". Unlike the "REQUEST" method,
when using issuing an "ADD" method, the "Organizer" does not send the
full "VEVENT" description; only the new instance(s). The "ADD" method is
especially useful if there are instance-specific properties to be
preserved in a recurring "VEVENT". For instance, an "Organizer" may have
originally scheduled a weekly Thursday meeting. At some point, several
instances changed. Location or start time may have changed, or some
instances may have unique "DESCRIPTION" properties. The "ADD" method
allows the "Organizer" to add new 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
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
updated with the latest version of the "VEVENT". If an "Attendee"
implementation does not support the "ADD" method it should respond with
a "REQUEST-STATUS" value of 5.3 and ask for a "REFRESH".
This method type is an iCalendar object that conforms to the following
property constraints:
Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
Silverberg/Mansour/Dawson/Hopson 20 Expires September 1998
VERSION MUST be "2.0"
METHOD MUST be "ADD"
VEVENT MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
SEQUENCE MUST be greater than 0
SUMMARY MUST be present, may be NULL
UID MUST match that of the original event
ATTACH MAY
ATTENDEE MAY
CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present and may be NULL
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PRIORITY MAY
RDATE MAY
RELATED-TO MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of TENTATIVE/CONFIRMED
TRANSP MAY
URL MAY
DURATION NOT
RECURRENCE-ID NOT
REQUEST-STATUS NOT
VTODO NOT
VJOURNAL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
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 "Attendees". The
message is sent by the "Organizer" of the event. For a recurring event,
either the whole event or instances of an event may be cancelled. To
cancel the complete range of recurring event, the "UID" property value
for the event MUST be specified and a "RECURRENCE-ID" MUST NOT be
Silverberg/Mansour/Dawson/Hopson 21 Expires September 1998
specified in the "CANCEL" method. In order to cancel an individual
instance of the event, the "RECURRENCE-ID" property value for the event
MUST be specified in the "CANCEL" method.
There are two options for canceling a sequence of instances of a
recurring "VEVENT" calendar component:
(a) the "RECURRENCE-ID" property for an instance in the sequence MUST be
specified with the "RANGE" property parameter value of THISANDPRIOR specified with the "RANGE" property parameter value of THISANDPRIOR
or THISANDFUTURE to indicate cancellation of the event instances (or THISANDFUTURE) to indicate cancellation of the specified
before and after the first event instance, respectively. Lastly, "VEVENT" calendar component and all instances before (or after); or
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 instances to
be cancelled. be cancelled.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "Event - Cancel" COMPONENT "VEVENT" METHOD "CANCEL" Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "CANCEL"
MUST COMPONENT = CALPROPS ( VEVENT MUST
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) DTSTAMP MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to one or more instances of
a recurring calendar component. Otherwise it
MUST NOT be present.
SEQUENCE MUST
UID MUST be the UID of the original REQUEST
Silverberg/Mansour/Dawson/Hopson 19 Expires MAY 1998 COMMENT MAY
MUST COMPONENT = VEVENT ( STATUS Must be set to "Cancelled". If uninviting specific
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID "Attendees" then MUST NOT be included.
associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, GEO, LAST-MODIFIED,
PRIORITY, RDATE, RELATED-TO, RESOURCES, REQUEST-STATUS,
RRULE, SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.1.5 REFRESH ATTACH MAY
ATTENDEE MAY
CATEGORIES MAY
CLASS MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY
DTSTART MAY
DURATION MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
PRIORITY MAY
RELATED-TO MAY
Silverberg/Mansour/Dawson/Hopson 22 Expires September 1998
REQUEST-STATUS MAY
RESOURCES MAY
RDATE MAY
RRULE MAY
STATUS MAY
SUMMARY MAY
TRANSP MAY
URL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
X-TOKENS MAY
VTODO NOT
VJOURNAL NOT
VFREEBUSY NOT
VALARM NOT
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 "Attendees" of an existing event to request an updated description from
from the event "Organizer". The "REFRESH" method MUST specify the the event "Organizer". The "REFRESH" method must specify the "UID"
"UID" property corresponding to the event needing update. A property of the event to update. A recurrence instance of an event may
recurrence instance of an event MAY be requested by specifying the be requested by specifying the "RECURRENCE-ID" property corresponding to
"RECURRENCE-ID" property corresponding to the associated event. The the associated event. The "Organizer" responds with the latest
"Organizer" MUST respond with the latest description and version of description and version of the event.
the event. This method is intended to facilitate machine processing
of event update requests by an "Attendee".
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "Event - Refresh" COMPONENT "VEVENT" METHOD "REFRESH" Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REFRESH"
MUST COMPONENT = CALPROPS ( VEVENT MUST
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) ATTENDEE MUST be the address of requestor
MUST COMPONENT = VEVENT ( DTSTAMP MUST
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP, RECURRENCE-ID MUST only if referring to an instance of a
SEQUENCE{IF NE 0}, UID{UID associated with original recurring calendar component. Otherwise it
REQUEST} must NOT be present.
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to UID MUST be the UID associated with original
"Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0} REQUEST
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, GEO,
LAST-MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES,
REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
Silverberg/Mansour/Dawson/Hopson 20 Expires MAY 1998 COMMENT MAY
)
3.1.6 COUNTER ATTACH NOT
ATEGORIES NOT
CLASS NOT
CONTACT MAY
CREATED NOT
The "COUNTER" method in a "VEVENT" calendar component is used by an Silverberg/Mansour/Dawson/Hopson 23 Expires September 1998
"Attendee" of an existing event to submit to the "Organizer" a DESCRIPTION NOT
counter proposal to the event description. The "Attendee" MUST send DTSTART NOT
the message to the "Organizer" of the event. DTEND NOT
DURATION NOT
EXDATE NOT
EXRULE NOT
GEO NOT
LAST-MODIFIED NOT
ORGANIZER NOT
PRIORITY NOT
RDATE NOT
RELATED-TO NOT
RESOURCES NOT
REQUEST-STATUS NOT
RRULE NOT
SEQUENCE NOT
SUMMARY NOT
STATUS NOT
TRANSP NOT
URL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
X-TOKENS MAY
VTODO NOT
VJOURNAL NOT
VFREEBUSY NOT
VALARM NOT
3.2.7 COUNTER
The "COUNTER" method for a "VEVENT" calendar component is used by an
"Attendee" of an existing event to submit to the "Organizer" a counter
proposal to the event description. The "Attendee" sends this 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 calendar component describing the complete description of the alternate
alternate event. event.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the "Attendee" a
"Attendee" a VEVENT "DECLINE-COUNTER" method. The "Organizer" accepts VEVENT "DECLINE-COUNTER" method. The "Organizer" accepts the counter
the counter proposal by sending all of the "Attendees" to the event a proposal by sending all of the "Attendees" to the event a VEVENT
VEVENT "REQUEST" method rescheduling the event. In the later case, "REQUEST" method rescheduling the event. In the latter case, the
the "Organizer" SHOULD reset the individual "RSVP" property parameter "Organizer" SHOULD reset the individual "RSVP" property parameter values
values to TRUE on each "ATTENDEE" property in order to force a to TRUE on each "ATTENDEE" property in order to force a response by the
response by the "Attendees". "Attendees".
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "Event - Counter Proposal" COMPONENT "EVENT" Component/Property Presence
METHOD "COUNTER"
MUST COMPONENT = CALPROPS ( Silverberg/Mansour/Dawson/Hopson 24 Expires September 1998
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"COUNTER"})
MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{STATUS parameter absent or
STATUS=NEEDS ACTION, Owner and Organizer if different,
MAY also be used to propose other "Attendees"},
DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART,
SEQUENCE{IF NE 0}, UID{MUST be the UID associated with
the REQUEST being countered}
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT{provides a
comment from the ATTENDEE to the "Organizer"}, CREATED,
DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,
PRIORITY, RDATE, RECURRENCE-ID, RELATED-TO, RESOURCES,
RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED/
CANCELLED} , SUMMARY {MAYBE NULL}, TRANSP, URL
NOT PROPERTY = COMPLETED, DUE, DURATION, REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM (IF COMPONENT EXISTS
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
Silverberg/Mansour/Dawson/Hopson 21 Expires MAY 1998 ------------------- ----------------------------------------------
NOT COMPONENT = VJOURNAL PRODID MUST
NOT COMPONENT = VFREEBUSY VERSION MUST be "2.0"
) METHOD MUST be "COUNTER"
3.1.7 DECLINECOUNTER VEVENT MUST
DTSTAMP MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
SEQUENCE MUST be present if non-zero, MAY be present if zero
SUMMARY MUST be present may be NULL
UID MUST be the UID associated with the REQUEST
being countered
The "DECLINE-COUNTER" method in a "VEVENT" calendar component is used ATTACH MAY
by the "Organizer" of an event to reject a counter proposal submitted ATTENDEE MAY be used to propose other "Attendees"
by an "Attendee". The "Organizer" MUST send the "DECLINE-COUNTER" CATEGORIES MAY
message to the "Attendee" that sent the "COUNTER" method to the CLASS MAY
"Organizer". COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present, may be NULL
DTSTART MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PRIORITY MAY
RDATE MAY
RELATED-TO MAY
RESOURCES MAY
RRULE MAY
STATUS MAY
TRANSP MAY
URL MAY
The counter proposal is an iCalendar object consisting of a VEVENT COMPLETED NOT
calendar component describing the complete description of the DUE NOT
alternate event. DURATION NOT
ORGANIZER NOT
REQUEST-STATUS NOT
The "Organizer" rejects the counter proposal by sending the VTIMEZONE MUST be present if any date/time refers to a
"Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the timezone
counter proposal by sending all of the "Attendees" to the event a VALARM MAY
"REQUEST" method; rescheduling the event. Since this is a rescheduled
event, the "SEQUENCE" property value will be incremented. In the
later case, the "Organizer" SHOULD reset the individual "RSVP"
parameter values to TRUE on all of the "ATTENDEE" properties; in
order to force a response by the "Attendees".
This method type is an iCalendar object that conforms to the X-TOKENS MAY
following property constraints: VTODO NOT
VJOURNAL NOT
VFREEBUSY NOT
(DESCRIPTION "Event - Cancel" COMPONENT "VEVENT" METHOD Silverberg/Mansour/Dawson/Hopson 25 Expires September 1998
"DECLINECOUNTER"
MUST COMPONENT = CALPROPS ( 3.2.8 DECLINECOUNTER
MUST PROPERTY = PRODID, VERSION{"2.0"},METHOD{
"DECLINECOUNTER"})
MUST COMPONENT = VEVENT (
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID
specified In Original REQUEST and subsequent COUNTER}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ
0}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, GEO,
LAST-MODIFIED, PRIORITY, RDATE, RELATED-TO, RESOURCES,
RRULE,STATUS, SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
Silverberg/Mansour/Dawson/Hopson 22 Expires MAY 1998 The "DECLINE-COUNTER" method in a "VEVENT" calendar component is used by
the "Organizer" of an event to reject a counter proposal submitted by an
"Attendee". The "Organizer" must send the "DECLINE-COUNTER" message to
the "Attendee" that sent the "COUNTER" method to the "Organizer".
3.2 Methods For VFREEBUSY Component This method type is an iCalendar object that conforms to the following
property constraints:
Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "DECLINECOUNTER"
VEVENT MUST
DTSTAMP MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
SEQUENCE MUST if non-zero, MAY be present if zero
UID MUST, same UID specified in original
REQUEST and subsequent COUNTER
COMMENT MAY
REQUEST-STATUS MAY
ATTACH NOT
ATTENDEE NOT
CATEGORIES NOT
CLASS NOT
CONTACT NOT
CREATED NOT
DESCRIPTION NOT
DTSTART NOT
DTEND NOT
DURATION NOT
EXDATE NOT
EXRULE NOT
GEO NOT
LAST-MODIFIED NOT
PRIORITY NOT
RDATE NOT
RELATED-TO NOT
RESOURCES NOT
RRULE NOT
STATUS NOT
SUMMARY NOT
TRANSP NOT
URL NOT
VTIMEZONE MUST be present if any date/time refers to a
Silverberg/Mansour/Dawson/Hopson 26 Expires September 1998
timezone
X-TOKENS MAY
VTODO NOT
VJOURNAL NOT
VFREEBUSY NOT
VALARM NOT
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 applicable to the "VFREEBUSY" calendar component. Each of the methods is
is defined using a grammar that specifies the property constraints defined using a restriction table.
that define the particular method.
This memo 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, periodicity, such as a calendar week, month, or year. In this case, each
each "VFREEBUSY" calendar component MUST include the "ATTENDEE", "VFREEBUSY" calendar component MUST include the "ATTENDEE", "DTSTART"
"DTSTART" and "DTEND" properties in order to specify the source of and "DTEND" properties in order to specify the source of the busy time
the busy time information and the date and time interval over which information and the date and time interval over which the busy time
the busy time information covers. information covers.
The "FREEBUSY" property value MAY include a list of values, separated The "FREEBUSY" property value MAY include a list of values, separated by
by the COMMA character (ASCII decimal 44). Alternately, multiple busy the COMMA character (ASCII decimal 44). Alternately, multiple busy time
time periods MAY be specified with multiple instances of the periods MAY be specified with multiple instances of the "FREEBUSY"
"FREEBUSY" property. Both forms MUST be supported by implementations property. Both forms MUST be supported by implementations conforming to
conforming to this document. Duplicate busy time periods SHOULD NOT this document. Duplicate busy time periods SHOULD NOT be specified in an
be specified in an iCalendar object. However, two different busy time iCalendar object. However, two different busy time periods MAY overlap.
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 the earliest periods first. For example, today's busy time information
information SHOULD appear after yesterday's busy time information. should appear after yesterday's busy time information. And the busy time
And the busy time for this half hour SHOULD appear after the busy for this half-hour should appear after the busy time for earlier today.
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 span a day boundary. Individual "A" requests busy time from individuals
individuals "B", "C" and "D". Individual "B" and "C" replies with "B", "C" and "D". Individual "B" and "C" replies with busy time data to
busy time data to individual "A". Individual "D" does not support individual "A". Individual "D" does not support busy time requests and
busy time requests and does not reply with any data. If the transport does not reply with any data. If the transport binding supports
binding supports exception messages, then a "unsupported capability" exception messages, then individual "D" returns an "unsupported
message is returned by individual "D" to individual "A". capability" message to individual "A".
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.
|================|==================================================| |================|==================================================|
Silverberg/Mansour/Dawson/Hopson 27 Expires September 1998
| 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. |
|================|==================================================| |================|==================================================|
Silverberg/Mansour/Dawson/Hopson 23 Expires MAY 1998 3.3.1 PUBLISH
3.2.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 "Calendar publish busy time data. The method may be sent from one CU to any other.
User" to any other. The purpose of the method is to provide a message The purpose of the method is to provide a message for sending
for sending unsolicited busy time data. That is, the busy time data unsolicited busy time data. That is, the busy time data is not being
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.
Busy time intervals are represented by individual instances of the
"FREEBUSY" property. There is one occurrence of the property for each
busy time interval. Duplicate busy time periods SHOULD NOT be
returned. However, two different busy time periods MAY overlap.
The "FREEBUSY" property value MAY include a list of values, separated
by the COMA character (ASCII decimal 44).
"FREEBUSY" properties SHOULD be sorted such that their values are in
ascending order, from the most recent to past. For example, today's
busy time information SHOULD appear after yesterday's busy time
information. 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 The "ATTENDEE" property must be specified in the busy time information.
span a day boundary. The value is the CU address of the originator of the busy time
information.
The busy time periods MAY be grouped into more than one "VFREEBUSY" This method type is an iCalendar object that conforms to the following
calendar component. This capability allows busy time periods to be property constraints:
grouped according to some common periodicity, such as a calendar
week, month, or year. In this case, each "VFREEBUSY" calendar
component MUST include the "ATTENDEE", "DTSTART" and "DTEND"
properties in order to specify the originator and date and time
interval for the busy time information.
The "ATTENDEE" property MUST be specified in the busy time Component/Property Presence
information. The value is the "Calendar User" address of the ------------------- ----------------------------------------------
originator of the busy time information. PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "PUBLISH"
This method type is an iCalendar object that conforms to the VFREEBUSY MUST
following property constraints: ATTENDEE MUST contain the address of originator of
busy time data
DTSTAMP MUST
FREEBUSY MUST be BUSYTIME. Multiple instances are allowed.
Multiple instances must be sorted in ascending
order.
ATTACH MAY
RELATED-TO MAY
COMMENT MAY
CONTACT MAY
CREATED MAY specifies when the busy time data was
Created
DTSTART MAY be present to represent start of the
interval for busy time data
DTEND MAY be present to represent the end of
the interval for busy time data
GEO MAY
ORGANIZER MAY
URL MAY (specifies busy time URL)
(DESCRIPTION "Busy - Busy Time Publish" COMPONENT "VFREEBUSY" CATEGORIES NOT
METHOD "PUBLISH" CLASS NOT
DESCRIPTION NOT
MUST COMPONENT = CALPROPS ( Silverberg/Mansour/Dawson/Hopson 28 Expires September 1998
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) DURATION NOT
MUST COMPONENT = VFREEBUSY ( EXDATE NOT
MUST PROPERTY = ATTENDEE{address of originator of busy time EXRULE NOT
data},FREEBUSY{values MUST all be of the same data type. LAST-MODIFIED NOT
Multiple instances are allowed. Multiple instances MUST PRIORITY NOT
be sorted in ascending order. Values MAY NOT overlap}, RDATE NOT
RELATED-TO{refers to another related VFREEBUSY RECURRENCE-ID NOT
REQUEST-STATUS NOT
RESOURCES NOT
RRULE NOT
SEQUENCE NOT
STATUS NOT
SUMMARY NOT
TRANSP NOT
UID NOT
Silverberg/Mansour/Dawson/Hopson 24 Expires MAY 1998 VTIMEZONE MUST be present if any date/time refers to a
component}, timezone
MAY PROPERTY = COMMENT{comment from attendee to originator of X-TOKENS NOT
request}, CREATED{specifies when the busy time data was VEVENT NOT
created}, DTSTART{represents start of interval for busy VTODO NOT
time data}, DTEND{represents end of interval for busy VJOURNAL NOT
time data},LAST-MODIFIED{specifies when busy time data VALARM NOT
was last modified}, SEQUENCE{IF EQ 0}, URL{specifies busy
time URL}
NOT PROPERTY = DTSTAMP, DURATION, REQUEST-STATUS, SEQUENCE,
UID)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VALARM
)
3.2.2 REQUEST 3.3.2 REQUEST
The "REQUEST" method in a "VFREEBUSY" calendar component is used to The "REQUEST" method in a "VFREEBUSY" calendar component is used to ask
ask a "Calendar User" for their busy time information. The request a "Calendar User" for their busy time information. The request may be
MAY be for a busy time information bounded by a specific date and for a busy time information bounded by a specific date and time
time interval. 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.
An "ATTENDEE" property MUST be included for the originator of the
request and each of the intended recipients that the method is sent
to. The originator is indicated with an "ATTENDEE" property parameter
sequence of ";ROLE=ORGANIZER". The recipients are indicated with an
"ATTENDEE" property parameter sequence of ";ROLE=ATTENDEE". The
requests MAY be fanned out in separate messages to the recipients,
with each "REQUEST" method only including the associated "ATTENDEE"
properties for the recipients of the message.
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 busy time request on the recipient's calendar system, then an exception
exception message is returned in a "REPLY" method, but no busy time message SHOULD be returned in a "REPLY" method, but no busy time data
data need be returned. need be returned.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "FREEBUSY - Request For Busy Time" COMPONENT Component/Property Presence
"VFREEBUSY" METHOD "REQUEST" ------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REQUEST"
MUST COMPONENT = CALPROPS ( VFREEBUSY MUST
ATTENDEE MUST contain the address of the calendar store
for which busy time is being requested.
Silverberg/Mansour/Dawson/Hopson 25 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 29 Expires September 1998
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) DTEND MUST
MUST COMPONENT = VFREEBUSY ( DTSTAMP MUST
MUST PROPERTY = ATTENDEE{Attendee instances for the Owner and DTSTART MUST
Organizer if different and the intended recipient of the ORGANIZER MUST be the request originator's address
request}, DTSTAMP, DTSTART, DTEND,SEQUENCE{IF NE 0}, UID
MAY PROPERTY = SEQUENCE{IF EQ 0}
NOT PROPERTY = COMMENT, CREATED, DURATION, FREEBUSY,
LAST-MODIFIED, RELATED-TO, URL, REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VALARM
)
3.2.3 REPLY ATTACH MAY
COMMENT MAY
CONTACT MAY
GEO MAY
URL MAY
The "REPLY" method in a "VFREEBUSY" calendar component is used to CATEGORIES NOT
respond to an existing busy time request. The method is sent from a CLASS NOT
recipient of a busy time request back to the originator of the CREATED NOT
request. The originator of the request is specified by the "ATTENDEE" DESCRIPTION NOT
property parameter sequence of ";ROLE=ORGANIZER". DURATION NOT
EXDATE NOT
EXRULE NOT
FREEBUSY NOT
LAST-MODIFIED NOT
PRIORITY NOT
RDATE NOT
RECURRENCE-ID NOT
RELATED-TO NOT
REQUEST-STATUS NOT
RESOURCES NOT
RRULE NOT
SEQUENCE NOT
STATUS NOT
SUMMARY NOT
TRANSP NOT
UID NOT
The "REPLY" method MAY also be used to respond to an unsuccessful VTIMEZONE MUST be present if any date/time refers to a
"REQUEST" method. Depending on the "REQUEST-STATUS" value, no busy
time information MAY be returned.
Busy time intervals are represented by individual instances of the X-TOKENS MAY
"FREEBUSY" property. There is one occurrence of the property for each VEVENT NOT
busy time interval. Duplicate busy time periods SHOULD NOT be VTODO NOT
returned. However, two different busy time periods MAY overlap. VJOURNAL NOT
VALARM NOT
The "FREEBUSY" property value MAY include a list of values, separated 3.3.3 REPLY
by the COMA character (ASCII decimal 44).
"FREEBUSY" properties SHOULD be sorted such that their values are in The "REPLY" method in a "VFREEBUSY" calendar component is used to
ascending order, from the most recent to past. For example, today's respond to a busy time request. The method is sent by the recipient of a
busy time information SHOULD appear after yesterday's busy time busy time request to the originator of the request.
information. 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 The "REPLY" method may also be used to respond to an unsuccessful
span a day boundary. "REQUEST" method. Depending on the "REQUEST-STATUS" value, no busy time
information may be returned.
The busy time periods MAY be grouped into more than one "VFREEBUSY" This method type is an iCalendar object that conforms to the following
calendar component. This capability allows busy time periods to be property constraints:
grouped according to some common periodicity, such as a calendar
week, month, or year. In this case, each "VFREEBUSY" calendar
component MUST include the "ATTENDEE", "DTSTART" and "DTEND"
Silverberg/Mansour/Dawson/Hopson 26 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 30 Expires September 1998
properties in order to identify the source and date and time range
for the busy time data.
The "ATTENDEE" property MUST be specified in the busy time reply. The Component/Property Presence
value is the fully qualified RFC 822 address of the recipient ------------------- ----------------------------------------------
replying to the busy time request. PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REPLY"
This method type is an iCalendar object that conforms to the VFREEBUSY MUST
following property constraints: ATTENDEE MUST (address of recipient replying)
DTSTAMP MUST
DTSTART MUST
DTEND MUST
FREEBUSY MUST (values MUST all be of the same data
type. Multiple instances are allowed.
Multiple instances MUST be sorted in
ascending order. Values MAY NOT overlap)
ORGANIZER MUST be the request originator's address
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
UID MUST
(DESCRIPTION "FreeBusy - Busy Time Reply" COMPONENT "VFREEBUSY" ATTACH MAY
METHOD "REPLY" COMMENT MAY
CONTACT MAY
CREATED MAY specifies when the busy time data was
created)
DTSTART MAY (represents start of interval for busy
time data}, DTEND{represents end of
interval for busy time data)
GEO MAY
RELATED-TO MAY
REQUEST-STATUS MAY
SEQUENCE MAY be present if non-zero
URL MAY (specifies busy time URL)
MUST COMPONENT = CALPROPS ( CATEGORIES NOT
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"}) CLASS NOT
MUST COMPONENT = VFREEBUSY ( DESCRIPTION NOT
MUST PROPERTY = ATTENDEE{address of recipient replying}, DURATION NOT
DTSTAMP, DTSTART, DTEND, FREEBUSY{values MUST all be of EXDATE NOT
the same data type. Multiple instances are allowed. EXRULE NOT
Multiple instances MUST be sorted in ascending order. FREEBUSY NOT
Values MAY NOT overlap}, RELATED-TO{refers to another LAST-MODIFIED NOT
related VFREEBUSY component}, REQUEST-STATUS, UID PRIORITY NOT
MAY PROPERTY = COMMENT{comment from attendee to originator of RDATE NOT
request}, CREATED{specifies when the busy time data was RESOURCES NOT
created}, DTSTART{represents start of interval for busy RRULE NOT
time data}, DTEND{represents end of interval for busy SEQUENCE NOT
time data},LAST-MODIFIED{specifies when busy time data STATUS NOT
was last modified}, SEQUENCE{IF EQ 0}, URL{specifies busy SUMMARY NOT
time URL} TRANSP NOT
NOT PROPERTY = DURATION, SEQUENCE)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY CREATED)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VALARM
)
3.3 Methods For VTODO Component VTIMEZONE MUST be present if any date/time refers to a
Silverberg/Mansour/Dawson/Hopson 31 Expires September 1998
timezone
X-TOKENS MAY
VEVENT NOT
VTODO NOT
VJOURNAL NOT
VALARM NOT
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 grammar that specifies the property constraints that defined using a restriction table that specifies the property
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 .
+================+==================================================+ +================+==================================================+
Silverberg/Mansour/Dawson/Hopson 27 Expires MAY 1998
| 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.VTODO 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 view it as a PUBLISH. | | | degrade the method to treat it as a PUBLISH. |
| | |
| REPLY | Reply to a VTODO request. Attendees MAYset | | REPLY | Reply to a VTODO request. Attendees MAYset |
| | status to ACCEPTED, DECLINED, TENTATIVE, | | | ATTSTAT to ACCEPTED, DECLINED, TENTATIVE, |
| | DELEGATED, PARTIAL, and COMPLETED. | | | DELEGATED, PARTIAL, and COMPLETED. |
| CANCEL | Cancel an existing VTODO assignment. | | | |
| ADD | Add one or more instances to an existing to-do. |
| | |
| CANCEL | Cancel one or more instances of an existing |
| | 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 | | | 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.3.1 PUBLISH Silverberg/Mansour/Dawson/Hopson 32 Expires September 1998
The "PUBLISH" method in a "VTODO" calendar component has no reply 3.4.1 PUBLISH
response associated with it. Instead, it is simply a posting of an
iCalendar object that MAY be added to a calendar by a "Calendar
User". It requires and accepts no responses to the "Organizer". It's
expected usage is for encapsulating an arbitrary "VTODO" calendar
component as an iCalendar object. The "Organizer" MAY subsequently
update (with another "PUBLISH" method) or cancel (with a "CANCEL"
method) a previously published "VTODO" calendar component .
This method type is an iCalendar object that conforms to the The "PUBLISH" method in a "VTODO" calendar component has no associated
following property constraints: response. It is simply a posting of an iCalendar object that maybe added
to a calendar by a "Calendar User". Its expected usage is for
encapsulating an arbitrary "VTODO" calendar component as an iCalendar
object. The "Organizer" MAY subsequently update (with another "PUBLISH"
method), add instances to (win an "ADD" method), or cancel (with a
"CANCEL" method) a previously published "VTODO" calendar component.
(DESCRIPTION "VTODO - Publish" COMPONENT "VTODO" METHOD "PUBLISH This method type is an iCalendar object that conforms to the following
property constraints:
MUST COMPONENT = CALPROPS ( Component/Property Presence
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) ------------------- ----------------------------------------------
MUST COMPONENT = VTODO( PRODID MUST
MUST PROPERTY = ATTENDEE{only Owner and Organizer if VERSION MUST be "2.0"
different}, DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART, METHOD MUST be "PUBLISH"
PRIORITY, SEQUENCE{IF NE 0}, UID VTODO MUST
MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER | DTSTAMP MUST
ORGANIZER}, CATEGORIES, CLASS, COMMENT, CREATED, DUE, DTSTART MUST
EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,PERCENT- ORGANIZER MUST
COMPLETE, RELATED-TO, RDATE, RECURRENCE-ID, RESOURCES, RECURRENCE-ID MUST only if referring to an instance of a
RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED recurring calendar component. Otherwise it
/CANCELLED}, SUMMARY{MAYBE NULL}, URL must NOT be present.
NOT PROPERTY = REQUEST-STATUS) SEQUENCE MUST be present if not 0, may be present if 0
MAY COMPONENT = VTIMEZONE ( SUMMARY MUST; may be null.
MUST PROPERTY = DTSTART, TZOFFSET UID MUST
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
Silverberg/Mansour/Dawson/Hopson 28 Expires MAY 1998 ATTENDEE MAY
MAY COMPONENT = VALARM ( ATTACH MAY
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT CATEGORIES MAY
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY CLASS MAY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL) COMMENT MAY
MAY COMPONENT = X-TOKENS (ANY) CONTACT MAY
NOT COMPONENT = VEVENT CREATED MAY
NOT COMPONENT = VJOURNAL DESCRIPTION MAY be present and MAY be NULL
NOT COMPONENT = VFREEBUSY DURATION MAY
) DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PERCENT-COMPLETE MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of COMPLETED/NEEDS ACTION/IN-PROCESS
TRANSP MAY
URL MAY
3.3.2 REQUEST Silverberg/Mansour/Dawson/Hopson 33 Expires September 1998
VEVENT NOT
VJOURNAL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
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 to-
do, without rescheduling it;
. Reconfirm an existing to-do, without rescheduling it; . Reconfirm an existing to-do, without rescheduling it;
. Delegate/reassign an existing to-do to another "Calendar User". . 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=ATTENDEE" property value component by individual "ATTENDEE;ROLE=REQ-PARTICIPANT" property value
sequences. 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, recipient of a "REQUEST" is the "Calendar User" assigned the to-do-the
called the Attendee. The "Attendee" uses the "REPLY" method to convey "Attendee". The "Attendee" uses the "REPLY" method to convey their
their acceptance and completion status to the "Organizer" of the acceptance and completion status to the "Organizer" of the "REQUEST".
"REQUEST".
The "UID" and "SEQUENCE" properties are used to distinguish the The "UID", "SEQUENCE", and "DTSTAMP" properties are used to distinguish
various uses of the "REQUEST" method. If the "UID" property value in the various uses of the "REQUEST" method. If the "UID" property value in
the "REQUEST" is not found on the recipient's calendar, then the the "REQUEST" is not found on the recipient's calendar, then the
"REQUEST" is for a new to-do. If the "UID" property value is found on "REQUEST" is for a new to-do. If the "UID" property value is found on
the recipient's calendar, then the "REQUEST" is for either a the recipient's calendar, then the "REQUEST" is a rescheduling, an
rescheduling, an update, or a reconfirm of the "VTODO" calendar update, or a reconfirm of the "VTODO" calendar object.
object.
If the "Organizer" of the "REQUEST" method is not authorized to make If the "Organizer" of the "REQUEST" method is not authorized to make a
a to-do request on the "Attendee's" calendar system, then an to-do request on the "Attendee's" calendar system, then an exception is
exception is returned in the "REQUEST-STATUS" property of a returned in the "REQUEST-STATUS" property of a subsequent "REPLY"
subsequent "REPLY" method, but no scheduling action is performed. method, but no scheduling action is performed.
Silverberg/Mansour/Dawson/Hopson 29 Expires MAY 1998 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:
(DESCRIPTION "VTODO - Request" COMPONENT "VTODO" METHOD "REQUEST" Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REQUEST"
MUST COMPONENT = CALPROPS ( Silverberg/Mansour/Dawson/Hopson 34 Expires September 1998
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"})
MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{For Owner and Organizer if different
and each Attendee},DESCRIPTION{MAYBE NULL}, DTSTAMP,
DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT,
CREATED, DUE, EXDATE, EXRULE, GEO, LAST-MODIFIED,
LOCATION, PERCENT-COMPLETE, RELATED-TO, RDATE,
RECURRENCE-ID, RESOURCES, RRULE, SEQUENCE{IF EQ 0},
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, SUMMARY{MAYBE
NULL}, URL
NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
)
3.3.2.1 REQUEST for Rescheduling a VTODO VTODO MUST
ATTENDEE MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
must NOT be present.
SEQUENCE MUST be present if not 0, may be present if 0
SUMMARY MUST; may be null.
UID MUST
ATTACH MAY
CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present and MAY be NULL
DURATION MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PERCENT-COMPLETE MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of COMPLETED/NEEDS ACTION/IN-PROCESS
TRANSP MAY
URL MAY
The "REQUEST" method MAY be used to reschedule a "VTODO" calendar VEVENT NOT
VJOURNAL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
3.4.2.1 REQUEST for Rescheduling a VTODO
The "REQUEST" method may be used to reschedule a "VTODO" calendar
component . component .
A rescheduled "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 it's start or due existing "VTODO" calendar component in terms of its start or due time or
time or recurrence intervals and possibly the description. If the recurrence intervals and possibly the description. If the recipient CUA
recipient "CUA" of a "REQUEST" method finds that the "UID" property of a "REQUEST" method finds that the "UID" property value already exists
value already exists on the calendar, but that the "SEQUENCE" on the calendar, but that the "SEQUENCE" property value in the "REQUEST"
property value in the "REQUEST" is greater than the value for the
existing VTODO, then the "REQUEST" method describes a rescheduling of
the "VTODO" calendar component.
Silverberg/Mansour/Dawson/Hopson 30 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 35 Expires September 1998
3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO is greater than the value for the existing VTODO, then the "REQUEST"
method describes a rescheduling of the "VTODO" calendar component.
The "REQUEST" method MAY be used to update or reconfirm 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"
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 changes to the start or due time or recurrence intervals, nor generally
generally to the description for the "VTODO" calendar component. If to the description for the "VTODO" calendar component. If the recipient
the recipient "CUA" of a "REQUEST" method finds that the "UID" CUA of a "REQUEST" method finds that the "UID" property value already
property value already exists on the calendar and that the "SEQUENCE" exists on the calendar and that the "SEQUENCE" property value in the
property value in the "REQUEST" is the same as the value for the "REQUEST" is the same as the value for the existing event, then the
existing event, then the "REQUEST" method describes an update of the "REQUEST" method describes an update of the "VTODO" calendar component
"VTODO" calendar component details, but no rescheduling of the details, but not a rescheduling of the "VTODO" calendar component.
"VTODO" calendar component.
The update "REQUEST" is the appropriate response to a "REFRESH" The update "REQUEST" is the appropriate response to a "REFRESH" method
method sent from an "Attendee" to the "Organizer" of a "VTODO" sent from an "Attendee" to the "Organizer" of a "VTODO" calendar
calendar component. component.
Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of Unsolicited "REQUEST" methods MAY be sent by the "Organizer" of a
a "VTODO" calendar component. The unsolicited "REQUEST" methods MAY "VTODO" calendar component. The unsolicited "REQUEST" methods are used
be used to either update the details of the VTODO, without to update the details of the "VTODO" (without rescheduling it or
rescheduling it or to update the completion status of "Attendees" or updating the completion status of "Attendees") or the "VTODO" calendar
the "VTODO" calendar component itself (i.e., reconfirm the VTODO). component itself (i.e., reconfirm the "VTODO").
3.3.2.3 REQUEST for Delegating a VTODO 3.4.2.3 REQUEST for Delegating a VTODO
The "REQUEST" method MAY be used to delegate or reassign ownership of The "REQUEST" method is also used to delegate or reassign ownership of a
a "VTODO" calendar component to another "Calendar User". The "VTODO" calendar component to another "Calendar User". For example, it
"REQUEST" method is used to delegate the "Attendee's" role (i.e. " may be used to delegate an "Attendee's" role (i.e. "chair", or
"Organizer", or "Attendee") for a "VTODO" calendar component. The "participant") for a "VTODO" calendar component. The "REQUEST" method is
"REQUEST" method is sent by one of the "Attendees" of an existing sent by one of the "Attendees" of an existing "VTODO" calendar component
"VTODO" calendar component request to some other individual. In order to some other individual. An "Attendee" of a "VTODO" calendar component
to avoid scheduling loops, the method MUST NOT be sent from an MUST NOT delegate to the "Organizer" of the event.
"Attendee" back to the "Organizer" of the "VTODO" calendar component.
An "Attendee" of a "VTODO" calendar component MAY NOT delegate to the
"Organizer" of the event.
For the purposes of this description, the "Attendee" delegating the For the purposes of this description, the "Attendee" delegating the
"VTODO" calendar component is referred to as the "delegator". The "VTODO" calendar component is referred to as the "Delegator". The
"Attendee" receiving the delegation request is referred to as the "Attendee" receiving the delegation request is referred to as the
"delegatee". "Delegate".
The "delegator" of a "VTODO" calendar component MUST forward the The "Delegator" of a "VTODO" calendar component MUST forward the
existing "REQUEST" method for a "VTODO" calendar component to the existing "REQUEST" method for a "VTODO" calendar component to the
"delegatee". The "VTODO" calendar component description MUST include "Delegate". The "VTODO" calendar component description MUST include the
the "delegator's" up-to-date "VTODO" calendar component definition. "Delegator's" up-to-date "VTODO" calendar component definition. The
The "REQUEST" method MUST also include an "ATTENDEE" property with "REQUEST" method MUST also include an "ATTENDEE" property with the
the calendar address of the "delegatee". The "delegator" MUST also calendar address of the "Delegate". The "Delegator" MUST also send a
send a "REPLY" method back to the "Organizer" with the "delegator's" "REPLY" method back to the "Organizer" with the "Delegator's" "Attendee"
"Attendee" property "STATUS" parameter value set to DELEGATED. In property "attstat" parameter value set to "DELEGATED". In addition, the
"delegated-to" parameter SHOULD be included with the calendar address of
Silverberg/Mansour/Dawson/Hopson 31 Expires MAY 1998
addition, the "DELEGATED-TO" parameter SHOULD be included with the
calendar address of the "delegatee". A response to the delegation
"REQUEST" is sent from the "delegatee" to the "Organizer" and
optionally, to the "delegator". The "REPLY" method from the
"delegatee" 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 the values of the "RSVP"
and "EXPECT" property parameters associated with the "delegator's"
"Attendee" property to that of the "delegatee's" "Attendee" property.
For example if the "delegator's" "Attendee" property specifies
"RSVP=TRUE;EXPECT=REQUEST", then the "delegatee's" "Attendee"
property MUST specify "RSVP=TRUE;EXPECT=REQUEST".
3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User Silverberg/Mansour/Dawson/Hopson 36 Expires September 1998
An "Attendee" assigned a "VTODO" calendar component MAY also assign the "Delegate". A response to the delegation "REQUEST" is sent from the
the "VTODO" calendar component to another new "Calendar User", not "Delegate" to the "Organizer" and optionally, to the "Delegator". The
previously associated with the "VTODO" calendar component. The "REPLY" method from the "Delegate" SHOULD include the "ATTENDEE"
current "Attendee" assigned the "VTODO" calendar component property with their calendar address and the "delegated-from" parameter
accomplishes this scheduling action by forwarding the original with the value of the "Delegator's" calendar address.
"REQUEST" method to the new "Calendar User".
An "Organizer" of a "VTODO" calendar component MAY also request an The delegation "REQUEST" method MUST assign a value for the "RSVP"
updated completion status from one of the "Attendees". This is property parameter associated with the "Delegator's" "Attendee" property
achieved by the "Organizer" sending a "REQUEST" method to the to that of the "Delegate's" "ATTENDEE" property. For example if the
"Attendee" with the "ATTENDEE;RSVP=TRUE" property sequence. The "Delegator's" "ATTENDEE" property specifies "RSVP=TRUE", then the
"SEQUENCE" property for the "VTODO" calendar component is not changed "Delegate's" "ATTENDEE" property MUST specify "RSVP=TRUE".
from its previous value. A recipient will determine 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.3.2.5 REQUEST Updated Attendee Status 3.4.2.4 REQUEST Forwarded To An Uninvited Calendar User
An "Organizer" of a to-do MAY also request an updated status from one An "Attendee" assigned a "VTODO" calendar component may assign the
of the "Attendees". This is achieved by the "Organizer" sending a "VTODO" calendar component to another new "Calendar User", not
"REQUEST" method to the "Attendee" with the "ATTENDEE;RSVP=TRUE" previously associated with the "VTODO" calendar component. The current
property sequence. The "SEQUENCE" property for the to-do is not "Attendee" assigned the "VTODO" calendar component accomplishes this
changed from its previous value. A recipient will determine that the scheduling action by forwarding the original "REQUEST" method to the new
only change in the "REQUEST" is that their "RSVP" property parameter "Calendar User".
indicates a request for an updated status. The recipient SHOULD
respond with a "REPLY" method indicating their current status with
respect to the "REQUEST".
This capability MAY also be achieved by the "Organizer" sending the 3.4.2.5 REQUEST Updated Attendee Status
"REFRESH" method to the "Attendees".
Silverberg/Mansour/Dawson/Hopson 32 Expires MAY 1998 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".
3.3.3 REPLY 3.4.3 REPLY
The "REPLY" method in a "VTODO" calendar component is used to respond The "REPLY" method in a "VTODO" calendar component is used to respond
(e.g., accept or decline) to a request or to reply to a delegation (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 request. It is also used by an "Attendee" to update their completion
status. When used to provide a delegation response, the "delegator" status. When used to provide a delegation response, the "Delegator"
SHOULD include the calendar address of the "delegatee" in the SHOULD include the calendar address of the "Delegate" in the "delegated-
"DELEGATED-TO" parameter of the "delegator's" "ATTENDEE" property. to" parameter of the "Delegator's" "ATTENDEE" property. The "Delegate"
The "delegatee" SHOULD include the calendar address of the SHOULD include the calendar address of the "Delegator" on the
"delegator" on the "DELEGATED-FROM" parameter of the "delegatee's" "delegated-from" parameter of the "Delegate's" "ATTENDEE" property.
"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
"VTODO" calendar component "REQUEST" method. Depending on the "VTODO" calendar component "REQUEST" method. Depending on the "REQUEST-
"REQUEST-STATUS" value, no scheduling action MAY have been performed. STATUS" value, no scheduling action may have been performed.
The "Organizer" of a "VTODO" calendar component MAY receive a "REPLY" The "Organizer" of a "VTODO" calendar component MAY receive a "REPLY"
method from a "Calendar User" not in the original "REQUEST". For method from a "Calendar User" not in the original "REQUEST". For
example, a "REPLY" method MAY be received from a "delegatee" of a example, a "REPLY" method MAY be received from a "Delegate" of a "VTODO"
"VTODO" calendar component. In addition, the "REPLY" method MAY be calendar component. In addition, the "REPLY" method MAY be received from
received from an unknown "Calendar User"; forwarded the "REQUEST"
from an original "Attendee" assigned 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 Silverberg/Mansour/Dawson/Hopson 37 Expires September 1998
following property constraints:
(DESCRIPTION "VTODO - Reply" COMPONENT "VTODO" METHOD "REPLY" 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.
MUST COMPONENT = CALPROPS ( This method type is an iCalendar object that conforms to the following
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"}) property constraints:
MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE
replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, EXDATE, EXRULE, RECURRENCE-ID, REQUEST-
STATUS, PERCENT-COMPLETE, SEQUENCE{IF EQ 0}, SUMMARY
{MAYBE NULL}, URL
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DUE, GEO, LAST-MODIFIED, PRIORITY,
RELATED-TO, RESOURCES, RDATE, RRULE, STATUS, SUMMARY,
TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
Silverberg/Mansour/Dawson/Hopson 33 Expires MAY 1998 Component/Property Presence
------------------- ---------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REPLY"
VTODO MUST
ATTENDEE MUST
UID MUST must be the address of the replying attendee
DTSTAMP MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
Recurring calendar component. Otherwise it
Must NOT be present
SEQUENCE MUST
3.3.4 CANCEL COMMENT MAY
PERCENT-COMPLETE MAY
REQUEST-STATUS MAY
DTSTART NOT
CREATED NOT
DESCRIPTION NOT
PRIORITY NOT
CLASS NOT
CATEGORIES NOT
CONTACT NOT
CREATED NOT
DTEND NOT
GEO NOT
LAST-MODIFIED NOT
LOCATION NOT
RDATE NOT
RRULE NOT
RELATED-TO NOT
RESOURCE NOT
STATUS NOT
TRANSP NOT
URL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM NOT
VEVENT NOT
VFREEBUSY NOT
X-TOKENS NOT
Silverberg/Mansour/Dawson/Hopson 38 Expires September 1998
3.4.4 ADD
The "ADD" method in a "VTODO" calendar component is used to add one or
more instances to an existing to-do.
If the "UID" property 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 updated with the latest version of the "VTODO". If an
"Attendee" implementation does not support the "ADD" method it should
respond with a "REQUEST-STATUS" value of 5.3 and ask for a "REFRESH".
This method type is an iCalendar object that conforms to the following
property constraints:
Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "ADD"
VTODO MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
SEQUENCE MUST be greater than 0
SUMMARY MUST; may be null.
UID MUST match that of the original to-do
ATTENDEE MAY
ATTACH MAY
CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present and MAY be NULL
DTEND MAY
DURATION MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PERCENT-COMPLETE MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of COMPLETED/NEEDS ACTION/IN-PROCESS
TRANSP MAY
URL MAY
Silverberg/Mansour/Dawson/Hopson 39 Expires September 1998
RECURRENCE-ID NOT
REQUEST-STATUS NOT
VEVENT NOT
VJOURNAL NOT
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY NOT
X-TOKENS MAY
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 request cancellation notice of an existing "VTODO" calendar request to the
to the "Attendees". The message is sent by the "Organizer" of a "Attendees". The message is sent by the "Organizer" of a "VTODO"
"VTODO" calendar component to the "Attendees" of the "VTODO" calendar calendar component to the "Attendees" of the "VTODO" calendar component.
component. For a recurring "VTODO" calendar component, either the For a recurring "VTODO" calendar component, either the whole "VTODO"
whole "VTODO" calendar component or instances of a "VTODO" calendar calendar component or instances of a "VTODO" calendar component may be
component MAY be cancelled. To cancel the complete range of a cancelled. To cancel the complete range of a recurring "VTODO" calendar
recurring "VTODO" calendar component, the "UID" property value for component, the "UID" property value for the "VTODO" calendar component
the "VTODO" calendar component MUST be specified in the "CANCEL" MUST be specified and a "RECURRENCE-ID" MUST NOT be specified in the
method. In order to cancel an individual instance of a recurring "CANCEL" method. In order to cancel an individual instance of a
"VTODO" calendar component, the "RECURRENCE-ID" property value for recurring "VTODO" calendar component, the "RECURRENCE-ID" property value
the "VTODO" calendar component MUST be specified in the "CANCEL" for the "VTODO" calendar component MUST be specified in the "CANCEL"
method. In order to cancel a sequence of instances of a recurring method.
"VTODO" calendar component, either the "RECURRENCE-ID" property for
the first instance in the sequence MUST be specified with the "RANGE"
property parameter value of THISANDPRIOR or THISANDFUTURE; to
indicate cancellation of the "VTODO" calendar component instances
before and after the first instance, respectively. Lastly, individual
recurrence instances MAY be cancelled by specifying multiple
"RECURRENCE-ID" properties corresponding to the instances to be
cancelled.
This method type is an iCalendar object that conforms to the There are two options for canceling a sequence of instances of a
following property constraints: recurring "VTODO" calendar component:
(DESCRIPTION "VTODO - Cancel" COMPONENT "VTODO" METHOD "CANCEL" (a) the "RECURRENCE-ID" property for an instance in the sequence MUST be
specified with the "RANGE" property parameter value of THISANDPRIOR
(or THISANDFUTURE) to indicate cancellation of the specified "VTODO"
calendar component and all instances before (or after); or
MUST COMPONENT = CALPROPS ( (b) individual recurrence instances may be cancelled by specifying
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) multiple "RECURRENCE-ID" properties corresponding to the instances to
MUST COMPONENT = VTODO( be cancelled.
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DUE, GEO, LAST-MODIFIED, PRIORITY,
RDATE, RELATED-TO, RESOURCES, REQUEST-STATUS, RRULE,
SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
Silverberg/Mansour/Dawson/Hopson 34 Expires MAY 1998 This method type is an iCalendar object that conforms to the following
property constraints:
3.3.5 REFRESH Component/Property Presence
------------------- ---------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "CANCEL"
VTODO MUST
UID MUST must echo original UID
DTSTAMP MUST
ORGANIZER MUST
SEQUENCE MUST
Silverberg/Mansour/Dawson/Hopson 40 Expires September 1998
RECURRENCE-ID MUST only if referring to one or more instances
of a recurring calendar component. Otherwise
it MUST NOT be present
COMMENT MAY
ATTENDEE MAY
DTSTART MAY
CREATED MAY
DESCRIPTION MAY
ORGANIZER MAY
PRIORITY MAY
CLASS MAY
CATEGORIES MAY
CONTACT MAY
CREATED MAY
DTEND MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PERCENT-COMPLETE MAY
PRIORITY MAY
RDATE MAY
RRULE MAY
RELATED-TO MAY
REQUEST-STATUS MAY
RESOURCE MAY
STATUS MAY If present it must be set to "CANCELLED".
MUST NOT be used if purpose is to remove
"ATTENDEES" rather than cancel the entire
VTODO.
TRANSP MAY
URL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VEVENT MAY
VFREEBUSY MAY
X-TOKENS MAY
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 also component. The "Organizer" of the "VTODO" calendar component MAY use
use this method to request an updated status from the "Attendees". this method to request an updated status from the "Attendees". The
The "REFRESH" method MUST specify the "UID" property corresponding to "REFRESH" method MUST specify the "UID" property corresponding to the
the "VTODO" calendar component needing update. "VTODO" calendar component needing update.
A refresh of a recurrence instance of a "VTODO" calendar component A refresh of a recurrence instance of a "VTODO" calendar component may
MAY be requested by specifying the "RECURRENCE-ID" property be requested by specifying the "RECURRENCE-ID" property corresponding to
corresponding to the associated "VTODO" calendar component. The the associated "VTODO" calendar component. The "Organizer" responds with
"Organizer" MUST respond with the latest description and rendition of the latest description and rendition of the "VTODO" calendar component.
the "VTODO" calendar component. This method is intended to facilitate
machine processing of requests for updates to a "VTODO" calendar
component.
This method type is an iCalendar object that conforms to the Silverberg/Mansour/Dawson/Hopson 41 Expires September 1998
following property constraints:
(DESCRIPTION "VTODO - Refresh" COMPONENT "VTODO" METHOD "REFRESH" This method is intended to facilitate machine processing of requests for
updates to a "VTODO" calendar component.
MUST COMPONENT = CALPROPS ( This method type is an iCalendar object that conforms to the following
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) property constraints:
MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP,
SEQUENCE{IF NE 0}, UID{UID associated with original
REQUEST} MAY PROPERTY = COMMENT{provides comment from
ATTENDEE to "Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ
0}
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DUE, EXDATE, EXRULE, GEO, LAST-
MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES,
REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.3.6 COUNTER Component/Property Presence
------------------- ---------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "REFRESH"
VTODO MUST
ATTENDEE MUST
DTSTAMP MUST
RECURRENCE-ID MUST only if referring to an instance of a
Recurring calendar component. Otherwise it
MUST NOT be present
UID MUST echo original UID
COMMENT MAY
REQUEST-STATUS MAY
DTSTART MAY
CREATED MAY
DESCRIPTION MAY
PRIORITY MAY
CLASS MAY
CATEGORIES MAY
CONTACT MAY
CREATED MAY
DTEND MAY
GEO MAY
LAST-MODIFIED MAY
PERCENT-COMPLETE MAY
ORGANIZER MAY
PRIORITY MAY
LOCATION MAY
RDATE MAY
RRULE MAY
RELATED-TO MAY
RESOURCE MAY
SEQUENCE MAY
STATUS MAY
TRANSP MAY
URL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VEVENT MAY
VFREEBUSY MAY
X-TOKENS MAY
Silverberg/Mansour/Dawson/Hopson 42 Expires September 1998
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. "Organizer" a counter proposal for the "VTODO" calendar component. The
The "Attendee" MUST send the message to the "Organizer" of the "Attendee" sends the message to the "Organizer" of the "VTODO" calendar
"VTODO" calendar component. component.
Silverberg/Mansour/Dawson/Hopson 35 Expires MAY 1998
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 calendar component describing the complete description of the alternate
alternate "VTODO" calendar component. "VTODO" calendar component.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the "Attendee" a
"Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the "DECLINE-COUNTER" method. The "Organizer" accepts the counter proposal
counter proposal by sending all of the "Attendees" of the "VTODO" by sending all of the "Attendees" of the "VTODO" calendar component a
calendar component a "REQUEST" method rescheduling the "VTODO" "REQUEST" method rescheduling the "VTODO" calendar component. In the
calendar component. In the later case, the "Organizer" SHOULD reset latter case, the "Organizer" SHOULD reset the individual "RSVP" property
the individual "RSVP" property parameter values to TRUE on each parameter values to TRUE on each "ATTENDEE" property; in order to force
"ATTENDEE" property; in order to force a response by the "Attendees". a response by the "Attendees".
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the following
following property constraints: property constraints:
(DESCRIPTION "VTODO- Request" COMPONENT "VTODO" METHOD "REQUEST" Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "COUNTER"
VTODO MUST
DTSTAMP MUST
DTSTART MAY
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
MUST NOT be present.
SEQUENCE MUST be present if NOT 0, MAY be present if 0
SUMMARY MUST be present; MAY be NULL
UID MUST
MUST COMPONENT = CALPROPS ( ATTENDEE MAY
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) ATTACH MAY
MUST COMPONENT = VTODO( CATEGORIES MAY
MUST PROPERTY = ATTENDEE{For Owner and Orginator if different CLASS MAY
and Attendees}, DESCRIPTION{MAYBE NULL}, DTSTAMP, COMMENT MAY
DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID CONTACT MAY
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT,CREATED, CREATED MAY
DUE, EXDATE, EXRULE, GEO, LAST-MODIFIED, DESCRIPTION MAY be present; MAY be NULL
LOCATION,RELATED-TO, RDATE, RECURRENCE-ID, RESOURCES, DURATION MAY
RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED DTEND MAY
/CANCELLED}, SUMMARY{MAYBE NULL}, URL EXDATE MAY
NOT PROPERTY = REQUEST-STATUS) EXRULE MAY
MAY COMPONENT = VTIMEZONE ( GEO MAY
MUST PROPERTY = DTSTART, TZOFFSET LAST-MODIFIED MAY
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
)
3.3.7 DECLINECOUNTER Silverberg/Mansour/Dawson/Hopson 43 Expires September 1998
LOCATION MAY
PERCENT-COMPLETE MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of COMPLETED/NEEDS ACTION/IN-PROCESS
TRANSP MAY
URL MAY
VEVENT MAY
VJOURNAL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VFREEBUSY MAY
X-TOKENS MAY
The "DECLINE-COUNTER" method in a "VTODO" calendar component is used 3.4.8 DECLINECOUNTER
by an "Organizer" of "VTODO" calendar component to reject a counter
proposal offered by one of the "Attendees". The "Organizer" MUST send The "DECLINE-COUNTER" method in a "VTODO" calendar component is used by
the message to the "Attendee" that sent the "COUNTER" method to the an "Organizer" of "VTODO" calendar component to reject a counter
proposal offered by one of the "Attendees". The "Organizer" sends the
message to the "Attendee" that sent the "COUNTER" method to the
"Organizer". "Organizer".
Silverberg/Mansour/Dawson/Hopson 36 Expires MAY 1998 This method type is an iCalendar object that conforms to the following
The counter proposal is an iCalendar object consisting of a "VTODO" property constraints:
calendar component describing the complete description of the
alternate "VTODO" calendar component.
The "Organizer" rejects the counter proposal by sending the Component/Property Presence
"Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the ------------------- ---------------------------------------------
counter proposal by sending all of the "Attendees" of the "VTODO" PRODID MUST
calendar component a "REQUEST" method rescheduling the "VTODO" VERSION MUST be "2.0"
calendar component. Since this is a rescheduled "VTODO", the
"SEQUENCE" property value will be incremented. In the later case, the
"Organizer" SHOULD reset the individual "RSVP" property parameter
values to TRUE on all of the "ATTENDEE" properties in order to force
a response by the "Attendees".
This method type is an iCalendar object that conforms to the METHOD MUST be "DECLINECOUNTER"
following property constraints:
(DESCRIPTION "VTODO - Cancel" COMPONENT "VTODO" METHOD VTODO MUST
"DECLINECOUNTER" ATTENDEE MUST for all attendees
UID MUST must echo original UID
DTSTAMP MUST
SEQUENCE MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
MUST NOT be present.
MUST COMPONENT = CALPROPS ( COMMENT MAY
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD PERCENT-COMPLETE MAY
{"DECLINECOUNTER"}) REQUEST-STATUS MAY
MUST COMPONENT = VTODO( DTSTART MAY
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID CREATED MAY
specified In Original REQUEST and subsequent COUNTER} DESCRIPTION MAY
MAY PROPERTY = COMMENT{provides comment from "Organizer" to ORGANIZER MAY
ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ PRIORITY MAY
0}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DUE, EXDATE, EXRULE, GEO, LAST-
MODIFIED, PRIORITY, RDATE, RELATED-TO, RESOURCES, RRULE,
STATUS, SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.4 Methods For VJOURNAL Component Silverberg/Mansour/Dawson/Hopson 44 Expires September 1998
CLASS MAY
CATEGORIES MAY
CONTACT MAY
CREATED MAY
DTEND MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
RDATE MAY
RRULE MAY
RELATED-TO MAY
RESOURCE MAY
STATUS MAY be one of COMPLETED/NEEDS ACTION/IN-PROCESS
TRANSP MAY
URL MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
VEVENT MAY
VTODO MAY
VFREEBUSY MAY
X-TOKENS MAY
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. Each of the methods applicable to the "VJOURNAL" calendar component.
is defined using a grammar that clarifies the property constraints
that define the particular method.
The following summarizes the methods that are defined for the The following summarizes the methods that are defined for the "VJOURNAL"
"VJOURNAL" calendar component. calendar component.
+================+==================================================+ +================+==================================================+
| Method | Description | | Method | Description |
Silverberg/Mansour/Dawson/Hopson 37 Expires MAY 1998
|================+==================================================| |================+==================================================|
| 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. |
| CANCEL | Cancel an existing journal entry request. | | | |
| REFRESH | A request sent to the journal "Organizer" for | | ADD | Add one or more instances to an existing journal |
| | the latest version of the journal entry to be | | | entry. |
| | resent the requester. | | | |
| CANCEL | Cancel one or more instances of an existing |
| | journal entry. |
+================+==================================================+ +================+==================================================+
3.4.1 PUBLISH 3.5.1 PUBLISH
The "PUBLISH" method in a "VJOURNAL" calendar component has no reply The "PUBLISH" method in a "VJOURNAL" calendar component has no
response associated with it. Instead, it is simply a posting of an associated response. It is simply a posting of an iCalendar object that
iCalendar object that MAY be added to a calendar by a "Calendar User" may be added to a calendar by a CUA. There is no response to the
agent. It requires and accepts no responses to the "Organizer". The "Organizer". The expected usage is for encapsulating an arbitrary
expected usage is for encapsulating an arbitrary journal entry as an journal entry as an iCalendar object. The "Organizer" MAY subsequently
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 Silverberg/Mansour/Dawson/Hopson 45 Expires September 1998
following property constraints:
(DESCRIPTION "Journal - Publish" COMPONENT "VJOURNAL" METHOD update (with another "PUBLISH" method) or cancel (with a "CANCEL"
"PUBLISH method) a previously published journal entry.
MUST COMPONENT = CALPROPS ( This method type is an iCalendar object that conforms to the following
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) property constraints:
MUST COMPONENT = VJOURNAL (
MUST PROPERTY = DESCRIPTION{MAYBE NULL}, DTSTAMP,
DTSTART{VALUE=DATE}, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, ATTENDEE{only ROLE=ORGANIZER and
OWNER if different}, CATEGORIES, CLASS, COMMENT,
CREATED, EXDATE, EXRULE, LAST-MODIFIED, RELATED-TO,
RDATE, RECURRENCE-ID, RRULE, SEQUENCE{IF EQ 0},
SUMMARY{MAYBE NULL}, URL
NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VALARM
NOT COMPONENT = VFREEBUSY
)
Silverberg/Mansour/Dawson/Hopson 38 Expires MAY 1998 Component/Property Presence
------------------- ----------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "PUBLISH"
VJOURNAL MUST
DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
MUST NOT be present.
SEQUENCE MUST be present if not 0, MAY be present if 0
SUMMARY MUST be present and MAY be NULL
UID MUST
3.4.2 CANCEL ATTENDEE MAY
ATTACH MAY
CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present; MAY be NULL.
DURATION MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of DRAFT/FINAL/CANCELLED
TRANSP MAY
URL MAY
The "CANCEL" method in a "VJOURNAL" calendar component is used to VEVENT MAY
send a cancellation notice of an existing journal entry request to VTODO MAY
the "Attendees". The message is sent by the "Organizer" of a journal VTIMEZONE MUST be present if any date/time refers to a
entry to the "Attendees" of the journal entry. For a recurring timezone
journal entry, either the whole journal entry or instances of a VALARM MAY
journal entry MAY be cancelled. To cancel the complete range of a VFREEBUSY MAY
recurring journal entry, the "UID" property value for the journal X-TOKENS MAY
entry MUST be specified in the "CANCEL" method. In order to cancel an
individual instance of the journal entry, the "RECURRENCE-ID"
property value for the journal entry MUST be specified in the
"CANCEL" method. In order to cancel a sequence of instances in a
recurring journal entry, the "RECURRENCE-ID" property for the first
journal entry instance in the sequence MUST be specified with the
"RANGE" property parameter value of THISANDPRIOR or THISANDFUTURE; to
indicate cancellation of the journal entry instances before and after
the first journal entry instance, respectively. Lastly, individual
recurrence instances MAY be cancelled by specifying multiple
"RECURRENCE-ID" properties corresponding to the instances to be
cancelled.
This method type is an iCalendar object that conforms to the Silverberg/Mansour/Dawson/Hopson 46 Expires September 1998
following property constraints:
(DESCRIPTION "Journal - Cancel" COMPONENT "VJOURNAL" METHOD 3.5.2 ADD
"CANCEL"
MUST COMPONENT = CALPROPS ( The "ADD" method in a "VJOURNAL" calendar component is used to add one
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) or more instances to an existing "VJOURNAL" entry. There is no response
MUST COMPONENT = VJOURNAL ( to the "Organizer".
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, LAST-MODIFIED, RDATE, RELATED-TO,
REQUEST-STATUS, RRULE, SUMMARY, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.4.3 REFRESH If the "UID" property value in the "ADD" is not found on the recipient's
calendar, then the recipient MAY treat the "ADD" as a "PUBLISH".
The "REFRESH" method in a "VJOURNAL" calendar component is used by This method type is an iCalendar object that conforms to the following
"Attendees" of an existing journal entry to request an updated property constraints:
description from the journal entry "Organizer". The "REFRESH" method
Silverberg/Mansour/Dawson/Hopson 39 Expires MAY 1998 Component/Property Presence
MUST specify the "UID" property corresponding to the journal entry ------------------- ----------------------------------------------
needing update. A recurrence instance of a journal entry MAY be PRODID MUST
requested by specifying the"RECURRENCE-ID" property corresponding to VERSION MUST be "2.0"
the associated journal entry. The "Organizer" MUST respond with the METHOD MUST be "ADD"
latest description and version of the journal entry. This method is VJOURNAL MUST
intended to facilitate machine processing of the "REFRESH" response. DTSTAMP MUST
DTSTART MUST
ORGANIZER MUST
SEQUENCE MUST be greater than 0
SUMMARY MUST be present and MAY be NULL
UID MUST match that of the original journal
This method type is an iCalendar object that conforms to the ATTACH MAY
following property constraints: CATEGORIES MAY
CLASS MAY
COMMENT MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY be present; may be null.
DURATION MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
LOCATION MAY
PRIORITY MAY
RELATED-TO MAY
RDATE MAY
RESOURCES MAY
RRULE MAY
STATUS MAY be one of DRAFT/FINAL/CANCELLED
TRANSP MAY
URL MAY
(DESCRIPTION "Journal - Refresh" COMPONENT "VJOURNAL" METHOD ATTENDEE NOT
"REFRESH" RECURRENCE-ID NOT
MUST COMPONENT = CALPROPS ( VEVENT MAY
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) VTODO MAY
MUST COMPONENT = VJOURNAL ( VTIMEZONE MUST be present if any date/time refers to a
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP,
SEQUENCE{IF NE 0}, UID{UID associated with original
REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0}
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, EXDATE, EXRULE, LAST-MODIFIED,
PRIORITY, RDATE, RELATED-TO, REQUEST-STATUS, RRULE,
SUMMARY, URL)
MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO
NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM
)
3.5 Status Replies Silverberg/Mansour/Dawson/Hopson 47 Expires September 1998
timezone
VALARM MAY
VFREEBUSY MAY
X-TOKENS MAY
The "REQUEST-STATUS" property MAY include the following values: 3.5.3 CANCEL
The "CANCEL" method in a "VJOURNAL" calendar component is used to send a
cancellation notice of an existing journal entry. The message is sent by
the "Organizer" of a journal entry. For a recurring journal entry,
either the whole journal entry or instances of a journal entry may be
cancelled. To cancel the complete range of a recurring journal entry,
the "UID" property value for the journal entry MUST be specified and a
"RECURRENCE-ID" property MUST NOT be specified in the "CANCEL" method.
In order to cancel an individual instance of the journal entry, the
"RECURRENCE-ID" property value for the journal entry MUST be specified
in the "CANCEL" method.
There are two options for canceling a sequence of instances of a
recurring "VJOURNAL" calendar component:
(a) the "RECURRENCE-ID" property for an instance in the sequence MUST be
specified with the "RANGE" property parameter value of THISANDPRIOR
(or THISANDFUTURE) to indicate cancellation of the specified "VTODO"
calendar component and all instances before (or after); or
(b) individual recurrence instances may be cancelled by specifying
multiple "RECURRENCE-ID" properties corresponding to the instances to
be cancelled.
This method type is an iCalendar object that conforms to the following
property constraints:
Component/Property Presence
------------------- ---------------------------------------------
PRODID MUST
VERSION MUST be "2.0"
METHOD MUST be "CANCEL"
VJOURNAL MUST
DTSTAMP MUST
ORGANIZER MUST
RECURRENCE-ID MUST only if referring to an instance of a
recurring calendar component. Otherwise it
MUST NOT be present.
SEQUENCE MUST
UID MUST be the UID of the original REQUEST
COMMENT MAY
STATUS MAY be present, must be "CANCELLED" if present
ATTACH MAY
ATTENDEE MAY
CATEGORIES MAY
Silverberg/Mansour/Dawson/Hopson 48 Expires September 1998
CLASS MAY
CONTACT MAY
CREATED MAY
DESCRIPTION MAY
DTSTART MAY
DTEND MAY
EXDATE MAY
EXRULE MAY
GEO MAY
LAST-MODIFIED MAY
%-COMPLETE MAY
PRIORITY MAY
RELATED-TO MAY
REQUEST-STATUS MAY
RESOURCES MAY
RDATE MAY
RRULE MAY
STATUS MAY
SUMMARY MAY
TRANSP MAY
URL MAY
VTODO MAY
VEVENT MAY
VFREEBUSY MAY
VTIMEZONE MUST be present if any date/time refers to a
timezone
VALARM MAY
X-TOKENS MAY
3.6 Status Replies
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. | |
|==============+============================+=========================| |==============+============================+=========================|
| 2.2 | Success, invalid property | Property name MAY be | | 2.2 | Success, invalid property | Property name MAY be |
| | ignored. | specified. | | | ignored. | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.3 | Success, invalid property | Property parameter name | | 2.3 | Success, invalid property | Property parameter name |
| | parameter ignored. | and value MAY be | | | parameter ignored. | and value MAY be |
Silverberg/Mansour/Dawson/Hopson 40 Expires MAY 1998
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.4 | Success, unknown non- | Non-standard property | | 2.4 | Success, unknown non- | Non-standard property |
Silverberg/Mansour/Dawson/Hopson 49 Expires September 1998
| | standard property ignored. | name MAY be specified. | | | standard property ignored. | name MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.5 | Success, unknown non | Property and non- | | 2.5 | Success, unknown non | Property and non- |
| | standard property value | standard value MAY be | | | standard property value | standard value MAY be |
| | ignored. | specified. | | | ignored. | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.6 | Success, invalid calendar | Calendar component | | 2.6 | Success, invalid calendar | Calendar component |
| | component ignored. | sentinel (e.g., "BEGIN: | | | component ignored. | sentinel (e.g., "BEGIN: |
| | | ALARM") MAY be | | | | ALARM") MAY be |
| | | specified. | | | | specified. |
skipping to change at line 2039 skipping to change at line 2582
| | ignored. Scheduled as a | name and value MAY be | | | ignored. Scheduled as a | name and value MAY be |
| | single event. | specified. | | | single event. | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.9 | Success, truncated end date| DTEND property value | | 2.9 | Success, truncated end date| DTEND property value |
| | time to date boundary. | MAY be specified. | | | time to date boundary. | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.10 | Success, repeating VTODO | RRULE or RDATE property | | 2.10 | Success, repeating VTODO | RRULE or RDATE property |
| | ignored. Scheduled as a | name and value MAY be | | | ignored. Scheduled as a | name and value MAY be |
| | single VTODO. | specified. | | | single VTODO. | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 2.11 | Success, RRULE or EXRULE | RRULE or EXRULE property|
| | too complex. Scheduled as | name and value MAY be |
| | a single event. | specified. |
|==============+============================+=========================|
| 2.12 | Success, unbounded RRULE | RRULE property name and |
| | clipped at some finite | value MAY be specified. |
| | number of instances | Number of instances MAY |
| | | also be specified. |
|==============+============================+=========================|
| 3.0 | Invalid property name. | Property name MAY be | | 3.0 | Invalid property name. | Property name MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.1 | Invalid property value. | Property name and value | | 3.1 | Invalid property value. | Property name and value |
| | | MAY be specified. | | | | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.2 | Invalid property parameter.| Property parameter name | | 3.2 | Invalid property parameter.| Property parameter name |
| | | and value MAY be | | | | and value MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.3 | Invalid property parameter | Property parameter name | | 3.3 | Invalid property parameter | Property parameter name |
| | value. | and value MAY be | | | value. | and value MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.4 | Invalid calendar component | Calendar component | | 3.4 | Invalid calendar component | Calendar component |
| | sequence. | sentinel MAY be | | | sequence. | sentinel MAY be |
| | | specified (e.g., BEGIN: | | | | specified (e.g., BEGIN: |
| | | VTIMEZONE). | | | | VTIMEZONE). |
|==============+============================+=========================| |==============+============================+=========================|
Silverberg/Mansour/Dawson/Hopson 50 Expires September 1998
| 3.5 | Invalid date or time. | Date/time value(s) MAY | | 3.5 | Invalid date or time. | Date/time value(s) MAY |
| | | be specified. | | | | be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.6 | Invalid rule. | Rule value MAY be | | 3.6 | Invalid rule. | Rule value MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
Silverberg/Mansour/Dawson/Hopson 41 Expires MAY 1998
| 3.7 | Invalid Calendar User. | Attendee property value | | 3.7 | Invalid Calendar User. | Attendee property value |
| | |MAY be specified. | | | |MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.8 | No authority. | PROFILE and ATTENDEE | | 3.8 | No authority. | PROFILE and Attendee |
| | | property values MAY be | | | | property values MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.9 | Unsupported version. | VERSION property name | | 3.9 | Unsupported version. | VERSION property name |
| | | and value MAY be | | | | and value MAY be |
| | | specified. | | | | specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.10 | Request entity too large. | None. | | 3.10 | Request entity too large. | None. |
|==============+============================+=========================| |==============+============================+=========================|
| 3.11 | Required component or | Component or property |
| | property missing. | name MAY be specified. |
|==============+============================+=========================|
| 4.0 | Event conflict. Date/time | DTSTART and DTEND | | 4.0 | Event conflict. Date/time | DTSTART and DTEND |
| | is busy. | property name and values| | | is busy. | property name and values|
| | | MAY be specified. | | | | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 5.0 | Request not supported. | Method property value | | 5.0 | Request MAY supported. | Method property value |
| | | MAY be specified. | | | | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 5.1 | Service unavailable. | ATTENDEE property value | | 5.1 | Service unavailable. | ATTENDEE property value |
| | | MAY be specified. | | | | MAY be specified. |
|==============+============================+=========================| |==============+============================+=========================|
| 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.6 Implementation Considerations 3.7 Implementation Considerations
3.6.1 Working With Recurrence Instances 3.7.1 Working With Recurrence Instances
iCalendar includes a recurrence grammar to represent recurring iCalendar includes a recurrence grammar to represent recurring events.
events. The benefit of such a grammar is the ability to represent a The benefit of such a grammar is the ability to represent a number of
number of events in a single object. However, while this simplifies events in a single object. However, while this simplifies creation of a
creation of a recurring event, meeting instances MAY still need to be recurring event, meeting instances still need to be referenced. For
referenced. For instance, an "Attendee" MAY decline the third instance, an "Attendee" may decline the third instance of a recurring
instance of a recurring Friday event. Similarly, the "Organizer" MAY Friday event. Similarly, the "Organizer" may change the time or location
change the time or location to a single instance of the recurring to a single instance of the recurring event.
event.
Since implementations MAY elect to store recurring events as either a Silverberg/Mansour/Dawson/Hopson 51 Expires September 1998
single event object or a collection of discreet, related event
objects, the protocol is designed so that each recurring instance MAY
be both referenced and versioned. Hence, implementations that choose
to maintain per-instance properties (such as "ATTENDEE" property
"STATUS" parameter) MAY do so. However, the protocol does not require
per-instance recognition unless the instance itself MUST be
renegotiated.
Silverberg/Mansour/Dawson/Hopson 42 Expires MAY 1998 Since implementations may elect to store recurring events as either a
The scenarios for recurrence instance referencing are listed below. single event object or a collection of discreet, related event objects,
For purposes of simplification a change to an event refers to a the protocol is designed so that each recurring instance may be both
"trigger property." That is, a property that has a substantive referenced and versioned. Hence, implementations that choose to maintain
affect on the meeting itself such as start time, location, due date per-instance properties (such as "ATTENDEE" property "attstat"
(for "VTODO" calendar component components) and possibly description. 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" deletes or changes a single instance of a recurring event
. "Organizer" makes changes that affect all future instances . "Organizer" makes changes that affect all future instances
. "Organizer" makes changes that affect all previous instances . "Organizer" makes changes that affect all previous instances
. "Organizer" deletes or modifies a previously changed instance . "Organizer" deletes or modifies a previously changed instance
. Attendee initiated actions: "Attendee" initiated actions:
. Attendee changes status for a particular recurrence instance
. Attendee sends Event-Counter for a particular recurrence . "Attendee" changes status for a particular recurrence instance
instance . "Attendee" sends Event-Counter for a particular recurrence instance
An instance of a recurring event is assigned a unique identification, An instance of a recurring event is assigned a unique identification,
"RECURRENCE-ID" property, when that instance MUST be renegotiated. "RECURRENCE-ID" property, when that instance is renegotiated.
Negotiation is necessary when the start time, end time, due date or Negotiation may be necessary when a substantive change to the event or
location are modified. If the "Organizer" wishes to identify a to-do has be made (such as changing the start time, end time, due date
specific recurrence instance it is done using the "RECURRENCE-ID" or location). The "Organizer" can identify a specific recurrence
property. The property value is equal to the date/time of the instance using the "RECURRENCE-ID" property. The property value is equal
instance. If the "Organizer" wishes to change the"DTSTART", the to the date/time of the instance. If the "Organizer" wishes to change
original "DTSTART" value is used for"RECURRENCE-ID" property and the the "DTSTART", the original "DTSTART" value is used for "RECURRENCE-ID"
new "DTSTART" and "DTEND" values reflect the change. If the property and the new "DTSTART" and "DTEND" values reflect the change.
"Organizer" wishes to add a new instance to the recurring event then Note that after the change has occurred, the "RECURRENCE-ID" has changed
a "REQUEST" is issued with an "RDATE" property equal to the new to the new "DTSTART" value.
instance date. It is recommended that the "Organizer" include the
"RECURRENCE-ID" property[SS1]. Since the creation of a new event
instance requires negotiation, the sequence number is also
incremented.
3.6.2 Attendee Property Considerations 3.7.2 Attendee Property Considerations
The "ATTENDEE" property for the "Organizer" is required on published The "ORGANIZER" property is required on published events, to-dos, and
events, to-dos, and journal entries for two reasons. First, a journal entries for two reasons. First, only the "Organizer" is allowed
published only the "Organizer" is allowed to update an event, to-do, to update and redistribute an event or to-do component. It follows that
or journal entry component. The "Organizer" "ATTENDEE" property MUST the "ORGANIZER" property MUST be present in the event, to-do, or journal
be present in the event, to-do, or journal entry component so that entry component so that the CUA has a basis for authorizing an update.
the "CUA" has a basis for authorizing an update. Second, it is Second, it is prudent to provide a point of contact for anyone who
prudent to provide a point of contact for anyone who receives a receives a published component in case of problems.
published component in case of problems.
There are valid RFC 822 addresses that represent groups. Sending There are valid RFC 822 addresses that represent groups. Sending email
email to such an address results in mail being sent to multiple 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.
Silverberg/Mansour/Dawson/Hopson 43 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 52 Expires September 1998
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 list.
It is recommended that the general approach to finding a "Calendar Thus, it is possible that the recipient of a "REQUEST" does not appear
User" in an attendee list be as follows: explicitly in the list.
It is recommended that the general approach to finding a "Calendar 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 2. Failing (1) look for attendees where "TYPE=GROUP" or
'TYPE=UNKNOWN". The "CUA" MUST then determine if the "CU" is a 'TYPE=UNKNOWN". The CUA then determines if the "Calendar User"
member of one of these groups. If so, the "REPLY" method sent to is a member of one of these groups. If so, the "REPLY" method
the "Organizer" MUST contain a new "ATTENDEE" property in which sent to the "Organizer" MUST contain a new "ATTENDEE" property
the "TYPE" property parameter is set to INDIVIDUAL and the in which the "TYPE" property parameter is set to INDIVIDUAL and
"GROUP" property parameter is set to the name of the group. the "group" property parameter is set to the name of the group.
3. Failing (2) the "CUA" MAY ignore or accept the request as the 3. Failing (2) the CUA MAY ignore or accept the request as the
"Calendar User" wishes. "Calendar User" wishes.
3.6.3 When To Refresh An Event 3.7.3 X-Tokens
An "VEVENT" or "VTODO" calendar component SHOULD be resent to all
"Attendees" whenever the "SEQUENCE" property is incremented or any
other substantive change is made.
3.6.4 Timezones
If a recurring event has any instance where "DTSTART" and "DTEND"
fall on different sides of a time zone shift, the "VTIMEZONE"
components are required.
The threat of duplicate time zone definitions exists. SHOULD an
iCalendar object contain multiple conflicting time zone components,
the one with the latest "DTSTART" property supersedes the others.
3.6.5 Alarms
It is recommended that application software ask the user whether or
not they want alarms included when they read the event.
3.6.6 SUMMARY Property
The minimum support for the "SUMMARY" property in a recipient MUST be
for a 255 byte value. Implementations MAY truncate longer length
values.
Silverberg/Mansour/Dawson/Hopson 44 Expires MAY 1998
3.6.7 X-Tokens
To make iCalendar objects extensible, new property types MAY be To make iCalendar objects extensible, new property types MAY be inserted
inserted into components. These properties are called X-Tokens as into components. These properties are called X-Tokens as they are
they are prefixed with "X-". A client is not required to make sense prefixed with "X-". A client is not required to make sense of X-Tokens.
of X-Tokens. Clients are not required to save X-Tokens or use them in Clients are not required to save X-Tokens or use them in replies.
event 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 In the calendaring and scheduling context, publication refers to the one
one way transfer of event information. Consumers of published events way transfer of event information. Consumers of published events simply
simply incorporate the event into a calendar. No reply is expected. incorporate the event into a calendar. No reply is expected. Individual
Individual "A" publishes an event. Individual "B" reads the event and "A" publishes an event. Individual "B" reads the event and incorporates
incorporates it into their calendar. Events MAY be published in it into their calendar. Events are published in several ways including:
several ways including: embedding the event as an object in a web embedding the event as an object in a web page, e-mailing the event to a
page, e-mailing the event to a distribution list, and posting the distribution list, and posting the event to a newsgroup.
event to a newsgroup.
The table below illustrates the sequence of events between the The table below illustrates the sequence of events between the publisher
publisher and the consumers of a published event. 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 |
Silverberg/Mansour/Dawson/Hopson 53 Expires September 1998
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| "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 The iCalendar object below describes a single event that begins on July
July 1, 1997 at 20:00 UTC. This event contains the minimum set of 1, 1997 at 20:00 UTC. This event contains the minimum set of properties
properties for a "PUBLISH" for a "VEVENT" calendar component. for a "PUBLISH" for a "VEVENT" calendar component.
Silverberg/Mansour/Dawson/Hopson 45 Expires MAY 1998
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
ATTENDEE;ROLE=OWNER:mailto:a@host.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@host.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 The iCalendar object below describes an update to the event described in
in 4.1.1, the time has been changed, an end time has been added, and 4.1.1, the time has been changed, an end time has been added, and the
the sequence number has been adjusted. 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
ATTENDEE;ROLE=OWNER:mailto:A@example.com ORGANIZER:mailto:a@example.com
DTSTAMP:19970612T190000Z DTSTAMP:19970612T190000Z
DTSTART:19970701T210000Z DTSTART:19970701T210000Z
DTEND:19970701T230000Z DTEND:19970701T230000Z
SEQUENCE:2 SEQUENCE:2
UID:0981234-1234234-23@host.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
Silverberg/Mansour/Dawson/Hopson 54 Expires September 1998
The "UID" property is used by the client to identify the event. The The "UID" property is used by the client to identify the event. The
"SEQUENCE" property indicates that this is the second change to the "SEQUENCE" property indicates that this is the second change to the
event. Events with sequence numbers 0 and 1 are superseded by this event. Events with sequence numbers 0 and 1 are superseded by this
event. event.
The "SEQUENCE" property provides a reliable way to distinguish The "SEQUENCE" property provides a reliable way to distinguish different
different versions of the same event. Each time an event is versions of the same event. Each time an event is published, its
published, its sequence number is incremented. If a client receives sequence number is incremented. If a client receives an event with a
an event with a sequence number 5 and finds it has the same event sequence number 5 and finds it has the same event with sequence number
with sequence number 2, the event SHOULD be updated. However, if the 2, the event SHOULD be updated. However, if the client received an event
client received an event with sequence number 2 and finds it already with sequence number 2 and finds it already has sequence number 5 of the
has sequence number 5 of the same event, the event SHOULD NOT be same event, the event MUST NOT be updated.
updated.
Silverberg/Mansour/Dawson/Hopson 46 Expires MAY 1998
4.1.3 Canceling A Published Event 4.1.3 Canceling A Published Event
The iCalendar object below cancels the event described in 4.1.1. This The iCalendar object below cancels the event described in 4.1.1. This
cancels the event with "SEQUENCE" property of 0, 1, and 2. cancels the event with "SEQUENCE" property of 0, 1, and 2.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:CANCEL METHOD:CANCEL
VERSION:2.0 VERSION:2.0
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER:mailto:A@example.com ORGANIZER:mailto:a@example.com
COMMENT:DUKES forfeit the game COMMENT:DUKES forfeit the game
SEQUENCE:2 SEQUENCE:2
UID:0981234-1234234-23@host.com UID:0981234-1234234-23@example.com
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
STATUS:CANCELLED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.1.4 A Rich Published Event 4.1.4 A Rich Published Event
This example describes the same event as in 4.1.1, but in much This example describes the same event as in 4.1.1, but in much greater
greater detail. detail.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:PUBLISH METHOD:PUBLISH
SCALE:GREGORIAN SCALE:GREGORIAN
SOURCE:http://www.midwaystadium.com/stadium-cal/1997-events.or4 SOURCE:http://www.midwaystadium.com/stadium-cal/1997-events.or4
NAME:1997 GAME SCHEDULE
VERSION:2.0 VERSION:2.0
BEGIN:VTIMEZONE
DAYLIGHT:TRUE
DTSTART:19970406T070000-0600
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZNAME:CDT
TZOFFSET:-0500
END:VTIMEZONE
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
DAYLIGHT:FALSE TZID:America-Chicago
DTSTART:19971026T0200-0500 TZURL:http://zones.stds_r_us.net/tz/America-Chicago
LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST TZNAME:CST
TZOFFSET:-0600
END:VTIMEZONE
BEGIN:VEVENT Silverberg/Mansour/Dawson/Hopson 55 Expires September 1998
ATTENDEE;ROLE=OWNER:mailto:A@example.com
Silverberg/Mansour/Dawson/Hopson 47 Expires MAY 1998 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.midwaystadium.com ATTACH:http://www.midwaystadium.com
CATEGORIES:SPORTS EVENT;ENTERTAINMENT CATEGORIES:SPORTS EVENT,ENTERTAINMENT
CLASS:PRIVATE CLASS:PRIVATE
CREATED:19970415T194319Z CREATED:19970415T194319Z
DESCRIPTION:MIDWAY STADIUM\n DESCRIPTION:MIDWAY STADIUM\n
Big time game. MUST see.\n Big time game. MUST see.\n
Expected duration:2 hours\n Expected duration:2 hours\n
DTEND:19970701T180000 DTEND;TZID=America-Chicago:19970701T180000
DTSTART:19970702T160000 DTSTART;TZID=America-Chicago:19970702T160000
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
STATUS:CONFIRMED STATUS:CONFIRMED
LAST-MODIFIED:19970416T162421Z LAST-MODIFIED:19970416T162421Z
LOCATION;VALUE=URL:http://www.midwaystadium.com/ LOCATION;VALUE=URL:http://www.midwaystadium.com/
PRIORITY:2 PRIORITY:2
RESOURCES:SCOREBOARD RESOURCES:SCOREBOARD
SEQUENCE:3 SEQUENCE:3
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
UID:0981234-1234234-23@host.com UID:0981234-1234234-23@example.com
RELATED-TO:0981234-1234234-14@host.com RELATED-TO:0981234-1234234-14@example.com
BEGIN:VALARM BEGIN:VALARM
DTSTART:19970701T190000Z TRIGGER:PT2H
REPEAT:2 ALARM-TYPE:DISPLAY
DURATION:PT2H
CATEGORIES:DISPLAY,AUDIO
DESCRIPTION:It's almost game time DESCRIPTION:It's almost game time
END:VALARM END:VALARM
BEGIN:VALARM BEGIN:VALARM
DTSTART:19970701T153000 TRIGGER:PT30M
CATEGORIES:DISPLAY,AUDIO ALARM-TYPE:AUDIO
DESCRIPTION:You SHOULD leave now. Game starts in 30 min! DESCRIPTION:You SHOULD leave now. Game starts in 30 minutes!
END:VALARM END:VALARM
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The "CLASS" property is specified, though it is not really needed The "RELATED-TO" field contains the "UID" property of a related calendar
here. Since this is a published event, a program that displays it event. The "SEQUENCE" property 3 indicates that this event supersedes
need not apply any content filtering based on the "CLASS" attribute.
If this event is copied into a user's calendar, the "CLASS" would be
included as part of the copy. The handling of the "CLASS" tag at
that point is implementation specific.
The "RELATED-TO" field contains the "UID" property of a related
calendar event. The handling of this property is application
dependent.
The "SEQUENCE" property 3 indicates that this event supersedes
versions 0, 1, and 2. versions 0, 1, and 2.
Silverberg/Mansour/Dawson/Hopson 48 Expires MAY 1998
4.1.5 Anniversaries or Events attached to entire days 4.1.5 Anniversaries or Events attached to entire days
This example demonstrates the use of the "value" parameter to tie a This example demonstrates the use of the "value" parameter to tie a
VEVENT to day rather than a specific time. VEVENT to day rather than a specific time.
Silverberg/Mansour/Dawson/Hopson 56 Expires September 1998
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:PUBLISH METHOD:PUBLISH
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
UID:0981234-1234234-23@host.com UID:0981234-1234234-23@example.com
DTSTART;VALUE=DATE:19970714 DTSTART;VALUE=DATE:19970714
RRULE:FREQ=YEARLY;INTERVAL=1 RRULE:FREQ=YEARLY;INTERVAL=1
SUMMARY: Bastille Day SUMMARY: Bastille Day
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.2 Group Event Examples 4.2 Group Event Examples
Group events are distinguished from published events in that they Group events are distinguished from published events in that they have
have "Attendees" and that there is interaction between the "Attendees" and that there is interaction between the "Attendees" and
"Attendees" with respect to the event. Individual "A" requests a the "Organizer" with respect to the event. Individual "A" requests a
meeting between individuals "A", "B", "C" and "D". Individual "B" meeting between individuals "A", "B", "C" and "D". Individual "B"
confirms attendance to the meeting. Individual "C" declines confirms attendance to the meeting. Individual "C" declines attendance.
attendance. Individual "D" tentatively confirms their attendance. Individual "D" tentatively confirms attendance. The following table
This is sometimes referred to as "penciling-in" the event on a illustrates the the message flow between these individuals. A, the CU
calendar. The following table illustrates the sequence of messages scheduling the meeting, is referenced as the "Organizer".
that would be exchanged between these individuals. The table below
illustrates the message flow.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| 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 STATUS para- | | | | ATTENDEE "attstat" 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 STATUS para- | | | | ATTENDEE "attstat" 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 STATUS para- | | | | ATTENDEE "attstat" para-|
| | | set to "tentative" |
Silverberg/Mansour/Dawson/Hopson 49 Expires MAY 1998
| | | 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 | "C" with updated | | | attendees | "C" with updated | |
| | information. | | | | information. | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Silverberg/Mansour/Dawson/Hopson 57 Expires September 1998
4.2.1 A Group Event Request 4.2.1 A Group Event Request
A sample meeting request that "A" sends to "B", "C", and "D". A sample meeting request is sent from "A" to "B", "C", and "D". _E_ is
also sent a copy of the request but is not expected to attend and need
not reply. "E" illustrates how CUAs might implement a "CC" type feature.
Note the use of the "role" parameter. The default value for the "role"
parameter is "req-participant" and it need not be enumerated. In this
case we are using the value "non-participant" to indicate "E" is a non-
attending CU. The parameter is not needed on 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
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED;CN=BIG A:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example. ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=B:Mailto:B@example.com
com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=C:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example. ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com
com ATTENDEE;RSVP=FALSE;TYPE=ROOM:conf_Big@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example. ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com
com
ATTENDEE;RSVP=FALSE;EXPECT=REQUIRE;TYPE=ROOM:CR_Big@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T100000-0700 DTSTART:19970701T200000Z
DTEND:19970701T103000-0700 DTEND:19970701T203000Z
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.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;STATUS=ACCEPTED:Mailto:B@example.com ATTENDEE;ATTSTAT=ACCEPTED:Mailto:B@example.com
UID:www.acme.com-873970198738777@host.com ORGANIZER:MAILTO:A@example.com
UID:www.acme.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
DTSTAMP:19970612T190000Z DTSTAMP:19970612T190000Z
Silverberg/Mansour/Dawson/Hopson 50 Expires MAY 1998
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"B" could have declined the meeting or indicated tentative acceptance Silverberg/Mansour/Dawson/Hopson 58 Expires September 1998
by setting the ATTENDEE;"STATUS" parameter to DECLINED or TENTATIVE,
respectively. "B" could have declined the meeting or indicated tentative acceptance by
setting the ATTENDEE "attstat" parameter to "declined" or "tentative",
respectively. Also, "REQUEST-STATUS" is not required on a 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(which remains the same) and the SEQUENCE (bumped to 1) property (unchanged) and the "SEQUENCE" (bumped to 1) properties
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
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example. ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example. ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:D@example.com
com ATTENDEE;RSVP=FALSE;TYPE=ROOM:Mailto:Conf@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example. ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com
com DTSTART:19970701T180000Z
ATTENDEE;RSVP=FALSE;EXPECT=REQUIRE;TYPE=ROOM:CR_Big@example.com DTEND:19970701T1200000Z
DTSTART:19970701T110000-0700
DTEND:19970701T113000-0700
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.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
Attendee A sends "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.
Attendee A sends "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
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
Silverberg/Mansour/Dawson/Hopson 59 Expires September 1998
Silverberg/Mansour/Dawson/Hopson 51 Expires MAY 1998
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;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:The Big Conference Room LOCATION:The Big Conference Room
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Attendee B sends "COUNTER" to A, requesting changes to time and "B" sends "COUNTER" to "A", requesting changes to time and place. "B"
place: uses the "COMMENT" property to communicate a rationale for the change:
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
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example. ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;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:The Small Conference Room LOCATION:The Small 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:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Attendee A accepts the changes from B "A" accepts the changes from "B". To accept a counter-proposal, the
"Organizer" sends a new Event REQUEST with an incremented sequence
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
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
Silverberg/Mansour/Dawson/Hopson 52 Expires MAY 1998 ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
DTSTART:19970701T160000Z DTSTART:19970701T160000Z
DTEND:19970701T190000Z DTEND:19970701T190000Z
Silverberg/Mansour/Dawson/Hopson 60 Expires September 1998
SUMMARY:Discuss the Merits of the election results - changed to SUMMARY:Discuss the Merits of the election results - changed to
suite B's schedule meet B's schedule
LOCATION:The Small Conference Room LOCATION:The Small Conference Room
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:1 SEQUENCE:1
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
A rejects B's counter proposal Instead, "A" rejects "B's" counter proposal
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:DECLINECOUNTER METHOD:DECLINECOUNTER
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
com
COMMENT:Sorry, I cannot change this meeting time COMMENT:Sorry, I cannot change this meeting time
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:1 SEQUENCE:1
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
END:VEVENT END:VEVENT
4.2.5 Delegate An Event 4.2.5 Delegating an Event
When delegating an event request to another "Calendar User", the When delegating an event request to another "Calendar User", the
"delegator" MUST both update the "Organizer" with a "REPLY" and send "Delegator" must both update the "Organizer" with a "REPLY" and send a
a request to the "delegatee". There is currently no protocol request to the "Delegate". There is currently no protocol limitation to
limitation to delegation depth. It is possible for the original delegation depth. It is possible for the original delegate to delegate
delegate to delegate the meeting to someone else, and so on. When a the meeting to someone else, and so on. When a request is delegated from
request is delegated from one "CUA" to another there are a number of one CUA to another there are a number of responsibilities required of
responsibilities required of the "delegator". They MUST: the "Delegator". They MUST:
. Send an REPLY to the "Organizer" with their attendee/status
property parameter set to "Delegated"
. Include the delegate as an additional attendee with the
"Delegated-From" property parameter set to the delegator
. Include the original UID of the REQUEST
Silverberg/Mansour/Dawson/Hopson 53 Expires MAY 1998
. The delegator MUST also send a copy of the original REQUEST to
the delegate. The delegator modifies the request to include:
. The ATTENDEE/STATUS property parameter for the delegator . Send an REPLY to the "Organizer" with their "ATTENDEE" property
(sender in this case) is set to "DELEGATED" "attstat" parameter set to "delegated"
. Include the delegate as an additional "Attendee" with the "delegated-
from" property parameter set to the value of the delegator
. Include the original UID of the "REQUEST" method
. The "Delegator" MUST also send a copy of the original "REQUEST"
method to the "Delegate". The delegator modifies the request as
follows:
. The "ATTENDEE" property "attstat" parameter for the delegator (sender
in this case) is set to "delegated"
. "ATTENDEE" "delegated-to" parameter is set to the address of the
"Delegate"
. An "ATTENDEE" property is added for the "Delegate"
. ATTENDEE/DELEGATED-TO parameter is set to the address of the It is not required that the "Delegate" include the "Delegator" in their
delegatee "REPLY" method. However, it is strongly advised since this will inform
the "Delegator" whether the "Delegate" plans to attend the meeting. If
. An ATTENDEE property is added for delegatee Silverberg/Mansour/Dawson/Hopson 61 Expires September 1998
As a rule, it is not required that the "delegatee" include the the "Delegate" declines the meeting, the "Delegator" may elect to
"delegator" in their "REPLY" method. However, it is strongly advised delegate the "REQUEST" to another CUA. The process is the same.
since this will inform the "delegator" whether their proxy plans to
attend the meeting. If the "delegatee" declines the meeting, the
"delegator" MAY elect to try and delegate the "REQUEST" to 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" | |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Delegate: | | "C" sends a REPLY to "A" | | Delegate: | | "C" sends a REPLY to "A" |
| "C" delegates to | | with the ATTENDEE.STATUS | | "C" delegates to | | with the ATTENDEE. |
| "E" | | parameter set to | | "E" | | "attstat"parameter set to|
| | | "DELEGATED" and with a | | | | "delegated" and with a |
| | | new ATTENDEE property | | | | new "ATTENDEE" property |
| | | for "E". "E's" ATTENDEE | | | | for "E". "E's" ATTENDEE |
| | | DELEGATED-FROM property | | | | "delegated-from" param |
| | | is set to "C". "C's" | | | | is set to "C". "C's" |
| | | ATTENDEE.DELEGATED-TO | | | | ATTENDEE "delegated-to" |
| | | property 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 |
| | | ATTENDEE/STATUS property | | | | "attstat" property |
| | | parameter for "C" is set | | | | parameter for "C" is set |
| | | to "DELEGATED" and the | | | | to "delegated" and the |
| | | ATTENDEE/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 |
| | | ATTENDEE/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 ATTENDEE/STATUS | | | | with its "attstat" |
| | | property parameter set | | | | property parameter set |
| | | to "accepted" |
Silverberg/Mansour/Dawson/Hopson 54 Expires MAY 1998
| | | to "ACCEPTED" |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Optional: | "A" sends REQUEST | | | Optional: | "A" sends REQUEST | |
| Redistribute | message to "B", "C" | | | Redistribute | message to "B", "C" | |
| meeting to | and "E". SEQUENCE | | | meeting to | and "E". SEQUENCE | |
| attendees | number is now 1. | | | attendees | number is now 1. | |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
Attendee "C" responds to meeting "Organizer" "A" "C" responds to the "Organizer".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
Silverberg/Mansour/Dawson/Hopson 62 Expires September 1998
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=ATTENDEE;STATUS=DELEGATED;DELEGATED- ORGANIZER:MAILTO:A@Example.com
TO="Mailto:E@example.com":Mailto:C@example.com ATTENDEE;ATTSTAT=DELEGATED;DELEGATED-
UID:www.acme.com-873970198738777@host.com TO=Mailto:E@example.com:Mailto:C@example.com
UID:www.acme.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Attendee "C" delegates presence at the meeting to "E". Attendee "C" delegates presence at the meeting to "E".
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
ATTENDEE;ROLE=ORGANIZER:Mailto:A@example.com ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com ATTENDEE;ATTSTAT=DELEGATED;DELEGATED-
ATTENDEE;ROLE=DELEGATE;RSVP=TRUE;EXPECT=REQUEST; TO=Mailto:E@example.com:Mailto:C@example.com
DELEGATED-FROM=_Mailto:C@example.com_:Mailto:E@example.com ATTENDEE;ROLE=DELEGATE;RSVP=TRUE;
ATTENDEE;ROLE=ATTENDEE;STATUS=DELEGATED; DELEGATED-FROM=Mailto:C@example.com:Mailto:E@example.com
DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com DTSTART:19970701T180000Z
DTSTART:19970701T110000-0700 DTEND:19970701T120000Z
DTEND:19970701T113000-0700
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Silverberg/Mansour/Dawson/Hopson 55 Expires MAY 1998
4.2.6 Delegate Accepts the Meeting 4.2.6 Delegate Accepts the Meeting
To accept a delegated meeting, the delegate sends the following To accept a delegated meeting, the delegate, "E", sends the following
message to "A" and "C" message to "A" and "C"
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;ROLE=ATTENDEE;STATUS=CONFIRMED; ORGANIZER:MAILTO:A@Example.com
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com ATTENDEE;ATTSTAT=CONFIRMED;DELEGATED-
UID:www.acme.com-873970198738777@host.com FROM=Mailto:C@example.com:Mailto:E@example.com
ATTENDEE;ATTSTAT=DELEGATED;DELEGATED-
TO=Mailto:E@example.com:Mailto:C@example.com
UID:www.acme.com-873970198738777@example.com
SEQUENCE:1 SEQUENCE:1
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
Silverberg/Mansour/Dawson/Hopson 63 Expires September 1998
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.2.7 Delegate Declines the Meeting 4.2.7 Delegate Declines the Meeting
In this example the delegate declines the meeting request and sets In this example the "Delegate" declines the meeting request and sets the
the "ATTENDEE" property "STATUS" parameter to DECLINED. The "ATTENDEE" property "attstat" parameter to DECLINED. The "Organizer"
"Organizer" SHOULD resend the "REQUEST" to "C" with the status of the SHOULD resend the "REQUEST" to "C" with the "attstat" parameter of the
delegate set to DECLINED. This lets the "delegator" know that the "Delegate" set to "declined". This lets the "Delegator" know that the
"delegate" has declined and provides an opportunity to the "Delegate" has declined and provides an opportunity to the "Delegator"
"delegator" to either accept or delegate the request to another to either accept the request or delegate it to another CU.
"Calendar User".
Response from "E" to "A" and "C". Response from "E" to "A" and "C".
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;ROLE=ATTENDEE;STATUS=DECLINED; ORGANIZER:MAILTO:A@Example.com
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com ATTENDEE;ATTSTAT=DECLINED;DELEGATED-
UID:www.acme.com-873970198738777@host.com FROM=Mailto:C@example.com:Mailto:E@example.com
UID:www.acme.com-873970198738777@example.com
ATTENDEE;ATTSTAT=DELEGATED;DELEGATED-
TO=Mailto:E@example.com:Mailto:C@example.com
SEQUENCE:1 SEQUENCE:1
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
Silverberg/Mansour/Dawson/Hopson 56 Expires MAY 1998
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=ATTENDEE;STATUS=DECLINED; ORGANIZER:MAILTO:A@Example.com
DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com ATTENDEE;ATTSTAT=DECLINED;DELEGATED-
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example. FROM=Mailto:C@example.com:Mailto:E@example.com
com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL:Mailto:C@example.com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@example.com
SEQUENCE:2 SEQUENCE:2
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
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
Silverberg/Mansour/Dawson/Hopson 64 Expires September 1998
END:VCALENDAR END:VCALENDAR
4.2.8 Forwarding an Event Request 4.2.8 Forwarding an Event Request
The protocol does not prevent an "Attendee" from "forwarding" an The protocol does not prevent an "Attendee" from "forwarding" an
"VEVENT" calendar component to other "Calendar Users". Forwarding "VEVENT" calendar component to other "Calendar Users". Forwarding
differs from delegation in that the forwarded "Calendar User" (often differs from delegation in that the forwarded "Calendar User" (often
referred to as a "Party Crasher") does not replace the forwarding referred to as a "Party Crasher") does not replace the forwarding
"Calendar User". Implementations are not required to add the "Party "Calendar User". Implementations are not required to add the "Party
Crasher" to the "Attendee" list and hence there is no guarantee that Crasher" to the "Attendee" list and hence there is no guarantee that a
a "Party Crasher" will receive additional updates to the Event. The "Party Crasher" will receive additional updates to the Event. The
forwarding "Calendar User" SHOULD NOT add the "Party Crasher" to the forwarding "Calendar User" SHOULD NOT add the "Party Crasher" to the
attendee list. attendee list. The "Organizer" MAY add the forwarded "Calendar User" to
the attendee list.
4.2.9 Cancel A Group Event 4.2.9 Cancel A Group Event
Individual "A" requests a meeting between individuals "A", "B" and Individual "A" requests a meeting between individuals "A", "B", "C", and
"C". Individual "B" declines attendance to the meeting. Individual "D". Individual "B" declines attendance to the meeting. Individual "A"
"A" decides to cancel the meeting. The following table illustrates decides to cancel the meeting. The following table illustrates the
the sequence of messages that would be exchanged between these sequence of messages that would be exchanged between these individuals.
individuals.
Messages related to a previously canceled event ("SEQUENCE" property Messages related to a previously canceled event ("SEQUENCE" property
value is less than the "SEQUENCE" property value of the "CANCEL" value is less than the "SEQUENCE" property value of the "CANCEL"
message) or "VTODO" calendar component MUST be ignored. message) MUST be ignored.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| 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", "C",| |
| | and "C" | | | | and "D" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Decline the meeting| | "B" sends a REPLY | | Decline the meeting| | "B" sends a "REPLY" |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | ATTENDEE STATUS para- | | | | "attstat" para- |
| | | set to "DECLINED". | | | | set to "declined". |
Silverberg/Mansour/Dawson/Hopson 57 Expires MAY 1998
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Cancel the meeting | "A" sends a CANCEL | | | Cancel the meeting | "A" sends a CANCEL | |
| | message to "B" and | | | | message to "B", "C" | |
| | "C" | | | | and "D" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
The example shows how "A" cancels the event. The example shows how "A" cancels the event.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:CANCEL METHOD:CANCEL
VERSION:2.0 VERSION:2.0