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

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Wed, 04 September 2013 20:03 UTC

Return-Path: <mzanaty@cisco.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 7128521E80F5 for <rtcweb@ietfa.amsl.com>; Wed, 4 Sep 2013 13:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 RLOTSXk-v01P for <rtcweb@ietfa.amsl.com>; Wed, 4 Sep 2013 13:03:08 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6B85E21E80EE for <rtcweb@ietf.org>; Wed, 4 Sep 2013 13:03:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3584; q=dns/txt; s=iport; t=1378324988; x=1379534588; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=aoyN33N1Ma1AaVwwICoFWJKpIvcoHyPL0+Ly9H/GS8s=; b=Slp1Gy16Ld7MdiUWUjwSjl4XiFyZG4tMQnSrLCvx2/+aY0EWOcizr43b 65y0GncQNigEZgRE7cRcJrRz61UYZWI00O8E4G9KWoyBvSwZFMVYn2CEz nl90bo3aI6H4cpos6j7FOL3UExPVyl5nllzNm7arEsnmEjW617uKptX94 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoIFANeQJ1KtJV2d/2dsb2JhbABagwc1SwbBRIEoFnSCJAEBAQQBAQE3NBcEAgEIEQQBAQsUCQcnCxQJCAIEARIIAYd5BwW6No4ngQgzBQaDF4EAA5QbhQmLC4UsgyCBcTk
X-IronPort-AV: E=Sophos;i="4.89,1023,1367971200"; d="scan'208";a="252640875"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 04 Sep 2013 20:03:08 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r84K373v006945 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Sep 2013 20:03:07 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.101]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Wed, 4 Sep 2013 15:03:07 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: 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: AQHOj52YNf0VLpHUzEKr6spLBSmfVZmnooUwgA6MUZA=
Date: Wed, 04 Sep 2013 20:03:06 +0000
Message-ID: <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com> <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se>
In-Reply-To: <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.150.29.130]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 04 Sep 2013 20:03:13 -0000

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