Browse Prior Art Database

iCalendar Message-Based Interoperability Protocol (iMIP) (RFC2447)

IP.com Disclosure Number: IPCOM000003025D
Original Publication Date: 1998-Nov-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 18 page(s) / 22K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Dawson: AUTHOR [+2]

Related Documents

10.17487/RFC2447: DOI

Abstract

This document specifies a binding from the iCalendar Transport- independent Interoperability Protocol (iTIP) to Internet email-based transports. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group F. Dawson Request for Comments: 2447 Lotus Category: Standards Track S. Mansour Netscape S. Silverberg Microsoft November 1998

iCalendar Message-Based Interoperability Protocol (iMIP)

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

This document, [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 [iCAL] are composed using constructs from [RFC-822], [RFC-2045], [RFC-2046], [RFC-2047], [RFC-2048] and [RFC-2049].

This document is based on discussions within the Internet Engineering Task Force (IETF) Calendaring and Scheduling (CALSCH) working group. More information about the IETF CALSCH working group activities can be found on the IMC web site at http://www.imc.org, the IETF web site at http://www.ietf.org/html.charters/calsch-charter.html. Refer to the references within this document for further information on how to access these various documents.

Dawson, et. al. Standards Track [Page 1]

RFC 2447 iMIP November 1998

Table of Contents

1 INTRODUCTION........................................................2 1.1 RELATED MEMOS ...................................................2 1.2 FORMATTING CONVENTIONS ..........................................3 1.3 TERMINOLOGY .....................................................4 2 MIME MESSAGE FORMAT BINDING.........................................4 2.1 MIME MEDIA TYPE .................................................4 2.2 SECURITY ........................................................4 2.2.1 Authorization ...............................................4 2.2.2 Authentication ..............................................5 2.2.3 Confidentiality .............................................5 2.3 [RFC-822] ADDRESSES .............................................5 2.4 CONTENT TYPE ....................................................5 2.5 CONTENT-TRANSFER-ENCODING .......................................6 2.6 CONTENT-DISPOSITION .............................................6 3 SECURITY CONSIDERATIONS.............................................7 4 EXAMPLES............................................................8 4.1 SINGLE COMPONENT WITH AN ATTACH PROPERTY ........................8 4.2 USING MULTIPART ALTERNATIVE FOR LOW FIDELITY CLIENTS ............8 4.3 SINGLE COMPONENT WITH AN ATTACH PROPERTY AND INLINE ATTACHMENT ..9 4.4 MULTIPLE SIMILAR COMPONENTS ....................................10 4.5 MULTIPLE MIXED COMPONENTS .......................................

Processing...
Loading...