Return-Path: <coverdale@sympatico.ca>
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 4284D1A0104 for <rtcweb@ietfa.amsl.com>;
 Mon, 24 Feb 2014 07:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.001
X-Spam-Level: **
X-Spam-Status: No, score=2.001 tagged_above=-999 required=5 tests=[BAYES_80=2,
 HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_PASS=-0.001] autolearn=no
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 gUDkYZUmGiPq for
 <rtcweb@ietfa.amsl.com>; Mon, 24 Feb 2014 07:23:55 -0800 (PST)
Received: from blu0-omc3-s10.blu0.hotmail.com (blu0-omc3-s10.blu0.hotmail.com
 [65.55.116.85]) by ietfa.amsl.com (Postfix) with ESMTP id E6C6E1A0102 for
 <rtcweb@ietf.org>; Mon, 24 Feb 2014 07:23:54 -0800 (PST)
Received: from BLU0-SMTP100 ([65.55.116.74]) by blu0-omc3-s10.blu0.hotmail.com
 with Microsoft SMTPSVC(6.0.3790.4675); Mon, 24 Feb 2014 07:23:54 -0800
X-TMN: [aeNLm/Mpy/hHfvG/UbIUX8Pynuot7FpA]
X-Originating-Email: [coverdale@sympatico.ca]
Message-ID: <BLU0-SMTP1006A2F5D99681B78DC94CED0860@phx.gbl>
Received: from PaulNewPC ([74.12.62.240]) by BLU0-SMTP100.phx.gbl over TLS
 secured channel with Microsoft SMTPSVC(6.0.3790.4675);
 Mon, 24 Feb 2014 07:23:53 -0800
From: Paul Coverdale <coverdale@sympatico.ca>
To: <rtcweb@ietf.org>
Date: Mon, 24 Feb 2014 10:23:51 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0041_01CF314A.83A40860"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac8xdGvn5+ttPje2T0GUNZrrdMIWGA==
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2014 15:23:53.0969 (UTC)
 FILETIME=[6D79A610:01CF3174]
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/6u9DJabEkUZsjocw54xKBwtghdM
Subject: [rtcweb] Draft-proust-rtcweb-audio-codecs-for-interop
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: Mon, 24 Feb 2014 15:23:56 -0000

------=_NextPart_000_0041_01CF314A.83A40860
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This draft seems like a good start to address the issue of interoperability
of audio codecs in WebRTC. As has been pointed out in previous postings,
AMR, AMR-WB and G.722 are particularly attractive codecs which should be
included, but I note that the authors have left the opportunity for
including others.

 

...Paul


------=_NextPart_000_0041_01CF314A.83A40860
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>This draft =
seems like a good start to address the issue of interoperability of =
audio codecs in WebRTC. As has been pointed out in previous postings, =
AMR, AMR-WB and G.722 are particularly attractive codecs which should be =
included, but I note that the authors have left the opportunity for =
including others.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>...Paul<o:p></o:p></p></div></body></html>
------=_NextPart_000_0041_01CF314A.83A40860--

