Subject: [calsify] VTIMEZONES with onset times in the future of appointments

From: Gren Elliot <[email-masked]>
Date: Fri, 26 Feb 2010 14:06:33 +0000

Hi,

I'm starting to see ICAL appearing in the wild from a well known mobile 
phone provider's devices with VEVENT dates referencing a VTIMEZONE 
component whose rules' onset times are in the future of the actual 
appointment.  Any views on how these should be treated?  The libical 
library we use assumes (not unreasonably IMHO) that such times are UTC - 
which is clearly at odds with the actual intent.

For example, the following contains a VTIMEZONE with only 2 rules that 
first apply from 14th March (DST) or 17th Nov (Standard) this year, but 
the appointment is on 17th February this year...

...
BEGIN:VTIMEZONE
TZID:US/Central
BEGIN:DAYLIGHT
DTSTART:20100314T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20101107T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
...
DTSTART;TZID=US/Central:20100217T170000
DTEND;TZID=US/Central:20100217T180000
...

Regards,
Gren.

-- 
Gren Elliot
Senior Software Engineer
*Scalix*
[email-masked]
Tel: +44 1344 381812
www.scalix.com

_______________________________________________
calsify mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/calsify