IETF Logo Mail Archive

Re: [rtcweb] Fwd: Last Call: <draft-ietf-rtcweb-audio-10.txt> (WebRTC Audio Codec and Processing Requirements) to Proposed Standard

Roman Shpount <roman@telurix.com> Fri, 04 March 2016 19:39 UTC

Return-Path: <roman@telurix.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D44A71A8898 for <rtcweb@ietfa.amsl.com>; Fri, 4 Mar 2016 11:39:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ng80Cqi4SF7L for <rtcweb@ietfa.amsl.com>; Fri, 4 Mar 2016 11:39:07 -0800 (PST)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2DC51A8896 for <rtcweb@ietf.org>; Fri, 4 Mar 2016 11:39:06 -0800 (PST)
Received: by mail-ig0-x230.google.com with SMTP id i18so2923299igh.1 for <rtcweb@ietf.org>; Fri, 04 Mar 2016 11:39:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=30fBBinhrpA+J4FAAnvV9IWuyOTjP7iaVQskAde3+Vs=; b=2TSZpCG0vUSK905fLkIa1j4mxn0EMuRAgV4482pRq3T2fJPecXs/RcWQGBxN1wDaXz eMxlDKQ0rTGvMBpmQHMNkDsNMYevu8ormRtqPaB2MIH3hucAuc5BLNcyyZGowABHmMVX uXclu3VbgAiwghv7EO41iN+/ieh0UFPdrjyGSUlNrq2qjofzv0WHtUasXVTh/Mz2ov1R /bCxwtuTOmiDtD9cJuraV5Ai72nrCBIYdwuWSoYestFJ/TS5zXcIQGNVjeZHuPdrwAym NWMYpyERbffu99u0MIV34g6KW3Ubv1ccYS9XFqkDZt9oCzdmqR6wR5os2yIyrmR7Aryg N4LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=30fBBinhrpA+J4FAAnvV9IWuyOTjP7iaVQskAde3+Vs=; b=a/CGmO1UUn4RoLSUqNqaY98hCa0rpeINHQStvkDosi/bkYM4HBVwKYQQtu0eS6tl25 vN0QLpx0PdM/Q+Xe4vczSqwHcFICi735Z0z5L6eGnJA8IN/5XvyajGmgDXw+YAGhEuvY wDNEOO2m2LkgFK+EvEqcA/gAyBtrmb2+dZQgA/YVciLgOdQzLJ2dIsIKUduPXiPQJW1o dzyDrzYysPsbZAKo/ePktm9HtZcDBzqA7vltkIyBX1yZCfdZOTFP+S6xsOCiRJll0Je0 75k9ajHys593xHEOu+SdCCzkoq8MCGhNIchMvFNUqS1TavASOXberlcTu8TiOanFoZ/k UYZQ==
X-Gm-Message-State: AD7BkJLgDkGOW5Gxj1yx7uEtd7BfDziMSfK6mTuGS8aqm6fLO1AumlB66kTUK6IAN7a/mA==
X-Received: by 10.50.138.72 with SMTP id qo8mr602307igb.81.1457120346285; Fri, 04 Mar 2016 11:39:06 -0800 (PST)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id me7sm216425igb.12.2016.03.04.11.39.04 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2016 11:39:04 -0800 (PST)
Received: by mail-io0-f172.google.com with SMTP id g203so73049059iof.2 for <rtcweb@ietf.org>; Fri, 04 Mar 2016 11:39:04 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.30.71 with SMTP id e68mr8785563ioe.145.1457120343890; Fri, 04 Mar 2016 11:39:03 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Fri, 4 Mar 2016 11:39:03 -0800 (PST)
In-Reply-To: <56D9678C.5050405@alvestrand.no>
References: <20160224213121.376.85278.idtracker@ietfa.amsl.com> <SN1PR0301MB15512FBBCA5186B4829FEFA8B2BB0@SN1PR0301MB1551.namprd03.prod.outlook.com> <1447FA0C20ED5147A1AA0EF02890A64B374B9596@ESESSMB209.ericsson.se> <SN1PR0301MB1551D1333297368D66B150ACB2BB0@SN1PR0301MB1551.namprd03.prod.outlook.com> <CAD5OKxvf+HBknqxXXY=_t9sCFGUFMUczu6k5DkMS-M8aV0Sjxw@mail.gmail.com> <SN1PR0301MB1551006A8D73179743E85322B2BB0@SN1PR0301MB1551.namprd03.prod.outlook.com> <CA+9kkMBGzjJFbLpo4te12tpaFFS_aoEXmoARudkq1EbZ5AnuYw@mail.gmail.com> <SN1PR0301MB1551CDEEA6EA1C7A696972B7B2BB0@SN1PR0301MB1551.namprd03.prod.outlook.com> <CA+9kkMA++uB6p0QYgWtgYtd9ysa9F5jb2wZnSm=Q-Fgig06_zg@mail.gmail.com> <SN1PR0301MB15514DE72ED6C92766D32E80B2BD0@SN1PR0301MB1551.namprd03.prod.outlook.com> <56D824BD.2080305@alvestrand.no> <CAD5OKxvVZuyHqWDZCcbOAYJTzKoFA4cm1DvvHoe8Zjm4LTRh3w@mail.gmail.com> <56D86A45.70406@alvestrand.no> <SN1PR0301MB15514E3DE966D04694948F16B2BE0@SN1PR0301MB1551.namprd03.prod.outlook.com> <56D9678C.5050405@alvestrand.no>
Date: Fri, 04 Mar 2016 14:39:03 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuT4MnYNDn=DSrE4aY2nux4VhYDiZ7T_uRGMRds1Z3XKA@mail.gmail.com>
Message-ID: <CAD5OKxuT4MnYNDn=DSrE4aY2nux4VhYDiZ7T_uRGMRds1Z3XKA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="001a1140d71e7e29ab052d3e445e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/CcJM7kJsSclJlJiMtZUnds1VHRI>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fwd: Last Call: <draft-ietf-rtcweb-audio-10.txt> (WebRTC Audio Codec and Processing Requirements) to Proposed Standard
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Mar 2016 19:39:08 -0000

On Fri, Mar 4, 2016 at 5:46 AM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> The hard limits are *not* in rtcweb-audio. They're in the WEBRTC WG
> (which is a WG of the W3C, not the IETF) API specification.
>

We are discussing adding tone and gap duration limits in rtcweb-audio. I
would argue that these limits should come from rtcweb-audio draft and
referenced in WEBRTC TR document. Not the other way around.

Do you disagree with this and do you think tone and gap duration limits
should only stay in WEBRTC TR?

Regards,
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email