draft-ietf-calsch-itip-01.txt   draft-ietf-calsch-itip-02.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
<draft-ietf-calsch-itip-01.txt> Ross Hopson, ON Technologies <ietf-draft-calsch-itip-02.txt> Ross Hopson, ON Technologies
Expires in six months from October 24,1997 Expires in six months from November 21,1997
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 its working groups. Note that other groups MAY also distribute and its working groups. Note that other groups MAY also distribute
skipping to change at line 54 skipping to change at line 54
static and dynamic event, to-do, journal and free/busy objects. static and dynamic event, to-do, journal and free/busy objects.
Static objects are used to transmit information from one entity to Static objects are used to transmit information from one entity to
another without the expectation of continuity or referential another without the expectation of continuity or referential
integrity with the original item. Dynamic objects are a superset of integrity with the original item. Dynamic objects are a superset of
static objects and will gracefully degrade to their static static objects and will gracefully degrade to their static
counterparts for clients that only support static objects. counterparts for clients that only support static objects.
Silverberg/Mansour/Dawson/Hopson 1 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 1 Expires MAY 1998
Silverberg/Mansour/Dawson/Hopson 2 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 2 Expires MAY 1998
Silverberg/Mansour/Dawson/Hopson 3 Expires MAY 1998
Table of Contents Table of Contents
1 7 1 8
Introduction 8 Introduction 9
1.1 Formatting Conventions 8 1.1 Formatting Conventions 9
1.2 Related Documents 9 1.2 Related Documents 10
1.3 Calendar Roles9 1.3 Calendar Roles 10
1.4 iTIP Transactions 10 1.4 iTIP Transactions 11
2 Interoperability Models 11 2 Interoperability Models 12
2.1 Application Protocol 11 2.1 Application Protocol 12
2.1.1 Calendar Entry State 12 2.1.1 Calendar Entry State 13
3 Application Protocol Elements 12 3 Application Protocol Elements 13
3.1 Methods For "VEVENT" Calendar Component13 3.1 Methods For "VEVENT" Calendar Component 15
3.1.1 PUBLISH 14 3.1.1 PUBLISH 15
3.1.2 REQUEST 15 3.1.2 REQUEST 16
3.1.2.1 REQUEST for Rescheduling an Event 16 3.1.2.1 REQUEST for Rescheduling an Event 18
3.1.2.2 REQUEST for Update or Reconfirmation of an Event 16 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 3.1.2.3 REQUEST for Delegating an Event from an "Attendee" to
another CU17 another CU 18
3.1.2.4 REQUEST for Delegating role of "Organizer" to another CU 17 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 3.1.2.5 REQUEST for Changing the "Organizer" from one CU to another
18 19
3.1.2.6 REQUEST for Changing the "Owner"18 3.1.2.6 REQUEST for Changing the "Owner" 19
3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User18 3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User 20
3.1.2.8 REQUEST Updated Attendee Status 18 3.1.2.8 REQUEST Updated Attendee Status 20
3.1.3 REPLY 18 3.1.3 REPLY 20
3.1.4 CANCEL19 3.1.4 CANCEL 21
3.1.5 REFRESH 20 3.1.5 REFRESH 22
3.1.6 COUNTER 21 3.1.6 COUNTER 23
3.1.7 DECLINECOUNTER 22 3.1.7 DECLINECOUNTER 24
3.2 Methods For VFREEBUSY Component 23 3.2 Methods For VFREEBUSY Component 25
3.2.1 PUBLISH 24 3.2.1 PUBLISH 26
3.2.2 REQUEST 25 3.2.2 REQUEST 27
3.2.3 REPLY 26 3.2.3 REPLY 28
3.3 Methods For VTODO Component 27 3.3 Methods For VTODO Component 29
3.3.1 PUBLISH 28 3.3.1 PUBLISH 30
3.3.2 REQUEST 29 3.3.2 REQUEST 31
3.3.2.1 REQUEST for Rescheduling a VTODO30 3.3.2.1 REQUEST for Rescheduling a VTODO 32
3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO30 3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO 33
3.3.2.3 REQUEST for Delegating a VTODO 31 3.3.2.3 REQUEST for Delegating a VTODO 33
3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User31 3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User 34
3.3.2.5 REQUEST Updated Attendee Status 32 3.3.2.5 REQUEST Updated Attendee Status 34
3.3.3 REPLY 32 3.3.3 REPLY 35
3.3.4 CANCEL33 3.3.4 CANCEL 36
3.3.5 REFRESH 34 3.3.5 REFRESH 37
3.3.6 COUNTER 35 3.3.6 COUNTER 37
3.3.7 DECLINECOUNTER 36 3.3.7 DECLINECOUNTER 38
3.4 Methods For VJOURNAL Component 37 3.4 Methods For VJOURNAL Component 39
3.4.1 PUBLISH 37 3.4.1 PUBLISH 40
3.4.2 CANCEL38 3.4.2 CANCEL 41
3.4.3 REFRESH 39 3.4.3 REFRESH 41
3.5 Status Replies39 3.5 Status Replies 42
3.6 Implementation Considerations41
Silverberg/Mansour/Dawson/Hopson 3 Expires MAY 1998
3.6.1 Working With Recurrence Instances 41
3.6.2 Attendee Property Considerations 42
3.6.3 When To Refresh An Event 43
3.6.4 Timezones 43
3.6.5 Alarms43
3.6.6 SUMMARY Property43
3.6.7 X-Tokens 43
4 Examples 44
4.1 Published Event Examples44
4.1.1 A Minimal Published Event 44
4.1.2 Changing A Published Event45
4.1.3 Canceling A Published Event 45
4.1.4 A Rich Published Event 46
4.1.5 Anniversaries or Events attached to entire days 47
4.2 Group Event Examples 48
4.2.1 A Group Event Request48
4.2.2 Reply To A Group Event Request 49
4.2.3 Update An Event 49
4.2.4 Countering an Event Proposal 50
4.2.5 Delegate An Event 51
4.2.6 Delegate Accepts the Meeting 54
4.2.7 Delegate Declines the Meeting 54
4.2.8 Forwarding an Event Request 55
4.2.9 Cancel A Group Event 55
4.3 Busy Time Examples 56
4.3.1 Request Busy Time 56
4.3.2 Reply To A Busy Time Request 57
4.4 Recurring Event and Time Zone Examples 57
4.4.1 A Recurring Event Spanning Time Zones 57
4.4.2 Modify A Recurring Instance 59
4.4.3 Cancel A Recurring Instance 60
4.4.4 Cancel An Exception 60
4.4.5 Cancel Recurring Event 61
4.4.6 Change All Future Instances 61
4.4.7 Add A New Instance To A Recurring Event 62
4.4.8 Counter An Instance Of A Recurring Event 62
4.4.9 Error Reply To A request 63
4.5 Group To-do Examples 64
4.5.1 A VTODO Request 65
4.5.2 A VTODO Reply 65
4.5.3 A VTODO Refresh 65
4.5.4 A Refresh Reply: Percent-Complete 66
4.5.5 A Refresh Reply: Completed66
4.5.6 An Updated VTODO Request 66
4.5.7 A Recurring VTODOs 67
4.5.7.1 Request for a Recurring VTODO 67
4.5.7.2 Calculating due dates in recurring VTODOs 68
4.5.7.3 Replying to an instance of a recurring VTODO 68
4.6 Journal Examples 68
4.7 Other Examples69
4.7.1 Event Refresh 69
4.7.2 Bad RECURRENCE-ID 69
5 Application Protocol Fallbacks 70
5.1 Partial Implementation 70
Silverberg/Mansour/Dawson/Hopson 4 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 4 Expires MAY 1998
5.1.1 Event-Related Fallbacks 70 3.6 Implementation Considerations 44
5.1.2 To-Do-Related Fallbacks 72 3.6.1 Working With Recurrence Instances 44
5.1.3 Journal-Related Fallbacks 74 3.6.2 Attendee Property Considerations 45
5.2 Latency Issues75 3.6.3 When To Refresh An Event 46
5.2.1 Cancellation of an Unknown Calendar Component.75 3.6.4 Timezones 46
5.2.2 Unexpected Reply from an Unknown Delegate75 3.6.5 Alarms 46
5.3 Sequence Number 76 3.6.6 SUMMARY Property 46
6 Security Considerations 76 3.6.7 X-Tokens 47
6.1 Security Threats 76 4 Examples 47
6.1.1 Spoofing the "Organizer" 76 4.1 Published Event Examples 47
6.1.2 Spoofing the "Attendee" 76 4.1.1 A Minimal Published Event 47
6.1.3 Eavesdropping 77 4.1.2 Changing A Published Event 48
6.1.4 Flooding a Calendar 77 4.1.3 Canceling A Published Event 49
6.1.5 Procedural Alarms 77 4.1.4 A Rich Published Event 49
6.2 Recommendations 77 4.1.5 Anniversaries or Events attached to entire days 51
6.2.1 Use of [RFC1847] to secure iTIP transactions 77 4.2 Group Event Examples 51
6.2.2 Implementation Controls 77 4.2.1 A Group Event Request 52
7 Acknowledgments 78 4.2.2 Reply To A Group Event Request 52
8 Bibliography 78 4.2.3 Update An Event 53
9 Authors Addresses 79 4.2.4 Countering an Event Proposal 53
10 Full Copyright Statement 80 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
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 1
Silverberg/Mansour/Dawson/Hopson 5 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 6 Expires MAY 1998
Introduction Introduction
This document specifies how calendaring systems use iCalendar objects This document specifies how calendaring systems use iCalendar objects
to interoperate with other calendar systems. In particular, it to interoperate with other calendar systems. In particular, it
specifies how to schedule events, to-dos, or daily journal entries. specifies how to schedule events, to-dos, or daily journal entries.
It further specifies how to search for available busy time It further specifies how to search for available busy time
information. It does so in a general way so as to allow multiple information. It does so in a general way so as to allow multiple
methods of communication between systems. Subsequent documents methods of communication between systems. Subsequent documents
specify interoperable methods of communications between systems that specify interoperable methods of communications between systems that
use this protocol. use this protocol.
skipping to change at line 242 skipping to change at line 244
"Organizer" of the calendar component. "Organizer" of the calendar component.
Properties defined by [ICAL] are referred to with capitalized, Properties defined by [ICAL] are referred to with capitalized,
quoted-strings of text, followed by the word "property". For example, quoted-strings of text, followed by the word "property". For example,
"ATTENDEE" property refers to the iCalendar property used to convey "ATTENDEE" property refers to the iCalendar property used to convey
the calendar address of a "Calendar User". Property parameters the calendar address of a "Calendar User". Property parameters
defined by this memo are referred to with lower case, quoted-strings defined by this memo are referred to with lower case, quoted-strings
of text, followed by the word "parameter". For example, "value" of text, followed by the word "parameter". For example, "value"
parameter refers to the iCalendar property parameter used to override parameter refers to the iCalendar property parameter used to override
the default data type for a property value. Enumerated values defined the default data type for a property value. Enumerated values defined
Silverberg/Mansour/Dawson/Hopson 7 Expires MAY 1998
by this memo are referred to with capitalized text, either alone or by this memo are referred to with capitalized text, either alone or
followed by the word "value". followed by the word "value".
Silverberg/Mansour/Dawson/Hopson 6 Expires MAY 1998
In tables, the quoted-string text is specified without quotes in In tables, the quoted-string text is specified without quotes in
order to minimize the table length. order to minimize the table length.
1.2 Related Documents 1.2 Related Documents
Implementers will need to be familiar with several other memos that, Implementers will need to be familiar with several other memos that,
along with this one, describe the Internet calendaring and scheduling along with this one, describe the Internet calendaring and scheduling
standards. This document, [ITIP], specifies an interoperability standards. This document, [ITIP], specifies an interoperability
protocol for scheduling between different implementations; protocol for scheduling between different implementations;
skipping to change at line 295 skipping to change at line 298
| | protocol. However, the Owner MAY delegate or | | | protocol. However, the Owner MAY delegate or |
| | assign an Organizer to manage the entry on their | | | assign an Organizer to manage the entry on their |
| | behalf. Usually, a calendar entry Owner is also the | | | behalf. Usually, a calendar entry Owner is also the |
| | Organizer. | | | Organizer. |
| | | | | |
| Organizer | The Organizer controls manipulation of the calendar | | Organizer | The Organizer controls manipulation of the calendar |
| | entry. In most cases, the Owner and the Organizer | | | entry. In most cases, the Owner and the Organizer |
| | are the same Calendar User. | | | are the same Calendar User. |
| | | | | |
| Attendee | An Attendee is a Calendar User associated with | | 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 | | | a calendar entry via a Request method issued by an |
| | Organizer or another Attendee. Attendees are not | | | Organizer or another Attendee. Attendees are not |
| | capable of directly manipulating calendar entries, | | | capable of directly manipulating calendar entries, |
| | but MUST act through the Organizer. | | | but MUST act through the Organizer. |
| | | | | |
| Delegate | A Delegate is a proxy that acts on behalf of another | | Delegate | A Delegate is a proxy that acts on behalf of another |
| | Calendar User. ITIP addresses two forms of | | | Calendar User. ITIP addresses two forms of |
Silverberg/Mansour/Dawson/Hopson 7 Expires MAY 1998
| | delegation: | | | delegation: |
| | 1) An Owner MAY delegate or re-assign an Organizer | | | 1) An Owner MAY delegate or re-assign an Organizer |
| | to manage a calendar entry | | | to manage a calendar entry |
| | 2) An Attendee MAY delegate a calendar entry request | | | 2) An Attendee MAY delegate a calendar entry request |
| | to another Calendar User. | | | to another Calendar User. |
+=====================================================================+ +=====================================================================+
1.4 iTIP Transactions 1.4 iTIP Transactions
This protocol defines seven methods for exchanging [ICAL] objects for This protocol defines seven methods for exchanging [ICAL] objects for
skipping to change at line 350 skipping to change at line 353
| | | | | |
| CANCEL | The Cancel method is used to cancel an existing | | CANCEL | The Cancel method is used to cancel an existing |
| | calendar entry such as a VEVENT or VTODO. | | | calendar entry such as a VEVENT or VTODO. |
| | | | | |
| 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- | | | DECLINE- | |
| COUNTER | Used by the "Organizer" to decline the proposed | | COUNTER | Used by the "Organizer" to decline the proposed |
| | counter-proprosal by an "Attendee" | | | counter-proprosal by an "Attendee" |
+================+==================================================+ +================+==================================================+
Silverberg/Mansour/Dawson/Hopson 8 Expires MAY 1998
2 Interoperability Models 2 Interoperability Models
There are two distinct protocols relevant to interoperability: an There are two distinct protocols relevant to interoperability: an
"Application Protocol" and a "Transport Protocol". The Application "Application Protocol" and a "Transport Protocol". The Application
Protocol defines the content of the iCalendar objects sent between Protocol defines the content of the iCalendar objects sent between
sender and receiver to accomplish the scheduling transactions listed sender and receiver to accomplish the scheduling transactions listed
in section 1.4. The Transport Protocol defines how the iCalendar in section 1.4. The Transport Protocol defines how the iCalendar
objects are sent between the sender and receiver. This document objects are sent between the sender and receiver. This document
focuses on the Application Protocol. focuses on the Application Protocol.
skipping to change at line 402 skipping to change at line 406
| 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 model for the application protocol is centered with the
"Organizer" of the calendar entry. That is, the "Organizer" of a "Organizer" of the calendar entry. That is, the "Organizer" of a
Silverberg/Mansour/Dawson/Hopson 10 Expires MAY 1998
Calendar entry sends a request to one or more "Attendees". The Calendar entry sends a request to one or more "Attendees". The
"Attendees" then reply to the "Organizer". The "Organizer" maintains "Attendees" then reply to the "Organizer". The "Organizer" maintains
the status of the event. the status of the event.
The "Owner" is usually the "Organizer" of the calendar entry. The "Owner" is usually the "Organizer" of the calendar entry.
However, the "Owner" MAY delegate or assign an "Organizer" to manage However, the "Owner" MAY delegate or assign an "Organizer" to manage
the calendar entry on their behalf. In cases where the "Owner" has the calendar entry on their behalf. In cases where the "Owner" has
delegated to another "Organizer", the "Owner" must still be specified delegated to another "Organizer", the "Owner" must still be specified
in associated "REQUEST" and "COUNTER" methods. in associated "REQUEST" and "COUNTER" methods.
Silverberg/Mansour/Dawson/Hopson 9 Expires MAY 1998
The data sources for the application protocol are the "Calendar The data sources for the application protocol are the "Calendar
Users". Examples of these users are the "Organizer" and "Attendees" Users". Examples of these users are the "Organizer" and "Attendees"
of an iCalendar event. The data objects are the iCalendar objects of an iCalendar event. The data objects are the iCalendar objects
that are exchanged between "Calendar Users". 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 state of the entry and the state associated with an overall state of the entry and the state associated with an
"Attendee" to that entry. "Attendee" to that entry.
skipping to change at line 456 skipping to change at line 461
+=================================================+ +=================================================+
| | 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 | Yes | No |
|Cancel | Yes | Yes | Yes | No | |Cancel | 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. Each method type is defined in terms of its associated properties.
Some properties are required, some are optional and others are Some properties are required, some are optional and others are
excluded. The property restrictions are expressed in this memo using excluded. The property restrictions are expressed in this memo using
the following formal notation: the following formal notation:
prop-restriction = "(" description component method prop-restriction = "(" description component method
1*MUST-component *MAY-component *not-component ")" 1*MUST-component *MAY-component *not-component ")"
Silverberg/Mansour/Dawson/Hopson 10 Expires MAY 1998
description = "DESCRIPTION" *ws text description = "DESCRIPTION" *ws text
component = "COMPONENT" *ws ("CALPROPOS" / "VEVENT" / component = "COMPONENT" *ws ("CALPROPOS" / "VEVENT" /
"VTODO" / "VJOURNAL") "VTODO" / "VJOURNAL")
method = "METHOD" *ws <any of the methods defined in this method = "METHOD" *ws <any of the methods defined in this
memo for the associated calendar component> memo for the associated calendar component>
MUST-component = "MUST COMPONENT =" *ws ("VEVENT" / "VTODO" / MUST-component = "MUST COMPONENT =" *ws ("VEVENT" / "VTODO" /
"VJOURNAL" / "VTIMEZONE" / "VALARM" / "VJOURNAL" / "VTIMEZONE" / "VALARM" /
"VFREEBUSY" / "X-TOKEN") "VFREEBUSY" / "X-TOKEN")
*ws "(" [ws] 1*MUST-props *ws *ws "(" [ws] 1*MUST-props *ws
skipping to change at line 511 skipping to change at line 517
constraint on the property parameters constraint on the property parameters
or values> or values>
any = "ANY" -- Specifies that any permissible any = "ANY" -- Specifies that any permissible
properties are allowed - - properties are allowed - -
ws = HTAB / SPACE ws = HTAB / SPACE
HTAB = <Horizontal TAB character> HTAB = <Horizontal TAB character>
SPACE = <Required Space character> SPACE = <Required Space character>
Silverberg/Mansour/Dawson/Hopson 12 Expires MAY 1998
3.1 Methods For "VEVENT" Calendar Component 3.1 Methods For "VEVENT" Calendar Component
This section defines the property set restrictions for the method This section defines the property set restrictions for the method
types that are applicable to the "VEVENT" calendar component. Each of types that are applicable to the "VEVENT" calendar component. Each of
the methods is defined using a grammar that clarifies the property the methods is defined using a grammar that clarifies the property
constraints that define the particular method. 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
"VEVENT" calendar component. "VEVENT" calendar component.
Silverberg/Mansour/Dawson/Hopson 11 Expires MAY 1998
+================+==================================================+ +================+==================================================+
| 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 |
skipping to change at line 562 skipping to change at line 569
encapsulating an arbitrary event or to-do as an iCalendar object. The encapsulating an arbitrary event or to-do as an iCalendar object. The
"Organizer" MAY subsequently update (with another "PUBLISH" method) "Organizer" MAY subsequently update (with another "PUBLISH" method)
or cancel (with a "CANCEL" method) a previously published "VEVENT" or cancel (with a "CANCEL" method) a previously published "VEVENT"
calendar component. 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 property constraints: following property constraints:
(DESCRIPTION "Event - Publish" COMPONENT "VEVENT" METHOD "PUBLISH (DESCRIPTION "Event - Publish" COMPONENT "VEVENT" METHOD "PUBLISH
Silverberg/Mansour/Dawson/Hopson 13 Expires MAY 1998
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{ROLE=OWNER and ORGANIZER if MUST PROPERTY = ATTENDEE{ROLE=OWNER and ORGANIZER if
different}, DESCRIPTION{MAY BE NULL},DTSTAMP, DTSTART, different}, DESCRIPTION{MAY BE NULL},DTSTAMP, DTSTART,
SEQUENCE{IF NE 0}, UID SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER | MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER |
ORGANIZER}, CATEGORIES, CLASS, COMMENT, CONTACT ORGANIZER}, CATEGORIES, CLASS, COMMENT,
CREATED, DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, CREATED, DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED,
LOCATION,PRIORITY, RELATED-TO, RDATE, RECURRENCE-ID, LOCATION,PRIORITY, RELATED-TO, RDATE, RECURRENCE-ID,
RESOURCES, RRULE, SEQUENCE{IF EQ 0}, RESOURCES, RRULE, SEQUENCE{IF EQ 0},
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, STATUS{TENTATIVE/CONFIRMED/CANCELLED},
SUMMARY{MAYBE NULL}, URL SUMMARY{MAYBE NULL}, URL
Silverberg/Mansour/Dawson/Hopson 12 Expires MAY 1998
NOT PROPERTY = REQUEST-STATUS, TRANSP) NOT PROPERTY = REQUEST-STATUS, TRANSP)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME, MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME,
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM ( MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL) URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
3.1.2 REQUEST 3.1.2 REQUEST
The "REQUEST" method in a "VEVENT" calendar component provides the The "REQUEST" method in a "VEVENT" calendar component provides the
following scheduling functions: following scheduling functions:
Invite "Attendees" to an event; . Invite "Attendees" to an event;
Reschedule an existing event; . Reschedule an existing event;
Update the details of an existing event, without rescheduling . Update the details of an existing event, without rescheduling
it; 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;
For an existing "VEVENT" calendar component, delegate the role . For an existing "VEVENT" calendar component, delegate the role
of "Attendee" to another "Calendar User"; of "Attendee" to another "Calendar User";
For an existing "VEVENT" calendar component, delegate the role . For an existing "VEVENT" calendar component, delegate the role
of "Organizer" to another "Calendar User". of "Organizer" to another "Calendar User".
Silverberg/Mansour/Dawson/Hopson 14 Expires MAY 1998
The originator of the "REQUEST" method is the "Organizer" of the The originator of the "REQUEST" method is the "Organizer" of the
event. Normally this is the "Owner" of the event. The recipient of event. Normally this is the "Owner" of the event. The recipient of
the "REQUEST" method is the "Calendar User" invited to the event, the "REQUEST" method is the "Calendar User" invited to the event,
called the "Attendee". The "Attendee" uses the "REPLY" method to called the "Attendee". The "Attendee" uses the "REPLY" method to
convey their attendance status to the "Organizer" of a VEVENT convey their attendance status to the "Organizer" of a VEVENT
"REQUEST". "REQUEST".
The "UID" and "SEQUENCE" properties are used to distinguish the The "UID" and "SEQUENCE" properties are used to distinguish the
various uses of the "REQUEST" method. If the "UID" property value in 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 "VEVENT" calendar component. If the "UID" "REQUEST" is for a new "VEVENT" calendar component. If the "UID"
property value is found on the recipient's calendar, then the property value is found on the recipient's calendar, then the
"REQUEST"' is for either a rescheduling, an update, or a reconfirm of "REQUEST"' is for either a rescheduling, an update, or a reconfirm of
the "VEVENT" calendar component. the "VEVENT" calendar component.
If the "Organizer" of the "REQUEST" method is not authorized to make If the "Organizer" of the "REQUEST" method is not authorized to make
an event request on the "Attendee's" calendar system, then an an event request on the "Attendee's" calendar system, then an
exception is returned in the "REQUEST-STATUS" property of a exception is returned in the "REQUEST-STATUS" property of a
subsequent "REPLY" method, but no scheduling action is performed. subsequent "REPLY" method, but no scheduling action is performed.
Silverberg/Mansour/Dawson/Hopson 13 Expires MAY 1998
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "Event - Request" COMPONENT "VEVENT" METHOD "REQUEST" (DESCRIPTION "Event - Request" COMPONENT "VEVENT" METHOD "REQUEST"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{ ROLE=OWNER and ORGANIZER if MUST PROPERTY = ATTENDEE{ ROLE=OWNER and ORGANIZER if
different and "STATUS parameter absent or different and "STATUS parameter absent or
STATUS=NEEDS-ACTION on Attendees}, DESCRIPTION{MAYBE STATUS=NEEDS-ACTION on Attendees}, DESCRIPTION{MAYBE
NULL}, DTSTAMP,DTSTART,SEQUENCE{IF NE 0}, UID NULL}, DTSTAMP,DTSTART,SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT, CONTACT, MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT, CREATED,
CREATED, DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,
LOCATION, PRIORITY, RDATE, RECURRENCE-ID, RELATED-TO, PRIORITY, RDATE, RECURRENCE-ID, RELATED-TO, RESOURCES,
RESOURCES, RRULE, SEQUENCE{IF EQ 0}, RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED
STATUS{TENTATIVE/CONFIRMED /CANCELLED}, SUMMARY {MAYBE /CANCELLED}, SUMMARY {MAYBE NULL}, TRANSP, URL
NULL}, TRANSP, URL
NOT PROPERTY = REQUEST-STATUS) NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM ( MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL) URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
Silverberg/Mansour/Dawson/Hopson 15 Expires MAY 1998
3.1.2.1 REQUEST for Rescheduling an Event 3.1.2.1 REQUEST for 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 A rescheduled event involves a change to the existing event in terms
of it's time or recurrence intervals and possibly the location or of it's time or recurrence intervals and possibly the location or
description. If the recipient "CUA" of a "REQUEST" method finds that description. If the recipient "CUA" of a "REQUEST" method finds that
the "UID" property value already exists on the calendar, but that the the "UID" property value already exists on the calendar, but that the
"SEQUENCE" property value in the "REQUEST" method is greater than the "SEQUENCE" property value in the "REQUEST" method is greater than the
value for the existing event, then the "REQUEST" method describes a value for the existing event, then the "REQUEST" method describes a
rescheduling of the event. rescheduling of the event.
3.1.2.2 REQUEST for Update or Reconfirmation of an Event 3.1.2.2 REQUEST for Update or Reconfirmation of an Event
The "REQUEST" method MAY be used to update or reconfirm an event. The "REQUEST" method MAY be used to update or reconfirm an event.
An update to an existing event does not involve changes to the time An update to an existing event does not involve changes to the time
or recurrence intervals, and might not involve a change to the or recurrence intervals, and might not involve a change to the
location or description for the event. If the recipient "CUA" of a location or description for the event. If the recipient "CUA" of a
"REQUEST" method finds that the "UID" property value already exists "REQUEST" method finds that the "UID" property value already exists
Silverberg/Mansour/Dawson/Hopson 14 Expires MAY 1998
on the calendar and that the "SEQUENCE" property value in the on the calendar and that the "SEQUENCE" property value in the
"REQUEST" is the same as the value for the existing event, then the "REQUEST" is the same as the value for the existing event, then the
"REQUEST" method describes an update of the event details, but no "REQUEST" method describes an update of the event details, but no
rescheduling of the event. 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" method sent from an "Attendee" to the "Organizer" of an "REFRESH" method sent from an "Attendee" to the "Organizer" of an
event. event.
Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of
skipping to change at line 724 skipping to change at line 729
for delegation is sent by one of the "Attendees" of an existing event for delegation is sent by one of the "Attendees" of an existing event
request to some other "Calendar User". In order to avoid scheduling request to some other "Calendar User". In order to avoid scheduling
loops, the method MUST NOT be sent from an "Attendee" back to the loops, the method MUST NOT be sent from an "Attendee" back to the
"Organizer" of the event. An "Attendee" MAY NOT delegate to the "Organizer" of the event. An "Attendee" MAY NOT delegate to the
"Organizer" of the event. "Organizer" of the event.
For the purposes of this description, the "Attendee" delegating the For the purposes of this description, the "Attendee" delegating the
event is referred to as the "delegator". The "Attendee" receiving the event is referred to as the "delegator". The "Attendee" receiving the
delegation request is referred to as the "delegatee". delegation request is referred to as the "delegatee".
Silverberg/Mansour/Dawson/Hopson 16 Expires MAY 1998
The "delegator" of an event MUST forward the existing "REQUEST" The "delegator" of an event MUST forward the existing "REQUEST"
method for an event to the "delegatee". The event description MUST method for an event to the "delegatee". The event description MUST
include the "delegator's" up-to-date event definition. The "REQUEST" include the "delegator's" up-to-date event definition. The "REQUEST"
method MUST also include an "ATTENDEE" property with the calendar method MUST also include an "ATTENDEE" property with the calendar
address of the "delegatee". The "delegator" MUST also send a "REPLY" address of the "delegatee". The "delegator" MUST also send a "REPLY"
method back to the "Organizer" with the "delegator's" "Attendee" method back to the "Organizer" with the "delegator's" "Attendee"
property "STATUS" parameter value set to DELEGATED. In addition, the property "STATUS" parameter value set to DELEGATED. In addition, the
"DELEGATED-TO" parameter SHOULD be included with the calendar address "DELEGATED-TO" parameter SHOULD be included with the calendar address
of the "delegatee". A response to the delegation "REQUEST" is sent of the "delegatee". A response to the delegation "REQUEST" is sent
from the "delegatee" to the "Organizer" and optionally, to the from the "delegatee" to the "Organizer" and optionally, to the
skipping to change at line 749 skipping to change at line 755
and "EXPECT" property parameters associated with the "delegator's" and "EXPECT" property parameters associated with the "delegator's"
"ATTENDEE" property to that of the "delegatee's" "ATTENDEE" property. "ATTENDEE" property to that of the "delegatee's" "ATTENDEE" property.
For example if the "delegator's" "ATTENDEE" property specifies For example if the "delegator's" "ATTENDEE" property specifies
"RSVP=TRUE;EXPECT=REQUEST", then the "delegatee's" "ATTENDEE" "RSVP=TRUE;EXPECT=REQUEST", then the "delegatee's" "ATTENDEE"
property MUST specify "RSVP=TRUE;EXPECT=REQUEST". property MUST specify "RSVP=TRUE;EXPECT=REQUEST".
3.1.2.4 REQUEST for Delegating role of "Organizer" to another CU 3.1.2.4 REQUEST for Delegating role of "Organizer" to another CU
If the "Owner" of an existing "VEVENT" calendar component wishes to If the "Owner" of an existing "VEVENT" calendar component wishes to
delegate the role of "Organizer" to another CU, they MAY issue delegate the role of "Organizer" to another CU, they MAY issue
Silverberg/Mansour/Dawson/Hopson 15 Expires MAY 1998
another "REQUEST" method that notifies all "Attendees" and the new another "REQUEST" method that notifies all "Attendees" and the new
"Organizer" of this change. The "Owner MUST modify several property "Organizer" of this change. The "Owner MUST modify several property
parameters of the "ATTENDEE" property including the "ROLE", where the parameters of the "ATTENDEE" property including the "ROLE", where the
role of "Owner" and "Organizer" MUST be specified. Additionally, the role of "Owner" and "Organizer" MUST be specified. Additionally, the
"DELEGATED-TO" and "DELEGATED-FROM" parameters MUST specify the "DELEGATED-TO" and "DELEGATED-FROM" parameters MUST specify the
"Organizer" and "Owner" calendar addresses. The "Owner" MAY request "Organizer" and "Owner" calendar addresses. The "Owner" MAY request
reconfirmation by incrementing the "SEQUENCE" property and setting reconfirmation by incrementing the "SEQUENCE" property and setting
the "RSVP" property parameter to TRUE. This will cause a the "RSVP" property parameter to TRUE. This will cause a
reconfirmation to be sent to the new organizer. reconfirmation to be sent to the new organizer.
skipping to change at line 774 skipping to change at line 778
"Organizer" from one "CU" to another by sending a "REQUEST" method. "Organizer" from one "CU" to another by sending a "REQUEST" method.
The "ROLE" property parameter value of ORGANIZER MUST be assigned to The "ROLE" property parameter value of ORGANIZER MUST be assigned to
the new "Organizer". If the old "Organizer" is still an "Attendee" the new "Organizer". If the old "Organizer" is still an "Attendee"
then "ROLE" property parameter for that "CU" MUST be set to ATTENDEE. then "ROLE" property parameter for that "CU" MUST be set to ATTENDEE.
3.1.2.6 REQUEST for Changing the "Owner" 3.1.2.6 REQUEST for Changing the "Owner"
This memo does not support the notion of changing ownership of a This memo does not support the notion of changing ownership of a
"VEVENT" calendar component. "VEVENT" calendar component.
Silverberg/Mansour/Dawson/Hopson 17 Expires MAY 1998
3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User 3.1.2.7 REQUEST Forwarded To An Uninvited Calendar User
An "Attendee" invited to an event MAY invite another uninvited An "Attendee" invited to an event MAY invite another uninvited
"Calendar User" to the event. The invited "Attendee" accomplishes "Calendar User" to the event. The invited "Attendee" accomplishes
this scheduling action by forwarding the original "REQUEST" method to this scheduling action by forwarding the original "REQUEST" method to
the uninvited "Calendar User". The forwarded "REQUEST" method need the uninvited "Calendar User". The forwarded "REQUEST" method need
not include a new "ATTENDEE" property for the uninvited "Attendee". not include a new "ATTENDEE" property for the uninvited "Attendee".
Whether the uninvited "Calendar User" is added to the attendee list, Whether the uninvited "Calendar User" is added to the attendee list,
and thus informed of changes to the "VEVENT" calendar component is an and thus informed of changes to the "VEVENT" calendar component is an
implementation issue. implementation issue.
skipping to change at line 805 skipping to change at line 811
respect to the "REQUEST". respect to the "REQUEST".
This capability MAY also be achieved by the "Organizer" sending the This capability MAY also be achieved by the "Organizer" sending the
"REFRESH" method to the "Attendees". "REFRESH" method to the "Attendees".
3.1.3 REPLY 3.1.3 REPLY
The "REPLY" method in a "VEVENT" calendar component is used to 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 respond (e.g., accept or decline) to a request or to reply to a
delegation request. When used in to provide a delegation response, delegation request. When used in to provide a delegation response,
Silverberg/Mansour/Dawson/Hopson 16 Expires MAY 1998
the "delegator" SHOULD include the calendar address of the the "delegator" SHOULD include the calendar address of the
"delegatee" on the "DELEGATED-TO" property parameter of the "delegatee" on the "DELEGATED-TO" property parameter of the
"delegator's" "ATTENDEE" property. The "delegatee" SHOULD include the "delegator's" "ATTENDEE" property. The "delegatee" SHOULD include the
calendar address of the "delegator" on the "DELEGATED-FROM" property calendar address of the "delegator" on the "DELEGATED-FROM" property
parameter of the "delegatee's" "ATTENDEE" property. parameter of the "delegatee's" "ATTENDEE" property.
The "REPLY" method MAY also be used to respond to an unsuccessful The "REPLY" method MAY also be used to respond to an unsuccessful
"REQUEST" method. Depending on the value of the "REQUEST-STATUS" "REQUEST" method. Depending on the value of the "REQUEST-STATUS"
property no scheduling action MAY have been performed. property no scheduling action MAY have been performed.
The "Organizer" of an event MAY receive the "REPLY" method from a The "Organizer" of an event MAY receive the "REPLY" method from a
"Calendar User" not in the original "REQUEST". For example, a "REPLY" "Calendar User" not in the original "REQUEST". For example, a "REPLY"
method MAY be received from a "delegatee" to an event. In addition, method MAY be received from a "delegatee" to an event. In addition,
the "REPLY" method MAY be received from an unknown "Calendar User", the "REPLY" method MAY be received from an unknown "Calendar User",
forwarded the "REQUEST" from an invited "Attendee". This uninvited forwarded the "REQUEST" from an invited "Attendee". This uninvited
"Attendee" MAY be accepted, or the "Organizer" MAY cancel the event "Attendee" MAY be accepted, or the "Organizer" MAY cancel the event
for the uninvited "Attendee" by sending them a "CANCEL" method to the for the uninvited "Attendee" by sending them a "CANCEL" method to the
univited "Attendee". univited "Attendee".
Silverberg/Mansour/Dawson/Hopson 18 Expires MAY 1998
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "Event - Reply" COMPONENT "VEVENT" METHOD "REPLY" (DESCRIPTION "Event - Reply" COMPONENT "VEVENT" METHOD "REPLY"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE
replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST} associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, EXDATE, EXRULE, RECURRENCE-ID, REQUEST- "Organizer"}, EXDATE, EXRULE, RECURRENCE-ID, REQUEST-
STATUS, SEQUENCE{IF EQ 0}, SUMMARY {MAYBE NULL}, URL STATUS, SEQUENCE{IF EQ 0}, SUMMARY {MAYBE NULL}, URL
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CONTACT, CREATED, NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, GEO, LAST-MODIFIED, DESCRIPTION, DTSTART, DTEND, GEO, LAST-MODIFIED,
PRIORITY, RELATED-TO, RESOURCES, RDATE, RRULE, STATUS, PRIORITY, RELATED-TO, RESOURCES, RDATE, RRULE, STATUS,
SUMMARY, TRANSP) SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
3.1.4 CANCEL 3.1.4 CANCEL
The "CANCEL" method in a "VEVENT" calendar component is used to send The "CANCEL" method in a "VEVENT" calendar component is used to send
a cancellation notice of an existing event request to the a cancellation notice of an existing event request to the
"Attendees". The message is sent by the "Organizer" of an event to "Attendees". The message is sent by the "Organizer" of an event to
the "Attendees" of the event. For a recurring event, either the whole the "Attendees" of the event. For a recurring event, either the whole
event or instances of an event MAY be cancelled. To cancel the event or instances of an event MAY be cancelled. To cancel the
complete range of recurring event, the "UID" property value for the complete range of recurring event, the "UID" property value for the
event MUST be specified in the "CANCEL" method. In order to cancel an event MUST be specified in the "CANCEL" method. In order to cancel an
individual instance of the event, the "RECURRENCE-ID" property value individual instance of the event, the "RECURRENCE-ID" property value
Silverberg/Mansour/Dawson/Hopson 17 Expires MAY 1998
for the event MUST be specified in the "CANCEL" method. In order to for the event MUST be specified in the "CANCEL" method. In order to
cancel a sequence of recurring events, either the"RECURRENCE-ID" cancel a sequence of recurring events, either the"RECURRENCE-ID"
property for the first event instance in the sequence MUST be property for the first event 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 event instances
before and after the first event instance, respectively. Lastly, before and after the first event instance, respectively. Lastly,
individual recurrence instances MAY be cancelled by specifying 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 property constraints: following property constraints:
(DESCRIPTION "Event - Cancel" COMPONENT "VEVENT" METHOD "CANCEL" (DESCRIPTION "Event - Cancel" COMPONENT "VEVENT" METHOD "CANCEL"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"})
Silverberg/Mansour/Dawson/Hopson 19 Expires MAY 1998
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST} associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED} 0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CONTACT, NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
CREATED, DESCRIPTION, DTSTART, DTEND, GEO, LAST- DESCRIPTION, DTSTART, DTEND, GEO, LAST-MODIFIED,
MODIFIED, PRIORITY, RDATE, RELATED-TO, RESOURCES, PRIORITY, RDATE, RELATED-TO, RESOURCES, REQUEST-STATUS,
REQUEST-STATUS, RRULE, SUMMARY, TRANSP, URL) RRULE, SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
3.1.5 REFRESH 3.1.5 REFRESH
skipping to change at line 919 skipping to change at line 924
of event update requests by an "Attendee". 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 property constraints: following property constraints:
(DESCRIPTION "Event - Refresh" COMPONENT "VEVENT" METHOD "REFRESH" (DESCRIPTION "Event - Refresh" COMPONENT "VEVENT" METHOD "REFRESH"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
Silverberg/Mansour/Dawson/Hopson 18 Expires MAY 1998
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP, MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP,
SEQUENCE{IF NE 0}, UID{UID associated with original SEQUENCE{IF NE 0}, UID{UID associated with original
REQUEST} REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0} "Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0}
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CONTACT, CREATED, NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, GEO, DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, GEO,
LAST-MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES, LAST-MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES,
REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL) REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
Silverberg/Mansour/Dawson/Hopson 20 Expires MAY 1998
) )
3.1.6 COUNTER 3.1.6 COUNTER
The "COUNTER" method in a "VEVENT" calendar component is used by an The "COUNTER" method in a "VEVENT" calendar component is used by an
"Attendee" of an existing event to submit to the "Organizer" a "Attendee" of an existing event to submit to the "Organizer" a
counter proposal to the event description. The "Attendee" MUST send counter proposal to the event description. The "Attendee" MUST send
the message to the "Organizer" of the event. the 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 event. alternate event.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the
"Attendee" a VEVENT "DECLINECOUNTER" method. The "Organizer" accepts "Attendee" a VEVENT "DECLINE-COUNTER" method. The "Organizer" accepts
the counter proposal by sending all of the "Attendees" to the event a the counter proposal by sending all of the "Attendees" to the event a
VEVENT "REQUEST" method rescheduling the event. In the later case, VEVENT "REQUEST" method rescheduling the event. In the later case,
the "Organizer" SHOULD reset the individual "RSVP" property parameter the "Organizer" SHOULD reset the individual "RSVP" property parameter
values to TRUE on each "ATTENDEE" property in order to force a values to TRUE on each "ATTENDEE" property in order to force a
response by the "Attendees". 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 property constraints: following property constraints:
(DESCRIPTION "Event - Counter Proposal" COMPONENT "EVENT" (DESCRIPTION "Event - Counter Proposal" COMPONENT "EVENT"
skipping to change at line 973 skipping to change at line 978
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"COUNTER"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"COUNTER"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = ATTENDEE{STATUS parameter absent or MUST PROPERTY = ATTENDEE{STATUS parameter absent or
STATUS=NEEDS ACTION, Owner and Organizer if different, STATUS=NEEDS ACTION, Owner and Organizer if different,
MAY also be used to propose other "Attendees"}, MAY also be used to propose other "Attendees"},
DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART, DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART,
SEQUENCE{IF NE 0}, UID{MUST be the UID associated with SEQUENCE{IF NE 0}, UID{MUST be the UID associated with
the REQUEST being countered} the REQUEST being countered}
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT{provides a MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT{provides a
comment from the ATTENDEE to the "Organizer"}, CONTACT, comment from the ATTENDEE to the "Organizer"}, CREATED,
CREATED, DTEND, EXDATE, EXRULE, GEO, LAST- DTEND, EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,
MODIFIED, LOCATION, PRIORITY, RDATE, RECURRENCE-ID, PRIORITY, RDATE, RECURRENCE-ID, RELATED-TO, RESOURCES,
RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED/
Silverberg/Mansour/Dawson/Hopson 19 Expires MAY 1998 CANCELLED} , SUMMARY {MAYBE NULL}, TRANSP, URL
RELATED-TO, RESOURCES, RRULE, SEQUENCE{IF EQ 0},
STATUS{TENTATIVE/CONFIRMED/CANCELLED} , SUMMARY {MAYBE
NULL}, TRANSP, URL
NOT PROPERTY = COMPLETED, DUE, DURATION, REQUEST-STATUS) NOT PROPERTY = COMPLETED, DUE, DURATION, REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM (IF COMPONENT EXISTS MAY COMPONENT = VALARM (IF COMPONENT EXISTS
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL) NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
Silverberg/Mansour/Dawson/Hopson 21 Expires MAY 1998
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
3.1.7 DECLINECOUNTER 3.1.7 DECLINECOUNTER
The "DECLINECOUNTER" method in a "VEVENT" calendar component is used The "DECLINE-COUNTER" method in a "VEVENT" calendar component is used
by the "Organizer" of an event to reject a counter proposal submitted by the "Organizer" of an event to reject a counter proposal submitted
by an "Attendee". The "Organizer" MUST send the "DECLINECOUNTER" by an "Attendee". The "Organizer" MUST send the "DECLINE-COUNTER"
message to the "Attendee" that sent the "COUNTER" method to the message to the "Attendee" that sent the "COUNTER" method to the
"Organizer". "Organizer".
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 event. alternate event.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the
"Attendee" a "DECLINECOUNTER" method. The "Organizer" accepts the "Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the
counter proposal by sending all of the "Attendees" to the event a counter proposal by sending all of the "Attendees" to the event a
"REQUEST" method; rescheduling the event. Since this is a rescheduled "REQUEST" method; rescheduling the event. Since this is a rescheduled
event, the "SEQUENCE" property value will be incremented. In the event, the "SEQUENCE" property value will be incremented. In the
later case, the "Organizer" SHOULD reset the individual "RSVP" later case, the "Organizer" SHOULD reset the individual "RSVP"
parameter values to TRUE on all of the "ATTENDEE" properties; in parameter values to TRUE on all of the "ATTENDEE" properties; in
order to force a response by the "Attendees". order to force 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 property constraints: following property constraints:
skipping to change at line 1032 skipping to change at line 1036
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"},METHOD{ MUST PROPERTY = PRODID, VERSION{"2.0"},METHOD{
"DECLINECOUNTER"}) "DECLINECOUNTER"})
MUST COMPONENT = VEVENT ( MUST COMPONENT = VEVENT (
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID
specified In Original REQUEST and subsequent COUNTER} specified In Original REQUEST and subsequent COUNTER}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ
0} 0}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CONTACT, NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, GEO,
Silverberg/Mansour/Dawson/Hopson 20 Expires MAY 1998 LAST-MODIFIED, PRIORITY, RDATE, RELATED-TO, RESOURCES,
CREATED, DESCRIPTION, DTSTART, DTEND, EXDATE, EXRULE, RRULE,STATUS, SUMMARY, TRANSP, URL)
GEO, LAST-MODIFIED, PRIORITY, RDATE, RELATED-TO,
RESOURCES, RRULE,STATUS, SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
Silverberg/Mansour/Dawson/Hopson 22 Expires MAY 1998
3.2 Methods For VFREEBUSY Component 3.2 Methods For VFREEBUSY Component
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 defined using a grammar that specifies the property constraints is defined using a grammar that specifies the property constraints
that define the particular method. that define the particular method.
This memo only addresses the transfer of busy time information. This memo 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.
skipping to change at line 1092 skipping to change at line 1096
span a day boundary. Individual "A" requests busy time from span a day boundary. Individual "A" requests busy time from
individuals "B", "C" and "D". Individual "B" and "C" replies with individuals "B", "C" and "D". Individual "B" and "C" replies with
busy time data to individual "A". Individual "D" does not support busy time data to individual "A". Individual "D" does not support
busy time requests and does not reply with any data. If the transport busy time requests and does not reply with any data. If the transport
binding supports exception messages, then a "unsupported capability" binding supports exception messages, then a "unsupported capability"
message is returned by individual "D" to individual "A". message is returned by individual "D" 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 21 Expires MAY 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.2.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 "Calendar
User" to any other. The purpose of the method is to provide a message User" to any other. The purpose of the method is to provide a message
for sending unsolicited busy time data. That is, the busy time data for sending unsolicited busy time data. That is, the busy time data
is not being sent as a "REPLY" to the receipt of a "REQUEST" method. is not being sent as a "REPLY" to the receipt of a "REQUEST" method.
Busy time intervals are represented by individual instances of the Busy time intervals are represented by individual instances of the
"FREEBUSY" property. There is one occurrence of the property for each "FREEBUSY" property. There is one occurrence of the property for each
skipping to change at line 1148 skipping to change at line 1153
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "Busy - Busy Time Publish" COMPONENT "VFREEBUSY" (DESCRIPTION "Busy - Busy Time Publish" COMPONENT "VFREEBUSY"
METHOD "PUBLISH" METHOD "PUBLISH"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"})
MUST COMPONENT = VFREEBUSY ( MUST COMPONENT = VFREEBUSY (
MUST PROPERTY = ATTENDEE{address of originator of busy time MUST PROPERTY = ATTENDEE{address of originator of busy time
Silverberg/Mansour/Dawson/Hopson 22 Expires MAY 1998
data},FREEBUSY{values MUST all be of the same data type. data},FREEBUSY{values MUST all be of the same data type.
Multiple instances are allowed. Multiple instances MUST Multiple instances are allowed. Multiple instances MUST
be sorted in ascending order. Values MAY NOT overlap}, be sorted in ascending order. Values MAY NOT overlap},
RELATED-TO{refers to another related VFREEBUSY RELATED-TO{refers to another related VFREEBUSY
Silverberg/Mansour/Dawson/Hopson 24 Expires MAY 1998
component}, component},
MAY PROPERTY = COMMENT{comment from attendee to originator of MAY PROPERTY = COMMENT{comment from attendee to originator of
request}, CREATED{specifies when the busy time data was request}, CREATED{specifies when the busy time data was
created}, DTSTART{represents start of interval for busy created}, DTSTART{represents start of interval for busy
time data}, DTEND{represents end of interval for busy time data}, DTEND{represents end of interval for busy
time data},LAST-MODIFIED{specifies when busy time data time data},LAST-MODIFIED{specifies when busy time data
was last modified}, SEQUENCE{IF EQ 0}, URL{specifies busy was last modified}, SEQUENCE{IF EQ 0}, URL{specifies busy
time URL} time URL}
NOT PROPERTY = DTSTAMP, DURATION, REQUEST-STATUS, SEQUENCE, NOT PROPERTY = DTSTAMP, DURATION, REQUEST-STATUS, SEQUENCE,
UID) UID)
skipping to change at line 1206 skipping to change at line 1211
busy time request on the recipient's calendar system, then an busy time request on the recipient's calendar system, then an
exception message is returned in a "REPLY" method, but no busy time exception message is returned in a "REPLY" method, but no busy time
data need be returned. data 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 property constraints: following property constraints:
(DESCRIPTION "FREEBUSY - Request For Busy Time" COMPONENT (DESCRIPTION "FREEBUSY - Request For Busy Time" COMPONENT
"VFREEBUSY" METHOD "REQUEST" "VFREEBUSY" METHOD "REQUEST"
Silverberg/Mansour/Dawson/Hopson 23 Expires MAY 1998
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
Silverberg/Mansour/Dawson/Hopson 25 Expires MAY 1998
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"})
MUST COMPONENT = VFREEBUSY ( MUST COMPONENT = VFREEBUSY (
MUST PROPERTY = ATTENDEE{Attendee instances for the Owner and MUST PROPERTY = ATTENDEE{Attendee instances for the Owner and
Organizer if different and the intended recipient of the Organizer if different and the intended recipient of the
request}, DTSTAMP, DTSTART, DTEND,SEQUENCE{IF NE 0}, UID request}, DTSTAMP, DTSTART, DTEND,SEQUENCE{IF NE 0}, UID
MAY PROPERTY = SEQUENCE{IF EQ 0} MAY PROPERTY = SEQUENCE{IF EQ 0}
NOT PROPERTY = COMMENT, CREATED, DURATION, FREEBUSY, NOT PROPERTY = COMMENT, CREATED, DURATION, FREEBUSY,
LAST-MODIFIED, RELATED-TO, URL, REQUEST-STATUS) LAST-MODIFIED, RELATED-TO, URL, REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
skipping to change at line 1261 skipping to change at line 1267
the busy time for earlier today. the busy time for earlier today.
Since events MAY span a day boundary, free busy time period MAY also Since events MAY span a day boundary, free busy time period MAY also
span a day boundary. span a day boundary.
The busy time periods MAY be grouped into more than one "VFREEBUSY" The busy time periods MAY be grouped into more than one "VFREEBUSY"
calendar component. This capability allows busy time periods to be calendar component. This capability allows busy time periods to be
grouped according to some common periodicity, such as a calendar grouped according to some common periodicity, such as a calendar
week, month, or year. In this case, each "VFREEBUSY" calendar week, month, or year. In this case, each "VFREEBUSY" calendar
component MUST include the "ATTENDEE", "DTSTART" and "DTEND" component MUST include the "ATTENDEE", "DTSTART" and "DTEND"
Silverberg/Mansour/Dawson/Hopson 26 Expires MAY 1998
properties in order to identify the source and date and time range properties in order to identify the source and date and time range
for the busy time data. for the busy time data.
Silverberg/Mansour/Dawson/Hopson 24 Expires MAY 1998
The "ATTENDEE" property MUST be specified in the busy time reply. The The "ATTENDEE" property MUST be specified in the busy time reply. The
value is the fully qualified RFC 822 address of the recipient value is the fully qualified RFC 822 address of the recipient
replying to the busy time request. replying to the busy time request.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "FreeBusy - Busy Time Reply" COMPONENT "VFREEBUSY" (DESCRIPTION "FreeBusy - Busy Time Reply" COMPONENT "VFREEBUSY"
METHOD "REPLY" METHOD "REPLY"
skipping to change at line 1314 skipping to change at line 1321
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 grammar that specifies the property constraints that
define the particular method. 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|
Silverberg/Mansour/Dawson/Hopson 25 Expires MAY 1998
| | one or more Calendar Users.VTODO REQUEST method | | | one or more Calendar Users.VTODO 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 view it as a PUBLISH. |
| REPLY | Reply to a VTODO request. Attendees MAY set | | REPLY | Reply to a VTODO request. Attendees MAY set |
| | status to ACCEPTED, DECLINED, TENTATIVE, | | | status to ACCEPTED, DECLINED, TENTATIVE, |
| | DELEGATED, PARTIAL, and COMPLETED. | | | DELEGATED, PARTIAL, and COMPLETED. |
| CANCEL | Cancel an existing VTODO assignment. | | CANCEL | Cancel an existing VTODO assignment. |
| 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 |
skipping to change at line 1359 skipping to change at line 1366
(DESCRIPTION "VTODO - Publish" COMPONENT "VTODO" METHOD "PUBLISH (DESCRIPTION "VTODO - Publish" COMPONENT "VTODO" METHOD "PUBLISH
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{only Owner and Organizer if MUST PROPERTY = ATTENDEE{only Owner and Organizer if
different}, DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART, different}, DESCRIPTION{MAYBE NULL}, DTSTAMP, DTSTART,
PRIORITY, SEQUENCE{IF NE 0}, UID PRIORITY, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER | MAY PROPERTY = ATTACH, ATTENDEE{other than ROLE=OWNER |
ORGANIZER}, CATEGORIES, CLASS, COMMENT, COMPLETED, ORGANIZER}, CATEGORIES, CLASS, COMMENT, CREATED, DUE,
CONTACT, CREATED, DUE, EXDATE, EXRULE, GEO, LAST- EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION,PERCENT-
MODIFIED, LOCATION,PERCENT-COMPLETE, RELATED-TO, RDATE, COMPLETE, RELATED-TO, RDATE, RECURRENCE-ID, RESOURCES,
RECURRENCE-ID, RESOURCES, RRULE, SEQUENCE{IF EQ 0}, RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, SUMMARY{MAYBE /CANCELLED}, SUMMARY{MAYBE NULL}, URL
NULL}, URL
NOT PROPERTY = REQUEST-STATUS) NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
Silverberg/Mansour/Dawson/Hopson 28 Expires MAY 1998
MAY COMPONENT = VALARM ( MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL) NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
Silverberg/Mansour/Dawson/Hopson 26 Expires MAY 1998
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
3.3.2 REQUEST 3.3.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 . Update the details of an existing to-do, without rescheduling
it; it;
Update the completion status of "Attendees" of an existing to- . Update the completion status of "Attendees" of an existing to-
do, without rescheduling it; 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=ATTENDEE" 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,
called the Attendee. The "Attendee" uses the "REPLY" method to convey called the Attendee. The "Attendee" uses the "REPLY" method to convey
their acceptance and completion status to the "Organizer" of the their acceptance and completion status to the "Organizer" of the
"REQUEST". "REQUEST".
skipping to change at line 1424 skipping to change at line 1430
"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 for either a
rescheduling, an update, or a reconfirm of the "VTODO" calendar rescheduling, an 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 to-do request on the "Attendee's" calendar system, then an a to-do request on the "Attendee's" calendar system, then an
exception is returned in the "REQUEST-STATUS" property of a exception is returned in the "REQUEST-STATUS" property of a
subsequent "REPLY" method, but no scheduling action is performed. subsequent "REPLY" 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 This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "VTODO - Request" COMPONENT "VTODO" METHOD "REQUEST" (DESCRIPTION "VTODO - Request" COMPONENT "VTODO" METHOD "REQUEST"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{For Owner and Organizer if different MUST PROPERTY = ATTENDEE{For Owner and Organizer if different
and each Attendee},DESCRIPTION{MAYBE NULL}, DTSTAMP, and each Attendee},DESCRIPTION{MAYBE NULL}, DTSTAMP,
DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT, CONTACT, MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT,
Silverberg/Mansour/Dawson/Hopson 27 Expires MAY 1998
CREATED, DUE, EXDATE, EXRULE, GEO, LAST-MODIFIED, CREATED, DUE, EXDATE, EXRULE, GEO, LAST-MODIFIED,
LOCATION, PERCENT-COMPLETE, RELATED-TO, RDATE, LOCATION, PERCENT-COMPLETE, RELATED-TO, RDATE,
RECURRENCE-ID, RESOURCES, RRULE, SEQUENCE{IF EQ 0}, RECURRENCE-ID, RESOURCES, RRULE, SEQUENCE{IF EQ 0},
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, SUMMARY{MAYBE STATUS{TENTATIVE/CONFIRMED/CANCELLED}, SUMMARY{MAYBE
NULL}, URL NULL}, URL
NOT PROPERTY = COMPLETED, REQUEST-STATUS) NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM ( MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO,
URL) URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
3.3.2.1 REQUEST for Rescheduling a VTODO 3.3.2.1 REQUEST for Rescheduling a VTODO
skipping to change at line 1473 skipping to change at line 1478
A rescheduled "VTODO" calendar component involves a change to the A rescheduled "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 it's start or due
time or recurrence intervals and possibly the description. If the time or recurrence intervals and possibly the description. If the
recipient "CUA" of a "REQUEST" method finds that the "UID" property recipient "CUA" of a "REQUEST" method finds that the "UID" property
value already exists on the calendar, but that the "SEQUENCE" value already exists on the calendar, but that the "SEQUENCE"
property value in the "REQUEST" is greater than the value for the property value in the "REQUEST" is greater than the value for the
existing VTODO, then the "REQUEST" method describes a rescheduling of existing VTODO, then the "REQUEST" method describes a rescheduling of
the "VTODO" calendar component. the "VTODO" calendar component.
Silverberg/Mansour/Dawson/Hopson 30 Expires MAY 1998
3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO 3.3.2.2 REQUEST for Update or Reconfirmation of a VTODO
The "REQUEST" method MAY be used to update or reconfirm a "VTODO" The "REQUEST" method MAY be used to update or reconfirm a "VTODO"
calendar component. Reconfirmation is merely an update of "Attendee" calendar component. Reconfirmation is merely an update of "Attendee"
completion status or overall "VTODO" calendar component status. completion status or overall "VTODO" calendar component status.
An update to an existing "VTODO" calendar component does not involve An update to an existing "VTODO" calendar component does not involve
changes to the start or due time or recurrence intervals, nor changes to the start or due time or recurrence intervals, nor
generally to the description for the "VTODO" calendar component. If generally to the description for the "VTODO" calendar component. If
the recipient "CUA" of a "REQUEST" method finds that the "UID" the recipient "CUA" of a "REQUEST" method finds that the "UID"
property value already exists on the calendar and that the "SEQUENCE" property value already exists on the calendar and that the "SEQUENCE"
property value in the "REQUEST" is the same as the value for the property value in the "REQUEST" is the same as the value for the
existing event, then the "REQUEST" method describes an update of the existing event, then the "REQUEST" method describes an update of the
"VTODO" calendar component details, but no rescheduling of the "VTODO" calendar component details, but no 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 sent from an "Attendee" to the "Organizer" of a "VTODO" method sent from an "Attendee" to the "Organizer" of a "VTODO"
calendar component. calendar component.
Silverberg/Mansour/Dawson/Hopson 28 Expires MAY 1998
Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of Unsolicited "REQUEST" methods MAY also be sent by the "Organizer" of
a "VTODO" calendar component. The unsolicited "REQUEST" methods MAY a "VTODO" calendar component. The unsolicited "REQUEST" methods MAY
be used to either update the details of the VTODO, without be used to either update the details of the VTODO, without
rescheduling it or to update the completion status of "Attendees" or rescheduling it or to update the completion status of "Attendees" or
the "VTODO" calendar component itself (i.e., reconfirm the VTODO). the "VTODO" calendar component itself (i.e., reconfirm the VTODO).
3.3.2.3 REQUEST for Delegating a VTODO 3.3.2.3 REQUEST for Delegating a VTODO
The "REQUEST" method MAY be used to delegate or reassign ownership of The "REQUEST" method MAY be used to delegate or reassign ownership of
a "VTODO" calendar component to another "Calendar User". The a "VTODO" calendar component to another "Calendar User". The
skipping to change at line 1526 skipping to change at line 1532
"delegatee". "delegatee".
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 "delegatee". The "VTODO" calendar component description MUST include
the "delegator's" up-to-date "VTODO" calendar component definition. the "delegator's" up-to-date "VTODO" calendar component definition.
The "REQUEST" method MUST also include an "ATTENDEE" property with The "REQUEST" method MUST also include an "ATTENDEE" property with
the calendar address of the "delegatee". The "delegator" MUST also the calendar address of the "delegatee". The "delegator" MUST also
send a "REPLY" method back to the "Organizer" with the "delegator's" send a "REPLY" method back to the "Organizer" with the "delegator's"
"Attendee" property "STATUS" parameter value set to DELEGATED. In "Attendee" property "STATUS" parameter value set to DELEGATED. In
Silverberg/Mansour/Dawson/Hopson 31 Expires MAY 1998
addition, the "DELEGATED-TO" parameter SHOULD be included with the addition, the "DELEGATED-TO" parameter SHOULD be included with the
calendar address of the "delegatee". A response to the delegation calendar address of the "delegatee". A response to the delegation
"REQUEST" is sent from the "delegatee" to the "Organizer" and "REQUEST" is sent from the "delegatee" to the "Organizer" and
optionally, to the "delegator". The "REPLY" method from the optionally, to the "delegator". The "REPLY" method from the
"delegatee" SHOULD include the "ATTENDEE" property with their "delegatee" SHOULD include the "ATTENDEE" property with their
calendar address and the "DELEGATED-FROM" parameter with the value of calendar address and the "DELEGATED-FROM" parameter with the value of
the "delegator's"calendar address. the "delegator's"calendar address.
The delegation "REQUEST" method MUST assign the values of the "RSVP" The delegation "REQUEST" method MUST assign the values of the "RSVP"
and "EXPECT" property parameters associated with the "delegator's" and "EXPECT" property parameters associated with the "delegator's"
skipping to change at line 1550 skipping to change at line 1558
3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User 3.3.2.4 REQUEST Forwarded To An Uninvited Calendar User
An "Attendee" assigned a "VTODO" calendar component MAY also assign An "Attendee" assigned a "VTODO" calendar component MAY also assign
the "VTODO" calendar component to another new "Calendar User", not the "VTODO" calendar component to another new "Calendar User", not
previously associated with the "VTODO" calendar component. The previously associated with the "VTODO" calendar component. The
current "Attendee" assigned the "VTODO" calendar component current "Attendee" assigned the "VTODO" calendar component
accomplishes this scheduling action by forwarding the original accomplishes this scheduling action by forwarding the original
"REQUEST" method to the new "Calendar User". "REQUEST" method to the new "Calendar User".
Silverberg/Mansour/Dawson/Hopson 29 Expires MAY 1998
An "Organizer" of a "VTODO" calendar component MAY also request an An "Organizer" of a "VTODO" calendar component MAY also request an
updated completion status from one of the "Attendees". This is updated completion status from one of the "Attendees". This is
achieved by the "Organizer" sending a "REQUEST" method to the achieved by the "Organizer" sending a "REQUEST" method to the
"Attendee" with the "ATTENDEE;RSVP=TRUE" property sequence. The "Attendee" with the "ATTENDEE;RSVP=TRUE" property sequence. The
"SEQUENCE" property for the "VTODO" calendar component is not changed "SEQUENCE" property for the "VTODO" calendar component is not changed
from its previous value. A recipient will determine that the only from its previous value. A recipient will determine that the only
change in the "REQUEST" is that their "RSVP" property parameter change in the "REQUEST" is that their "RSVP" property parameter
indicates a request for an updated status. The recipient SHOULD indicates a request for an updated status. The recipient SHOULD
respond with a "REPLY" method indicating their current status with respond with a "REPLY" method indicating their current status with
respect to the "REQUEST". respect to the "REQUEST".
skipping to change at line 1577 skipping to change at line 1584
property sequence. The "SEQUENCE" property for the to-do is not property sequence. The "SEQUENCE" property for the to-do is not
changed from its previous value. A recipient will determine that the changed from its previous value. A recipient will determine that the
only change in the "REQUEST" is that their "RSVP" property parameter only change in the "REQUEST" is that their "RSVP" property parameter
indicates a request for an updated status. The recipient SHOULD indicates a request for an updated status. The recipient SHOULD
respond with a "REPLY" method indicating their current status with respond with a "REPLY" method indicating their current status with
respect to the "REQUEST". respect to the "REQUEST".
This capability MAY also be achieved by the "Organizer" sending the This capability MAY also be achieved by the "Organizer" sending the
"REFRESH" method to the "Attendees". "REFRESH" method to the "Attendees".
Silverberg/Mansour/Dawson/Hopson 32 Expires MAY 1998
3.3.3 REPLY 3.3.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 "delegatee" in the
"DELEGATED-TO" parameter of the "delegator's" "ATTENDEE" property. "DELEGATED-TO" parameter of the "delegator's" "ATTENDEE" property.
The "delegatee" SHOULD include the calendar address of the The "delegatee" SHOULD include the calendar address of the
"delegator" on the "DELEGATED-FROM" parameter of the "delegatee's" "delegator" on the "DELEGATED-FROM" parameter of the "delegatee's"
skipping to change at line 1608 skipping to change at line 1617
from an original "Attendee" assigned the "VTODO" calendar component. from an original "Attendee" assigned the "VTODO" calendar component.
This uninvited "Attendee" MAY be accepted, or the "Organizer" MAY This uninvited "Attendee" MAY be accepted, or the "Organizer" MAY
cancel the "VTODO" calendar component for the uninvited "Attendee" by cancel the "VTODO" calendar component for the uninvited "Attendee" by
sending them a "CANCEL" method. sending them a "CANCEL" method.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "VTODO - Reply" COMPONENT "VTODO" METHOD "REPLY" (DESCRIPTION "VTODO - Reply" COMPONENT "VTODO" METHOD "REPLY"
Silverberg/Mansour/Dawson/Hopson 30 Expires MAY 1998
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REPLY"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE MUST PROPERTY = ATTENDEE{MUST be address of ATTENDEE
replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID replying}, DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST} associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, COMPLETED, EXDATE, EXRULE, RECURRENCE-ID, "Organizer"}, EXDATE, EXRULE, RECURRENCE-ID, REQUEST-
REQUEST-STATUS, PERCENT-COMPLETE, SEQUENCE{IF EQ 0}, STATUS, PERCENT-COMPLETE, SEQUENCE{IF EQ 0}, SUMMARY
SUMMARY {MAYBE NULL}, URL {MAYBE NULL}, URL
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CONTACT, CREATED, NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, DUE, GEO, LAST-MODIFIED, PRIORITY, DESCRIPTION, DTSTART, DUE, GEO, LAST-MODIFIED, PRIORITY,
RELATED-TO, RESOURCES, RDATE, RRULE, STATUS, SUMMARY, RELATED-TO, RESOURCES, RDATE, RRULE, STATUS, SUMMARY,
TRANSP) TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
Silverberg/Mansour/Dawson/Hopson 33 Expires MAY 1998
3.3.4 CANCEL 3.3.4 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 request
to the "Attendees". The message is sent by the "Organizer" of a to the "Attendees". The message is sent by the "Organizer" of a
"VTODO" calendar component to the "Attendees" of the "VTODO" calendar "VTODO" calendar component to the "Attendees" of the "VTODO" calendar
component. For a recurring "VTODO" calendar component, either the component. For a recurring "VTODO" calendar component, either the
whole "VTODO" calendar component or instances of a "VTODO" calendar whole "VTODO" calendar component or instances of a "VTODO" calendar
component MAY be cancelled. To cancel the complete range of a component MAY be cancelled. To cancel the complete range of a
recurring "VTODO" calendar component, the "UID" property value for recurring "VTODO" calendar component, the "UID" property value for
skipping to change at line 1662 skipping to change at line 1672
"RECURRENCE-ID" properties corresponding to the instances to be "RECURRENCE-ID" properties corresponding to the instances to be
cancelled. cancelled.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "VTODO - Cancel" COMPONENT "VTODO" METHOD "CANCEL" (DESCRIPTION "VTODO - Cancel" COMPONENT "VTODO" METHOD "CANCEL"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"})
Silverberg/Mansour/Dawson/Hopson 31 Expires MAY 1998
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST} associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED} 0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
COMPLETED, CONTACT, CREATED, DESCRIPTION, DTSTART, DUE, DESCRIPTION, DTSTART, DUE, GEO, LAST-MODIFIED, PRIORITY,
GEO, LAST-MODIFIED, PRIORITY, RDATE, RELATED-TO, RDATE, RELATED-TO, RESOURCES, REQUEST-STATUS, RRULE,
RESOURCES, REQUEST-STATUS, RRULE, SUMMARY, TRANSP, URL) SUMMARY, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
Silverberg/Mansour/Dawson/Hopson 34 Expires MAY 1998
3.3.5 REFRESH 3.3.5 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 also
use this method to request an updated status from the "Attendees". use this method to request an updated status from the "Attendees".
The "REFRESH" method MUST specify the "UID" property corresponding to The "REFRESH" method MUST specify the "UID" property corresponding to
the "VTODO" calendar component needing update. the "VTODO" calendar component needing update.
skipping to change at line 1713 skipping to change at line 1723
(DESCRIPTION "VTODO - Refresh" COMPONENT "VTODO" METHOD "REFRESH" (DESCRIPTION "VTODO - Refresh" COMPONENT "VTODO" METHOD "REFRESH"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP, MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP,
SEQUENCE{IF NE 0}, UID{UID associated with original SEQUENCE{IF NE 0}, UID{UID associated with original
REQUEST} MAY PROPERTY = COMMENT{provides comment from REQUEST} MAY PROPERTY = COMMENT{provides comment from
ATTENDEE to "Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ ATTENDEE to "Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ
0} 0}
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, COMPLETED, CONTACT, NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
CREATED, DESCRIPTION, DTSTART, DUE, EXDATE, EXRULE, GEO, DESCRIPTION, DTSTART, DUE, EXDATE, EXRULE, GEO, LAST-
LAST-MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES, MODIFIED, PRIORITY, RDATE,RELATED-TO, RESOURCES,
REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL) REQUEST-STATUS, RRULE,SUMMARY, STATUS, TRANSP, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
Silverberg/Mansour/Dawson/Hopson 32 Expires MAY 1998
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
3.3.6 COUNTER 3.3.6 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 "Attendee" MUST send the message to the "Organizer" of the The "Attendee" MUST send the message to the "Organizer" of the
"VTODO" calendar component. "VTODO" calendar 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 "VTODO" calendar component. alternate "VTODO" calendar component.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the
"Attendee" a "DECLINECOUNTER" method. The "Organizer" accepts the "Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the
counter proposal by sending all of the "Attendees" of the "VTODO" counter proposal by sending all of the "Attendees" of the "VTODO"
calendar component a "REQUEST" method rescheduling the "VTODO" calendar component a "REQUEST" method rescheduling the "VTODO"
calendar component. In the later case, the "Organizer" SHOULD reset calendar component. In the later case, the "Organizer" SHOULD reset
the individual "RSVP" property parameter values to TRUE on each the individual "RSVP" property parameter values to TRUE on each
"ATTENDEE" property; in order to force a response by the "Attendees". "ATTENDEE" property; in order to force a response by the "Attendees".
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
(DESCRIPTION "VTODO- Request" COMPONENT "VTODO" METHOD "REQUEST" (DESCRIPTION "VTODO- Request" COMPONENT "VTODO" METHOD "REQUEST"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REQUEST"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = ATTENDEE{For Owner and Orginator if different MUST PROPERTY = ATTENDEE{For Owner and Orginator if different
and Attendees}, DESCRIPTION{MAYBE NULL}, DTSTAMP, and Attendees}, DESCRIPTION{MAYBE NULL}, DTSTAMP,
DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID DTSTART, PRIORITY, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT, COMPLETED, MAY PROPERTY = ATTACH, CATEGORIES, CLASS, COMMENT,CREATED,
CONTACT, CREATED, DUE, EXDATE, EXRULE, GEO, LAST- DUE, EXDATE, EXRULE, GEO, LAST-MODIFIED,
MODIFIED,LOCATION,RELATED-TO, RDATE, RECURRENCE-ID, LOCATION,RELATED-TO, RDATE, RECURRENCE-ID, RESOURCES,
RESOURCES, RRULE, SEQUENCE{IF EQ 0}, RRULE, SEQUENCE{IF EQ 0}, STATUS{TENTATIVE/CONFIRMED
STATUS{TENTATIVE/CONFIRMED/CANCELLED}, SUMMARY{MAYBE /CANCELLED}, SUMMARY{MAYBE NULL}, URL
NULL}, URL
NOT PROPERTY = REQUEST-STATUS) NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = VALARM ( MAY COMPONENT = VALARM (
MUST PROPERTY = CATEGORIES, DTSTART, DURATION, REPEAT MUST PROPERTY = CATEGORIES, DSTART, DURATION, REPEAT
MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY MAY PROPERTY = ATTACH, DESCRIPTION, SUMMARY
NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL) NOT PROPERTY = COMMENT, CREATED, LAST-MODIFIED, RELATED-TO, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
Silverberg/Mansour/Dawson/Hopson 33 Expires MAY 1998
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
3.3.7 DECLINECOUNTER 3.3.7 DECLINECOUNTER
The "DECLINECOUNTER" method in a "VTODO" calendar component is used The "DECLINE-COUNTER" method in a "VTODO" calendar component is used
by an "Organizer" of "VTODO" calendar component to reject a counter by an "Organizer" of "VTODO" calendar component to reject a counter
proposal offered by one of the "Attendees". The "Organizer" MUST send proposal offered by one of the "Attendees". The "Organizer" MUST send
the message to the "Attendee" that sent the "COUNTER" method to the the message to the "Attendee" that sent the "COUNTER" method to the
"Organizer". "Organizer".
Silverberg/Mansour/Dawson/Hopson 36 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 "VTODO" calendar component. alternate "VTODO" calendar component.
The "Organizer" rejects the counter proposal by sending the The "Organizer" rejects the counter proposal by sending the
"Attendee" a "DECLINECOUNTER" method. The "Organizer" accepts the "Attendee" a "DECLINE-COUNTER" method. The "Organizer" accepts the
counter proposal by sending all of the "Attendees" of the "VTODO" counter proposal by sending all of the "Attendees" of the "VTODO"
calendar component a "REQUEST" method rescheduling the "VTODO" calendar component a "REQUEST" method rescheduling the "VTODO"
calendar component. Since this is a rescheduled "VTODO", the calendar component. Since this is a rescheduled "VTODO", the
"SEQUENCE" property value will be incremented. In the later case, the "SEQUENCE" property value will be incremented. In the later case, the
"Organizer" SHOULD reset the individual "RSVP" property parameter "Organizer" SHOULD reset the individual "RSVP" property parameter
values to TRUE on all of the "ATTENDEE" properties in order to force values to TRUE on all of the "ATTENDEE" properties 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 property constraints: following property constraints:
skipping to change at line 1818 skipping to change at line 1825
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD
{"DECLINECOUNTER"}) {"DECLINECOUNTER"})
MUST COMPONENT = VTODO( MUST COMPONENT = VTODO(
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{same UID
specified In Original REQUEST and subsequent COUNTER} specified In Original REQUEST and subsequent COUNTER}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ ATTENDEE}, RECURRENCE-ID, REQUEST-STATUS, SEQUENCE{IF EQ
0} 0}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
COMPLETED, CONTACT, CREATED, DESCRIPTION, DTSTART, DUE, DESCRIPTION, DTSTART, DUE, EXDATE, EXRULE, GEO, LAST-
EXDATE, EXRULE, GEO, LAST-MODIFIED, PRIORITY, RDATE, MODIFIED, PRIORITY, RDATE, RELATED-TO, RESOURCES, RRULE,
RELATED-TO, RESOURCES, RRULE, STATUS, SUMMARY, TRANSP, STATUS, SUMMARY, TRANSP, URL)
URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VJOURNAL NOT COMPONENT = VJOURNAL
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
Silverberg/Mansour/Dawson/Hopson 34 Expires MAY 1998
3.4 Methods For VJOURNAL Component 3.4 Methods For VJOURNAL Component
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. Each of the methods
is defined using a grammar that clarifies the property constraints is defined using a grammar that clarifies the property constraints
that define the particular method. 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" calendar component. "VJOURNAL" 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. | | CANCEL | Cancel an existing journal entry request. |
| REFRESH | A request sent to the journal "Organizer" for | | REFRESH | A request sent to the journal "Organizer" for |
| | the latest version of the journal entry to be | | | the latest version of the journal entry to be |
| | resent the requester. | | | resent the requester. |
+================+==================================================+ +================+==================================================+
3.4.1 PUBLISH 3.4.1 PUBLISH
skipping to change at line 1878 skipping to change at line 1884
(DESCRIPTION "Journal - Publish" COMPONENT "VJOURNAL" METHOD (DESCRIPTION "Journal - Publish" COMPONENT "VJOURNAL" METHOD
"PUBLISH "PUBLISH
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"PUBLISH"})
MUST COMPONENT = VJOURNAL ( MUST COMPONENT = VJOURNAL (
MUST PROPERTY = DESCRIPTION{MAYBE NULL}, DTSTAMP, MUST PROPERTY = DESCRIPTION{MAYBE NULL}, DTSTAMP,
DTSTART{VALUE=DATE}, SEQUENCE{IF NE 0}, UID DTSTART{VALUE=DATE}, SEQUENCE{IF NE 0}, UID
MAY PROPERTY = ATTACH, ATTENDEE{only ROLE=ORGANIZER and MAY PROPERTY = ATTACH, ATTENDEE{only ROLE=ORGANIZER and
OWNER if different}, CATEGORIES, CLASS, COMMENT, OWNER if different}, CATEGORIES, CLASS, COMMENT,
CONTACT, CREATED, EXDATE, EXRULE, LAST-MODIFIED, CREATED, EXDATE, EXRULE, LAST-MODIFIED, RELATED-TO,
RELATED-TO, RDATE, RECURRENCE-ID, RRULE, SEQUENCE{IF EQ RDATE, RECURRENCE-ID, RRULE, SEQUENCE{IF EQ 0},
0}, SUMMARY{MAYBE NULL}, URL SUMMARY{MAYBE NULL}, URL
NOT PROPERTY = REQUEST-STATUS) NOT PROPERTY = REQUEST-STATUS)
MAY COMPONENT = VTIMEZONE ( MAY COMPONENT = VTIMEZONE (
MUST PROPERTY = DTSTART, TZOFFSET MUST PROPERTY = DTSTART, TZOFFSET
MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME MAY PROPERTY = COMMENT, DAYLIGHT, (RDATE / RRULE), TZNAME
NOT PROPERTY = CREATED) NOT PROPERTY = CREATED)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
Silverberg/Mansour/Dawson/Hopson 35 Expires MAY 1998
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
) )
Silverberg/Mansour/Dawson/Hopson 38 Expires MAY 1998
3.4.2 CANCEL 3.4.2 CANCEL
The "CANCEL" method in a "VJOURNAL" calendar component is used to The "CANCEL" method in a "VJOURNAL" calendar component is used to
send a cancellation notice of an existing journal entry request to send a cancellation notice of an existing journal entry request to
the "Attendees". The message is sent by the "Organizer" of a journal the "Attendees". The message is sent by the "Organizer" of a journal
entry to the "Attendees" of the journal entry. For a recurring entry to the "Attendees" of the journal entry. For a recurring
journal entry, either the whole journal entry or instances of a journal entry, either the whole journal entry or instances of a
journal entry MAY be cancelled. To cancel the complete range of a journal entry MAY be cancelled. To cancel the complete range of a
recurring journal entry, the "UID" property value for the journal recurring journal entry, the "UID" property value for the journal
entry MUST be specified in the "CANCEL" method. In order to cancel an entry MUST be specified in the "CANCEL" method. In order to cancel an
skipping to change at line 1931 skipping to change at line 1937
"CANCEL" "CANCEL"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"CANCEL"})
MUST COMPONENT = VJOURNAL ( MUST COMPONENT = VJOURNAL (
MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID MUST PROPERTY = DTSTAMP, SEQUENCE{IF NE 0}, UID{UID
associated with original REQUEST} associated with original REQUEST}
MAY PROPERTY = COMMENT{provides comment from "Organizer" to MAY PROPERTY = COMMENT{provides comment from "Organizer" to
ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ ATTENDEE}, EXDATE, EXRULE, RECURRENCE-ID, SEQUENCE{IF EQ
0}, STATUS{CANCELLED} 0}, STATUS{CANCELLED}
NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CONTACT, NOT PROPERTY = ATTACH, ATTENDEE, CATEGORIES, CLASS, CREATED,
CREATED, DESCRIPTION, DTSTART, LAST-MODIFIED, RDATE, DESCRIPTION, DTSTART, LAST-MODIFIED, RDATE, RELATED-TO,
RELATED-TO, REQUEST-STATUS, RRULE, SUMMARY, URL) REQUEST-STATUS, RRULE, SUMMARY, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
Silverberg/Mansour/Dawson/Hopson 36 Expires MAY 1998
3.4.3 REFRESH 3.4.3 REFRESH
The "REFRESH" method in a "VJOURNAL" calendar component is used by The "REFRESH" method in a "VJOURNAL" calendar component is used by
"Attendees" of an existing journal entry to request an updated "Attendees" of an existing journal entry to request an updated
description from the journal entry "Organizer". The "REFRESH" method description from the journal entry "Organizer". The "REFRESH" method
Silverberg/Mansour/Dawson/Hopson 39 Expires MAY 1998
MUST specify the "UID" property corresponding to the journal entry MUST specify the "UID" property corresponding to the journal entry
needing update. A recurrence instance of a journal entry MAY be needing update. A recurrence instance of a journal entry MAY be
requested by specifying the"RECURRENCE-ID" property corresponding to requested by specifying the"RECURRENCE-ID" property corresponding to
the associated journal entry. The "Organizer" MUST respond with the the associated journal entry. The "Organizer" MUST respond with the
latest description and version of the journal entry. This method is latest description and version of the journal entry. This method is
intended to facilitate machine processing of the "REFRESH" response. intended to facilitate machine processing of the "REFRESH" response.
This method type is an iCalendar object that conforms to the This method type is an iCalendar object that conforms to the
following property constraints: following property constraints:
skipping to change at line 1970 skipping to change at line 1976
"REFRESH" "REFRESH"
MUST COMPONENT = CALPROPS ( MUST COMPONENT = CALPROPS (
MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"}) MUST PROPERTY = PRODID, VERSION{"2.0"}, METHOD{"REFRESH"})
MUST COMPONENT = VJOURNAL ( MUST COMPONENT = VJOURNAL (
MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP, MUST PROPERTY = ATTENDEE{address of requestor}, DTSTAMP,
SEQUENCE{IF NE 0}, UID{UID associated with original SEQUENCE{IF NE 0}, UID{UID associated with original
REQUEST} REQUEST}
MAY PROPERTY = COMMENT{provides comment from ATTENDEE to MAY PROPERTY = COMMENT{provides comment from ATTENDEE to
"Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0} "Organizer"}, RECURRENCE-ID, SEQUENCE{IF EQ 0}
NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CONTACT, CREATED, NOT PROPERTY = ATTACH, CATEGORIES, CLASS, CREATED,
DESCRIPTION, DTSTART, EXDATE, EXRULE, LAST-MODIFIED, DESCRIPTION, DTSTART, EXDATE, EXRULE, LAST-MODIFIED,
PRIORITY, RDATE, RELATED-TO, REQUEST-STATUS, RRULE, PRIORITY, RDATE, RELATED-TO, REQUEST-STATUS, RRULE,
SUMMARY, URL) SUMMARY, URL)
MAY COMPONENT = X-TOKENS (ANY) MAY COMPONENT = X-TOKENS (ANY)
NOT COMPONENT = VEVENT NOT COMPONENT = VEVENT
NOT COMPONENT = VTODO NOT COMPONENT = VTODO
NOT COMPONENT = VFREEBUSY NOT COMPONENT = VFREEBUSY
NOT COMPONENT = VTIMEZONE NOT COMPONENT = VTIMEZONE
NOT COMPONENT = VALARM NOT COMPONENT = VALARM
) )
skipping to change at line 1997 skipping to change at line 2003
| 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 |
Silverberg/Mansour/Dawson/Hopson 37 Expires MAY 1998
| | 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 |
| | 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 |
skipping to change at line 2054 skipping to change at line 2060
| | 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). |
|==============+============================+=========================| |==============+============================+=========================|
| 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. |
Silverberg/Mansour/Dawson/Hopson 38 Expires MAY 1998
|==============+============================+=========================| |==============+============================+=========================|
| 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. |
skipping to change at line 2110 skipping to change at line 2116
instance of a recurring Friday event. Similarly, the "Organizer" MAY instance of a recurring Friday event. Similarly, the "Organizer" MAY
change the time or location to a single instance of the recurring change the time or location to a single instance of the recurring
event. event.
Since implementations MAY elect to store recurring events as either a Since implementations MAY elect to store recurring events as either a
single event object or a collection of discreet, related event single event object or a collection of discreet, related event
objects, the protocol is designed so that each recurring instance MAY objects, the protocol is designed so that each recurring instance MAY
be both referenced and versioned. Hence, implementations that choose be both referenced and versioned. Hence, implementations that choose
to maintain per-instance properties (such as "ATTENDEE" property to maintain per-instance properties (such as "ATTENDEE" property
"STATUS" parameter) MAY do so. However, the protocol does not require "STATUS" parameter) MAY do so. However, the protocol does not require
Silverberg/Mansour/Dawson/Hopson 39 Expires MAY 1998
per-instance recognition unless the instance itself MUST be per-instance recognition unless the instance itself MUST be
renegotiated. renegotiated.
Silverberg/Mansour/Dawson/Hopson 42 Expires MAY 1998
The scenarios for recurrence instance referencing are listed below. The scenarios for recurrence instance referencing are listed below.
For purposes of simplification a change to an event refers to a For purposes of simplification a change to an event refers to a
"trigger property." That is, a property that has a substantive "trigger property." That is, a property that has a substantive
affect on the meeting itself such as start time, location, due date affect on the meeting itself such as start time, location, due date
(for "VTODO" calendar component components) and possibly description. (for "VTODO" calendar component components) and possibly description.
"Organizer" initiated actions: . "Organizer" initiated actions:
"Organizer" deletes or changes a single instance of a recurring . "Organizer" deletes or changes a single instance of a recurring
event 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 changes status for a particular recurrence instance
Attendee sends Event-Counter for a particular recurrence . Attendee sends Event-Counter for a particular recurrence
instance 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 MUST be renegotiated.
Negotiation is necessary when the start time, end time, due date or Negotiation is necessary when the start time, end time, due date or
location are modified. If the "Organizer" wishes to identify a location are modified. If the "Organizer" wishes to identify a
specific recurrence instance it is done using the "RECURRENCE-ID" specific recurrence instance it is done using the "RECURRENCE-ID"
property. The property value is equal to the date/time of the property. The property value is equal to the date/time of the
instance. If the "Organizer" wishes to change the"DTSTART", the instance. If the "Organizer" wishes to change the"DTSTART", the
original "DTSTART" value is used for"RECURRENCE-ID" property and the original "DTSTART" value is used for"RECURRENCE-ID" property and the
skipping to change at line 2168 skipping to change at line 2173
events, to-dos, and journal entries for two reasons. First, a events, to-dos, and journal entries for two reasons. First, a
published only the "Organizer" is allowed to update an event, to-do, published only the "Organizer" is allowed to update an event, to-do,
or journal entry component. The "Organizer" "ATTENDEE" property MUST or journal entry component. The "Organizer" "ATTENDEE" property MUST
be present in the event, to-do, or journal entry component so that be present in the event, to-do, or journal entry component so that
the "CUA" has a basis for authorizing an update. Second, it is the "CUA" has a basis for authorizing an update. Second, it is
prudent to provide a point of contact for anyone who receives a prudent to provide a point of contact for anyone who 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 to such an address results in mail being sent to multiple email to such an address results in mail being sent to multiple
Silverberg/Mansour/Dawson/Hopson 43 Expires MAY 1998
recipients. Such an address MAY be used as the value of an "ATTENDEE" 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 property. Thus, it is possible that the recipient of a "REQUEST" does
not appear explicitly in the list list. not appear explicitly in the list list.
Silverberg/Mansour/Dawson/Hopson 40 Expires MAY 1998
It is recommended that the general approach to finding a "Calendar It is recommended that the general approach to finding a "Calendar
User" in an attendee list be as follows: User" in an attendee list be as follows:
1. Search for the "Calendar User" in the attendee list where 1. Search for the "Calendar User" in the attendee list where
"TYPE=INDIVIDUAL" "TYPE=INDIVIDUAL"
2. Failing (1) look for attendees where "TYPE=GROUP" or 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" MUST then determine if the "CU" is a
member of one of these groups. If so, the "REPLY" method sent to member of one of these groups. If so, the "REPLY" method sent to
the "Organizer" MUST contain a new "ATTENDEE" property in which the "Organizer" MUST contain a new "ATTENDEE" property in which
skipping to change at line 2216 skipping to change at line 2222
It is recommended that application software ask the user whether or It is recommended that application software ask the user whether or
not they want alarms included when they read the event. not they want alarms included when they read the event.
3.6.6 SUMMARY Property 3.6.6 SUMMARY Property
The minimum support for the "SUMMARY" property in a recipient MUST be The minimum support for the "SUMMARY" property in a recipient MUST be
for a 255 byte value. Implementations MAY truncate longer length for a 255 byte value. Implementations MAY truncate longer length
values. values.
Silverberg/Mansour/Dawson/Hopson 44 Expires MAY 1998
3.6.7 X-Tokens 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 into components. These properties are called X-Tokens as inserted into components. These properties are called X-Tokens as
they are prefixed with "X-". A client is not required to make sense they are prefixed with "X-". A client is not required to make sense
of X-Tokens. Clients are not required to save X-Tokens or use them in of X-Tokens. Clients are not required to save X-Tokens or use them in
event replies. event replies.
Silverberg/Mansour/Dawson/Hopson 41 Expires MAY 1998
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 way transfer of event information. Consumers of published events one way transfer of event information. Consumers of published events
simply incorporate the event into a calendar. No reply is expected. simply incorporate the event into a calendar. No reply is expected.
Individual "A" publishes an event. Individual "B" reads the event and Individual "A" publishes an event. Individual "B" reads the event and
incorporates it into their calendar. Events MAY be published in incorporates it into their calendar. Events MAY be published in
several ways including: embedding the event as an object in a web several ways including: embedding the event as an object in a web
skipping to change at line 2268 skipping to change at line 2274
| "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 1, 1997 at 20:00 UTC. This event contains the minimum set of July 1, 1997 at 20:00 UTC. This event contains the minimum set of
properties for a "PUBLISH" for a "VEVENT" calendar component. properties 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:a@host.com ATTENDEE;ROLE=OWNER:mailto:a@host.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@host.com
END:VEVENT END:VEVENT
Silverberg/Mansour/Dawson/Hopson 42 Expires MAY 1998
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 4.1.1, the time has been changed, an end time has been added, and in 4.1.1, the time has been changed, an end time has been added, and
the sequence number has been adjusted. the sequence number has been adjusted.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:PUBLISH METHOD:PUBLISH
VERSION:2.0 VERSION:2.0
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER:a@acme.com ATTENDEE;ROLE=OWNER: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@host.com
SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES SUMMARY:ST. PAUL SAINTS -VS- DULUTH-SUPERIOR DUKES
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The "UID" property is used by the client to identify the event. The The "UID" property is used by the client to identify the event. The
skipping to change at line 2318 skipping to change at line 2323
The "SEQUENCE" property provides a reliable way to distinguish The "SEQUENCE" property provides a reliable way to distinguish
different versions of the same event. Each time an event is different versions of the same event. Each time an event is
published, its sequence number is incremented. If a client receives published, its sequence number is incremented. If a client receives
an event with a sequence number 5 and finds it has the same event an event with a sequence number 5 and finds it has the same event
with sequence number 2, the event SHOULD be updated. However, if the with sequence number 2, the event SHOULD be updated. However, if the
client received an event with sequence number 2 and finds it already client received an event with sequence number 2 and finds it already
has sequence number 5 of the same event, the event SHOULD NOT be has sequence number 5 of the same event, the event SHOULD 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:a@acme.com ATTENDEE;ROLE=OWNER: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@host.com
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
STATUS:CANCELLED STATUS:CANCELLED
Silverberg/Mansour/Dawson/Hopson 43 Expires MAY 1998
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 detail. greater detail.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:PUBLISH METHOD:PUBLISH
CALSCALE: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 NAME:1997 GAME SCHEDULE
VERSION:2.0 VERSION:2.0
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
DAYLIGHT:TRUE DAYLIGHT:TRUE
DTSTART:19970406T070000-0600 DTSTART:19970406T070000-0600
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZNAME:CDT TZNAME:CDT
TZOFFSET:-0500 TZOFFSET:-0500
skipping to change at line 2370 skipping to change at line 2375
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
DAYLIGHT:FALSE DAYLIGHT:FALSE
DTSTART:19971026T0200-0500 DTSTART:19971026T0200-0500
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CST TZNAME:CST
TZOFFSET:-0600 TZOFFSET:-0600
END:VTIMEZONE END:VTIMEZONE
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER:a@acme.com ATTENDEE;ROLE=OWNER:mailto:A@example.com
Silverberg/Mansour/Dawson/Hopson 47 Expires MAY 1998
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:19970701T180000
DTSTART:19970702T160000 DTSTART: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@host.com
Silverberg/Mansour/Dawson/Hopson 44 Expires MAY 1998
RELATED-TO:0981234-1234234-14@host.com RELATED-TO:0981234-1234234-14@host.com
BEGIN:VALARM BEGIN:VALARM
DTSTART:19970701T190000Z DTSTART:19970701T190000Z
REPEAT:2 REPEAT:2
DURATION:PT2H DURATION:PT2H
CATEGORIES:DISPLAY,AUDIO CATEGORIES:DISPLAY,AUDIO
DESCRIPTION:Its almost game time DESCRIPTION:It's almost game time
END:VALARM END:VALARM
BEGIN:VALARM BEGIN:VALARM
DTSTART:19970701T153000 DTSTART:19970701T153000
CATEGORIES:DISPLAY,AUDIO CATEGORIES:DISPLAY,AUDIO
DESCRIPTION:You SHOULD leave now. Game starts in 30 min! DESCRIPTION:You SHOULD leave now. Game starts in 30 min!
END:VALARM END:VALARM
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The "CLASS" property is specified, though it is not really needed The "CLASS" property is specified, though it is not really needed
here. Since this is a published event, a program that displays it here. Since this is a published event, a program that displays it
need not apply any content filtering based on the "CLASS" attribute. need not apply any content filtering based on the "CLASS" attribute.
If this event is copied into a users calendar, the "CLASS" would be 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 included as part of the copy. The handling of the "CLASS" tag at
that point is implementation specific. that point is implementation specific.
The "RELATED-TO" field contains the "UID" property of a related The "RELATED-TO" field contains the "UID" property of a related
calendar event. The handling of this property is application calendar event. The handling of this property is application
dependent. dependent.
The "SEQUENCE" property 3 indicates that this event supersedes 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.
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@host.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
Silverberg/Mansour/Dawson/Hopson 45 Expires MAY 1998
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 "Attendees" and that there is interaction between the have "Attendees" and that there is interaction between the
"Attendees" with respect to the event. Individual "A" requests a "Attendees" 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. Individual "D" tentatively confirms their attendance. attendance. Individual "D" tentatively confirms their attendance.
This is sometimes referred to as "penciling-in" the event on a This is sometimes referred to as "penciling-in" the event on a
calendar. The following table illustrates the sequence of messages calendar. The following table illustrates the sequence of messages
skipping to change at line 2477 skipping to change at line 2482
| | | 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 STATUS 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 STATUS para- |
Silverberg/Mansour/Dawson/Hopson 49 Expires MAY 1998
| | | set to "TENTATIVE" | | | | set to "TENTATIVE" |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Confirm meeting | "A" sends a REQUEST | | | Confirm meeting | "A" sends a REQUEST | |
| status with | message to "B" and | | | status with | message to "B" and | |
| attendees | "C" with updated | | | attendees | "C" with updated | |
| | information. | | | | information. | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
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 that "A" sends to "B", "C", and "D".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
com
Silverberg/Mansour/Dawson/Hopson 46 Expires MAY 1998 ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:D@acme.com com
ATTENDEE;RSVP=NO;EXPECT=REQUIRE;TYPE=ROOM:CR_Big_One@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example.
com
ATTENDEE;RSVP=FALSE;EXPECT=REQUIRE;TYPE=ROOM:CR_Big@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T100000-0700 DTSTART:19970701T100000-0700
DTEND:19970701T103000-0700 DTEND:19970701T103000-0700
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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:B@acme.com ATTENDEE;STATUS=ACCEPTED:Mailto:B@example.com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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 "B" could have declined the meeting or indicated tentative acceptance
by setting the ATTENDEE;"STATUS" parameter to DECLINED or TENTATIVE, by setting the ATTENDEE;"STATUS" parameter to DECLINED or TENTATIVE,
respectively. respectively.
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(which remains the same) and the SEQUENCE (bumped to 1)
properties indicate the update. properties 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;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:D@acme.com com
ATTENDEE;RSVP=NO;EXPECT=REQUIRE;TYPE=ROOM:CR_Big_One@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example.
com
ATTENDEE;RSVP=FALSE;EXPECT=REQUIRE;TYPE=ROOM:CR_Big@example.com
DTSTART:19970701T110000-0700 DTSTART:19970701T110000-0700
DTEND:19970701T113000-0700 DTEND:19970701T113000-0700
SUMMARY:Phone Conference SUMMARY:Phone Conference
Silverberg/Mansour/Dawson/Hopson 47 Expires MAY 1998
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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 Attendee A sends "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": Attendee A sends "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;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com 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@host.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 Attendee B sends "COUNTER" to A, requesting changes to time and
place: place:
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;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@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@host.com
SEQUENCE:0 SEQUENCE:0
Silverberg/Mansour/Dawson/Hopson 48 Expires MAY 1998
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Attendee A accepts the changes from B Attendee A accepts the changes from B
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;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com
Silverberg/Mansour/Dawson/Hopson 52 Expires MAY 1998
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
SUMMARY:Discuss the Merits of the election results - changed to SUMMARY:Discuss the Merits of the election results - changed to
suite B's schedule suite 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@host.com
SEQUENCE:1 SEQUENCE:1
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
A rejects B's counter proposal A rejects B's counter proposal
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:COUNTERDECLINE METHOD:DECLINECOUNTER
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@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@host.com
SEQUENCE:1 SEQUENCE:1
DTSTAMP:19970614T190000Z DTSTAMP:19970614T190000Z
END:VEVENT END:VEVENT
4.2.5 Delegate An Event 4.2.5 Delegate 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 request to the "delegatee". There is currently no protocol a request to the "delegatee". There is currently no protocol
limitation to delegation depth. It is possible for the original limitation to delegation depth. It is possible for the original
delegate to delegate the meeting to someone else, and so on. When a delegate to delegate the meeting to someone else, and so on. When a
request is delegated from one "CUA" to another there are a number of request is delegated from one "CUA" to another there are a number of
responsibilities required of the "delegator". They MUST: responsibilities required of the "delegator". They MUST:
Silverberg/Mansour/Dawson/Hopson 49 Expires MAY 1998 . Send an REPLY to the "Organizer" with their attendee/status
Send an REPLY to the "Organizer" with their attendee/status
property parameter set to "Delegated" property parameter set to "Delegated"
Include the delegate as an additional attendee with the . Include the delegate as an additional attendee with the
"Delegated-From" property parameter set to the delegator "Delegated-From" property parameter set to the delegator
Include the original UID of the REQUEST . Include the original UID of the REQUEST
The delegator MUST also send a copy of the original REQUEST to 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 delegate. The delegator modifies the request to include:
The ATTENDEE/STATUS property parameter for the delegator . The ATTENDEE/STATUS property parameter for the delegator
(sender in this case) is set to "DELEGATED" (sender in this case) is set to "DELEGATED"
ATTENDEE/DELEGATED-TO parameter is set to the address of the . ATTENDEE/DELEGATED-TO parameter is set to the address of the
delegatee delegatee
An ATTENDEE property is added for delegatee . An ATTENDEE property is added for delegatee
As a rule, it is not required that the "delegatee" include the As a rule, it is not required that the "delegatee" include the
"delegator" in their "REPLY" method. However, it is strongly advised "delegator" in their "REPLY" method. However, it is strongly advised
since this will inform the "delegator" whether their proxy plans to since this will inform the "delegator" whether their proxy plans to
attend the meeting. If the "delegatee" declines the meeting, the attend the meeting. If the "delegatee" declines the meeting, the
"delegator" MAY elect to try and delegate the "REQUEST" to another "delegator" MAY elect to try and delegate the "REQUEST" to another
"CUA". The process is the same. "CUA". The process is the same.
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
skipping to change at line 2717 skipping to change at line 2744
| | | parameter for "C" is set | | | | parameter for "C" is set |
| | | to "DELEGATED" and the | | | | to "DELEGATED" and the |
| | | ATTENDEE/DELEGATED-TO | | | | ATTENDEE/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 | | | | ATTENDEE/DELEGATED-FROM |
| | | parameter is set to | | | | parameter is set to |
| | | the address of "C". | | | | the address of "C". |
Silverberg/Mansour/Dawson/Hopson 50 Expires MAY 1998
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| 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 ATTENDEE/STATUS |
| | | property parameter set | | | | property parameter set |
Silverberg/Mansour/Dawson/Hopson 54 Expires MAY 1998
| | | to "ACCEPTED" | | | | to "ACCEPTED" |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
| Optional: | "A" sends REQUEST | | | Optional: | "A" sends REQUEST | |
| Redistribute | message to "B", "C" | | | Redistribute | message to "B", "C" | |
| meeting to | and "E". SEQUENCE | | | meeting to | and "E". SEQUENCE | |
| attendees | number is now 1. | | | attendees | number is now 1. | |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
Attendee "C" responds to meeting "Organizer" "A" Attendee "C" responds to meeting "Organizer" "A"
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=DELEGATED;DELEGATED- ATTENDEE;ROLE=ATTENDEE;STATUS=DELEGATED;DELEGATED-
TO=E@acme.com:C@acme.com TO="Mailto:E@example.com":Mailto:C@example.com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=ORGANIZER:Mailto:A@example.com
ATTENDEE;ROLE=DELEGATE;RSVP=YES;EXPECT=REQUEST; ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
DELEGATED-FROM=C@acme.com:E@acme.com ATTENDEE;ROLE=DELEGATE;RSVP=TRUE;EXPECT=REQUEST;
DELEGATED-FROM=_Mailto:C@example.com_:Mailto:E@example.com
ATTENDEE;ROLE=ATTENDEE;STATUS=DELEGATED; ATTENDEE;ROLE=ATTENDEE;STATUS=DELEGATED;
DELEGATED-TO=E@acme.com:C@acme.com DELEGATED-TO="Mailto:E@example.com":Mailto:C@example.com
DTSTART:19970701T110000-0700 DTSTART:19970701T110000-0700
DTEND:19970701T113000-0700 DTEND:19970701T113000-0700
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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 51 Expires MAY 1998 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 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; ATTENDEE;ROLE=ATTENDEE;STATUS=CONFIRMED;
DELEGATED-FROM=C@acme.com:E@acme.com DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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
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
skipping to change at line 2810 skipping to change at line 2838
"Calendar User". "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; ATTENDEE;ROLE=ATTENDEE;STATUS=DECLINED;
DELEGATED-FROM=C@acme.com:E@acme.com DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.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
Silverberg/Mansour/Dawson/Hopson 52 Expires MAY 1998
ATTENDEE;ROLE=ATTENDEE;STATUS=DECLINED; ATTENDEE;ROLE=ATTENDEE;STATUS=DECLINED;
DELEGATED-FROM=C@acme.com:E@acme.com DELEGATED-FROM="Mailto:C@example.com":Mailto:E@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.com
SEQUENCE:2 SEQUENCE:2
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
DTSTAMP:19970614T200000Z DTSTAMP:19970614T200000Z
COMMENT:DELEGATE (ATTENDEE E@acme.com) DECLINED YOUR INVITATION COMMENT:DELEGATE (ATTENDEE Mailto:E@example.com) DECLINED YOUR
INVITATION
END:VEVENT END:VEVENT
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
skipping to change at line 2874 skipping to change at line 2904
| 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 | |
| | and "C" | | | | and "C" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| 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- | | | | ATTENDEE STATUS 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" and | |
| | "C" | | | | "C" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
The example shows how "A" cancels the event. The example shows how "A" cancels the event.
Silverberg/Mansour/Dawson/Hopson 53 Expires MAY 1998
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:CANCEL METHOD:CANCEL
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
COMMENT:Mr. B cannot attend. Ill reschedule the meeting later. COMMENT:Mr. B cannot attend. I'll reschedule the meeting later.
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
STATUS:CANCELLED STATUS:CANCELLED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The "Organizer" of a meeting MAY "uninvite" or remove "Attendees" by The "Organizer" of a meeting MAY "uninvite" or remove "Attendees" by
sending a "CANCEL" method to only those "Attendees". sending a "CANCEL" method to only those "Attendees".
skipping to change at line 2925 skipping to change at line 2957
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Reply to the busy | | "B" sends a REPLY | | Reply to the busy | | "B" sends a REPLY |
| request with busy | | message to "A" with | | request with busy | | message to "A" with |
| time data | | busy time data | | time data | | busy time data |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
4.3.1 Request Busy Time 4.3.1 Request Busy Time
"A" sends a BUSY-"REQUEST" to "B" and "C" for busy time "A" sends a BUSY-"REQUEST" to "B" and "C" for busy time
Silverberg/Mansour/Dawson/Hopson 58 Expires MAY 1998
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ATTENDEE;ROLE=OWNER:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE:C@acme.com ATTENDEE:Mailto:B@example.com
ATTENDEE:Mailto:C@example.com
DTSTAMP:19970613T190000Z DTSTAMP:19970613T190000Z
DTSTART:19970701T080000-0700 DTSTART:19970701T080000-0700
Silverberg/Mansour/Dawson/Hopson 54 Expires MAY 1998
DTEND:19970701T200000-0700 DTEND:19970701T200000-0700
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.com
END:VFREEBUSY END:VFREEBUSY
END:VCALENDAR END:VCALENDAR
4.3.2 Reply To A Busy Time Request 4.3.2 Reply To A Busy Time Request
"B" sends a "REPLY" method type of a "VFREEBUSY" calendar component "B" sends a "REPLY" method type of a "VFREEBUSY" calendar component
to "A" to "A"
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ATTENDEE:B@acme.com ATTENDEE:Mailto:B@example.com
DTSTART:19970701T080000-0700 DTSTART:19970701T080000-0700
DTEND:19970701T200000-0700 DTEND:19970701T200000-0700
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.com
FREEBUSY:19970701T090000-0700/PT1H,19970701T140000-0700/PT30H FREEBUSY:19970701T090000-0700/PT1H,19970701T140000-0700/PT30H
DTSTAMP:19970613T190030Z DTSTAMP:19970613T190030Z
END:VFREEBUSY END:VFREEBUSY
END:VCALENDAR END:VCALENDAR
B is busy from 09:00 to 10:00 and from 14:00 to 14:30. B is busy from 09:00 to 10:00 and from 14:00 to 14:30.
skipping to change at line 2974 skipping to change at line 3006
4.4.1 A Recurring Event Spanning Time Zones 4.4.1 A Recurring Event Spanning Time Zones
This event describes a weekly phone conference. The "Attendees" are This event describes a weekly phone conference. The "Attendees" are
each in a different time zone. each in a different time zone.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
Silverberg/Mansour/Dawson/Hopson 59 Expires MAY 1998
VERSION:2.0 VERSION:2.0
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
DAYLIGHT:TRUE DAYLIGHT:TRUE
DTSTART:19970406T200000-0800 DTSTART:19970406T200000-0800
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZNAME:PDT TZNAME:PDT
TZOFFSET:-0700 TZOFFSET:-0700
END:VTIMEZONE END:VTIMEZONE
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
DAYLIGHT:FALSE DAYLIGHT:FALSE
DTSTART:19971026T200000-0700 DTSTART:19971026T200000-0700
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:PST TZNAME:PST
Silverberg/Mansour/Dawson/Hopson 55 Expires MAY 1998
TZOFFSET:-0800 TZOFFSET:-0800
END:VTIMEZONE END:VTIMEZONE
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:sman@mcom.com ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:gb@mcom.fr ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@example.fr
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:kimiko@mcom.jp ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:c@example.jp
DTSTAMP:19970613T190030Z DTSTAMP:19970613T190030Z
DTSTART:19970701T140000 DTSTART:19970701T140000
DTEND:19970701T150000 DTEND:19970701T150000
RRULE:FREQ=WEEKLY;INTERVAL=20;WKST=SU;BYDAY=TU RRULE:FREQ=WEEKLY;INTERVAL=20;WKST=SU;BYDAY=TU
RDATE:19970910T140000 RDATE:19970910T140000
EXDATE:19970909T140000 EXDATE:19970909T140000
EXDATE:19971028T150000 EXDATE:19971028T150000
SUMMARY:Weekly Phone Conference SUMMARY:Weekly Phone Conference
UID:www.acme.com-873970198738777@host.com UID:www.acme.com-873970198738777@host.com
SEQUENCE:0 SEQUENCE:0
skipping to change at line 3030 skipping to change at line 3062
The first two components of this iCalendar object are the time zone The first two components of this iCalendar object are the time zone
components. The "DTSTART" date coincides with the first instance of components. The "DTSTART" date coincides with the first instance of
the RRULE property. the RRULE property.
The recurring meeting is defined in a particular time zone, The recurring meeting is defined in a particular time zone,
presumably that of the originator. The client for each "Attendee" has presumably that of the originator. The client for each "Attendee" has
the responsibility of determining the recurrence time in the the responsibility of determining the recurrence time in the
"Attendee's" time zone. "Attendee's" time zone.
Silverberg/Mansour/Dawson/Hopson 60 Expires MAY 1998
The repeating event starts on Tuesday, July 1, 1997 at 2:00pm. Since The repeating event starts on Tuesday, July 1, 1997 at 2:00pm. Since
no time zone is specified in the "DTSTART" property, the time zone no time zone is specified in the "DTSTART" property, the time zone
component of PDT applies to the start and end times. "Attendee" component of PDT applies to the start and end times. "Attendee"
gb@mcom.fr is in France where the local time on this date is 7 hours B@example.fr is in France where the local time on this date is 7
later than PDT or 21:00. "Attendee" kimiko@mcom.jp is in Japan where hours later than PDT or 21:00. "Attendee" C@example.jp is in Japan
local time is 9 hours ahead of than UTC or Wednesday, July 2 at where local time is 9 hours ahead of than UTC or Wednesday, July 2 at
07:00. The event repeats weekly on Tuesdays (in PST/PDT). The "RRULE" 07:00. The event repeats weekly on Tuesdays (in PST/PDT). The "RRULE"
property results in 20 instances. The last instance falls on Tuesday, property results in 20 instances. The last instance falls on Tuesday,
November 11, 1997 2:00pm PST. The "RDATE" property adds another November 11, 1997 2:00pm PST. The "RDATE" property adds another
instance: WED, 10-SEP-1997 21:00 GMT. instance: WED, 10-SEP-1997 21:00 GMT.
There are two exceptions to this recurring appointment. The first one There are two exceptions to this recurring appointment. The first one
is: is:
TUE, 09-SEP-1997 21:00 GMT TUE, 09-SEP-1997 21:00 GMT
TUE, 09-SEP-1997 14:00 PDT TUE, 09-SEP-1997 14:00 PDT
WED, 10-SEP-1997 07:00 JDT WED, 10-SEP-1997 07:00 JDT
Silverberg/Mansour/Dawson/Hopson 56 Expires MAY 1998
and the second is: and the second is:
TUE, 28-OCT-1997 22:00 GMT TUE, 28-OCT-1997 22:00 GMT
TUE, 28-OCT-1997 14:00 PST TUE, 28-OCT-1997 14:00 PST
WED, 29-OCT-1997 07:00 JST WED, 29-OCT-1997 07:00 JST
4.4.2 Modify A Recurring Instance 4.4.2 Modify A Recurring Instance
In this example the "Organizer" issues a recurring meeting. Later the In this example the "Organizer" issues a recurring meeting. Later the
"Organizer" changes an instance of the event by changing the "Organizer" changes an instance of the event by changing the
skipping to change at line 3073 skipping to change at line 3105
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1.com UID:guid-1@host1.com
SEQUENCE:0 SEQUENCE:0
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970601T210000Z DTSTART:19970601T210000Z
DTEND:19970601T220000Z DTEND:19970601T220000Z
LOCATION:Conference Call LOCATION:Conference Call
Silverberg/Mansour/Dawson/Hopson 61 Expires MAY 1998
DTSTAMP:19970526T083000 DTSTAMP:19970526T083000
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
The event request below is to change a time and create an exception. The event request below is to change a time and create an exception.
This creates an exception on July 3rd. This creates an exception on July 3rd.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1com UID:guid-1@host1com
RECURRENCE-ID:19970701T210000Z RECURRENCE-ID:19970701T210000Z
SEQUENCE:1 SEQUENCE:1
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
Silverberg/Mansour/Dawson/Hopson 57 Expires MAY 1998 ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970703T210000Z DTSTART:19970703T210000Z
DTEND:19970703T220000Z DTEND:19970703T220000Z
LOCATION:Conference Call LOCATION:Conference Call
DTSTAMP:19970626T093000 DTSTAMP:19970626T093000
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
skipping to change at line 3135 skipping to change at line 3169
METHOD:CANCEL METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:guid-1@host1.com UID:guid-1@host1.com
RECURRENCE-ID:19970801T210000Z RECURRENCE-ID:19970801T210000Z
SEQUENCE:2 SEQUENCE:2
DTSTAMP:19970721T093000 DTSTAMP:19970721T093000
STATUS:CANCELLED STATUS:CANCELLED
END:VEVENT END:VEVENT
Silverberg/Mansour/Dawson/Hopson 62 Expires MAY 1998
END:VCALENDAR END:VCALENDAR
4.4.4 Cancel An Exception 4.4.4 Cancel An Exception
In the following example, the "Organizer" has created an exception In the following example, the "Organizer" has created an exception
(as in 4.4.3) and now wishes to cancel it. In this case a "CANCEL" (as in 4.4.3) and now wishes to cancel it. In this case a "CANCEL"
method is sent with the specific "RECURRENCE-ID", "UID" and method is sent with the specific "RECURRENCE-ID", "UID" and
"SEQUENCE" properties of the exception. This same sequence MAY be "SEQUENCE" properties of the exception. This same sequence MAY be
used to decline a previously accepted modification to a recurring used to decline a previously accepted modification to a recurring
event (as in 4.4.2). event (as in 4.4.2).
skipping to change at line 3157 skipping to change at line 3193
METHOD:CANCEL METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:guid-1@host1.com UID:guid-1@host1.com
RECURRENCE-ID:19970801T210000Z RECURRENCE-ID:19970801T210000Z
SEQUENCE:2 SEQUENCE:2
DTSTAMP:19970721T103000 DTSTAMP:19970721T103000
STATUS:CANCELLED STATUS:CANCELLED
END:VEVENT END:VEVENT
Silverberg/Mansour/Dawson/Hopson 58 Expires MAY 1998
END:VCALENDAR END:VCALENDAR
4.4.5 Cancel Recurring Event 4.4.5 Cancel Recurring Event
In this example the "Organizer" wishes to cancel the entire recurring In this example the "Organizer" wishes to cancel the entire recurring
event and any child exceptions. event and any child exceptions.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:CANCEL METHOD:CANCEL
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
skipping to change at line 3185 skipping to change at line 3219
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.4.6 Change All Future Instances 4.4.6 Change All Future Instances
This example changes the meeting location from a conference call to This example changes the meeting location from a conference call to
Seattle starting Sept 1 and extends to all future instances. Seattle starting Sept 1 and extends to all future instances.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
Silverberg/Mansour/Dawson/Hopson 63 Expires MAY 1998
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1.com UID:guid-1@host1.com
RECURRENCE-ID;THISANDFUTURE:19970901T210000Z RECURRENCE-ID;THISANDFUTURE:19970901T210000Z
SEQUENCE:3 SEQUENCE:3
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970901T210000Z [SS2][SS3] DTSTART:19970901T210000Z [SS2][SS3]
DTEND:19970901T220000Z DTEND:19970901T220000Z
LOCATION:Building 32, Microsoft, Seattle, WA LOCATION:Building 32, Microsoft, Seattle, WA
DTSTAMP:19970526T083000 DTSTAMP:19970526T083000
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Silverberg/Mansour/Dawson/Hopson 59 Expires MAY 1998
4.4.7 Add A New Instance To A Recurring Event 4.4.7 Add A New Instance To A Recurring Event
This example adds a one-time additional instance to the recurring This example adds a one-time additional instance to the recurring
event. "Organizer" adds a second July meeting on the 15th. event. "Organizer" adds a second July meeting on the 15th.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1.com UID:guid-1@host1.com
RECURRENCE-ID:19970715T210000Z RECURRENCE-ID:19970715T210000Z
SEQUENCE:4 SEQUENCE:4
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
RDATE;VALUE=PERIOD:19970715T210000Z/19970715T220000Z RDATE;VALUE=PERIOD:19970715T210000Z/19970715T220000Z
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970715T210000Z DTSTART:19970715T210000Z
DTEND:19970715T220000Z DTEND:19970715T220000Z
LOCATION:Conference Call LOCATION:Conference Call
DTSTAMP:19970629T093000 DTSTAMP:19970629T093000
Silverberg/Mansour/Dawson/Hopson 64 Expires MAY 1998
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.4.8 Counter An Instance Of A Recurring Event 4.4.8 Counter An Instance Of A Recurring Event
In this example one of the "Attendees" counters the "DTSTART" In this example one of the "Attendees" counters the "DTSTART"
property of the proposed second July meeting. property of the proposed second July meeting.
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:COUNTER METHOD:COUNTER
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1.com UID:guid-1@host1.com
RECURRENCE-ID:19970715T210000Z RECURRENCE-ID:19970715T210000Z
SEQUENCE:4 SEQUENCE:4
RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z RRULE:FREQ=MONTHLY;BYMONTHDAY=1;UNTIL=19980901T210000Z
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
Silverberg/Mansour/Dawson/Hopson 60 Expires MAY 1998
DTSTART:19970715T220000Z DTSTART:19970715T220000Z
DTEND:19970715T230000Z DTEND:19970715T230000Z
LOCATION:Conference Call LOCATION:Conference Call
COMMENT:May we bump this by an hour? I have a conflict COMMENT:May we bump this by an hour? I have a conflict
DTSTAMP:19970629T094000 DTSTAMP:19970629T094000
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.4.9 Error Reply To A request 4.4.9 Error Reply To A request
skipping to change at line 3288 skipping to change at line 3325
Original Request: Original Request:
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
CREATED:19970526T083000 CREATED:19970526T083000
UID:guid-1@host1.com UID:guid-1@host1.com
Silverberg/Mansour/Dawson/Hopson 65 Expires MAY 1998
SEQUENCE:0 SEQUENCE:0
RRULE:FREQ=MONTHLY;BYMONTHDAY=1 RRULE:FREQ=MONTHLY;BYMONTHDAY=1
ATTENDEE;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
CLASS:PUBLIC CLASS:PUBLIC
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970601T210000Z DTSTART:19970601T210000Z
DTEND:19970601T220000Z DTEND:19970601T220000Z
DTSTAMP:19970602T094000 DTSTAMP:19970602T094000
LOCATION:Conference Call LOCATION:Conference Call
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
skipping to change at line 3318 skipping to change at line 3358
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
REQUEST-STATUS:2.8;Repeating event ignored. Scheduled as a single REQUEST-STATUS:2.8;Repeating event ignored. Scheduled as a single
event;RRULE event;RRULE
UID:guid-1@host1.com UID:guid-1@host1.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970603T094000 DTSTAMP:19970603T094000
END:VEVENT END:VEVENT
Silverberg/Mansour/Dawson/Hopson 61 Expires MAY 1998
END:VCALENDAR END:VCALENDAR
4.5 Group To-do Examples 4.5 Group To-do Examples
Individual "A" creates a group task in which individuals "A", "B", Individual "A" creates a group task in which individuals "A", "B",
"C" and "D" will participate. Individual "B" confirms acceptance of "C" and "D" will participate. Individual "B" confirms acceptance of
the task. Individual "C" declines the task. Individual "D" the task. Individual "C" declines the task. Individual "D"
tentatively accepts the task. The following table illustrates the tentatively accepts the task. The following table illustrates the
sequence of messages that would be exchanged between these sequence of messages that would be exchanged between these
individuals. Individual "A" then issues a "REFRESH" method to obtain individuals. Individual "A" then issues a "REFRESH" method to obtain
the status of the to-do from each participant. The response indicates the status of the to-do from each participant. The response indicates
the individual "Attendee's" completion status. The table below the individual "Attendee's" completion status. The table below
illustrates the message flow. illustrates the message flow.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Action | "Organizer" | Attendee | | Action | "Organizer" | Attendee |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Initiate a to-do | "A" sends a REQUEST | | | Initiate a to-do | "A" sends a REQUEST | |
| request | message to "B", "C",| | | request | message to "B", "C",| |
| | and "D" | | | | and "D" | |
Silverberg/Mansour/Dawson/Hopson 66 Expires MAY 1998
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Accept the to-do | | "B" sends a REPLY | | Accept the to-do | | "B" sends a REPLY |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | ATTENDEE STATUS para- | | | | ATTENDEE STATUS para- |
| | | set to "ACCEPTED". | | | | set to "ACCEPTED". |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Decline the to-do | | "C" sends a REPLY | | Decline the to-do | | "C" sends a REPLY |
| request | | message to "A" with its | | request | | message to "A" with its |
| | | ATTENDEE STATUS para- | | | | ATTENDEE STATUS para- |
| | | set to "DECLINED". | | | | set to "DECLINED". |
skipping to change at line 3370 skipping to change at line 3411
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Attendee indicates | | "B" sends a REPLY | | Attendee indicates | | "B" sends a REPLY |
| percent complete | | message indicating | | percent complete | | message indicating |
| | | percent complete | | | | percent complete |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Attendee indicates | | "C" sends a REPLY | | Attendee indicates | | "C" sends a REPLY |
| completion | | message indicating | | completion | | message indicating |
| | | completion | | | | completion |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Silverberg/Mansour/Dawson/Hopson 62 Expires MAY 1998
4.5.1 A VTODO Request 4.5.1 A VTODO Request
A sample "REQUEST" with for a "VTODO" calendar component that "A" A sample "REQUEST" with for a "VTODO" calendar component that "A"
sends to "B", "C", and "D". sends to "B", "C", and "D".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:D@acme.com com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example.
com
DTSTART:19970701T100000-0700 DTSTART:19970701T100000-0700
DUE:19970722T100000-0700 DUE:19970722T100000-0700
SUMMARY:Create the requirements document SUMMARY:Create the requirements document
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
Silverberg/Mansour/Dawson/Hopson 67 Expires MAY 1998
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970717T200000Z DTSTAMP:19970717T200000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.5.2 A VTODO Reply 4.5.2 A VTODO Reply
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:VTODO BEGIN:VTODO
ATTENDEE;STATUS=ACCEPTED:B@acme.com ATTENDEE;STATUS=ACCEPTED:Mailto:B@example.com
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
COMMENT:I'll send you my input by e-mail COMMENT:I'll send you my input by e-mail
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970717T203000Z DTSTAMP:19970717T203000Z
REQUEST-STATUS:2.0;Success REQUEST-STATUS:2.0;Success
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
"B" could have declined the meeting or indicated tentative acceptance "B" could have declined the meeting or indicated tentative acceptance
by setting the "ATTENDEE;STATUS=" property parameter sequence to by setting the "ATTENDEE;STATUS=" property parameter sequence to
DECLINED or TENTATIVE, respectively. DECLINED or TENTATIVE, respectively.
4.5.3 A VTODO Refresh 4.5.3 A VTODO Refresh
"A" requests status from all "Attendees". "A" requests status from all "Attendees".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
Silverberg/Mansour/Dawson/Hopson 63 Expires MAY 1998
METHOD:REFRESH METHOD:REFRESH
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:D@acme.com com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:D@example.
com
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
DTSTAMP:19970717T230000Z DTSTAMP:19970717T230000Z
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
Silverberg/Mansour/Dawson/Hopson 68 Expires MAY 1998
4.5.4 A Refresh Reply: Percent-Complete 4.5.4 A Refresh Reply: Percent-Complete
A reply indicating that the task in being worked on and that "B" is A reply indicating that the task in being worked on and that "B" is
75% complete with "B's" part of the assignment. 75% complete with "B's" part of the assignment.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;STATUS=IN-PROCESS:B@acme.com ATTENDEE;STATUS=IN-PROCESS:Mailto:B@example.com
PERCENT-COMPLETE:75 PERCENT-COMPLETE:75
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
DTSTAMP:19970717T233000Z DTSTAMP:19970717T233000Z
SEQUENCE:0 SEQUENCE:0
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.5.5 A Refresh Reply: Completed 4.5.5 A Refresh Reply: Completed
A reply indicating that "C" finished with "C's" part of the A reply indicating that "C" finished with "C's" part of the
assignment. assignment.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;STATUS=COMPLETED:C@acme.com ATTENDEE;STATUS=COMPLETED:Mailto:C@example.com
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
DTSTAMP:19970717T233000Z DTSTAMP:19970717T233000Z
SEQUENCE:0 SEQUENCE:0
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.5.6 An Updated VTODO Request 4.5.6 An Updated VTODO Request
Owner "A" resends the "VTODO" calendar component. "A" set's the Owner "A" resends the "VTODO" calendar component. "A" set's the
overall completion for the to-do at 40%. overall completion for the to-do at 40%.
Silverberg/Mansour/Dawson/Hopson 64 Expires MAY 1998
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;STATUS=ACCEPTED;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;STATUS=COMPLETED;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;STATUS=ACCEPTED;TYPE=INDIVIDUAL:Mailto:B@example.com
ATTENDEE;STATUS=TENTATIVE;TYPE=INDIVIDUAL:D@acme.com ATTENDEE;STATUS=COMPLETED;TYPE=INDIVIDUAL:Mailto:C@example.com
Silverberg/Mansour/Dawson/Hopson 69 Expires MAY 1998
ATTENDEE;STATUS=TENTATIVE;TYPE=INDIVIDUAL:Mailto:D@example.com
DTSTART:19970701T100000-0700 DTSTART:19970701T100000-0700
DUE:19970722T100000-0700 DUE:19970722T100000-0700
SUMMARY:Create the requirements document SUMMARY:Create the requirements document
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
SEQUENCE:1 SEQUENCE:1
DTSTAMP:19970718T100000Z DTSTAMP:19970718T100000Z
STATUS:IN-PROGRESS STATUS:IN-PROGRESS
PERCENT-COMPLETE:40 PERCENT-COMPLETE:40
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
skipping to change at line 3514 skipping to change at line 3565
4.5.7.1 Request for a Recurring VTODO 4.5.7.1 Request for a Recurring VTODO
In this example "A" sends a recurring "VTODO" calendar component to In this example "A" sends a recurring "VTODO" calendar component to
"B" and "C". "B" and "C".
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;ROLE=OWNER;STATUS=ACCEPTED:A@acme.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:B@acme.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;RSVP=YES;EXPECT=REQUEST;TYPE=INDIVIDUAL:C@acme.com ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:B@example.
com
ATTENDEE;RSVP=TRUE;EXPECT=REQUEST;TYPE=INDIVIDUAL:Mailto:C@example.
com
RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR
DTSTART:19980101T100000-0700 DTSTART:19980101T100000-0700
DUE:19980103T100000-0700 DUE:19980103T100000-0700
SUMMARY:Send Status Reports to Area Managers SUMMARY:Send Status Reports to Area Managers
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
SEQUENCE:0 SEQUENCE:0
DTSTAMP:19970717T200000Z DTSTAMP:19970717T200000Z
STATUS:CONFIRMED STATUS:CONFIRMED
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
Silverberg/Mansour/Dawson/Hopson 65 Expires MAY 1998
4.5.7.2 Calculating due dates in recurring VTODOs 4.5.7.2 Calculating due dates in recurring VTODOs
The due date in a recurring "VTODO" calendar component is either a The due date in a recurring "VTODO" calendar component is either a
fixed interval specified in the "REQUEST" method or specified fixed interval specified in the "REQUEST" method or specified
specifically using the "RECURRENCE-ID" property. The former is specifically using the "RECURRENCE-ID" property. The former is
Silverberg/Mansour/Dawson/Hopson 70 Expires MAY 1998
calculated by applying the difference between "DTSTART" and "DUE" calculated by applying the difference between "DTSTART" and "DUE"
properties and applying it to each of the start of each recurring properties and applying it to each of the start of each recurring
instance. Hence, if the initial "VTODO" calendar component specifies instance. Hence, if the initial "VTODO" calendar component specifies
a "DTSTART" property value of "19970701T190000Z" and a "DUE" property a "DTSTART" property value of "19970701T190000Z" and a "DUE" property
value of "19970801T190000Z" the interval of one day which could be value of "19970801T190000Z" the interval of one day which could be
applied to each recurring instance of the "VTODO" calendar component. applied to each recurring instance of the "VTODO" calendar component.
4.5.7.3 Replying to an instance of a recurring VTODO 4.5.7.3 Replying to an instance of a recurring VTODO
In this example "B" updates "A" on a single instance of the "VTODO" In this example "B" updates "A" on a single instance of the "VTODO"
calendar component. calendar component.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REPLY METHOD:REPLY
VERSION:2.0 VERSION:2.0
BEGIN:VTODO BEGIN:VTODO
ATTENDEE;STATUS=IN-PROCESS:B@acme.com ATTENDEE;STATUS=IN-PROCESS:Mailto:B@example.com
PERCENT-COMPLETE:75 PERCENT-COMPLETE:75
UID:www.acme.com-873970198738777-00@host.com UID:www.acme.com-873970198738777-00@host.com
DTSTAMP:19970717T233000Z DTSTAMP:19970717T233000Z
RECURRENCE-ID:19980101T100000-0700 RECURRENCE-ID:19980101T100000-0700
SEQUENCE:0 SEQUENCE:0
END:VTODO END:VTODO
END:VCALENDAR END:VCALENDAR
4.6 Journal Examples 4.6 Journal Examples
skipping to change at line 3582 skipping to change at line 3636
DTSTART:19971002T200000Z DTSTART:19971002T200000Z
SUMMARY:Phone conference minutes SUMMARY:Phone conference minutes
DESCRIPTION:The editors meeting was held on October 1, 1997. DESCRIPTION:The editors meeting was held on October 1, 1997.
Details are in the attached document. Details are in the attached document.
UID:0981234-1234234-2410@host.com UID:0981234-1234234-2410@host.com
RELATED-TO:0981234-1234234-2402-35@host.com RELATED-TO:0981234-1234234-2402-35@host.com
ATTACH:ftp\://ftp.example.com/pub/ed/minutes100197.txt ATTACH:ftp\://ftp.example.com/pub/ed/minutes100197.txt
END:VJOURNAL END:VJOURNAL
END:VCALENDAR END:VCALENDAR
Silverberg/Mansour/Dawson/Hopson 66 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 71 Expires MAY 1998
4.7 Other Examples 4.7 Other Examples
4.7.1 Event Refresh 4.7.1 Event Refresh
Refresh the event with "UID" property value of "guid-1- Refresh the event with "UID" property value of "guid-1-
12345@host1.com": 12345@host1.com":
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
METHOD:REFRESH METHOD:REFRESH
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;ROLE=OWNER;EXPECT=REQUEST:Sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Frank_Dawson@Lotus.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Deriks@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
ATTENDEE;EXPECT=REQUEST:Alecd@Microsoft.com ATTENDEE;EXPECT=REQUEST:Mailto:C@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:D@example.com
UID: guid-1-12345@host1.com UID: guid-1-12345@host1.com
DTSTAMP:19970603T094000 DTSTAMP:19970603T094000
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
4.7.2 Bad RECURRENCE-ID 4.7.2 Bad RECURRENCE-ID
If an "Attendee" receives a request that references a "RECURRENCE-ID" If an "Attendee" receives a request that references a "RECURRENCE-ID"
property that can not be found, the "Attendee" SHOULD send a property that can not be found, the "Attendee" SHOULD send a
"REFRESH" method back to the "Organizer" for the latest copy of the "REFRESH" method back to the "Organizer" for the latest copy of the
skipping to change at line 3633 skipping to change at line 3688
| Refresh the entire | "A" sends the | | | Refresh the entire | "A" sends the | |
| Event | latest copy of the | | | Event | latest copy of the | |
| | Event to "B" | | | | Event to "B" | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
| Attendee handles | | "B" updates to the | | Attendee handles | | "B" updates to the |
| the request and | | latest copy of the | | the request and | | latest copy of the |
| updates the | | meeting. | | updates the | | meeting. |
| instance | | | | instance | | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Silverberg/Mansour/Dawson/Hopson 72 Expires MAY 1998
Request from "A": Request from "A":
BEGIN:VCALENDAR BEGIN:VCALENDAR
METHOD:REQUEST METHOD:REQUEST
Silverberg/Mansour/Dawson/Hopson 67 Expires MAY 1998
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
UID:acme-12345@host1.com UID:acme-12345@host1.com
SEQUENCE:3 SEQUENCE:3
RRULE:FREQ=WEEKLY RRULE:FREQ=WEEKLY
RDATE;VALUE=PERIOD:19970819T210000Z/199700819T220000Z RDATE;VALUE=PERIOD:19970819T210000Z/199700819T220000Z
ATTENDEE;STATUS=ACCEPTED;ROLE=OWNER:sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:stevesil@microsoft.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
DESCRIPTION:IETF-C&S Conference Call DESCRIPTION:IETF-C&S Conference Call
SUMMARY:IETF Calendaring Working Group Meeting SUMMARY:IETF Calendaring Working Group Meeting
DTSTART:19970801T210000Z DTSTART:19970801T210000Z
DTEND:19970801T220000Z DTEND:19970801T220000Z
DTSTAMP:19970726T083000 DTSTAMP:19970726T083000
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
"B" has the event with "UID" property"acme-12345@host1.com" but the "B" has the event with "UID" property"acme-12345@host1.com" but the
skipping to change at line 3669 skipping to change at line 3724
instance at the specified recurrence time. This means that the instance at the specified recurrence time. This means that the
"Owner" is either adding a new instance or that the new instance was "Owner" is either adding a new instance or that the new instance was
added when "SEQUENCE" property value "2" of the event was generated. added when "SEQUENCE" property value "2" of the event was generated.
In either case, "B" needs a new copy of the event. In either case, "B" needs a new copy of the event.
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN PRODID:-//RDU Software//NONSGML HandCal//EN
METHOD:REFRESH METHOD:REFRESH
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ATTENDEE;STATUS=ACCEPTED;ROLE=OWNER:sman@netscape.com ATTENDEE;ROLE=OWNER:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:stevesil@microsoft.com ATTENDEE;ROLE=ATTENDEE;STATUS=ACCEPTED:Mailto:A@example.com
ATTENDEE;EXPECT=REQUEST:Mailto:B@example.com
UID:acme-12345@host1.com UID:acme-12345@host1.com
DTSTAMP:19970603T094000 DTSTAMP:19970603T094000
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
5 Application Protocol Fallbacks 5 Application Protocol Fallbacks
5.1 Partial Implementation 5.1 Partial Implementation
Applications that support this memo are not required to support the Applications that support this memo are not required to support the
entire protocol. The following describes how methods and properties entire protocol. The following describes how methods and properties
SHOULD "fallback" in applications that do not support the complete SHOULD "fallback" in applications that do not support the complete
Silverberg/Mansour/Dawson/Hopson 73 Expires MAY 1998
protocol. If a method or property is not addressed in this section, protocol. If a method or property is not addressed in this section,
it MAY be ignored. it MAY be ignored.
5.1.1 Event-Related Fallbacks 5.1.1 Event-Related Fallbacks
Method Fallback Method Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
Silverberg/Mansour/Dawson/Hopson 68 Expires MAY 1998
PUBLISH Required. PUBLISH Required.
CANCEL Required. CANCEL Required.
REQUEST PUBLISH REQUEST PUBLISH
REPLY Required. REPLY Required.
DELEGATE Reply with Not Supported. DELEGATE Reply with Not Supported.
REQUEST Reply with Not Supported. REQUEST Reply with Not Supported.
REPLY Reply with Not Supported. REPLY Reply with Not Supported.
COUNTER Reply with Not Supported COUNTER Reply with Not Supported
DECLINECOUNTER Required if EVENT-COUNTER is implemented; otherwise DECLINECOUNTER Required if EVENT-COUNTER is implemented; otherwise
reply with Not Supported. reply with Not Supported.
skipping to change at line 3739 skipping to change at line 3794
CATEGORIES Required if in VALARM and VALARM is implemented, CATEGORIES Required if in VALARM and VALARM is implemented,
otherwise ignore. otherwise ignore.
CLASS Ignore. CLASS Ignore.
COMMENT Ignore. COMMENT Ignore.
COMPLETED Ignore. COMPLETED Ignore.
CREATED Ignore. CREATED Ignore.
DAYLIGHT Required if VTIMEZONE is implemented; otherwise DAYLIGHT Required if VTIMEZONE is implemented; otherwise
Ignore. Ignore.
DESCRIPTION Required. DESCRIPTION Required.
DELEGATED-FROM Required if EVENT-DELEGATE is implemented; otherwise DELEGATED-FROM Required if EVENT-DELEGATE is implemented; otherwise
Silverberg/Mansour/Dawson/Hopson 74 Expires MAY 1998
Ignore. Ignore.
DELEGATED-TO Required if EVENT-DELEGATE is implemented; otherwise DELEGATED-TO Required if EVENT-DELEGATE is implemented; otherwise
Ignore. Ignore.
DUE Ignore. DUE Ignore.
DURATION Reply with Not Supported. DURATION Reply with Not Supported.
DTSTAMP Required. DTSTAMP Required.
DTSTART Required. DTSTART Required.
DTEND Required. DTEND Required.
Silverberg/Mansour/Dawson/Hopson 69 Expires MAY 1998
EXDATE Ignore. EXDATE Ignore.
EXRULE Ignore. EXRULE Ignore.
FREEBUSY Reply with Not Supported. FREEBUSY Reply with Not Supported.
LAST-MODIFIED Ignore. LAST-MODIFIED Ignore.
LOCATION Required. LOCATION Required.
PRIORITY Ignore. PRIORITY Ignore.
RELATED-TO Ignore. RELATED-TO Ignore.
RDATE Ignore. If implemented, VTIMEZONE MUST also be RDATE Ignore. If implemented, VTIMEZONE MUST also be
implemented. implemented.
RRULE Ignore. The first instance occurs on the DTStart RRULE Ignore. The first instance occurs on the DTStart
skipping to change at line 3794 skipping to change at line 3848
iCalendar iCalendar
Property Fallback Property Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
CALSCALE Ignore; assume GREGORIAN. CALSCALE Ignore; assume GREGORIAN.
GEO Ignore. GEO Ignore.
PRODID Ignore. PRODID Ignore.
METHOD Required as described in the Method list above. METHOD Required as described in the Method list above.
SOURCE Ignore SOURCE Ignore
NAME Ignore. NAME Ignore.
Silverberg/Mansour/Dawson/Hopson 75 Expires MAY 1998
VERSION Ignore. VERSION Ignore.
To-Do-Related To-Do-Related
Components Fallback Components Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
VALARM Reply with Not Supported. VALARM Reply with Not Supported.
VTIMEZONE Required if RRULE or RDATE is implemented; VTIMEZONE Required if RRULE or RDATE is implemented;
otherwise ignore and use local time. otherwise ignore and use local time.
Silverberg/Mansour/Dawson/Hopson 70 Expires MAY 1998
Component Component
Property Fallback Property Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
CALSCALE Ignore; assume GREGORIAN. CALSCALE Ignore; assume GREGORIAN.
GEO Ignore. GEO Ignore.
PRODID Ignore. PRODID Ignore.
PROFILE Required as described in the Method list above. PROFILE Required as described in the Method list above.
SOURCE Ignore SOURCE Ignore
NAME Ignore. NAME Ignore.
VERSION Assume "2.0". VERSION Assume "2.0".
skipping to change at line 3850 skipping to change at line 3905
RRULE Ignore. The first instance occurs on the DTStart RRULE Ignore. The first instance occurs on the DTStart
property. property.
RESOURCES Ignore. RESOURCES Ignore.
SEQUENCE Required. SEQUENCE Required.
STATUS Required. STATUS Required.
SUMMARY Ignore. SUMMARY Ignore.
TRANSP Required if FREEBUSY is implemented; otherwise Ignore. TRANSP Required if FREEBUSY is implemented; otherwise Ignore.
TZNAME Required if VTIMEZONE is implemented; otherwise TZNAME Required if VTIMEZONE is implemented; otherwise
Ignore. Ignore.
TZOFFSET Required if VTIMEZONE is implemented; otherwise TZOFFSET Required if VTIMEZONE is implemented; otherwise
Silverberg/Mansour/Dawson/Hopson 76 Expires MAY 1998
Ignore. Ignore.
URL Ignore. URL Ignore.
UID Required. UID Required.
X- Ignore. X- Ignore.
Silverberg/Mansour/Dawson/Hopson 71 Expires MAY 1998
5.1.3 Journal-Related Fallbacks 5.1.3 Journal-Related Fallbacks
Method Fallback Method Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
PUBLISH Implementations MAY ignore the profile type. The PUBLISH Implementations MAY ignore the profile type. The
REQUEST-STATUS "302;Request not supported" MUST be REQUEST-STATUS "302;Request not supported" MUST be
returned. returned.
CANCEL Implementations MAY ignore the profile type. The CANCEL Implementations MAY ignore the profile type. The
REQUEST-STATUS "302;Request not supported" MUST be REQUEST-STATUS "302;Request not supported" MUST be
returned. returned.
skipping to change at line 3904 skipping to change at line 3959
Component Component
Property Fallback Property Fallback
-------------- ----------------------------------------------------- -------------- -----------------------------------------------------
ATTACH Ignore. ATTACH Ignore.
ATTENDEE Required if JOURNAL-REQUEST is implemented; otherwise ATTENDEE Required if JOURNAL-REQUEST is implemented; otherwise
ignore. ignore.
CATEGORIES Ignore. CATEGORIES Ignore.
CLASS Ignore. CLASS Ignore.
COMMENT Ignore. COMMENT Ignore.
Silverberg/Mansour/Dawson/Hopson 77 Expires MAY 1998
CREATED Ignore. CREATED Ignore.
DAYLIGHT Required if VTIMEZONE is implemented; otherwise DAYLIGHT Required if VTIMEZONE is implemented; otherwise
Ignore. Ignore.
DESCRIPTION Required. DESCRIPTION Required.
DTSTAMP Required. DTSTAMP Required.
DTSTART Required. DTSTART Required.
Silverberg/Mansour/Dawson/Hopson 72 Expires MAY 1998
DTEND Required. DTEND Required.
EXDATE Ignore. EXDATE Ignore.
EXRULE Ignore. EXRULE Ignore.
LAST-MODIFIED Ignore. LAST-MODIFIED Ignore.
RELATED-TO Ignore. RELATED-TO Ignore.
RDATE Ignore. If implemented, VTIMEZONE MUST also be RDATE Ignore. If implemented, VTIMEZONE MUST also be
implemented. implemented.
RRULE Ignore. The first instance occurs on the DTStart RRULE Ignore. The first instance occurs on the DTStart
property. property.
SEQUENCE Required. SEQUENCE Required.
skipping to change at line 3957 skipping to change at line 4012
them out if no other messages arrive with the same "UID" property them out if no other messages arrive with the same "UID" property
value and a lower sequence number. value and a lower sequence number.
5.2.2 Unexpected Reply from an Unknown Delegate 5.2.2 Unexpected Reply from an Unknown Delegate
When an "Attendee" delegates an item to another "Calendar User" they When an "Attendee" delegates an item to another "Calendar User" they
MUST send a "REPLY" method to the "Organizer" using the "ATTENDEE" MUST send a "REPLY" method to the "Organizer" using the "ATTENDEE"
properties to indicate the fact that the request was delegated and to properties to indicate the fact that the request was delegated and to
whom the item was delegated. Hence it is possible for an "Organizer" whom the item was delegated. Hence it is possible for an "Organizer"
to receive an "REPLY" from a "Calendar User" not listed as one of the to receive an "REPLY" from a "Calendar User" not listed as one of the
Silverberg/Mansour/Dawson/Hopson 78 Expires MAY 1998
original "Attendees". The resolution is left to the implementation original "Attendees". The resolution is left to the implementation
but it is expected that the calendaring software will either accept but it is expected that the calendaring software will either accept
the reply or hold it until the related "REPLY" method is received the reply or hold it until the related "REPLY" method is received
from the "delegator". If the version of the "REPLY" method is out of from the "delegator". If the version of the "REPLY" method is out of
date the "Organizer" SHOULD treat the message as a "STATUS-REQUEST" date the "Organizer" SHOULD treat the message as a "STATUS-REQUEST"
and update the delegate with the correct version. and update the delegate with the correct version.
Silverberg/Mansour/Dawson/Hopson 73 Expires MAY 1998
5.3 Sequence Number 5.3 Sequence Number
Under some conditions, a "CUA" MAY receive requests and replies with Under some conditions, a "CUA" MAY receive requests and replies with
the same "SEQUENCE" property value. The "DTSTAMP" property is the same "SEQUENCE" property value. The "DTSTAMP" property is
utilized as a tie-breaker when two items with the same "SEQUENCE" utilized as a tie-breaker when two items with the same "SEQUENCE"
property value are evaluated. Furthermore, the "SEQUENCE" property is property value are evaluated. Furthermore, the "SEQUENCE" property is
only incremented when one or more of the following properties only incremented when one or more of the following properties
changes: changes:
DTSTART . DTSTART
DTEND . DTEND
RDATE . RDATE
RRULE . RRULE
EXDATE . EXDATE
EXRULE . EXRULE
DUE (for VTODO components) . DUE (for VTODO components)
and possibly LOCATION . and possibly LOCATION
6 Security Considerations 6 Security Considerations
This memo outlines an abstract transport protocol which will be bound This memo outlines an abstract transport protocol which will be bound
to a real-time transport, a store-and-forward transport, and perhaps to a real-time transport, a store-and-forward transport, and perhaps
other transports. The transport protocol will be responsible for other transports. The transport protocol will be responsible for
providing facilities for authentication and encryption using standard providing facilities for authentication and encryption using standard
Internet mechanisms that are mutually understood between the sender Internet mechanisms that are mutually understood between the sender
and receiver. and receiver.
skipping to change at line 4011 skipping to change at line 4066
6.1.1 Spoofing the "Organizer" 6.1.1 Spoofing the "Organizer"
In this memo, the "Organizer" is the only person authorized to make In this memo, the "Organizer" is the only person authorized to make
changes to an existing "VEVENT", "VTODO", "VJOURNAL" calendar changes to an existing "VEVENT", "VTODO", "VJOURNAL" calendar
component and redistribute the updates to the "Attendees". An component and redistribute the updates to the "Attendees". An
iCalendar object that maliciously changes or cancels an existing iCalendar object that maliciously changes or cancels an existing
"VEVENT", "VTODO" or "VJOURNAL" calendar component MAY be constructed "VEVENT", "VTODO" or "VJOURNAL" calendar component MAY be constructed
by someone other than the "Organizer" and sent to the "Attendees". by someone other than the "Organizer" and sent to the "Attendees".
Silverberg/Mansour/Dawson/Hopson 79 Expires MAY 1998
6.1.2 Spoofing the "Attendee" 6.1.2 Spoofing the "Attendee"
In this memo, an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL" In this memo, an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL"
calendar component is the only person authorized to update any calendar component is the only person authorized to update any
parameter associated with their "ATTENDEE" property and send it to parameter associated with their "ATTENDEE" property and send it to
the "Organizer". An iCalendar object that maliciously changes the the "Organizer". An iCalendar object that maliciously changes the
"ATTENDEE" parameters MAY be constructed by someone other than the "ATTENDEE" parameters MAY be constructed by someone other than the
real "Attendee" and sent to the "Organizer". real "Attendee" and sent to the "Organizer".
Silverberg/Mansour/Dawson/Hopson 74 Expires MAY 1998
6.1.3 Eavesdropping 6.1.3 Eavesdropping
The iCalendar object is constructed with human-readable clear text. The iCalendar object is constructed with human-readable clear text.
Any information contained in an iCalendar object MAY be read and/or Any information contained in an iCalendar object MAY be read and/or
changed by unauthorized persons while the object is in transit. changed by unauthorized persons while the object is in transit.
6.1.4 Flooding a Calendar 6.1.4 Flooding a Calendar
Implementations MAY provide a means to automatically incorporate Implementations MAY provide a means to automatically incorporate
"REQUEST" methods into a calendar. This presents the opportunity for "REQUEST" methods into a calendar. This presents the opportunity for
skipping to change at line 4058 skipping to change at line 4113
the network is subject is subject to a high probability of attack, the network is subject is subject to a high probability of attack,
iTIP transactions SHOULD be secured. This MAY be accomplished using iTIP transactions SHOULD be secured. This MAY be accomplished using
public key technology, specifically Security Multiparts for MIME public key technology, specifically Security Multiparts for MIME
[RFC1847] in the iTIP transport binding. This helps mitigate the [RFC1847] in the iTIP transport binding. This helps mitigate the
threats of spoofing, eavesdropping and malicious changes in transit. threats of spoofing, eavesdropping and malicious changes in transit.
6.2.1 Use of [RFC1847] to secure iTIP transactions 6.2.1 Use of [RFC1847] to secure iTIP transactions
iTIP transport bindings SHOULD provide a mechanism based on Security iTIP transport bindings SHOULD provide a mechanism based on Security
Multiparts for MIME [RFC1847] to enable authentication of the Multiparts for MIME [RFC1847] to enable authentication of the
senders identity, and privacy and integrity of the data being sender's identity, and privacy and integrity of the data being
transmitted. This allows the receiver of a signed iCalendar object to transmitted. This allows the receiver of a signed iCalendar object to
verify the identity of the sender. This sender MAY then be correlated verify the identity of the sender. This sender MAY then be correlated
Silverberg/Mansour/Dawson/Hopson 80 Expires MAY 1998
to an "ATTENDEE" property in the iCalendar object. If the correlation to an "ATTENDEE" property in the iCalendar object. If the correlation
is made and the sender is authorized to make the requested change or is made and the sender is authorized to make the requested change or
update then the operation MAY proceed. It also allows the message to update then the operation MAY proceed. It also allows the message to
be encrypted to prevent unauthorized reading of the message contents be encrypted to prevent unauthorized reading of the message contents
in transit. iTIP transport binding documents describe this process in in transit. iTIP transport binding documents describe this process in
detail. detail.
6.2.2 Implementation Controls 6.2.2 Implementation Controls
The threat of flooding a calendar SHOULD be mitigated by a calendar The threat of flooding a calendar SHOULD be mitigated by a calendar
system that uses this protocol by providing controls that MAY be used system that uses this protocol by providing controls that MAY be used
to limit the acceptable sources for iTIP transactions, and perhaps to limit the acceptable sources for iTIP transactions, and perhaps
the size of messages and volume of traffic, by source. the size of messages and volume of traffic, by source.
Silverberg/Mansour/Dawson/Hopson 75 Expires MAY 1998
The threat of malicious procedural alarms SHOULD be mitigated by a The threat of malicious procedural alarms SHOULD be mitigated by a
calendar system that uses this protocol by providing controls that calendar system that uses this protocol by providing controls that
MAY be used to disallow procedural alarms in iTIP transactions and/or MAY be used to disallow procedural alarms in iTIP transactions and/or
remove all alarms from the object before delivery to the recipient. remove all alarms from the object before delivery to the recipient.
7 Acknowledgments 7 Acknowledgments
A hearty thanks to the following individuals who have participated in A hearty thanks to the following individuals who have participated in
the drafting, review and discussion of this memo: the drafting, review and discussion of this memo:
skipping to change at line 4116 skipping to change at line 4172
drafts/draft-ietf-calsch-imip-01.txt. drafts/draft-ietf-calsch-imip-01.txt.
[ISO8601] "Data elements and interchange formats - information [ISO8601] "Data elements and interchange formats - information
interchange - Representation of dates and times", ISO 8601, 1996-06- interchange - Representation of dates and times", ISO 8601, 1996-06-
15, +1 (212) 642-4900 for ANSI Sales. 15, +1 (212) 642-4900 for ANSI Sales.
[VCAL] "vCalendar - The Electronic Calendaring and Scheduling Format [VCAL] "vCalendar - The Electronic Calendaring and Scheduling Format
- Version 1.0", Versit Consortium, September 18, 1996, - Version 1.0", Versit Consortium, September 18, 1996,
http://www.imc.org/pdi/vcal-10.doc. http://www.imc.org/pdi/vcal-10.doc.
Silverberg/Mansour/Dawson/Hopson 81 Expires MAY 1998
[VCARD] "vCard - The Electronic Business Card Exchange Format - [VCARD] "vCard - The Electronic Business Card Exchange Format -
Version 2.1", Versit Consortium, September 18, 1996, Version 2.1", Versit Consortium, September 18, 1996,
http://www.imc.org/pdi/vcard-21.doc. http://www.imc.org/pdi/vcard-21.doc.
[RFC821] Postel, "Simple Mail Transfer Protocol", RFC 821, [RFC821] Postel, "Simple Mail Transfer Protocol", RFC 821,
organization name, November 1996, organization name, November 1996,
http://ds.internic.net/rfc/rfc821.txt. http://ds.internic.net/rfc/rfc821.txt.
[RFC1983] "Internet Users' Glossary", RFC 1983, August 1996, [RFC1983] "Internet Users' Glossary", RFC 1983, August 1996,
http://ds.internic.net/rfc/rfc1983.txt. http://ds.internic.net/rfc/rfc1983.txt.
[RFC2119] "Key words for use in RFCs to Indicate Requirement Levels", [RFC2119] "Key words for use in RFCs to Indicate Requirement Levels",
RFC 2119, March 1997, http://ds.internic.net/rfc/rfc2119.txt. RFC 2119, March 1997, http://ds.internic.net/rfc/rfc2119.txt.
[RFC2045] N. Freed and N. Borenstein, "Multipurpose Internet Mail [RFC2045] N. Freed and N. Borenstein, "Multipurpose Internet Mail
Extensions - Part One - Format of Internet Message Bodies", RFC 2045, Extensions - Part One - Format of Internet Message Bodies", RFC 2045,
Innosoft, First Virtual, November 1996, Innosoft, First Virtual, November 1996,
http://ds.internic.net/rfc/rfc2045.txt. http://ds.internic.net/rfc/rfc2045.txt.
Silverberg/Mansour/Dawson/Hopson 76 Expires MAY 1998
[RFC2046] N. Freed and N. Borenstein, "Multipurpose Internet Mail [RFC2046] N. Freed and N. Borenstein, "Multipurpose Internet Mail
Extensions - Part Two - Media Types", RFC 2046, Innosoft, First Extensions - Part Two - Media Types", RFC 2046, Innosoft, First
Virtual, November 1996, http://ds.internic.net/rfc/rfc2046.txt. Virtual, November 1996, http://ds.internic.net/rfc/rfc2046.txt.
[UNICODE] The Unicode Consortium, "The Unicode Standard -Version [UNICODE] The Unicode Consortium, "The Unicode Standard -Version
2.0", Addison-Wesley Developers Press, July 1996. UTF-8 is described 2.0", Addison-Wesley Developers Press, July 1996. UTF-8 is described
in section A-2. in section A-2.
[US-ASCII] Coded Character Set--7-bit AmeriMAYStandard Code for [US-ASCII] Coded Character Set--7-bit AmeriMAYStandard Code for
Information Interchange, ANSI X3.4-1986. Information Interchange, ANSI X3.4-1986.
skipping to change at line 4171 skipping to change at line 4227
EMAIL;INTERNET:Frank_Dawson@Lotus.com EMAIL;INTERNET:Frank_Dawson@Lotus.com
URL:http://home.earthlink.net/~fdawson URL:http://home.earthlink.net/~fdawson
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
FN:Ross Hopson FN:Ross Hopson
ORG:On Technology, Inc. ORG:On Technology, Inc.
ADR;WORK;POSTAL;PARCEL:Suite 1600;;434 Fayetteville St. ADR;WORK;POSTAL;PARCEL:Suite 1600;;434 Fayetteville St.
Mall, Two Hannover Square;Raleigh;NC;27601 Mall, Two Hannover Square;Raleigh;NC;27601
TEL;WORK;MSG:+1-919-890-4036 TEL;WORK;MSG:+1-919-890-4036
Silverberg/Mansour/Dawson/Hopson 82 Expires MAY 1998
TEL;WORK;FAX:+1-919-890-4100 TEL;WORK;FAX:+1-919-890-4100
EMAIL;INTERNET:rhopson@on.com EMAIL;INTERNET:rhopson@on.com
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
FN:Steve Mansour FN:Steve Mansour
ORG:Netscape Communications Corporation ORG:Netscape Communications Corporation
ADR;WORK;POSTAL;PARCEL:;;501 East Middlefield Road;Mountain ADR;WORK;POSTAL;PARCEL:;;501 East Middlefield Road;Mountain
View;CA;94043;USA View;CA;94043;USA
TEL;WORK;MSG:+1-415-937-2378 TEL;WORK;MSG:+1-415-937-2378
TEL;WORK;FAX:+1-415-428-4059 TEL;WORK;FAX:+1-415-428-4059
EMAIL;INTERNET:sman@netscape.com EMAIL;INTERNET:sman@netscape.com
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
FN:Steve Silverberg FN:Steve Silverberg
ORG:Microsoft Corporation ORG:Microsoft Corporation
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way; ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way;
Redmond;WA;98052-6399;USA Redmond;WA;98052-6399;USA
TEL;WORK;MSG:+1-425-936-9277 TEL;WORK;MSG:+1-425-936-9277
Silverberg/Mansour/Dawson/Hopson 77 Expires MAY 1998
TEL;WORK;FAX:+1-425-936-8019 TEL;WORK;FAX:+1-425-936-8019
EMAIL;INTERNET:stevesil@Microsoft.com EMAIL;INTERNET:stevesil@Microsoft.com
END:VCARD END:VCARD
The iCalendar object is a result of the work of the Internet The iCalendar object is a result of the work of the Internet
Engineering Task Force Calendaring and scheduling Working Group. The Engineering Task Force Calendaring and scheduling Working Group. The
chairman of that working group is: chairman of that working group is:
BEGIN:VCARD BEGIN:VCARD
FN:Anik Ganguly FN:Anik Ganguly
skipping to change at line 4225 skipping to change at line 4281
This document and translations of it MAY be copied and furnished to This document and translations of it MAY be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation MAY be prepared, copied, published and or assist in its implmentation MAY be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself MAY NOT be modified in any way, such as by removing document itself MAY NOT be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
Silverberg/Mansour/Dawson/Hopson 83 Expires MAY 1998
copyrights defined in the Internet Standards process MUST be copyrights defined in the Internet Standards process MUST be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Silverberg/Mansour/Dawson/Hopson 78 Expires MAY 1998 Silverberg/Mansour/Dawson/Hopson 84 Expires MAY 1998
 End of changes. 258 change blocks. 
475 lines changed or deleted 533 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/