Conference Policy Control Protocol Building Blocks
draft-ekim-xcon-cpcp-bb-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eunsook Kim | ||
| Last updated | 2003-10-17 | ||
| 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
In a tightly coupled conference, conference participants can communicate with the conference policy server using a conference policy control protocol (CPCP). This document generally describes how to use CPCP to efficiently provide and augment interaction between clients and conference policy server. This document describes what information is needed for conference policy control, and what operation is needed to manipulate and interact with the policy information. It is noted that the purpose of this draft is not to suggest a new mechanism of CPCP, but to suggest building block approach to CPCP work.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)