iCalendar Transport-Independent Interoperability Protocol (iTIP) Part Two: Scheduling To-Dos
draft-ietf-calsch-itip-part2-00
Document | Type |
Expired Internet-Draft
(calsch WG)
Expired & archived
|
|
---|---|---|---|
Authors | Frank Dawson , Ross Hopson | ||
Last updated | 1997-07-22 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
This set of documents, collectively called the iCalendar Transport-independent Interoperability Protocol, or iTIP, defines a transport-independent message protocol to allow for searching for busy time and the scheduling of events, journals, or journal entries on different calendaring and scheduling systems. These documents are based on earlier work documented in the iCalendar format. Because iCalendar delt mainly with the format of calendaring information and said so little about the method for conveying scheduling semantics, these documents add scheduling semantics to the base calendaring functionality defined in iCalendar.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)