iCalendar Transport-Independent Interoperability Protocol
RFC 5546, “iCalendar Transport-Independent Interoperability Protocol”, is a Proposed Standard document published in December 2009 by C. Daboo. It updates RFC 5545. It obsoletes RFC 2446. It has since been updated by RFC 6638. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5546 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5545 Internet Calendaring and Scheduling Core Object Specification
- RFC 5547 A Session Description Protocol Offer/Answer Mechanism to Enable File Transfer
- RFC 5548 Routing Requirements for Urban Low-Power and Lossy Networks
- RFC 5543 BGP Traffic Engineering Attribute
- RFC 5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
- RFC 5542 Definitions of Textual Conventions for Pseudowire Management
- RFC 5550 The Internet Email to Support Diverse Service Environments Profile
- RFC 5541 Encoding of Objective Functions in the Path Computation Element Communication Protocol