[clue] Requirement on centralized media mixing

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 14 June 2011 14:23 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9907711E80B6 for <clue@ietfa.amsl.com>; Tue, 14 Jun 2011 07:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level:
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8JXduoup6M6 for <clue@ietfa.amsl.com>; Tue, 14 Jun 2011 07:23:07 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 92EF011E80A0 for <clue@ietf.org>; Tue, 14 Jun 2011 07:23:06 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-f6-4df76ec25919
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id D4.52.09774.2CE67FD4; Tue, 14 Jun 2011 16:22:58 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.136]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Tue, 14 Jun 2011 16:22:57 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Tue, 14 Jun 2011 16:22:57 +0200
Thread-Topic: Requirement on centralized media mixing
Thread-Index: Acwqno7BLwl3j+PMSjaOF3ZfYi/FNw==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194E3A1471@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A0585194E3A1471ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [clue] Requirement on centralized media mixing
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 14:23:07 -0000

Hi,

During the last interim meeting (May 12th) we discussed a requirement proposal
stating that an endpoint must be able to request central audio rendering
of different predefined formats, including 3D binaural rendering.
(Link to proposal: http://www.ietf.org/mail-archive/web/clue/current/msg00179.html)

The proposal was well received, with the reservation that it should not be mandatory
for the solution to implement centralized 3D binaural rendering, i.e.an endpoint should
be able to request 3D binaural rendering, but had no guaranty that such rendering was
supported by the system.

It was decided to look how such requirement could look like.

When I look the -03 version of the req draft, Requirement 2c states:

    "The solution MUST NOT preclude the use of binaural audio."

I think that requirement is unclear, and it doesn't really give any guidance to our work.

Due to that, and also due to the fact that rather than talking about specific rendering types,
I would like to propose more general requirement text on the negotiation of the media mixing type,
and the usage of centralized media mixing in the first place.

The mechanism would be extendable, so new types can be added in future.

So, the proposed requirements are:

REQ-x:    It MUST be possible to negotiate the usage of centralized media mixing. System support of centralized media mixing is optional.

REQ-y:    When centralized media mixing is used, it MUST be possible to negotiate the type of media rendering provided for each media stream received by a client.

Regards,

Christer