RFC 3283 (rfc3283) - Page 2 of 16
Guide to Internet Calendaring
Alternative Format: Original Text Document
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 . . . . . . . . . . . . . . . . . . . . . . . 12
6.3 Using E-mail . . . . . . . . . . . . . . . . . . . . . . . . 13
6.4 Other Issues . . . . . . . . . . . . . . . . . . . . . . . . 13
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 13
References . . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 15
Full Copyright Statement . . . . . . . . . . . . . . . . . . 16
1. Introduction
Calendaring and scheduling protocols are intended to aid individuals
in obtaining calendaring information and scheduling meetings across
the Internet, to aid organizations in providing calendaring
information on the Internet, and to provide for organizations looking
for a calendaring and scheduling solution to deploy internally.
It is the intent of this document to provide a context for these
documents, assist in their understanding, and potentially help in the
design of standards-based calendaring and scheduling systems.
Problems not solved by these protocols, as well as security issues to
be kept in mind, are discussed at the end of the document.
1.1 Terminology
This memo uses much of the same terminology as iCalendar [RFC-2445],
iTIP [RFC-2446], iMIP [RFC-2447], and [CAP]. The following
definitions are provided as an introduction; the definitions in the
protocol specifications themselves should be considered canonical.
Mahoney, et. al. Informational