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

"Olle E. Johansson" <> Thu, 14 March 2013 07:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E25F121F8DAB for <>; Thu, 14 Mar 2013 00:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uFW1o-mgUFBf for <>; Thu, 14 Mar 2013 00:51:55 -0700 (PDT)
Received: from ( [IPv6:2a02:920:212e::205]) by (Postfix) with ESMTP id 1EF0B21F8A0D for <>; Thu, 14 Mar 2013 00:51:50 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPA id 2530293DE40; Thu, 14 Mar 2013 07:51:38 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: "Olle E. Johansson" <>
In-Reply-To: <3246_1363214890_5141022A_3246_1976_1_34a49fde-fad7-4a0a-8b01-9d48a5b6eeab@PEXCVZYH01.corporate.adroot.infra.ftgroup>
Date: Thu, 14 Mar 2013 08:51:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <31611_1363212891_5140FA5B_31611_17197_1_35788a76-852d-49ce-8987-d2be2f21fcaf@PEXCVZYH02.corporate.adroot.infra.ftgroup> <> <3246_1363214890_5141022A_3246_1976_1_34a49fde-fad7-4a0a-8b01-9d48a5b6eeab@PEXCVZYH01.corporate.adroot.infra.ftgroup>
To: <>
X-Mailer: Apple Mail (2.1499)
Cc: MARJOU Xavier OLNC/OLN <>, "" <>
Subject: Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Mar 2013 07:51:56 -0000

13 mar 2013 kl. 23:48 skrev <>om>:

> The reason is simply that AMR and AMR-WB are supported in billions of devices !
I think it's time to stop discussing historical numbers, current numbers and future numbers of installed codecs in various devices. We're all impressed, but it doesn't seem to change our position on the MTI codec list.

This is a very complex matrix and the codec landscape is every changing. That's why the offer/answer exchange is open for future additions. SIP only mandated a very small set of codecs in RFC 3261 over ten years ago. That did not stop the use of AMR, G722, H.264 or other codecs in SIP devices today. I've even seen Opus being used in SIP without updating RFC 3261. 

I'm pretty sure I will see quite a lot of offers with both AMR and H264 in WebRTC, as I have met them many times in my SIP life.

It seems that we need to clarify this openness to use any codec in the specification, since it seems to be widely misunderstood.