{"draft":"draft-ietf-calsify-rfc2447bis-11","doc_id":"RFC6047","title":"iCalendar Message-Based Interoperability Protocol (iMIP)","authors":["A. Melnikov, Ed."],"format":["ASCII","HTML"],"page_count":"22","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Calendaring and Scheduling Standards Simplification","abstract":"This document, \"iCalendar Message-Based Interoperability Protocol\r\n(iMIP)\", specifies a binding from the iCalendar Transport-independent\r\nInteroperability Protocol (iTIP) to Internet email-based transports.\r\nCalendaring entries defined by the iCalendar Object Model (iCalendar) are\r\nwrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046,\r\nRFC 2047, and RFC 2049), and then transported over SMTP.  [STANDARDS-TRACK]","pub_date":"December 2010","keywords":["[IMIP]","electronic mail","transport","itip","iCalendar Transport-independent Interoperability Protocol","iCalendar Object Model"],"obsoletes":["RFC2447"],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC6047","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc6047"}