iCalendar Transport-Independent Interoperability Protocol (iTIP) iTip draft-ietf-calext-itipbis-00draft-ietf-calext-itipbis-00 Michael Douglass Bedework Commercial Services
226 3rd StreetTroyNYUnited States of America
mdouglass@bedework.comhttps://bcs.com/
Internet Engineering Task Force IETF2022-06-27en

This document specifies a protocol that uses calendar objects 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. Other documents define profiles of this protocol that use specific, interoperable methods of communication between systems.

The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the calendar object specifications 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.

standard2024 Internet Engineering Task Force IETF 2024-12-09 Internet Calendaring and Scheduling Core Object Specification (iCalendar) https://www.rfc-editor.org/info/rfc5545 RFC 5545 10.17487/RFC5545 RFC5545 2009-09 B. Desruisseaux RFC Publisher RFC Series en

This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]

RFC 5545 IETF calsify calsched calsch caldav calendar calendaring meeting event task to-do journal appointment agenda schedule scheduling ical icalendar itip imip text/calendar ischedule xCalendar
IETF full-standard internet-draftietfInternettrust200902trueyes