database logo graphic

RFC 6047

"iCalendar Message-Based Interoperability Protocol (iMIP)", December 2010

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6047.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Obsoletes:
RFC 2447
Author:
A. Melnikov, Ed.
Stream:
IETF
Source:
calsify (app)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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 4844.


Go to the RFC Editor Homepage.