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:50 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 0BC161A8901 for <rtcweb@ietfa.amsl.com>; Fri, 4 Mar 2016 11:50:32 -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 FNOyQ2m7uckj for <rtcweb@ietfa.amsl.com>; Fri, 4 Mar 2016 11:50:31 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 176971A88F3 for <rtcweb@ietf.org>; Fri, 4 Mar 2016 11:50:31 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id g203so73362479iof.2 for <rtcweb@ietf.org>; Fri, 04 Mar 2016 11:50:31 -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=Z6R+TA9JfZ2wnjfcEEubF3l1pMG254DAL/ro9u23aS4=; b=odaPWlAc+y9PAjbUnT+uZ3FlN01JvFv4WR218afK/oGV/b05HwQQ/TOAnZH1sMr8Pd 4UpG39OLXkG/cEwj0LANWaQMvp9IxZfILn9/xYCOmaL2xg7L6he6y04xh9vM1X+rg/h7 fUZNFihOa1mcpcPdtzx6ZyqeBICLkJlqxGsNqxmZc5RjU9ghjHGaazSA3h8Pjb2YL1QH kpHCPCF2umWWPFpd2hf18436dSsO87JPXR+gdviZwMSzSuRrQkUuPbaGm0uTdmDftrLA fT06TKXkC+rgHlm+YMzwI6fIfe5OofgySWVf6z0RgYe2NttCxtXHUdSJM+Eksu0Y1qbL UqYg==
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=Z6R+TA9JfZ2wnjfcEEubF3l1pMG254DAL/ro9u23aS4=; b=B32nRMe1jvNAmftxvXI3RUqS63W4GQO3LjhLehtdv39depuvkcps6Th/FIlLiki68P 1mJ1CDjnzjgc8PB3hrxJXFvx9pzVq8eeeRYG20MPj6CPNHrCOjTbLDMiup5hArpeZX5n kOHCKW1U/xrhWfXt4BSjm6cRurKd3mLtFetu+1QdXNyWY4OMDrTGK3UUo6DOM0BOD2ca rSnFLDlZzAsmhMbskoF5tCcXa6P5XuFNqn1fpuDTRzLLB0AXWbYKScxP6lg5WzKsKGFc gvIgI7PTVPmLY7JeY28R88cLr7ScdvoteS5QcKDSE9vySarrY9w9wWunViRhQIGGMqjk XQvw==
X-Gm-Message-State: AD7BkJIS16VCPWv6/drtnh/PXvjzjhxRtPkYfrZF1vu1RXmV4Frkb6/tSiZkDxM8Dgwh7A==
X-Received: by 10.107.41.148 with SMTP id p142mr11212351iop.182.1457121030519; Fri, 04 Mar 2016 11:50:30 -0800 (PST)
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com. [209.85.213.173]) by smtp.gmail.com with ESMTPSA id x3sm235660igl.11.2016.03.04.11.50.28 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2016 11:50:28 -0800 (PST)
Received: by mail-ig0-f173.google.com with SMTP id i18so3136791igh.1 for <rtcweb@ietf.org>; Fri, 04 Mar 2016 11:50:28 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.30.104 with SMTP id r8mr740408igh.2.1457121028187; Fri, 04 Mar 2016 11:50:28 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Fri, 4 Mar 2016 11:50:27 -0800 (PST)
In-Reply-To: <SN1PR0301MB155106EB460584246C3F83EDB2BE0@SN1PR0301MB1551.namprd03.prod.outlook.com>
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> <CAD5OKxuT4MnYNDn=DSrE4aY2nux4VhYDiZ7T_uRGMRds1Z3XKA@mail.gmail.com> <SN1PR0301MB155106EB460584246C3F83EDB2BE0@SN1PR0301MB1551.namprd03.prod.outlook.com>
Date: Fri, 04 Mar 2016 14:50:27 -0500
X-Gmail-Original-Message-ID: <CAD5OKxs6UACt96mUfkG4ovnQ_4UJRcAqXKd4BVDm3KgLaQ09kQ@mail.gmail.com>
Message-ID: <CAD5OKxs6UACt96mUfkG4ovnQ_4UJRcAqXKd4BVDm3KgLaQ09kQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "Asveren, Tolga" <tasveren@sonusnet.com>
Content-Type: multipart/alternative; boundary="047d7bdca2ec47b1df052d3e6df7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/nFm7VSwoOvnu_i0niz7wwtHPv0o>
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:50:32 -0000

On Fri, Mar 4, 2016 at 2:47 PM, Asveren, Tolga <tasveren@sonusnet.com>
wrote:

> That they stay only in WEBRTC TC would address my practical concerns. And
> *if* the main argument for the limits is making appellations less error
> prone, i.e. browsers enforcing limits,
>
W3C WEBRTC working group is not the right to group define the acceptable
limits for DTMF tone duration. They can determine that API needs to have a
valid parameter range but defining the range should be in IETF.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email