LO67053: ICAL UPDATES A SINGLE INSTANCE OF A REPEATING EVENT: NOTES INSER TS AN RDATE WHICH IS UNECESSARY AND CAUSES INTEROP ISSUES

APAR status

• Closed as fixed if next.

Error description

• In the latest CalConnect interoperability conference, something
  was brought to
  my attention about our iCalendar that is giving other
  applications fits. Note:
  Most major vendors work with our current implementaiton.
  
  
  Steps:
  1) Create a 5 day repeat meeting and send to an internet
  address
  2) Open up one instance and change some aspect (time, subject,
  etc) and send an
  update.  Select 'Just This Instance'.
  At this point we send out iCalendar that has a RECURRENCE-ID
  which specifies
  the instance that changes.  This is correct and is what
  implementations key off
  of.
  Problem:
  In addition to the RECURRENCE-ID, we also add on a single RDATE
  for the
  instance that changed.  This is unecessary as it was already
  defined by the
  RECURRENCE-ID
  
  RFC 2445, Section 4.8.5.3 covers this with:
  
     The recurrence dates, if specified, are used in computing
  the
     recurrence set. The recurrence set is the complete set of
  recurrence
     instances for a calendar component. The recurrence set is
  generated
     by considering the initial "DTSTART" property along with the
  "RRULE",
     "RDATE", "EXDATE" and "EXRULE" properties contained within
  the
     iCalendar object. The "DTSTART" property defines the first
  instance
     in the recurrence set. Multiple instances of the "RRULE" and
  "EXRULE"
     properties can also be specified to define more
  sophisticated
     recurrence sets. The final recurrence set is generated by
  gathering
     all of the start date/times generated by any of the specified
  "RRULE"
     and "RDATE" properties, and excluding any start date/times
  which fall
     within the union of start date/times generated by any
  specified
     "EXRULE" and "EXDATE" properties. This implies that start
  date/times
     within exclusion related properties (i.e., "EXDATE" and
  "EXRULE")
     take precedence over those specified by inclusion properties
  (i.e.,
     "RDATE" and "RRULE"). Where duplicate instances are generated
  by the
     "RRULE" and "RDATE" properties, only one recurrence is
  considered.
     Duplicate instances are ignored.
  
  
  RFC 5546, 3.2.2
     |   RDATE            | 0+       |
        |
     |   RECURRENCE-ID    | 0 or 1   | Only if referring to an
  instance  |
     |                    |          | of a recurring calendar
        |
     |                    |          | component.  Otherwise, it
  MUST    |
     |                    |          | NOT be present.
        |
  

Local fix

Problem summary

• Low priority closures
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# NRBY8A7MGL.
  This was closed as part of a batch closure of sprs with minimal
   customer impact. Low weight, Sev 3 or lower, and a defect
   creation date of 12/31/2012 or earlier. If this issue persists
   in 9.0.1 or above by additional customers, it may be re-raised
   for triage.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R852 PSN

     UP