API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5546
[ACTIVE]

iCalendar Transport-Independent Interoperability Protocol (iTIP)

Metadata

Publisher
IETF
Doc Type
Standard
Pages
133
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]
Publication Date
2009-12-01
Status Note
Proposed Standard
DOI
10.17487/RFC5546
Link
https://doi.org/10.17487/RFC5546
Author(s)
Cyrus Daboo
Keyword(s)
Calendaring, Scheduling
Latest version of IETF RFC 5546

Document Versions — IETF RFC 5546

  • ▶ IETF RFC 5546 (2009-12-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

Normative Reference(s)

Bibliographic Reference(s)

  • Melnikov, A., Ed., "iCalendar Message-Based Interoperability Protocol (iMIP)", Work in Progress, October 2009. EXTERNAL
  • IETF RFC 2446 [Superseded*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5546.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5546, iCalendar Transport-Independent Interoperability Protocol (iTIP). Available at https://doi.org/10.17487/RFC5546
Snippet:
IETF RFC 5546, iCalendar Transport-Independent Interoperability Protocol (iTIP). Available at https://doi.org/10.17487/RFC5546

HTML (ISO 690 compliant)

Preview:
IETF RFC 5546, iCalendar Transport-Independent Interoperability Protocol (iTIP). Available at https://doi.org/10.17487/RFC5546
Snippet:
<span class="citation"><cite>IETF RFC 5546</cite>, iCalendar Transport-Independent Interoperability Protocol (iTIP). Available at <a href="https://doi.org/10.17487/RFC5546" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5546</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5546, iCalendar Transport-Independent Interoperability Protocol (iTIP)
doi: 10.17487/RFC5546
url: https://doi.org/10.17487/RFC5546
Snippet:
<li>
<cite id="bib-rfc5546">IETF RFC 5546</cite>, iCalendar Transport-Independent Interoperability Protocol (iTIP)
<span class="doi">10.17487/RFC5546</span>
</li>

Referenced By