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> Thu, 25 February 2016 20:58 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 9A7461B3536 for <rtcweb@ietfa.amsl.com>; Thu, 25 Feb 2016 12:58:33 -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 xN2ZpsQVC9z4 for <rtcweb@ietfa.amsl.com>; Thu, 25 Feb 2016 12:58: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 725551B3535 for <rtcweb@ietf.org>; Thu, 25 Feb 2016 12:58:31 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id g203so101750147iof.2 for <rtcweb@ietf.org>; Thu, 25 Feb 2016 12:58: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=2w8/m4peEGfE1dftwMAtHHOQKIyzA2U2KoKqnk9NWn8=; b=ImV8pfq9CSITsbFGvdgY2v6O2G1tSp7gOPNRTtzENRdQcx3+IVF4lFnBLWmoRLI0Ll 0lfMfg8klTzAarQZ0ZHcAxL3Uv50OWCN4IGHV48nifL+TEnrca3FAl6/LT7A2wavA518 j/Kf83XvHReWgI3nfrGYHnBup/hv5lHs1Cbs+NfvBfAo8Oz6+KPWne9QSbORq81WZ1MN B/CFNE+Mhavq+yF1cOzyJYRUdCCcrinesKh6H4ppLIfdQ5awZtR7tWi+mhlda+SQAbnO lpAA2zqX1gYsrMqMGxCGK4gt/Mt29J5bzGuR6C8zj/mzzjJlaoAG9ISstkZIrm/IXxUE VmVA==
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=2w8/m4peEGfE1dftwMAtHHOQKIyzA2U2KoKqnk9NWn8=; b=SuptuSVODCYppvLl0+CJphmegqJBmgwhI6k5EJOybs1KKY3KZaJk4kWmv0Yc+Lhh1t jOvW9bKveZqSV3eJnXaLkBErBE9iPY7dr0NHZxIWpX61sgLLB3161q83sBO2wlikvVA6 yIl82Dz5iXWelRTKbP/lPYwU/eAp+cMRR69Uf2z51ZLAR/W8ssg9pQwZdYEH9R8aBaIO 07nAnEb4ZWRzJFgpWS2p8IfVuaM8N7knrQJ5zRzJvOhUBAq7UDlE8NM6CAMLEqRDuJii Hl+qlm0si6wnbXl1hPjqI45Q3KbR3vafOxtOx6+zSSPiz3lCnjSMWG4m8w0J66U5+xf8 IdCA==
X-Gm-Message-State: AG10YOT2t2NDmgcCp8T0t1D41+U+4y084EnwZY16hbyuk/Ohf1Dk+kBqesZpyJ3IkK7zbw==
X-Received: by 10.107.128.21 with SMTP id b21mr5635672iod.143.1456433910800; Thu, 25 Feb 2016 12:58:30 -0800 (PST)
Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com. [209.85.213.180]) by smtp.gmail.com with ESMTPSA id o65sm3969487ioi.24.2016.02.25.12.58.29 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Feb 2016 12:58:29 -0800 (PST)
Received: by mail-ig0-f180.google.com with SMTP id y8so23702862igp.0 for <rtcweb@ietf.org>; Thu, 25 Feb 2016 12:58:29 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.159.7 with SMTP id wy7mr752483igb.24.1456433908805; Thu, 25 Feb 2016 12:58:28 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Thu, 25 Feb 2016 12:58:28 -0800 (PST)
In-Reply-To: <SN1PR0301MB15510A18734956A22BD5FB5AB2A60@SN1PR0301MB1551.namprd03.prod.outlook.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>
Date: Thu, 25 Feb 2016 15:58:28 -0500
X-Gmail-Original-Message-ID: <CAD5OKxu3HSKDNMNhEWHgoBrHj4zOvjwbGFQSyLmBgLo6cL2Lhg@mail.gmail.com>
Message-ID: <CAD5OKxu3HSKDNMNhEWHgoBrHj4zOvjwbGFQSyLmBgLo6cL2Lhg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "Asveren, Tolga" <tasveren@sonusnet.com>
Content-Type: multipart/alternative; boundary="001a1136a72ec5faa1052c9e719f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/chLIobmj0p6XH1IpN7qbn5qpZPI>
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: Thu, 25 Feb 2016 20:58:33 -0000

Tolga,

