imip-agent

docs/wiki/CalendaringSupport

1465:0c623c86704f
2020-08-03 Paul Boddie Changed diagram font to sans-serif.
     1 = Calendaring Support =     2      3 imip-agent aims to provide broad support for the following standards:     4      5  * [[https://tools.ietf.org/html/rfc5545|iCalendar]]     6  * [[https://tools.ietf.org/html/rfc5546|iTIP]]     7  * [[https://tools.ietf.org/html/rfc6047|iMIP]]     8      9 The following sections indicate notable deviations or deficiencies in the support    10 for these standards.    11     12 == iCalendar ==    13     14 The general iCalendar format should be mostly supported, but the interpretation    15 of calendar objects in imip-agent is currently limited to events and free/busy    16 data, and the software does not seek to understand the other object types    17 described in the specification.    18     19 The `VTIMEZONE` component is not interpreted. Instead, `TZID` properties are    20 expected to provide [[https://en.wikipedia.org/wiki/Tz_database|tz database]]    21 (tzinfo, zoneinfo, Olson database) identifiers that indicate the time zone or    22 "regime" applying to the indicated datetimes.    23     24 The `VALARM` component is not interpreted since imip-agent does not seek to    25 implement reminders or notifications, although it is conceivable that a mechanism    26 could be implemented to achieve this over e-mail.    27     28 Week numbers (`BYWEEKNO`) are not yet supported in recurring datetimes.    29     30 Only the essential scheduling properties are interpreted by imip-agent. Thus,    31 support for attachments, categories, and so on is not provided in the    32 [[../CalendarManager|management interface]]. Such support may eventually be    33 added, and existing calendar clients may, of course, use such features without    34 any restrictions imposed by imip-agent.    35     36 == iTIP ==    37     38 Only event and free/busy object types are supported in scheduling.    39     40 `VTIMEZONE` and `VALARM` are not interpreted.    41     42 Delegation    43 ([[http://tools.ietf.org/html/rfc5546#section-2.1.2|RFC 5546 section 2.1.2]])    44 is not yet supported.    45     46 Multiple recurrence updates using the `THISANDFUTURE` attribute on the    47 `RECURRENCE-ID` property    48 ([[http://tools.ietf.org/html/rfc5546#section-4.4.5|RFC 5546 section 4.4.5]])    49 is not yet supported.    50     51 The `REQUEST-STATUS` property is not yet supported. (See    52 [[http://tools.ietf.org/html/rfc5546#section-7.3|RFC 5546 section 7.3]].)    53     54 Support is provided in the [[../Configuration|configuration]] of imip-agent    55 for interpreting `REQUEST` messages that should really be `COUNTER` messages,    56 generated by some mail programs. See the `IMIP_COUNTER_AS_REQUEST` setting in    57 `config.txt`.    58     59 == iMIP ==    60     61 Since attachments are not supported by the    62 [[../CalendarManager|management interface]], imip-agent does not generate or    63 interpret the various methods of referencing attachments in exchanged objects.    64 (See [[https://tools.ietf.org/html/rfc6047#section-4.3|RFC 6047 section 4.3]].)