Conference Focus Indicating CCMP Support
draft-yusef-xcon-ccmp-indication-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rifaat Shekh-Yusef , Mary Barnes | ||
| Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
| 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 Centralized Conferencing Manipulation Protocol document defines away for a client to discover a conference control server that supports CCMP. However, it does not define a way for a client involved in a conference to determine if the conference focus supports CCMP. This information would allow a CCMP-enabled client that joins a conference using SIP to also register for the XCON conference event package and take advantage of CCMP operations on the conference. This draft describes few options to address the above limitation with the pros and cons for each approach.
Authors
Rifaat Shekh-Yusef
Mary Barnes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)