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

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Fri, 06 September 2013 16:59 UTC

Return-Path: <andrew.hutton@siemens-enterprise.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 0747511E80E0 for <rtcweb@ietfa.amsl.com>; Fri, 6 Sep 2013 09:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level:
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599]
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 vKNWQ2QdXyeP for <rtcweb@ietfa.amsl.com>; Fri, 6 Sep 2013 09:59:18 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id BEC1B21E80C2 for <rtcweb@ietf.org>; Fri, 6 Sep 2013 09:59:11 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id CE0251EB8514; Fri, 6 Sep 2013 18:59:08 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Fri, 6 Sep 2013 18:59:08 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Lijing (Jessie, Huawei)" <lijing80@huawei.com>, "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: AQHOj52YNf0VLpHUzEKr6spLBSmfVZmnooUwgA6MUZCAAhrMgIAA2u1Q
Date: Fri, 06 Sep 2013 16:59:08 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BAEA15@MCHP04MSX.global-ad.net>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com> <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se> <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com> <A3045C90BB645147BC99159AA47ABAC741A0B7C1@szxeml558-mbs.china.huawei.com>
In-Reply-To: <A3045C90BB645147BC99159AA47ABAC741A0B7C1@szxeml558-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
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: Fri, 06 Sep 2013 16:59:24 -0000

There was a discussion on this back in January and I then I thought we had converged on the following text which made a lower case type recommendation:

"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"

See http://www.ietf.org/mail-archive/web/rtcweb/current/msg06121.html

Andy



> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Lijing (Jessie, Huawei)
> Sent: 06 September 2013 05:06
> To: Mo Zanaty (mzanaty); Bo Burman; rtcweb@ietf.org
> Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
> 
> +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
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb