RFC 6047
iCalendar Message-Based Interoperability Protocol (iMIP), December 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 2447
- Author:
- A. Melnikov, Ed.
- Stream:
- IETF
- Source:
- calsify (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6047
Discuss this RFC: Send questions or comments to the mailing list calsify@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6047
Abstract
This document, "iCalendar Message-Based Interoperability Protocol (iMIP)", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.