CurrentPROPOSED STANDARDIETF stream

RFC 6047: iCalendar Message-Based Interoperability Protocol (iMIP)

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6047
Published
December 2010
Authors
A. Melnikov
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
22
Also known as
Obsoletes:
RFC 2447

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6047-icalendar-message-based-interoperability-protocol-imip