Reference document

Org
IETF
Pubnum
RFC 5546
Date
2009-12
Version
Title
iCalendar Transport-Independent Interoperability Protocol (iTIP)

Applicability

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.

Responsible Party

Name
FMN CPWG

Status

URI
https://www.ietf.org/rfc/rfc5546.txt

History

Flag Date RFC Version
added 2018-11-27 12.0
UUID
d363017c-ddc4-4752-bd0c-38e1c05fd3d2

Relationships

This standard is used by the following service profiles: