Calendaring Interoperability Protocol
draft-ietf-calsch-cip-00
| Document | Type |
Expired Internet-Draft
(calsch WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Anik Ganguly , Steve Hanna , Bill Spencer | ||
| Last updated | 1996-11-27 | ||
| 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
The Calendaring Interoperability Protocol (CIP) provides a standard mechanism for exchanging events and other information between scheduling systems. This allows users to schedule meetings with anyone else, no matter what scheduling software they use. CIP is one of three standards under development by the Calendaring and Scheduling Working Group of the IETF. The other two are the Core Object Specification (COS), a standard data format for representing scheduled events, and the Calendaring Access Protocol (CAP), a standard mechanism that scheduling user agents may use to access user calendars (analogous to POP).
Authors
Anik Ganguly
Steve Hanna
Bill Spencer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)