IETF Logo Mail Archive

Re: [rtcweb] confirming sense of the room: mti codec

Gaelle Martin-Cocher <gmartincocher@blackberry.com> Fri, 12 December 2014 15:28 UTC

Return-Path: <gmartincocher@blackberry.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05C581A6FF3 for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 07:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C29tAn_vnJAu for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 07:28:03 -0800 (PST)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 4511A1A8932 for <rtcweb@ietf.org>; Fri, 12 Dec 2014 07:28:03 -0800 (PST)
Received: from xct102cnc.rim.net ([10.65.161.202]) by mhs215cnc.rim.net with ESMTP/TLS/AES128-SHA; 12 Dec 2014 10:27:58 -0500
Received: from XMB111CNC.rim.net ([fe80::fcd6:cc6c:9e0b:25bc]) by XCT102CNC.rim.net ([fe80::2066:5d4f:8c45:af55%17]) with mapi id 14.03.0210.002; Fri, 12 Dec 2014 10:27:58 -0500
From: Gaelle Martin-Cocher <gmartincocher@blackberry.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] confirming sense of the room: mti codec
Thread-Index: AQHQEJCKBITgiQUj50CzzuygMU2TV5yGgaCAgAWZ93A=
Date: Fri, 12 Dec 2014 15:27:57 +0000
Message-ID: <92D0D52F3A63344CA478CF12DB0648AADF360327@XMB111CNC.rim.net>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <D0AB64D8.3FA7A%mzanaty@cisco.com>
In-Reply-To: <D0AB64D8.3FA7A%mzanaty@cisco.com>
Accept-Language: fr-FR, en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.160.250]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/IcC13YeJUUWZiumK30Uvy-jekKQ
Subject: Re: [rtcweb] confirming sense of the room: mti codec
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 15:28:05 -0000

Multiple codecs can be supported even if there is only a single MTI defined in WebRTC. 
This has been confirmed by those who will implement scalable codecs.

I am not aware of anyone asking for removing the codec negotiation/capability discovery even if there is a single MTI. 
As such supporting multiple codecs is independent from the MTI discussion.
The question is not do we need multiple codecs but do we need multiple MTIs (and which). 

Gaëlle


-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Mo Zanaty (mzanaty)
Sent: Monday, December 08, 2014 3:42 PM
To: Sean Turner; rtcweb@ietf.org
Subject: Re: [rtcweb] confirming sense of the room: mti codec


To reiterate another point from the meeting, there are technical advantages to supporting multiple codecs. Dynamic discovery of local capabilities, negotiation of remote capabilities, understanding how different error resilience mechanisms can work (or not) with different codecs, faster adoption of new (non-mandatory) codecs, easier path to deprecating old (mandatory) codecs, etc. All those legs never get exercised effectively in single-codec implementations, leaving land mines in browsers, apps, services and sometimes even specs. They become easier or free once the groundwork is laid for multiple codecs. While some have argued against that extra complexity, I see it as essential for any important standard.

Mo

v2.27.6 | Report a Bug | By Email | System Status