Requirements for conference policy data
draft-koskelainen-sipping-conf-policy-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Petri Koskelainen | ||
| Last updated | 2003-02-24 | ||
| 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
The conference participants may communicate with the conference policy server, using a conference policy control protocol (CPCP) which is a strictly client-server transactional protocol. This document describes the requirements for conference policy data. Media policy related requirements are beyond the scope of this document. CPCP protocol is not mandatory and the only mechanism to manipulate conference policy data in a conference. For example, web interface can be used as well to perform conference policy manipulation. However, for automata a protocol is needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)