[XCON] Comment on floor control requirements

"Drage, Keith (Keith)" <drage@lucent.com> Tue, 11 November 2003 04:50 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05511 for <xcon-archive@odin.ietf.org>; Mon, 10 Nov 2003 23:50:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJQTb-0000Hu-M8 for xcon-archive@odin.ietf.org; Mon, 10 Nov 2003 23:50:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAB4o3bV001106 for xcon-archive@odin.ietf.org; Mon, 10 Nov 2003 23:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJQTb-0000Hl-Ha for xcon-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 23:50:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05457 for <xcon-web-archive@ietf.org>; Mon, 10 Nov 2003 23:49:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJQTZ-0004le-00 for xcon-web-archive@ietf.org; Mon, 10 Nov 2003 23:50:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJQTY-0004lW-00 for xcon-web-archive@ietf.org; Mon, 10 Nov 2003 23:50:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJQTZ-0000FF-BN; Mon, 10 Nov 2003 23:50:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJQSc-0008UQ-2l for xcon@optimus.ietf.org; Mon, 10 Nov 2003 23:49:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05401 for <xcon@ietf.org>; Mon, 10 Nov 2003 23:48:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJQSZ-0004jm-00 for xcon@ietf.org; Mon, 10 Nov 2003 23:48:59 -0500
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AJQSZ-0004jU-00 for xcon@ietf.org; Mon, 10 Nov 2003 23:48:59 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57]) by auemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAB4nPA20160 for <xcon@ietf.org>; Mon, 10 Nov 2003 22:49:26 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2656.59) id <4M3XAS05>; Tue, 11 Nov 2003 04:48:25 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00A4FF9DB@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: xcon@ietf.org
Date: Tue, 11 Nov 2003 04:48:24 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [XCON] Comment on floor control requirements
Sender: xcon-admin@ietf.org
Errors-To: xcon-admin@ietf.org
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>

In draft-koskelainen-xcon-floor-control-req-00 there are hints that some sort of queue exists when the number of participants requesting the floor exceeds the number of participants allows simultaneous use of the floor.

For example REQ-10 refers to the number of simultaneous floor holders, and REQ-11 refers to passing the floor to the next in line after a time interval.

It would appear to me that this queuing needs to be more extensively discussed in the above requirements document. 

Firstly REQ-11 implies that the queue is first in, first out (and I stress that this is an implication), whereas in real life certain users may preempt others in the queue. 

Secondly it would appear to be appropriate to have requirements for the floor control chair to have requirements for manipulating the queue, e.g. to designate the order of obtaining the floor, to clear the queue and so on.

Additionally, perhaps other participants may also require visibility of the queue.

My proposal would therefore to update the draft to explicitly define this queue concept, and then to revise the requirements to reflect the existence of the queue, and add requirements for the manipulation of the queue.

regards

Keith

Keith Drage
Lucent Technologies
drage@lucent.com
tel: +44 1793 776249

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon