2.2.97 [RFC5546] Section 2 Interoperability Models
V0221:The specification states that an application written to this specification may work with bindings for the store-and-forward transport, the real time transport, or both. Also note that iTIP could be bound to other transports.
Microsoft Exchange Server 2007, Microsoft Exchange Server 2010, Microsoft Exchange Server 2013, Microsoft Exchange Server 2016, Microsoft Exchange Server 2019
Microsoft Exchange Server can export certain types of iTIP data within a text/calendar MIME part of an e-mail. The following table specifies what type of data can be exported.
iTIP Method |
MIME Part |
---|---|
PUBLISH |
Cannot export |
REQUEST |
Can export |
REPLY |
Can export |
ADD |
Cannot export |
CANCEL |
Can export |
REFRESH |
Cannot export |
COUNTER |
Can export |
DECLINE-COUNTER |
Cannot export |
Microsoft Exchange can import certain types of iTIP data from a text/calendar MIME part of an e-mail. The following table specifies what type of data can be imported.
iTIP Method |
MIME Part |
---|---|
PUBLISH |
Can import (Treated as a REQUEST) |
REQUEST |
Can import |
REPLY |
Can import |
ADD |
Cannot import (rendered as raw content lines in message body) |
CANCEL |
Can import |
REFRESH |
Cannot import (rendered as raw content lines in message body) |
COUNTER |
Can import |
DECLINE-COUNTER |
Cannot import (rendered as raw content lines in message body) |