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, 26 February 2016 21:38 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 1B23B1B30EB for <rtcweb@ietfa.amsl.com>; Fri, 26 Feb 2016 13:38:30 -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 NjvgCE5OYRVH for <rtcweb@ietfa.amsl.com>; Fri, 26 Feb 2016 13:38:29 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (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 125D51B30EA for <rtcweb@ietf.org>; Fri, 26 Feb 2016 13:38:29 -0800 (PST)
Received: by mail-ig0-x22c.google.com with SMTP id g6so47806759igt.1 for <rtcweb@ietf.org>; Fri, 26 Feb 2016 13:38:29 -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=g/DpkP19AkbLyQyExs5LXr9BLdej1AnD+kdv/i3dkn0=; b=zFSmYTHBmvCDnnPTUsvnYdHP0M+ELRWakhtMd4z87hhnT1ejIBVweU9wWShb+tA52/ P/9N7vEreB5cz4otWCrEIr7CRNJeVGvfNI4dQKQywOzPf31IsN98skhFo+R31F+s4swd j6/aXCBrmfikBo/Eo8tPzh6OSigtk/ufqU/joih2BaCMqDHZSSNHaW0fFAjrnnMrILBK BMLX1XWA2ZinHwgaVtg7/1x+nZvMhc+d9gZ1tTigJAHVPyUCSBOD9V8Br0vnaukibgd0 Ef1oS1W/wSpgdEO0XPD9QhFeR8nzaLrgP+mELylKXizRaZpJN6rmcLO9+VBLmyQPahop G4kg==
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=g/DpkP19AkbLyQyExs5LXr9BLdej1AnD+kdv/i3dkn0=; b=HCSdeI0mvZyPUIR6fm34wxq6eXc67hWm2PmPsK1siZ4/aMW0lSSzubNs24/Vj2mECI gdhB2cVpIZ0mKR627606PM+uomqQR/kbsEMl/oXCvdGuDegr/hP27EJenovjZX725DGv BaiUdF4ZZ2f6xnImUS2nz/zM6juKKBkeEJeKQYmaA+G+RR3MjM/i4RoWCygsSOik3pon BSIciQn6WU3ewNxx3YT87AJEV1ySanetPEhFEtBeS5CAqjEoyEcbmkGK9H71pskC8UbU HLIqRdVjBzSARC+RsGVIil5NWGF33ID558osoAwdudTuQJnTPGoP/F/m+xAEt+pugEAk MwFA==
X-Gm-Message-State: AD7BkJJWJ1b1GIiV9JCHibpsKu/888RVP8xzrXDCeXWUG+1NCQG/aBJKx3ocid9pD5ylSg==
X-Received: by 10.50.64.178 with SMTP id p18mr80195igs.55.1456522708473; Fri, 26 Feb 2016 13:38:28 -0800 (PST)
Received: from mail-io0-f181.google.com (mail-io0-f181.google.com. [209.85.223.181]) by smtp.gmail.com with ESMTPSA id h131sm6128875ioe.7.2016.02.26.13.38.26 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Feb 2016 13:38:26 -0800 (PST)
Received: by mail-io0-f181.google.com with SMTP id l127so135226158iof.3 for <rtcweb@ietf.org>; Fri, 26 Feb 2016 13:38:26 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.12.226 with SMTP id 95mr10732173iom.70.1456522706365; Fri, 26 Feb 2016 13:38:26 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Fri, 26 Feb 2016 13:38:26 -0800 (PST)
In-Reply-To: <56D0097D.40308@mozilla.com>
References: <20160224213121.376.85278.idtracker@ietfa.amsl.com> <CAD5OKxsa9cwYOLqkHDVjoe2vr8NoOsPYO7jD_4TPNSnxU7u53Q@mail.gmail.com> <56CE2CF4.70001@jmvalin.ca> <CA+9kkMAqNZiHX7asFZnNgMnJw3G2bPBB7zXfLex3xdkfcW2tQQ@mail.gmail.com> <SN1PR0301MB15510A18734956A22BD5FB5AB2A60@SN1PR0301MB1551.namprd03.prod.outlook.com> <CAD5OKxu3HSKDNMNhEWHgoBrHj4zOvjwbGFQSyLmBgLo6cL2Lhg@mail.gmail.com> <56D0097D.40308@mozilla.com>
Date: Fri, 26 Feb 2016 16:38:26 -0500
X-Gmail-Original-Message-ID: <CAD5OKxvJ5w3gZAwMFQa80D1wgYk0i5DdL37031dnHmK78Xu=_Q@mail.gmail.com>
Message-ID: <CAD5OKxvJ5w3gZAwMFQa80D1wgYk0i5DdL37031dnHmK78Xu=_Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Jean-Marc Valin <jmvalin@mozilla.com>
Content-Type: multipart/alternative; boundary="001a113f8f8e8536e1052cb31e90"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/GeW6uuqneZ1vlo1bp2pd2CZTEMU>
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, 26 Feb 2016 21:38:30 -0000

On Fri, Feb 26, 2016 at 3:14 AM, Jean-Marc Valin <jmvalin@mozilla.com>
wrote:

> Just as a clarification, are we talking about the duration of RFC4733
> tone events or the duration of audio tones (or both)? I agree that
> going below 40 ms is just not possible. As for the upper bound, more
> than 6000 ms is definitely insane, but I have no precise opinion on
> the exact threshold that should be used, or why anyone would want such
> long tones in the first place.
>

I think Cullen put the 6000 ms max limit in the specification. RFC 2833
tones have a limit of maximum duration of 8191 ms before the duration
counter overflows when 8 KHz clock is used.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email