1 / 6

Policy-Free Floor Control

This draft explores policy-free floor control mechanisms for seamless management of conference inputs, emphasizing voice and data interactions. It discusses various floor binding options, activity awareness, and participant states for optimal control. The document also compares implicit and explicit floor control methods, highlighting the need for trigger specifications and group definitions. It concludes with suggestions for integrating these features into the working group document.

vmary
Download Presentation

Policy-Free Floor Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Policy-Free Floor Control draft-brunner-xcon-fc-issues-00.txt Marcus Brunner NEC

  2. Motivation for Floor Control • Admission Control for Conference Input • Mainly voice • But also data (e.g, shared workspace applications) • Control parallel input to a single input application • Create sequential input from parallel NEC Europe Ltd., 2003 Network Laboratories, Heidelberg

  3. Issues and Requirements • Floor can be bound to various entities • Per-flow, per-session, several floors per session (independently controlled) • Floor can be hold concurrently • More than one participant must be able to hold the floor • Activity awareness • Participant must be aware of the current state of the floor control NEC Europe Ltd., 2003 Network Laboratories, Heidelberg

  4. Policy-free Floor Control • There are several floor control policies • Ring passing • Pre-emptive • Based on time • Moderated • The IETF meeting model • The floor control mechanism must not be targeted to one of these policies, • it should be part of the conference application NEC Europe Ltd., 2003 Network Laboratories, Heidelberg

  5. Implicit versus Explicit Floor Control • Explicit: A floor chair controls the floor • Implicit: Automatic floor passing passed on policies and triggers • Must be able to specify the trigger for floor change • Must be able to define a group of participant, where the floor can automatically change to • The trigger for the floor change must be specified • When the trigger control is distributed we need mechanisms for handling this NEC Europe Ltd., 2003 Network Laboratories, Heidelberg

  6. Next steps • Integrate all or some of these requirements into the wg document NEC Europe Ltd., 2003 Network Laboratories, Heidelberg

More Related