Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2446

Updates:

RFC 5545

Updated by:

RFC 6638

Author:

C. Daboo, Ed.

Stream:

IETF

Source:

calsify (app)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5546

Discuss this RFC: Send questions or comments to the mailing listcalsify@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5546

Abstract

This document specifies a protocol that uses the iCalendar objectspecification to provide scheduling interoperability betweendifferent calendaring systems. This is done without reference to aspecific transport protocol so as to allow multiple methods ofcommunication between systems. Subsequent documents will defineprofiles of this protocol that use specific, interoperable methods ofcommunication between systems.

The iCalendar Transport-Independent Interoperability Protocol (iTIP)complements the iCalendar object specification by adding semanticsfor group scheduling methods commonly available in currentcalendaring systems. These scheduling methods permit two or morecalendaring systems to perform transactions such as publishing,scheduling, rescheduling, responding to scheduling requests,negotiating changes, or canceling. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.