Subject: [XCON] Comments on draft-evan-xcon-conference-scenarios-00

From: eburger at snowshore.com (Eric Burger)
Date: Mon Jul 14 10:09:57 2003

2. Conference Scenarios
What is meant by the UA providing DTMF tones.  Does this mean "provide DTMF tones", e.g., generate in-band tone?  What about compressed codecs?  Does this mean "RFC2833"?  If so, the data is going to the wrong place.  Does this mean "KPML"?  If so, it is bending the use of KPML into the IVR realm, which KPML is explicitly not suited for.

2.1 Ad-hoc conference
What is a "number" in SIP?  This paragraph refers to calling and called number.  Do you mean Request-URI and a From or Contact URI?

3.5 Advanced conference features
Is it likely that participants will be manipulating the mix directly?  See my rant on who might do what with whom.

4.1 Video mixing scenarios
Are there any protocol issues here?  By definition, an application creates the web page and it deals with the POST.  Who needs a protocol?  Certainly not the user agent.

4.3 Conference Sidebar scenario
Will the user really set the main mix gain?  Will they specify it in dB, 1-10, 1-100?  What about AGC?

Isn't the behavior of moving someone into the sidebar application-specific?  It should be.  Some just dump people in, others announce them to the sidebar, others do a tone.  I don't think we should be standardizing (or creating protocols that enable) only one way of doing it.

By the way, specifying all of the options presented in this scenario virtually requires at least a 2D GUI.  See 4.1.

4.5 Presentation and QA session
The scenario states the panel members are identified.  Note that often, all listeners are identified to the panel members but not to each other, until (optionally) they get the floor ("now speaking...").