Application Working Group Doug Royer/INET-Consulting LLC Internet Draft October 4, 2003 Expires: March 2004 RECURRENCE-ID in iCal draft-royer-rid-ical-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire March 2004. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. ABSTRACT The initial version of this draft are going to be controversial. The idea is to develope ways to make the various ways of using the [iCAL] and [iTIP] "RECURRENCE-ID" property work between vendors and to document the procedures to work with "RECURRENCE-ID"s. 1. Definitions The following definitions will be used in this memo: uid-object An [iCAL] object that is uniquly identifed by a UID. The term "uid-object" will be used to mean any version of an object with a given UID. So all [iCAL] objects with the same UID are the same "uid-object". Royer Expires: March 2004 [Page 1] Internet Draft RECURRENCE-ID in iCal October 4, 2003 update Within this memo 'update' means a change to a uid-object without modifying, addition, or deletion any of DTSTART, DTEND, RRULE, RDATE, EXRULE, or EXDATE. reschedule Within this memo 'reschedule' means a change one or more of the instances to an uid-object that does modify, add, or delete any of DTSTART, DTEND, RRULE, RDATE, EXRULE, or EXDATE. These also include uid-objects with and without RECURRENCE- IDs. single instance reschedule This means an [iCAL] object that has a METHOD:REQUEST with a RECURRENCE-ID property value set to an existing instance and UID already known to the "Attendee". full update An [iCAL] object sent that causes one or more GUI instances to be replaced and is a complete replacement for an [iCAL] object where the UID is already known to the "Attendee". This would be an object without RECURRENCE-ID sent in the object. GUI instance The effective start date/time as seen on the CUs GUI without regard to how it is represented in any [iCAL] object for a single UID at a specific point in time. object instance The term 'object instance' or will refer to the effective start date/time of any one specific single instance in an [iCAL] object that may or might not have any of RRULE, RDATE, EXRULE, or EXDATE. GUI pattern The 'GUI pattern' will refer to the full set of effective start dates/times of all instances as seen on the CUs GUI without regard to how it is represented in any [iCAL] object for a single UID at a specific point in time. object pattern The term 'object pattern' will refer to the effective start dates/times of all instances in a specific [iCAL] object that may or might not have any of RRULE, RDATE, EXRULE, or EXDATE. GUI cancel If the "Organizer" issues an object that has an effect of removing one or more GUI instances from the CUs GUI if Royer Expires: March 2004 [Page 2] Internet Draft RECURRENCE-ID in iCal October 4, 2003 accepted. This can be a METHOD:CANCEL or full object update and it will be referred to as a 'GUI cancel'. instance cancel A specific [iCAL] object issued by the "Organizer" that informs a CUA that one or more GUI instances are to be removed. This can be a METHOD:CANCEL or a full update. method:cancel A specific METHOD:CANCEL object issued by the "Organizer" that informs the "Attendee" to cancel one or more GUI instances. update cancel A specific object issued by the "Organizer" that informs a CUA to cause a GUI cancel and is *not* a METHOD:CANCEL object. This can also be a 'full update'. 2. Currently Perceived Models This is an attempt to summarize the views sent on the CALSCH working group mailing list (the WG). There are claims that there are two basic camps; "fixed" (F) and "changing" (C) RECURRENCE-IDs. However I think after re-reading the hundreds of emails that there are several variations of the "fixed" camp. There also some that think that how you invite an "Attendee" is related to the RECURRENCE-ID issue. This will also be covered in this memo. The text that follows will be what will be called the orginal uid-object '1' for futher discussions in this memo. In order to simplify the examples and not have to include "VTIMEZONE" components all examples will be in GMT. BEGIN:VCALENDAR PRODID:-//ACME/DesktopCalendar//EN METHOD:REQUEST VERSION:2.0 BEGIN:VEVENT ORGANIZER:mailto:A@example.com ATTENDEE:mailto:A@example.com ATTENDEE:mailtoB@example.com ATTENDEE:mailto:C@example.com ATTENDEE:mailto:D@example.com ATTENDEE:mailto:E@example.com DTSTAMP:19970611T190000Z DTSTART:20031007T120000Z DTEND:20031007T130000Z Royer Expires: March 2004 [Page 3] Internet Draft RECURRENCE-ID in iCal October 4, 2003 SUMMARY:Conference UID:1 SEQUENCE:0 STATUS:CONFIRMED LOCATION: Los Angles, building B room R1 END:VEVENT END:VCALENDAR The above uid-object '1' (Sequence 0 of uid-object '1') would produce exactly one GUI instance on the "Organizers" CUA. And it would produce exactly one GUI instance on each of the "Attendee"s CUAs. The one meeting is Tuesday October 7th at noon GMT in Los Angles building 'B' in room 'R1' and lasts up to and not including 1pm GMT on the same day. 3. Inviting an Attendee 3.1 Invite to a Single Instances This example shows how you should add a new "Attendee" to exactly one instance of an existing object (to uid-object '1'). If the "Organizer" determines that the other "Attendees" ('A'-'E') do not need to see that "Attendee" 'F' is attending then the "Organizer" could send the following object only to 'F': BEGIN:VCALENDAR PRODID:-//ACME/DesktopCalendar//EN METHOD:REQUEST VERSION:2.0 BEGIN:VEVENT ORGANIZER:mailto:A@example.com ATTENDEE:mailto:F@example.com DTSTAMP:19970611T190000Z DTSTART:19970701T200000Z DTEND:19970701T2000000Z SUMMARY:Conference UID:1 SEQUENCE:1 STATUS:CONFIRMED LOCATION: Los Angles, building B room R1 END:VEVENT END:VCALENDAR If the "Organizer" whishs 'F' to know about the other "Attendees", then the following object would be sent to 'F' instead: Royer Expires: March 2004 [Page 4] Internet Draft RECURRENCE-ID in iCal October 4, 2003 BEGIN:VCALENDAR PRODID:-//ACME/DesktopCalendar//EN METHOD:REQUEST VERSION:2.0 BEGIN:VEVENT ORGANIZER:mailto:A@example.com ATTENDEE:mailto:A@example.com ATTENDEE:mailtoB@example.com ATTENDEE:mailto:C@example.com ATTENDEE:mailto:D@example.com ATTENDEE:mailto:E@example.com DTSTAMP:19970611T190000Z DTSTART:19970701T200000Z DTEND:19970701T2000000Z SUMMARY:Conference UID:1 SEQUENCE:1 STATUS:CONFIRMED LOCATION: Los Angles, building B room R1 END:VEVENT END:VCALENDAR The above example could also only have included one, two, three, or four of the other "Attendees". It is the "Organizer"s decission to include information about other "Attendee"s to each "Attendee", it is not a over the wire protocol issue. If the object sent to 'F@example.com' has zero or more of the other "Attendee"s would have exactly one GUI instance on the 'F@example.com's GUI. And that one instance in this example would be at the same date and time on all other "Attendee"s CUAs and on the "Organizer"s CUA. They all see the same GUI pattern. Now the uid-object '1' is at sequence '1' and has one instance and six attendees. 3.2 Adding a new instance for all attendees There are two example to add one instance to uid-object '1'. The first example is a 'full update': BEGIN:VCALENDAR PRODID:-//ACME/DesktopCalendar//EN METHOD:REQUEST VERSION:2.0 BEGIN:VEVENT ORGANIZER:Mailto:A@example.com Royer Expires: March 2004 [Page 5] Internet Draft RECURRENCE-ID in iCal October 4, 2003 ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN=BIG A:Mailto:A@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=B:Mailto:B@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=C:Mailto:C@example.com ATTENDEE;RSVP=TRUE;TYPE=INDIVIDUAL;CN=Hal:Mailto:D@example.com ATTENDEE;RSVP=FALSE;TYPE=ROOM:conf Big@example.com ATTENDEE;ROLE=NON-PARTICIPANT;RSVP=FALSE:Mailto:E@example.com DTSTAMP:19970611T190000Z DTSTART:20031007T120000Z DTEND:20031007T130000Z SUMMARY:Conference UID:1 SEQUENCE:2 STATUS:CONFIRMED LOCATION: Los Angles, building B room R1 END:VEVENT END:VCALENDAR xxx 3.3 Invite to multiple Instance - one object For a existing UID that has 5 GUI instances (uid-object '2', Monday, Tuesday, Wednesday, Thursday, and Friday and you with to invite the new "Attendee" to the Tuesday and Thursday meetings. With Tuesday being October 7th 2003 an the Thursday being October 9th 2003. Assume the "Organizer"s view is SEQUENCE:10 of the object when the "Organizer" first wishes to invite the "Attendee". Send the Attendee: BEGIN:VCALENDAR PRODID:-//ACME/DesktopCalendar//EN METHOD:REQUEST VERSION:2.0 BEGIN:VEVENT ORGANIZER:Mailto:A@example.com ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN=BIG A:Mailto:A@example.com DTSTAMP:20030611T190000Z DTSTART:20031007T120000Z DTEND:20031007T130000Z RDATE:20031009T120000Z SUMMARY:Conference UID:calsrv.example.com-873970198738777@example.com SEQUENCE:11 STATUS:CONFIRMED END:VEVENT END:VCALENDAR Royer Expires: March 2004 [Page 6] Internet Draft RECURRENCE-ID in iCal October 4, 2003 4. Sequence and updates The SEQUENCE:0 followed by U updates is equivalent to the SEQUENCE:U object. So that it does not matter how the "Attendee" got to SEQUENCE:U because the net result is that SEQUENCE:0 plus U reschedules both replicate the exact same GUI pattern for the "Attendee". 4.0.1 C - Single instance reschedule This example shows how this camp thinks you should do a single instance reschedule For a existing UID that has 5 GUI instances, Monday, Tuesday, Wednesday, Thursday, and Friday all at 1pm. And you wish to change the Friday GUI instance to 2pm. The last object sent by the "Organizer" was SEQUENCE:10 SEQUENCE:11 RECURRENCE-ID:...Friday...1pm DTSTART:...Firday...2pm ..rest of VEVENT data 4.0.2 C - Full Update This example shows how this camp thinks you should do a single instance reschedule For a existing UID that has 5 instances, Monday, Tuesday, Wednesday, Thursday, and Friday all at 1pm. And you wish to change them all to 2pm. The last object sent by the "Organizer" was SEQUENCE:10 SEQUENCE:11 DTSTART:...Monday...2pm RRULE;FREQ=DAILY;COUNT=5 ..rest of VEVENT data 4.1 Bibliography [iCAL] Dawson, F. and Stenerson, D., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1998 ftp://ftp.isi.edu/in-notes/rfc2445.txt [iTIP] Silverberg, S., Mansour, S., Dawson, F. and Hopson, R., "iCalendar Transport-Independent Interoperability Protocol (iTIP) Events, BusyTime, To-dos and Journal Entries", RFC 2446, November 1998 ftp://ftp.isi.edu/in-notes/rfc2446.txt Royer Expires: March 2004 [Page 7] Internet Draft RECURRENCE-ID in iCal October 4, 2003 [iMIP] Dawson, F., Mansour, S. and Silverberg, "iCalendar Message-Based Interoperability Protocol (iMIP)", RFC 2447, November 1998 ftp://ftp.isi.edu/in-notes/rfc2447.txt [CAP] Royer, D., Babics, G., Hill, P. Mansour, S. "Calendar Access Protocol (CAP)", work in progress, draft-ietf-calsch-cap-12.txt [INVITATION] Royer, D. "How to create dynamic UPNs for invited ATTENDEEs", work in progress, draft-royer-calsch-dynamic-upn-01.txt 5. Author's Address Doug Royer http://INET-Consulting.com 1795 W. Broadway #266 Idaho Falls, Idaho 83402 US Phone: 208-520-4044 Fax: 866-594-8574 EMail: Doug@Royer.com URI: http://Royer.com/People/Doug Royer Expires: March 2004 [Page 8] Internet Draft RECURRENCE-ID in iCal October 4, 2003 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than nglish. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Royer Expires: March 2004 [Page 9] Internet Draft RECURRENCE-ID in iCal October 4, 2003 Funding for the RFC Editor function is currently provided by the Internet Society. Royer Expires: March 2004 [Page 10]