Browse Prior Art Database

iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries (RFC2446)

IP.com Disclosure Number: IPCOM000003024D
Original Publication Date: 1998-Nov-01
Included in the Prior Art Database: 2019-Feb-11

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Silverberg: AUTHOR [+3]

Related Documents

10.17487/RFC2446: DOI

Abstract

This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. [STANDARDS-TRACK]

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

Network Working Group S. Silverberg Request for Comments: 2446 Microsoft Category: Standards Track S. Mansour Netscape F. Dawson Lotus R. Hopson ON Technologies November 1998

iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries

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 specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. Subsequent documents specify interoperable methods of communications between systems that use this protocol.

The document outlines a model for calendar exchange that defines both static and dynamic event, to-do, journal and free/busy objects. Static objects are used to transmit information from one entity to another without the expectation of continuity or referential integrity with the original item. Dynamic objects are a superset of static objects and will gracefully degrade to their static counterparts for clients that only support static objects.

This document specifies an Internet protocol based on the iCalendar object specification that provides scheduling interoperability between different calendar systems. The Internet protocol is called the "iCalendar Transport-Independent Interoperability Protocol (iTIP)".

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

RFC 2446 iTIP November 1998

iTIP complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendar systems. These scheduling methods permit two or more calendar systems to perform transactions such as publish, schedule, reschedule, respond to scheduling requests, negotiation of changes or cancel iCalendar-based calendar components.

iTIP is defined independent of the particular transport used to transmit the scheduling information. Companion memos to iTIP provide bindings of the interoperability protocol to a number of Internet protocols.

Table of Contents

1 INTRODUCTION...................................................5 1.1 FORMATTING CONVENTIONS .....................................5 1.2 RELATED DOCUMENTS ..........................................6 1.3 ITIP ROLES AND TRANSACTIONS ................................6 2 INTEROPERABILITY MODELS........................................8 2.1 APPLICATION PROTOCOL .......................................9 2.1.1 Calendar Entry State ...................................9 2.1.2 Delegation .............................................9 2.1.3 Acting on...

Processing...
Loading...