[Ietf-calsify] Issue 63: Section 18.104.22.168 Recurrence Date/Times:
RDATE < DTSTART
bernard.desruisseaux at oracle.com
Fri Aug 3 14:22:51 PDT 2007
Disclaimer: This is the third time I bring up this issue. See:
Cyrus recently brought up the fact that the deprecation of
RANGE=THISANDFUTURE (Issue 48) might be an issue with unbounded
recurring calendar components in the context of iTIP.
I have already suggested a solution for the case where an
organizer cancels all future recurrence instances of a
recurring calendar component. See:
This time I would like to suggest a solution for the case where
an organizer changes all future recurrence instances of a recurring
1- Specify RDATE properties for all past recurrence instances
and define exception components for them if needed. The
number of past recurrence instances is always finite...
2- Remove EXDATE properties for any past recurrence instances.
3- Set DTSTART to the first recurrence instance to which you
want the change to apply.
The only issue here is that we need to clarify that RDATE can
specify a value less than the value specified by DTSTART.
More information about the Ietf-calsify