Skip to main content

iCalendar Transport-Independent Interoperability Protocol (iTIP)
RFC 5546

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between …
Received changes through RFC Editor sync (changed abstract to 'This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems.

The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from calsify-chairs@ietf.org, draft-ietf-calsify-2446bis@ietf.org to (None)
2010-02-23
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2010-02-23
Cindy Morgan [Note]: ' RFC 5546' added by Cindy Morgan
2009-12-23
(System) RFC published