In the proposed text I have copied the requirements from
https://www.w3.org/TR/webrtc/#rtcdtmfsender to make sure specifications are
consistent with each other. Here is the text present in WebRTC TR:

The duration parameter indicates the duration in ms to use for each
character passed in the tones parameters. The duration cannot be more than
6000 ms or less than 40 ms. The default duration is 100 ms for each tone.

The interToneGap parameter indicates the gap between tones. It must be at
least 30 ms. The default value is 70 ms.


I believe the limits in WebRTC TR are based on ITU-T Q.24, which are, in
turn, based on physical limitation imposed by transmitting DTMF tones using
8Khz audio. It is physically impossible to design an inband DTMF detector
which can detect DTMF digits of duration less then 40 ms with gaps less
then 30 ms and still be capable of handling talk off. This requirement is
the MUST level to provide minimal support necessary for PSTN interop.

Regards,
_____________
Roman Shpount

On Thu, Feb 25, 2016 at 2:44 PM, Asveren, Tolga <tasveren@sonusnet.com>
wrote:

> Roman,
>
>
> What is the rationale of having this "MUST" strength mandate?
>
>
> Thanks,
>
> Tolga
>
>
> ------------------------------
> *From:* rtcweb <rtcweb-bounces@ietf.org> on behalf of Ted Hardie <
> ted.ietf@gmail.com>
> *Sent:* Thursday, February 25, 2016 1:07 PM
> *To:* rtcweb@ietf.org
> *Subject:* [rtcweb] Fwd: Last Call: <draft-ietf-rtcweb-audio-10.txt>
> (WebRTC Audio Codec and Processing Requirements) to Proposed Standard
>
> Mailman claims this was auto-discarded and it doesn't show in the
> archives, so I'm forwarding.  I will separately check on why it got chucked.
>
> regards,
>
> Ted
> ---------- Forwarded message ----------
> From: Jean-Marc Valin <jmvalin@jmvalin.ca>
> Date: Wed, Feb 24, 2016 at 2:21 PM
> Subject: Re: [rtcweb] Last Call: <draft-ietf-rtcweb-audio-10.txt> (WebRTC
> Audio Codec and Processing Requirements) to Proposed Standard
> To: Roman Shpount <roman@telurix.com>, rtcweb-chairs@ietf.org,
> alcoop@cisco.com, "rtcweb@ietf.org" <rtcweb@ietf.org>,
> draft-ietf-rtcweb-audio@ietf.org
>
>
> On 02/24/2016 04:42 PM, Roman Shpount wrote:
> > Generated events MUST have duration of no more than 6000 ms and no
> > less than 40 ms with the recommended default duration of 100 ms for each
> > tone. The gap between events MUST be no less then 30 ms with the
> > recommended default duration of 70 ms.
>
> OK, I missed that part, but I'm fine with it. Unless anyone objects, I
> can add it to the draft.
>
>         Jean-Marc
>
>
> > Regards,
> > _____________
> > Roman Shpount
> >
> > On Wed, Feb 24, 2016 at 4:31 PM, The IESG <iesg-secretary@ietf.org
> > <mailto:iesg-secretary@ietf.org>> wrote:
> >
> >
> >     The IESG has received a request from the Real-Time Communication in
> >     WEB-browsers WG (rtcweb) to consider the following document:
> >     - 'WebRTC Audio Codec and Processing Requirements'
> >       <draft-ietf-rtcweb-audio-10.txt> as Proposed Standard
> >
> >     The IESG plans to make a decision in the next few weeks, and solicits
> >     final comments on this action. Please send substantive comments to
> the
> >     ietf@ietf.org <mailto:ietf@ietf.org> mailing lists by 2016-03-09.
> >     Exceptionally, comments may be
> >     sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In either
> >     case, please retain the
> >     beginning of the Subject line to allow automated sorting.
> >
> >     Abstract
> >
> >
> >        This document outlines the audio codec and processing requirements
> >        for WebRTC endpoints.
> >
> >
> >
> >
> >     The file can be obtained via
> >     https://datatracker.ietf.org/doc/draft-ietf-rtcweb-audio/
> >
> >     IESG discussion can be tracked via
> >     https://datatracker.ietf.org/doc/draft-ietf-rtcweb-audio/ballot/
> >
> >
> >     No IPR declarations have been submitted directly on this I-D.
> >
> >
> >     _______________________________________________
> >     rtcweb mailing list
> >     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/rtcweb
> >
> >
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>