Policy-Free Floor Control

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

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

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

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

6
Next steps

• Integrate all or some of these requirements into
  the wg document