Re: [rtcweb] DTMF resolution proposal

Jean-Marc Valin <jmvalin@mozilla.com> Wed, 09 March 2016 01:29 UTC

Return-Path: <jmvalin@mozilla.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 997B712DD2D for <rtcweb@ietfa.amsl.com>; Tue, 8 Mar 2016 17:29:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mozilla-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpPJOqXgw3E8 for <rtcweb@ietfa.amsl.com>; Tue, 8 Mar 2016 17:29:19 -0800 (PST)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 7B4BC12DD2E for <rtcweb@ietf.org>; Tue, 8 Mar 2016 17:29:19 -0800 (PST)
Received: by mail-pf0-x22a.google.com with SMTP id 129so26153173pfw.1 for <rtcweb@ietf.org>; Tue, 08 Mar 2016 17:29:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=C8dExjVDeHmCXbvBDLBFhNufPPs1yOVqraFtG+Dw6rA=; b=S2Bf2/ERiQLO035b2BWSvGKmxXfZXPikqYRMQHd+sY8ek/v9fsc/52a2NKNINIp6ps /6s1kxKMCZb1l9JzGtg/e3HNNFVCGZsBUvq9FFWHcJc73/ZsQIE75w8L5Nsg8hgPg7Bc szv7wQb/i1Y/3IZ/xhnt+Js9RwzSSGTBlox2MaXqAWJj51PaDfEiGcplGCvZtYLlxlTi l7Wg8cKFmQGPCQZYKLIpVhiWAE2SB3+hPAPKPY6sY/K6i7vLShQWykZrPYEQb31EbAYH 7frFbnfmPYPTouWCuYglhqSMLnfcwIrI5lVQ2V0HCLR+RXZ1sbIGfREoYB/EpzDBJGKu F/XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=C8dExjVDeHmCXbvBDLBFhNufPPs1yOVqraFtG+Dw6rA=; b=mQ+VKO74XCeyLout/S4wOvMKPZbL0R46evgvsXuQx5xJk1U6X4PUQCwX5EUj2suYfP CGhw0cSJltWZDwot8ehGP2LXUsgDL8wi1GWXCxmnehAf0cn577DZM+raE8VinukU9wE9 XgGg17uyvu1vSIqo5XeoXA42s66d8XxyPm6DQHD7oz5Tc5aXece1ptSPE9hv5mUig+Yg yo+nIEydd8b93mwnqpxKlVHMU1LV+h9vZejcHMrwAjtQL52JzzSleREsaJUDCZifOmfA yZRniMnALEP0v6sZBIokOc0syIueexXc7y9DEYc2ZetVGQuBTw0BFbWKfM9eq3JLcxOb RK9Q==
X-Gm-Message-State: AD7BkJL/3vOPj/G963k1dsHRtmIjy20afdAalHh0MzXJE/WLQVDaPqFx1SdvZ103rYxdSoLi
X-Received: by 10.98.86.77 with SMTP id k74mr29617059pfb.28.1457486958923; Tue, 08 Mar 2016 17:29:18 -0800 (PST)
Received: from panoramix.jmvalin.ca ([2620:101:80fc:224:7e7a:91ff:fe20:963f]) by smtp.gmail.com with ESMTPSA id b79sm7677743pfj.25.2016.03.08.17.29.17 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Mar 2016 17:29:17 -0800 (PST)
To: Roman Shpount <roman@telurix.com>, "Asveren, Tolga" <tasveren@sonusnet.com>
References: <CA+9kkMANw8uPLObeGt68Rz+usObeDjQDYp-eQjp=WiCnWPByaQ@mail.gmail.com> <56DDF13F.1050505@mozilla.com> <CA+9kkMA3S2rgts+HRHqoDjzySzfq7w-mi4Ge8e_1b9wD=bEs8g@mail.gmail.com> <SN1PR0301MB15514F08779F54B3CD74BA34B2B20@SN1PR0301MB1551.namprd03.prod.outlook.com> <CAD5OKxsJpvGi3rp-AhCibei8vxvJ77cLf_z1b7GuJDzO2mq-Nw@mail.gmail.com>
From: Jean-Marc Valin <jmvalin@mozilla.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56DF7C6B.4050400@mozilla.com>
Date: Tue, 08 Mar 2016 20:29:15 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxsJpvGi3rp-AhCibei8vxvJ77cLf_z1b7GuJDzO2mq-Nw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/tkl4BS3agcrfGh7KGDNVclbPFWs>
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTMF resolution proposal
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 09 Mar 2016 01:29:23 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I'm not going to make a big deal out of this, but it feels to me like
the default duration should be in the W3C doc rather than in the IETF
doc since it describes browser behaviour rather than something can can
be observed on the wire. Of course, it doesn't hurt either, so I won't
object if people disagree with me.

