iCalendar Scheduling
draft-royer-calsch-sched-ex-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Doug Royer | ||
| Last updated | 2004-01-07 | ||
| 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
A proposal to specify booked persistent data in calendar stores to track 'SEQUENCE' and 'DTSTAMP' property values for CUAs with direct access to calendar stores. With iMIP the iCalendar CUA's do not see the others stored CS data. With WebDAV, HTTP, or FTP access, the CUA can see into the public data of other calendars. The storage of persistent data mandated by [iTIP] has not been standardized yet. This memo proposes a way to standardize on those persistent items. Also included are ways to make the various ways of using the [iCAL] and [iTIP] 'RECURRENCE-ID' property work between vendors and to document the procedures to work with 'RECURRENCE-ID's.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)