Calendar:ITIP and iMIP Support: Difference between revisions

m (links where switched)
Line 3: Line 3:
[[Calendar:Feature Implementations:iTIP-iMIP:Current iTIP Design|Current iTIP-iMIP design]]
[[Calendar:Feature Implementations:iTIP-iMIP:Current iTIP Design|Current iTIP-iMIP design]]


A common problem among users of any calendaring software is scheduling shared events, or meetings between people. In general, there should be a natural method to schedule these events that works well within the current paradigms of the software. The RFC specifications for [http://www.ietf.org/rfc/rfc2446.txt iTIP] and [http://www.ietf.org/rfc/rfc2447.txt iMIP] address this. This document will confine itself to our proposed implementation, for questions about the specifications, please refer to these RFC's.  Also, there are various diagrams throughout, and in those diagrams, Thunderbird components appear in blue while  Lightning components (either existing or proposed) appear in yellow. However, this distinction has nothing to do with which components need to be extended in order to fully support iTIP and iMIP.
A common problem among users of any calendaring software is scheduling shared events, or meetings between people. In general, there should be a natural method to schedule these events that works well within the current paradigms of the software. The RFC specifications for [http://tools.ietf.org/html/rfc5546 iTIP] and [http://www.ietf.org/rfc/rfc2447.txt iMIP] address this. This document will confine itself to our proposed implementation, for questions about the specifications, please refer to these RFC's.  Also, there are various diagrams throughout, and in those diagrams, Thunderbird components appear in blue while  Lightning components (either existing or proposed) appear in yellow. However, this distinction has nothing to do with which components need to be extended in order to fully support iTIP and iMIP.


== Current Implementation ==
== Current Implementation ==
Confirmed users
30

edits