Technical Summary
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. If
approved, this document will obsolete RFC 2447.
Working Group Summary
This document is a product of the CALSIFY WG. It received reviews by
several WG participants in prior to and during Working Group Last Call,
with rough consensus that the changes from RFC 2447 are appropriate.
Document Quality
The CALSIFY WG and the responsible area director have deemed the
document to be of good quality.
Personnel
The Working Group chair is Eliot Lear. The responsible area director is
Peter Saint-Andre.
RFC Editor Note
Add the following text to the document header:
Obsoletes: RFC 2447
In Section 1:
OLD:
This binding document provides the transport specific information
necessary to convey iCalendar Transport-independent Interoperability
Protocol (iTIP) [iTIP] over Internet email (using MIME) as defined in
[RFC-5322] and [RFC-2045].
NEW:
This document provides the transport specific information ("binding")
necessary to convey iCalendar Transport-independent Interoperability
Protocol (iTIP) [iTIP] over Internet email (using MIME) as defined in
[RFC-5322] and [RFC-2045].