Cheers,

	Jean-Marc

On 03/08/2016 07:57 PM, Roman Shpount wrote:
> Unless someone objects, I think the language would be:
> 
> WebRTC endpoints generated events MUST have duration of no more
> than 8000 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.
> 
> WebRTC endpoints limits this language to browsers and removes this 
> requirements from the gateways.
> 
> I do not think we should add any language about retransmission of
> the final packets since this will cause another unnecessary debate
> (for instance I think the value of 20 ms is wrong and it should be
> much shorter). If you want to change this please write an update
> draft for RFC 4733 and we can discuss it there.
> 
> Regards, _____________ Roman Shpount
> 
> On Tue, Mar 8, 2016 at 2:24 AM, Asveren, Tolga
> <tasveren@sonusnet.com <mailto:tasveren@sonusnet.com>> wrote:
> 
> Would the text be crafted so that it pertains **only** to the 
> RFC4733 digit packets emitted by a browser? ____
> 
> __ __
> 
> Information about gap between retransmission of the final packet 
> could be useful as well and I suggest 20ms for that one.____
> 
> __ __
> 
> Thanks,____
> 
> Tolga____
> 
> __ __
> 
> *From:*rtcweb [mailto:rtcweb-bounces@ietf.org 
> <mailto:rtcweb-bounces@ietf.org>] *On Behalf Of *Ted Hardie *Sent:*
> Monday, March 07, 2016 5:19 PM *To:* Jean-Marc Valin
> <jmvalin@mozilla.com <mailto:jmvalin@mozilla.com>> *Cc:* Cullen
> Jennings <fluffy@cisco.com <mailto:fluffy@cisco.com>>; 
> rtcweb@ietf.org <mailto:rtcweb@ietf.org> *Subject:* Re: [rtcweb]
> DTMF resolution proposal____
> 
> __ __
> 
> On Mon, Mar 7, 2016 at 1:23 PM, Jean-Marc Valin
> <jmvalin@mozilla.com <mailto:jmvalin@mozilla.com>> wrote:____
> 
> As proposed by Roman, I think we should also include the "minimum
> gap of 30 ms". Otherwise, I support the proposal.____
> 
>> __ __
> 
>> Thank you Jean-Marc; I had not thought to include that in my
>> note, but I agree.____
> 
>> regards,____
> 
>> Ted____
> 
> 
>> ____
> 
> Jean-Marc____
> 
> 
> On 03/07/2016 03:35 PM, Ted Hardie wrote:
>> We've had about 60 or so messages on this topic, and the rough 
>> consensus seems to be align this document with the limits set
>> out in the W3C work here:
> 
>> https://www.w3.org/TR/webrtc/#rtcdtmfsender
> 
>> However, there was also a proposal to slightly modify those
> limits.
>> They are currently:
> 
>> "The duration cannot be more than 6000 ms or less than 40 ms.
>> The default duration is 100 ms for each tone."
> 
>> Based on Roman's note, a minimum of 40ms and a maximum 8000 ms
>> to align with the ITU and RFC2833.
> 
>> To resolve this, I propose that we ask the WebRTC group to raise 
>> their max to 8000 and, on receiving a positive response, publish 
>> this document with 40/8000 as the min and max.  If they give a 
>> negative response, we retain 40/6000.  This values alignment 
>> between the two documents higher than the reference 2833, but
>> that seems sensible in this context.
> 
>> If you have an objection to this way forward, please send your 
>> reasoning to the list by March 14th.
> 
>> thanks,
> 
>> Ted
> 
> 
>> ____
> 
>> _______________________________________________ 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
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJW33xoAAoJEJ6/8sItn9q9agEIAIDvDjcyiWb1jrDPRiPmY2z0
uOtzfmdg7FurvbEM4uIn5S30DrbB1i5ncl2xTmM24/jIHKAVtr/pXbMt5jH5a/F8
XMQs5zkgK7w1tP/EykJ3f2ti5pWc18Lia8rYMzKdm0GEwcUQMemUCZ+7WrqT0N3p
BHYPZY8B4qR/7TK+AquxcWUUZsQdPi3LaGcJwJF9+KwRKuXAQcEphUVs2SnF48+F
IMFlhRyT097gaz5lOFS36AeyS8SO1So8W1Y2hwGMIjmuHJAMJm4vN4E8JO4R49MF
gsvqeYimx8YZtxJww02aBN/gauUwdecol5N6xXk3haWTgdgvBJjfWzRIOsSluVo=
=WJ2n
-----END PGP SIGNATURE-----