1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/wiki/CalendaringSupport Mon Nov 02 20:08:20 2015 +0100
1.3 @@ -0,0 +1,64 @@
1.4 += Calendaring Support =
1.5 +
1.6 +imip-agent aims to provide broad support for the following standards:
1.7 +
1.8 + * [[https://tools.ietf.org/html/rfc5545|iCalendar]]
1.9 + * [[https://tools.ietf.org/html/rfc5546|iTIP]]
1.10 + * [[https://tools.ietf.org/html/rfc6047|iMIP]]
1.11 +
1.12 +The following sections indicate notable deviations or deficiencies in the support
1.13 +for these standards.
1.14 +
1.15 +== iCalendar ==
1.16 +
1.17 +The general iCalendar format should be mostly supported, but the interpretation
1.18 +of calendar objects in imip-agent is currently limited to events and free/busy
1.19 +data, and the software does not seek to understand the other object types
1.20 +described in the specification.
1.21 +
1.22 +The `VTIMEZONE` component is not interpreted. Instead, `TZID` properties are
1.23 +expected to provide [[https://en.wikipedia.org/wiki/Tz_database|tz database]]
1.24 +(tzinfo, zoneinfo, Olson database) identifiers that indicate the time zone or
1.25 +"regime" applying to the indicated datetimes.
1.26 +
1.27 +The `VALARM` component is not interpreted since imip-agent does not seek to
1.28 +implement reminders or notifications, although it is conceivable that a mechanism
1.29 +could be implemented to achieve this over e-mail.
1.30 +
1.31 +Week numbers (`BYWEEKNO`) are not yet supported in recurring datetimes.
1.32 +
1.33 +Only the essential scheduling properties are interpreted by imip-agent. Thus,
1.34 +support for attachments, categories, and so on is not provided in the
1.35 +[[../CalendarManager|management interface]]. Such support may eventually be
1.36 +added, and existing calendar clients may, of course, use such features without
1.37 +any restrictions imposed by imip-agent.
1.38 +
1.39 +== iTIP ==
1.40 +
1.41 +Only event and free/busy object types are supported in scheduling.
1.42 +
1.43 +`VTIMEZONE` and `VALARM` are not interpreted.
1.44 +
1.45 +Delegation
1.46 +([[http://tools.ietf.org/html/rfc5546#section-2.1.2|RFC 5546 section 2.1.2]])
1.47 +is not yet supported.
1.48 +
1.49 +Multiple recurrence updates using the `THISANDFUTURE` attribute on the
1.50 +`RECURRENCE-ID` property
1.51 +([[http://tools.ietf.org/html/rfc5546#section-4.4.5|RFC 5546 section 4.4.5]])
1.52 +is not yet supported.
1.53 +
1.54 +The `REQUEST-STATUS` property is not yet supported. (See
1.55 +[[http://tools.ietf.org/html/rfc5546#section-7.3|RFC 5546 section 7.3]].)
1.56 +
1.57 +Support is provided in the [[../Configuration|configuration]] of imip-agent
1.58 +for interpreting `REQUEST` messages that should really be `COUNTER` messages,
1.59 +generated by some mail programs. See the `IMIP_COUNTER_AS_REQUEST` setting in
1.60 +`config.py`.
1.61 +
1.62 +== iMIP ==
1.63 +
1.64 +Since attachments are not supported by the
1.65 +[[../CalendarManager|management interface]], imip-agent does not generate or
1.66 +interpret the various methods of referencing attachments in exchanged objects.
1.67 +(See [[https://tools.ietf.org/html/rfc6047#section-4.3|RFC 6047 section 4.3]].)