IETF Logo Mail Archive

Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01

Andrew Allen <aallen@blackberry.com> Wed, 13 March 2013 18:11 UTC

Return-Path: <prvs=2784a1a91b=aallen@blackberry.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5407621F8E7B for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 11:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.348
X-Spam-Level:
X-Spam-Status: No, score=-5.348 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrtX5CjOtDEI for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 11:11:40 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1F721F8E7A for <rtcweb@ietf.org>; Wed, 13 Mar 2013 11:11:40 -0700 (PDT)
X-AuditID: 0a41282f-b7fa06d000002431-ea-5140c15b4f3e
Received: from XCT104ADS.rim.net (xct104ads.rim.net [10.67.111.45]) by mhs060cnc.rim.net (SBG) with SMTP id F3.1E.09265.B51C0415; Wed, 13 Mar 2013 13:11:39 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT104ADS.rim.net ([fe80::90f9:3b89:1d94:aa9b%22]) with mapi id 14.02.0328.009; Wed, 13 Mar 2013 13:11:39 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "adam@nostrum.com" <adam@nostrum.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01
Thread-Index: AQHOIBMyr0S8clvDH0eEEMyuKlC7H5ij7EJm
Date: Wed, 13 Mar 2013 18:11:37 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338D28B68@XMB104ADS.rim.net>
In-Reply-To: <5140BC2C.90206@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.67.110.253]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGKsWRmVeSWpSXmKPExsXC5Zyvqxt90CHQ4NIVPYs9fxexW6z9187u wOSxZMlPJo9ZO5+wBDBFNTDaJCWWlAVnpufp29kk5uXllySWpCqkpBYn2yr5pKYn5igEFGWW JSZXKrhkFifnJGbmphYpKWSm2CqZKCkU5CQmp+am5pXYKiUWFKTmpSjZcSlgABugssw8hdS8 5PyUzLx0WyXPYH9dCwtTS11DJTvdhE6ejG8/1jEVPOOuOL/jB3MD4wPOLkYODgkBE4m5a3W6 GDmBTDGJC/fWs4HYQgIrGSXaH7B2MXIB2ZsZJV48amMESbAJaEnsPzydCcQWEfCTWNT1igXE FhaIl7g/8T4jRDxB4s/n3+wg80UEjCTmvU8DMVkEVCW+7cgDqeAV8JDYuWAvWDWngKbEtz0T wGxGoBO+n1oDNp1ZQFzi1pP5TBCnCUgs2XOeGcIWlXj5+B8rhK0o8Xfvd1aIej2JG1OnsEHY 2hLLFr5mhtglKHFy5hOWCYwis5CMnYWkZRaSlllIWhYwsqxiFMzNKDYwM0jOS9YryszVy0st 2cQIinhHDf0djG/fWxxiFOBgVOLhFd/lECjEmlhWXJl7iFGCg1lJhHd5LlCINyWxsiq1KD++ qDQntfgQoyswICYyS3En5wOTUV5JvLGBAW6OkjivSKBooJBAOjC9ZKemFqQWwcxh4uAE2cMl JVIMTBKpRYmlJRnxoFQWXwxMZlINjMx6e0IY5pbGcvE9Ek2PV34Sv/r+stAJS/jrJnCKlKcw 3ktWddE/YfKwb0/gzfPG1/7/feW7Ys7LkKupk3w6TG9/ubn+mr166J6Zq8WknZpq74dtFtqw UqWUm9tjapNlq04Tp06JvMCjwicx2p07k/9WftlgOWvbjWuZYsH1dwtuz/joLjT7mBJLcUai oRZzUXEiAEF1kRE5AwAA
Subject: Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 18:11:41 -0000

+1

It seems clear to me that other codecs will be included by most if not all RTCweb compliant browsers but which ones should be left up to implementers based on commercial decisions and which ones they include may change over time as codecs become obsoleted by new codecs. The MTIs are the ones that will always be supported to ensure interoperability other codecs will be supported when it makes sense.

Andrew 



----- Original Message -----
From: Adam Roach [mailto:adam@nostrum.com]
Sent: Wednesday, March 13, 2013 12:49 PM Central Standard Time
To: rtcweb@ietf.org <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda time request for	draft-marjou-rtcweb-audio-codecs-for-interop-01

On 3/13/13 11:42, Olle E. Johansson wrote:
> I don't think everyone gets the that selecting a small subset as mandatory for WebRTC does NOT exclude all other codecs. Feel free to add everything you got. Have fun. Let the best mutual codec with the best mutual properties win the session.

Olle hit the nail squarely on the head. This is exactly the purpose of 
offer/answer negotiation: to find the best intersection of endpoint 
capabilities for the desired communication session. I'm bewildered by 
the fairly consistent misinterpretation that having an MTI codec somehow 
implies that every other codec becomes "MNTI".

/a
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

v2.8.10 | Report a Bug | By Email