Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

"Lijing (Jessie, Huawei)" <lijing80@huawei.com> Fri, 06 September 2013 04:06 UTC

Return-Path: <lijing80@huawei.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 2FCAC11E8256 for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 21:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 8p8b+3-a3+7E for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 21:06:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 929CB11E824C for <rtcweb@ietf.org>; Thu, 5 Sep 2013 21:06:02 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVC33291; Fri, 06 Sep 2013 04:05:59 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 6 Sep 2013 05:05:37 +0100
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 6 Sep 2013 05:05:57 +0100
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.175]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0323.007; Fri, 6 Sep 2013 12:05:53 +0800
From: "Lijing (Jessie, Huawei)" <lijing80@huawei.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, Bo Burman <bo.burman@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: I-D Action: draft-ietf-rtcweb-audio-02.txt
Thread-Index: AQHOj52YNf0VLpHUzEKr6spLBSmfVZmnooUwgA6MUZCAAhrMgA==
Date: Fri, 06 Sep 2013 04:05:52 +0000
Message-ID: <A3045C90BB645147BC99159AA47ABAC741A0B7C1@szxeml558-mbs.china.huawei.com>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com> <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se> <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com>
In-Reply-To: <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.171.171]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
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: Fri, 06 Sep 2013 04:06:10 -0000

+1

I also support this proposal.

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Mo Zanaty (mzanaty)
Sent: Thursday, September 05, 2013 4:03 AM
To: Bo Burman; rtcweb@ietf.org
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

I support the proposed text addition. But rather than adding at the end of section 3, replace the beginning of section 3 as below.

OLD:
   To ensure a baseline level of interoperability between WebRTC
   clients, a minimum set of required codecs are specified below.
   While this section specifies the codecs that will be mandated for all
   WebRTC client implementations, it leaves the question of supporting
   additional codecs to the will of the implementer.

NEW:
   To ensure a baseline level of interoperability between WebRTC
   clients, a minimum set of required codecs are specified below.
   If other suitable audio codecs are available to the browser to use, 
   it is RECOMMENDED that they are also included in the offer in order 
   to maximize the possibility to establish the session without the need 
   for audio transcoding.

Mo

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Bo Burman
Sent: Tuesday, August 27, 2013 10:53 AM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

Based on the previous discussion thread http://www.ietf.org/mail-archive/web/rtcweb/current/msg08501.html, I believe there is support to add some text into this document.

I thus propose to add the following text at the end of section 3:

If other suitable audio codecs are available to the browser to use, 
it is RECOMMENDED that they are also included in the offer in order 
to maximize the possibility to establish the session without the need 
for audio transcoding

Cheers,
Bo

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: den 2 augusti 2013 18:30
> To: i-d-announce@ietf.org
> Cc: rtcweb@ietf.org
> Subject: I-D Action: draft-ietf-rtcweb-audio-02.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
> 
> 	Title           : WebRTC Audio Codec and Processing Requirements
> 	Author(s)       : Jean-Marc Valin
>                           Cary Bran
> 	Filename        : draft-ietf-rtcweb-audio-02.txt
> 	Pages           : 6
> 	Date            : 2013-08-02
> 
> Abstract:
>    This document outlines the audio codec and processing requirements
>    for WebRTC client application and endpoint devices.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-audio
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-audio-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-audio-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are
> available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
_______________________________________________
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