Internet Calendaring and Scheduling Core Object Specification (iCalendar)
draft-cstoner-rfc2445bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chris Stoner | ||
| Last updated | 2005-07-15 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Calendar systems export, transport and sometimes even store calendar information in a standard, interoperable format. This memo defines the common format for openly exchanging calendaring and scheduling information across the Internet, known as the iCalendar object format. An iCalendar object may represent an event, to-do or task, or journal entry (note). Comments are solicited and should be addressed to the working group's mailing list at ietf-calsify@osafoundation.org and/or the editor.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)