Re: [rtcweb] Conclusion statement for Recommended Audio Codecs call
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 27 January 2013 20:08 UTC
Return-Path: <dromasca@avaya.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 EED5421F87F7 for <rtcweb@ietfa.amsl.com>; Sun, 27 Jan 2013 12:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.407
X-Spam-Level:
X-Spam-Status: No, score=-103.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 uMFyy7nP46zS for <rtcweb@ietfa.amsl.com>; Sun, 27 Jan 2013 12:08:13 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0644821F853E for <rtcweb@ietf.org>; Sun, 27 Jan 2013 12:08:12 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAP0QA1HGmAcF/2dsb2JhbABFDoJdu2cWc4IeAQEBAQMBAQEPCx00CwwEAgEIDQEDBAEBAQoUCQcnCxQJCAIEAQ0FCBqHbQELoViccASQXmEDnBqKO4I5PoIk
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="341284664"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 27 Jan 2013 15:08:06 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Jan 2013 15:07:36 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Sun, 27 Jan 2013 15:08:27 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Burger Eric <eburger@cs.georgetown.edu>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: [rtcweb] Conclusion statement for Recommended Audio Codecs call
Thread-Index: AQHN+lJlS8xNYunZw0yrsQtXbpVqGphc6GWggAECl4D//7RrQA==
Date: Sun, 27 Jan 2013 20:08:26 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0786E3@AZ-FFEXMB04.global.avaya.com>
References: <50FD4C4B.9020700@ericsson.com> <CA+9kkMD7hYacr-P+iBdPiPYu4PWbMmu7tXYnYsNHRA18jogb=w@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB11338EB86@xmb-aln-x02.cisco.com> <50FEB1EC.9060803@ericsson.com> <CA+9kkMDCn1M084-qcMWh38oao+A64ToQBZTo1wauyBbhD4mhjw@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB113397466@xmb-aln-x02.cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA076D1E@AZ-FFEXMB04.global.avaya.com> <FB05674A-6502-4549-B061-F7F1B7E3A02F@cs.georgetown.edu>
In-Reply-To: <FB05674A-6502-4549-B061-F7F1B7E3A02F@cs.georgetown.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <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 <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: Sun, 27 Jan 2013 20:08:14 -0000
+1 Dan > -----Original Message----- > From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf > Of Burger Eric > Sent: Sunday, January 27, 2013 9:39 PM > To: Cullen Jennings (fluffy) > Cc: rtcweb@ietf.org > Subject: Re: [rtcweb] Conclusion statement for Recommended Audio Codecs > call > > A different document would be good. No need to to have an argument over > non-normative text hold up publication. > > On Jan 27, 2013, at 4:14 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> > wrote: > > > Hi WG chairs, > > > > Clarification question: > > > >> In lieu of additional normative text, we believe the WG discussion > >> supports the inclusion of a new section on "Additional Relevant > Codecs". > > > > Inclusion where? > > > > Thanks and Regards, > > > > Dan > > > > > > > > > >> -----Original Message----- > >> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On > >> 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 > >> Codecs call > >> > >> > >> We have been running a call for consensus regarding Selecting > >> 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 > >> potentially important codecs including a description why they should > >> be considered to be supported in WebRTC implementations. > >> > >> In lieu of additional normative text, we believe the WG discussion > >> supports the inclusion of a new section on "Additional Relevant > Codecs". > >> That can contain a list of codecs which are relevant in specific > >> contexts, along with a short description of the context for each. > >> Specifically there seems to be interest in understanding the > >> advantages and costs of G.722, AMR, and AMR-WB. We hope that text > >> 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 > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- Re: [rtcweb] Conclusion statement for Recommended… Cullen Jennings (fluffy)
- Re: [rtcweb] Conclusion statement for Recommended… Romascanu, Dan (Dan)
- Re: [rtcweb] Conclusion statement for Recommended… Burger Eric
- Re: [rtcweb] Conclusion statement for Recommended… Andrew Allen
- Re: [rtcweb] Conclusion statement for Recommended… Romascanu, Dan (Dan)
- Re: [rtcweb] Conclusion statement for Recommended… Bernard Aboba
- Re: [rtcweb] Conclusion statement for Recommended… Magnus Westerlund
- Re: [rtcweb] Conclusion statement for Recommended… Cullen Jennings
- Re: [rtcweb] Conclusion statement for Recommended… DRAGE, Keith (Keith)
- Re: [rtcweb] Conclusion statement for Recommended… stephane.proust
- Re: [rtcweb] Conclusion statement for Recommended… Magnus Westerlund
- Re: [rtcweb] Conclusion statement for Recommended… Cameron Byrne
- Re: [rtcweb] Conclusion statement for Recommended… Andrew Allen
- Re: [rtcweb] Conclusion statement for Recommended… Roman Shpount
- Re: [rtcweb] Conclusion statement for Recommended… Xavier Marjou
- Re: [rtcweb] Conclusion statement for Recommended… Roman Shpount
- Re: [rtcweb] Conclusion statement for Recommended… Matthew Kaufman (SKYPE)
- Re: [rtcweb] Conclusion statement for Recommended… Cullen Jennings (fluffy)
- Re: [rtcweb] Conclusion statement for Recommended… Ralph Giles
- Re: [rtcweb] Conclusion statement for Recommended… Roman Shpount
- Re: [rtcweb] Conclusion statement for Recommended… Harald Alvestrand