[MEDIACTRL] Questions for draft-ietd-mediactrl-mixer-control-package

"Henry Lum" <Henry.Lum@alcatel-lucent.com> Mon, 11 January 2010 22:33 UTC

Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CDB23A6803 for <mediactrl@core3.amsl.com>; Mon, 11 Jan 2010 14:33:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HW8Am1GciDiY for <mediactrl@core3.amsl.com>; Mon, 11 Jan 2010 14:33:26 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by core3.amsl.com (Postfix) with ESMTP id 52A4E3A6881 for <mediactrl@ietf.org>; Mon, 11 Jan 2010 14:33:26 -0800 (PST)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id o0BMXNv2022348 for <mediactrl@ietf.org>; Mon, 11 Jan 2010 16:33:23 -0600 (CST)
Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id o0BMXNvo028020 for <mediactrl@ietf.org>; Mon, 11 Jan 2010 16:33:23 -0600 (CST)
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id o0BMXMhh007694 for <mediactrl@ietf.org>; Mon, 11 Jan 2010 14:33:22 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Jan 2010 14:33:22 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA930E.15070ADB"
Date: Mon, 11 Jan 2010 14:33:21 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7405277F69@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Questions for draft-ietd-mediactrl-mixer-control-package
Thread-Index: AcqTDhR0x3bJ/K7gRmmVm/EtXKZ3MA==
From: Henry Lum <Henry.Lum@alcatel-lucent.com>
To: mediactrl@ietf.org
X-OriginalArrivalTime: 11 Jan 2010 22:33:22.0470 (UTC) FILETIME=[15011C60:01CA930E]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.27
Subject: [MEDIACTRL] Questions for draft-ietd-mediactrl-mixer-control-package
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2010 22:33:32 -0000

Hi,

 

I have a bunch of questions for the mixer control  package:

 

-          When <destroyconference> is called, what happens to a dialog
that is connected to the conference? It looks like the dialog will
receive a <dialogexit> rather than a <unjoin-notify>, but it's a bit
unclear in the text in section 4.2.1.3.

-          Can conference be destroyed automatically when the last
participant has left (<unjoin>) from the conference? 

-          I see that <conferenceexit> has a status code to timeout a
conference with a maximum duration, is this system specific?

-          Can I add my own audio mixing policy by extending the
<audio-mixing> type attribute? Looks like I can do this with
<video-switch>.

-          When an automatic mixing is applied with <join>, would
<auditresponse> show up as a conference or just a bunch of joins?

-          I find the wording for <stream> direction to be a bit too
much like SDP because the word sendonly implies it's only sending, but
at the same time you can also use another <stream> to reference the
reverse stream with recvonly. I think we should use plain language like
"id1-to-id2", "id2-to-id1", "both", for sendonly, recvonly, and
sendrecv, respectively.

-          For <modifyjoin>, there is one statement that says "It MUST
NOT change the configuration of any streams not included as child
elements.", but then later in the examples part contradicts with this
statement. I actually agree with the example because it's simpler, and
that it means a <modifyjoin> changes the entire configuration of the
existing join and whatever the child elements defined in modifyjoin will
become the new configuration of the join.

-          Section 4.2.2.5.2 - can we simplify the tones attribute with
a default value? For example, the default would be to clamp out all DTMF
tones.

-          Section 4.2.2.5.3 - What is the exact naming of a region? I
see that in this draft it's called 1,2,3.., while in the IVR package it
is called r1.

 

Thanks

Henry


					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.