Browse Prior Art Database

Guide to Internet Calendaring (RFC3283)

IP.com Disclosure Number: IPCOM000008640D
Original Publication Date: 2002-Jun-01
Included in the Prior Art Database: 2002-Jul-01
Document File: 17 page(s) / 32K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Mahoney: AUTHOR [+3]

Abstract

This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them. Its intent is to provide a context for these documents, assist in their understanding, and potentially aid in the design of standards-based calendaring and scheduling systems. The standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and RFC 2447 (iMIP). The work in progress addressed is "Calendar Access Protocol" (CAP). This document also describes issues and problems that are not solved by these protocols, and that could be targets for future work.

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

Network Working Group                                         B. Mahoney

Request for Comments: 3283                                           MIT

Category: Informational                                        G. Babics

                                                                 Steltor

                                                                A. Taler

                                                               June 2002

                     Guide to Internet Calendaring

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

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

Abstract

   This document describes the various Internet calendaring and

   scheduling standards and works in progress, and the relationships

   between them.  Its intent is to provide a context for these

   documents, assist in their understanding, and potentially aid in the

   design of standards-based calendaring and scheduling systems.  The

   standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and

   RFC 2447 (iMIP).  The work in progress addressed is "Calendar Access

   Protocol" (CAP).  This document also describes issues and problems

   that are not solved by these protocols, and that could be targets for

   future work.

Table of Contents

   1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  2

   1.1   Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  2

   1.2   Concepts and Relationships . . . . . . . . . . . . . . . . .  4

   2.    Requirements . . . . . . . . . . . . . . . . . . . . . . . .  4

   2.1   Fundamental Needs  . . . . . . . . . . . . . . . . . . . . .  4

   2.2   Protocol Requirements  . . . . . . . . . . . . . . . . . . .  5

   3.    Solutions  . . . . . . . . . . . . . . . . . . . . . . . . .  7

   3.1   Examples . . . . . . . . . . . . . . . . . . . . . . . . . .  7

   3.2   Systems  . . . . . . . . . . . . . . . . . . . . . . . . . .  8

   3.2.1 Standalone Single-user System  . . . . . . . . . . . . . . .  8

   3.2.2 Single-user Systems Communicating  . . . . . . . . . . . . .  8

   3.2.3 Single-user with Multiple CUAs . . . . . . . . . . . . . . .  9

   3.2.4 Single-user with Multiple Calendars  . . . . . . . . . . . .  9

Mahoney, et. al.             Informational                      [Page 1]

RFC 3283             Guide to Internet Calendaring             June 2002

   3.2.5 Users Communicating on a Multi-user System . . . . . . . . . 10

   3.2.6 Users Communicating through Different Multi-user Systems . . 10

   4.    Important Aspects  . . . . . . . . . . . . . . . . . . . . . 10

   4.1   Timezones  . . . . . . . . . . . . . . . . . . . . . . . . . 10

   4.2   Choice of Transport  . . . . . . . . . . . . . . . . . . . . 11

   4.3   Security . . . . . . . . . . . . . . . . . . . . . . . . . . 11

   4.4   Amount of data . . . . . . . . . . . . . . . . . . . . . . . 11

   4.5   Recurring Components . . . . . . . . . . . . . . . . . . . . 11

   5.    Open Issues  . . . . . . . . . . . . . . . . . . . . . . . . 11

   5.1   Scheduling People, not Calendars . . . . . . . . . . . . . . 12

   5.2   Administration . . . . . . . . . . . . . . . . . . . . . . . 12

   5.3   Notification . . . . . . . . . . . . . . . . . . . . . . . . 12

   6.    Security Considerations  . . . . . . . . . . . . . . . . . . 12

   6.1   Access Control . . . . . . . . . . . . . . . . . . . . . . . 12

   6.2   Authentication . . . . . . . . . . . . . . . ....