RE: [XCON] Control Values and the Data Model

["Brian Rosen" <br at brianrosen.net>]

-----Original Message-----
From: Umesh.Chandra at nokia.com [mailto:Umesh.Chandra at nokia.com] 
Sent: Thursday, May 04, 2006 9:32 AM
To: br at brianrosen.net; cboulton at ubiquity.net; adam at nostrum.com;
xcon at ietf.org
Subject: RE: [XCON] Control Values and the Data Model

 inline as [UC}

>-----Original Message-----
>From: ext Brian Rosen [mailto:br at brianrosen.net] 
>Sent: Thursday, May 04, 2006 8:18 AM
>To: Chandra Umesh (Nokia-NRC/Dallas); cboulton at ubiquity.net; 
>adam at nostrum.com; xcon at ietf.org
>Subject: RE: [XCON] Control Values and the Data Model
>
>I don't think we really need to change permissions during a 
>conference, but I don't think it's very difficult to allow it. 
> I think that you need a permission system to be able to 
>define who gets to view and/or change what.

[UC} But then how do we indicate the change of the permissions in the
template. The template is defining roles and in roles we are defining
certain controls that are availble for that particular role. So if a
template says that control foo is available only to a role of creator,
then it is available only to the role of creator and not any other role.

<br>well, "available to" is problematic.  It's defined ON the role; only
people in the role have one.  There is another question of who gets to view
and/or change it.  That's different from who owns it.

>
>I think, for example, in most systems, you can get a roster, 
>but you won't be able to see the details of all the streams 
>each participant is sending or getting from the mixer.
>
>I do think that some controls will be available only to 
>participants in a role.  The example you are using (mute) is 
>not a good one, because the user needs to control his own 
>mute, and moderated conferences need the ability for the 
>moderator to control it.  I can even imagine defining a floor, 
>where getting the floor changes the state of the mutes automatically.
>
>Brian
>


[UC} The control Mute is applicable not only to the participant role
(the participant can mute its stream so as the moderator). We have
defined the controlArray element in the moderator role section where the
idea is to have the moderator be able to mute the streams of all the
participants in the conference. And I do agree with your earlier comment
that logicalstream might not be a good idea. We are planning to change
that.

<br> But then you have two controls that do exactly the same thing, and the
user can't see the moderator's control. 

Would it not be better to have one control, and change who can set it?

Brian


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