Real-time Protocol Requirements
draft-ietf-calsch-rtreq-00
| Document | Type |
Expired Internet-Draft
(calsch WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Anik Ganguly | ||
| Last updated | 1997-03-28 | ||
| 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 purpose of this document is to create a framework for selecting the appropriate solution for a real-time protocol designed to allow calendaring and scheduling systems from different vendors to interoperate. To that end, it describes the assumptions about the context in which this protocol will operate, and the requirements that the protocol must meet. These requirements are not intended to apply to a companion protocol which will use E-mail based transport to achieve interoperability. The E-mail based protocol, which is the subject of a different document, will not make any assumptions about transport latency.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)