iCalendar Message-Based Interoperability Protocol
RFC 6047, “iCalendar Message-Based Interoperability Protocol”, is a Proposed Standard document published in December 2010 by A. Melnikov. It obsoletes RFC 2447. The canonical text is published by the RFC Editor.
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]
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 6047 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6046 Transport of Real-time Inter-network Defense Messages
- RFC 6048 Network News Transfer Protocol Additions to LIST Command
- RFC 6045 Real-time Inter-network Defense
- RFC 6044 Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol
- RFC 6050 A Session Initiation Protocol Extension for the Identification of Services
- RFC 6051 Rapid Synchronisation of RTP Flows
- RFC 6042 Transport Layer Security Authorization Using KeyNote
- RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators