[Ietf-calsify] Status of simplification work
lear at cisco.com
Mon May 29 05:49:53 PDT 2006
[Again, with my chair hat off]
Sorry for my delayed posting (I am on holiday). In the future, I
suggest that each such question below or new questions be separated by
subject so that they don't get lost in the shuffle. Here is my opinion
about the below.
> 1. Have the recurrence issues been resolved? If so, what is the simplified
> support for recurrence rules or were they dropped entirely?
They have not been resolved.
> 2. At one point there was a discussion about dropping timezones,
> transmitting all time data in UCT and leaving timezone conversion as a UI
> issue (but there were some unresolved issues regarding recurring time sets
> which crossed daylight-savings-time boundaries, I think)
This has not been resolved.
> 3. It's been a while since I saw a notice of a draft posted - what is the
> latest draft related to this work?
A draft will be posted prior to the Montreal meeting. Bernard has his
hands full, but as we are able to close on the above issues they will
either make that draft or the next.
> 4. IF any of the developers for major implementations still read this list,
> or if CalConnect would care to take another survey, can we get a show of
> hands whether non-folded lines break an implementation? And conversely, are
> there known implementations that naively assume that the line-ending
> sequence always means the end of a component?
I do not know the answer to this question for the calendar clients but
as someone who has written calendars I didn't think that folding the
text isn't all that big a deal, and not that hard to test, and I'm not a
great programmer. Again, chair hat off. YMMV.
More information about the Ietf-calsify