ࡱ> ",  !$%&'()*+Root EntrydO)Pkm#PowerPoint Document(>SummaryInformation( DocumentSummaryInformation88v( / 00DTimes New Roman0|dv 0|( 0XDComic Sans MSn0|dv 0|( 0XB DTahomaans MSn0|dv 0|( 0X"0DWingdings MSn0|dv 0|( 0X ` .  @n?" dd@  @@`` h, *    c $@@uʚ;2Nʚ; ?@% ,53rd IETF - March 2002O =#Requirements for Conference ControlG Xiaotao Wu Petri Koskelainen Clayton C. Chen Columbia University/Nokia H.Conference ControlFocus on media-independent control (see Orit Levin s talk for media issues) Conference models: centralized: lowest-hanging fruit centralized with replication: seems similar fully meshed: probably same mechanisms, but harder to coordinate (distributed system) multicast: may also work for SSM Core property: single media  choke point <_*_*(""Taxonomy of functions (incomplete)0Needed throughout conference life cycle Create new conference properties: duration, media, user limit, ... mass-invitation but: is this needed beyond the current ad-hoc conference creation? Admit users similar to presence subscriber problem? proactive policy ( don t admit *.fbi.gov ) CPL? individual decisions:  Alice wants to join Eject users (less important?) Shared resource access, aka floor control > (^I> (+   -  I>l FunctionsNot every conference needs all functions Web interface can be done, but hard to script Don t assume single person has multiple roles bouncer (sergeant-at-arms) vs. moderator Need to deal with moderator failure distributed leader election problem is hard may want to punt Provide mechanisms, avoid guessing at policy  only admit Joe if fewer than 4 participants and if 65% of participants agree Z)Z$Z=Z-ZOZ)$=-O   Floor controlGeneral: management of shared resources audio channel (typically, one) video (limited by bandwidth, screen) whiteboard and shared applications (one, but also multiple pointers) Managed by automated queuing policy can be messy ( priority to speakers that have talked for less than 5 minutes ) suggestion: punt on policy one or more moderators( q( q Floor control requirementsCreate a managed resource zero, one or multiple media Remove managed resource Change resource configuration moderator, users, concurrency Request resource Grant resource Revoke resource including pending requests Release resource Reorder resource claims 60*60* $Commonalities across functionalitiesFunctions are largely orthogonal But share communication needs: asynchronous events  Bob joined conference (sip-call-package)  Carol has released floor  David has requested floor commands to conference avoid commands directly to participants @b(@b  Questions~How hostile is the conference? If participants basically trust each other, moderator failure is much easier to deal with Define trusted subgroup? Panel discussion model: panel vs. mob audience Scaling requirements? Primarily notifications are issue Centralized conference model imposes some limitations, but can still be hundreds REFER can provide some functionality (invite, eject)ZsZ/ZZsZ5Zs/  s  5   SummaryConference control probably misnomer Keep media stream control separate  may be needed for unicast just as much Divide into components, possibly prioritize: conference creation and deletion user admission resource management&DD ` ` ̙33` 333MMM` ff3333f` f` f` 3>?" dd@(?dd@   " @ ` n?" dd@   @@``PR    @ ` ` p>> j(    6^   T Click to edit Master title style! !  0 `  RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  0 ``  B*?  0@ `   @*  0 `   @*H  0޽h ? ̙330 zr0  (     0 P    P*    0T     R*  d  c $ ?    0 r  @  RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  6y `P   P*    6 `   R*  H  0޽h ? ̙33 KC (  r  S p  r  S  `      < /   CHenning SchulzrinneH  0޽h ? ̙33  @0(  x  c $   x  c $h`  H  0޽h ? ̙33  P0(  x  c $   x  c $0`  H  0޽h ? ̙33   0(   x  c $t   x  c $`  H  0޽h ? ̙33  `0(  x  c $   x  c $`  H  0޽h ? ̙33  ($(  (r ( S    r ( S `  H ( 0޽h ? ̙33  p0(  x  c $DQ   x  c $`  H  0޽h ? ̙33J  $(  $x $ c $ܷ  N x $ c $ `  RB $ s *DjJ@@`@H $ 0޽h ? ̙33  ,$(  ,r , S xN  N r , S TTN` N H , 0޽h ? ̙33r4~+&s.k0c2[4?87:S6< u>   !"#$%&'()*+,-./012345679:;<=>?@ABCDFOh+'0 hp    (Requirements for eHenning SchulzrinneennHenning Schulzrinne2nnMicrosoft PowerPointP@ g@We@þkmG| g  61& &&#TNPP2OMi & TNPP &&TNPP    --- !---&G&qw@ LSwUSw0- @Times New RomanLSwUSw0- .2 R 15 March 2002   .&Gy&  .2  53rd IETF   . . 2 -. .2  March 2002  .--iyH-- @BComic Sans MS LSwUSw0- .12 rRequirements for Conference ") . .2 _Control .--Q1-- @"Tahomaw@L LSwUSw0- .2  Xiaotao Wu . .!2 {Petri Koskelainen  . .2 *Clayton C. Chen .@"Tahomaw@ LSwUSw0- .-2 PFColumbia University/NokiaL    .&P&--&&̙- $PP&&&- & $PP&&-&& &&-B( UUUU-&&P&&̙- $PP&- --&& @"Tahomaw@L LSwUSw0- .$2 ZHenning Schulzrinne  .--"System 0-&TNPP &՜.+,0   ( 0 rOn-screen Show&Computer Science, Columbia Universityn>T  Times New RomanComic Sans MSTahoma WingdingsDefault Design$Requirements for Conference ControlConference Control#Taxonomy of functions (incomplete) FunctionsFloor controlFloor control requirements%Commonalities across functionalities QuestionsSummary  Fonts UsedDesign Template Slide Titles +_>Henning SchulzrinneHenning SchulzrinneCurrent UserEY