Return-Path: 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 ECEDB21F870E for ; Mon, 28 Jan 2013 08:03:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] 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 fkU8h6p7-DLK for ; Mon, 28 Jan 2013 08:03:04 -0800 (PST) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 0DEDB21F86FA for ; Mon, 28 Jan 2013 08:02:58 -0800 (PST) Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 81064324279; Mon, 28 Jan 2013 17:02:57 +0100 (CET) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 634202380A6; Mon, 28 Jan 2013 17:02:57 +0100 (CET) Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Mon, 28 Jan 2013 17:02:56 +0100 From: To: Magnus Westerlund , "Romascanu, Dan (Dan)" Thread-Topic: [rtcweb] Conclusion statement for Recommended Audio Codecs call Thread-Index: AQHN/S8mkLzfDqN6Ck6wzddU0ym4y5he2MLw Date: Mon, 28 Jan 2013 16:02:56 +0000 Message-ID: <29466_1359388977_5106A131_29466_1646_1_2842AD9A45C83B44B57635FD4831E60A079E39@PEXCVZYM14.corporate.adroot.infra.ftgroup> References: <50FD4C4B.9020700@ericsson.com> <50FEB1EC.9060803@ericsson.com> <9904FB1B0159DA42B0B887B7FA8119CA076D1E@AZ-FFEXMB04.global.avaya.com> <510632D1.4020704@ericsson.com> In-Reply-To: <510632D1.4020704@ericsson.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.2] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.24.110314 Cc: "Cullen Jennings \(fluffy\)" , "rtcweb@ietf.org" Subject: Re: [rtcweb] Conclusion statement for Recommended Audio Codecs call X-BeenThere: rtcweb@ietf.org 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: Mon, 28 Jan 2013 16:03:05 -0000 Hello, > We chairs was considering inclusion in draft-ietf-webrtc-audio, but we di= dn't have any strong opinions on this > I thus decided that we will start out with an independent document If the Chairs have still no strong opinion about this, I would request to l= eave this somewhat editorial issue still open. It makes more sense that all the relevant information for audio and especia= lly the relevant codecs with their different status be clearly listed in th= e same "webrtc audio" specification. Especially because we want to address = the same interoperability issue. This will be more consistent and readable. Then, if more informative text on additional codecs is needed, a separate d= ocument can be considered to avoid overloading this webrtc audio document w= ith purely informative text. St=E9phane=09 -----Message d'origine----- De=A0: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] De la part = de Magnus Westerlund Envoy=E9=A0: lundi 28 janvier 2013 09:12 =C0=A0: Romascanu, Dan (Dan) Cc=A0: Cullen Jennings (fluffy); rtcweb@ietf.org Objet=A0: Re: [rtcweb] Conclusion statement for Recommended Audio Codecs ca= ll Hi, We chairs was considering inclusion in draft-ietf-webrtc-audio, but we didn= 't have any strong opinions on this. Based on that several WG participants = thinks this should be an independent document, I thus decided that we will = start out with an independent document. If the WG feels differently later w= e can always fold the text into the audio codec and processing requirements= document. I would recommend that the individuals interested in contributing a codec w= rites an independent submission with focus on the codec considerations arou= nd the codec(s) they are interested in. Then we can merge this into a commo= n WG document. Cheers Magnus On 2013-01-27 10:14, Romascanu, Dan (Dan) wrote: > Hi WG chairs, >=20 > Clarification question:=20 >=20 >> In lieu of additional normative text, we believe the WG discussion=20 >> supports the inclusion of a new section on "Additional Relevant Codecs". >=20 > Inclusion where?=20 >=20 > Thanks and Regards, >=20 > Dan >=20 >=20 >=20 >=20 >> -----Original Message----- >> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On=20 >> Behalf Of Cullen Jennings (fluffy) >> Sent: Thursday, January 24, 2013 6:47 PM >> To: rtcweb@ietf.org >> Subject: Re: [rtcweb] Conclusion statement for Recommended Audio=20 >> Codecs call >> >> >> We have been running a call for consensus regarding Selecting=20 >> Recommended Audio Codecs. >> >> At this point the chairs are calling this as "no WG consensus". >> >> We can however note a strong interest in a non-normative listing of=20 >> potentially important codecs including a description why they should=20 >> be considered to be supported in WebRTC implementations. >> >> In lieu of additional normative text, we believe the WG discussion=20 >> supports the inclusion of a new section on "Additional Relevant Codecs". >> That can contain a list of codecs which are relevant in specific=20 >> contexts, along with a short description of the context for each. >> Specifically there seems to be interest in understanding the=20 >> advantages and costs of G.722, AMR, and AMR-WB. We hope that text=20 >> would broaden understanding of the WebRTC use case contexts. >> >> The WG chairs >> Magnus, Ted and Cullen >> >> >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >=20 >=20 --=20 Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 F=E4r=F6gatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you.