iCalendar SIP-Based Interoperability Protocol
draft-pessi-ical-isip-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pekka Pessi , Martti Mela | ||
| Last updated | 2003-06-30 | ||
| 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
This document proposes a binding from the abstract iCalendar Transport-independent Interoperability Protocol (iTIP) using Session Initiation Protocol (SIP) as transport and SIP/SIPS URIs as addresses. The iTIP objects are used as a MIME payload format with SIP. iTIP is an abstract transport protocol for exchanging calendaring information between calendar systems using the iCalendar, Internet Calendaring and Scheduling Core Object Specification defined by RFC-2445. SIP is a application-layer signaling protocol for creating, modifying, and terminating multimedia sessions, retrieving user presence and sending instant messages.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)