2.2.142 [RFC5546] Section 3.7.1 Working with Recurrence Instances

V0296:

The specification states that implementations that choose to maintain per-instance properties (such as ATTENDEE property PARTSTAT parameter) may do so. However, the protocol does not require per-instance recognition unless the instance itself must be renegotiated.

Microsoft Office Outlook 2007, Microsoft Outlook 2010, Microsoft Outlook 2013, Microsoft Outlook 2016, Microsoft Outlook 2019

Outlook stores recurring appointments as a single parent object, with child objects created as needed when a single instance is referenced.

V0297:

The specification states that negotiation may be necessary when a substantive change to the event or to-do has been made (such as changing the start time, end time, due date, or location).

Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019

Outlook does not permit the organizer to save changes to start time, end time, or location without sending an update to the attendees.

V0298:

The specification states that the organizer can identify a specific recurrence instance using the RECURRENCE-ID property.

Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019

Outlook allows the organizer to send updates to a specific instance of a recurrence. The resulting iCalendar object contains the RECURRENCE-ID property.

On import, Outlook treats VEVENT components with a RECURRENCE-ID property as a specific instance of a recurrence.