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

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Thu, 05 September 2013 14:41 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 1EF0211E80EC for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 07:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 LmnlYPCupGJb for <rtcweb@ietfa.amsl.com>; Thu, 5 Sep 2013 07:41:51 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id C360511E81B2 for <rtcweb@ietf.org>; Thu, 5 Sep 2013 07:41:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22856; q=dns/txt; s=iport; t=1378392109; x=1379601709; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9e47XMbheQ5yix/6IuPgMwwP/IlCEubf2Lo6LjR3i8E=; b=HN7AjGjb2eMlbdDSiWcM2yhDdmJT9xNRR5l29PjZSSyBre+ez6v3umUG 2TTd+pgMn9kNq/RNa3dzZ0p7Re1O/2eSddbDQPkaaFmDKdsvNnQXePtjC 8rKLPs6A9kuBmVLH2tuCGysV5BGDEWj7C2yRB70pqhVTDw6ih+6QReJN1 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmgFACSXKFKtJV2Y/2dsb2JhbABbgkNENUsGuQ2IPIEnFnSCJAEBAQQBAQEkBkELDAQCAQgOAwQBAQsdByEGCxQJCAIEAQ0FCAGHZwMPBwWxKw2IbIx0gTOBCC0EBgEGA4MUgQADlBuBcYMYiwgDhSyDIIFxOQ
X-IronPort-AV: E=Sophos; i="4.90,847,1371081600"; d="scan'208,217"; a="255976881"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 05 Sep 2013 14:41:48 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r85EfmJI027832 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Sep 2013 14:41:48 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.101]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Thu, 5 Sep 2013 09:41:48 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Leon Geyser <lgeyser@gmail.com>, Bo Burman <bo.burman@ericsson.com>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
Thread-Index: AQHOqkEXCTCNRbUxykmV6tr8IYwOK5m3NXTQ
Date: Thu, 05 Sep 2013 14:41:47 +0000
Message-ID: <3879D71E758A7E4AA99A35DD8D41D3D91D5265C8@xmb-rcd-x14.cisco.com>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com> <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se> <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com> <56C2F665D49E0341B9DF5938005ACDF80E8A65@DEMUMBX005.nsn-intra.net> <BBE9739C2C302046BD34B42713A1E2A22DF88232@ESESSMB105.ericsson.se> <CAGgHUiSK-bZrdXtxf-An8NM+pw-iqoWCrsG_bRUpxcD2DOCQrQ@mail.gmail.com>
In-Reply-To: <CAGgHUiSK-bZrdXtxf-An8NM+pw-iqoWCrsG_bRUpxcD2DOCQrQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.150.29.189]
Content-Type: multipart/alternative; boundary="_000_3879D71E758A7E4AA99A35DD8D41D3D91D5265C8xmbrcdx14ciscoc_"
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Thu, 05 Sep 2013 14:41:59 -0000

If you mean for the required codecs, that is already in the next sentence. Full context:

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.

WebRTC clients are REQUIRED to implement the following audio codecs.

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.

WebRTC clients are REQUIRED to implement the following audio codecs.


From: Leon Geyser [mailto:lgeyser@gmail.com]
Sent: Thursday, September 05, 2013 10:06 AM
To: Bo Burman
Cc: Rauschenbach, Uwe (NSN - DE/Munich); Mo Zanaty (mzanaty); rtcweb@ietf.org
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

It would be nice if a word like mandated/mandatory is present in the new text like it was in the old text. Maybe REQUIRED in uppercase?

On 5 September 2013 15:05, Bo Burman <bo.burman@ericsson.com<mailto:bo.burman@ericsson.com>> wrote:
I also support it.
/Bo

> -----Original Message-----
> From: Rauschenbach, Uwe (NSN - DE/Munich) [mailto:uwe.rauschenbach@nsn.com<mailto:uwe.rauschenbach@nsn.com>]
> Sent: den 5 september 2013 12:14
> To: ext Mo Zanaty (mzanaty); Bo Burman; rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> Subject: RE: I-D Action: draft-ietf-rtcweb-audio-02.txt
>
> I support this proposal.
>
> Kind regards,
> Uwe
>
>
> > -----Original Message-----
> > From: rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org> [mailto:rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>] On
> > Behalf Of ext Mo Zanaty (mzanaty)
> > Sent: Wednesday, September 04, 2013 10:03 PM
> > To: Bo Burman; rtcweb@ietf.org<mailto: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> [mailto: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<mailto: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> [mailto:i-d-announce-<mailto:i-d-announce->
> > bounces@ietf.org<mailto:bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> > > Sent: den 2 augusti 2013 18:30
> > > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> > > Cc: rtcweb@ietf.org<mailto: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<http://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<mailto: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<mailto:rtcweb@ietf.org>
> > https://www.ietf.org/mailman/listinfo/rtcweb
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> > https://www.ietf.org/mailman/listinfo/rtcweb
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb