Use of "Roles" in CLUE
draft-groves-clue-role-clarifications-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Groves , Weiwei Yang , Roni Even | ||
| Last updated | 2014-01-09 (Latest revision 2013-07-08) | ||
| 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
There have been recent discussions on the CLUE and DISPATCH mailing lists about "roles" associated with multimedia conferences. From the discussions it was apparent that there is some confusion as to what the current defined roles actually imply and that people had different understanding of the meaning and scope of the term "role". This draft seeks to identify the various "roles" that may be associated with a multimedia conference and to provide a grouping and nomenclature for further discussions on this topic. Specific to CLUE this draft proposes a number of attributes to be able to clearly identify the various roles that may be associated with a media capture.
Authors
Christian Groves
Weiwei Yang
Roni Even
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)