IETF Logo Mail Archive

Re: [rtcweb] Confirmation of DTMF issue

Ted Hardie <ted.ietf@gmail.com> Wed, 20 April 2016 16:03 UTC

Return-Path: <ted.ietf@gmail.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 25BB512E6D6 for <rtcweb@ietfa.amsl.com>; Wed, 20 Apr 2016 09:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aQHtl_rth4w0 for <rtcweb@ietfa.amsl.com>; Wed, 20 Apr 2016 09:03:22 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::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 C582212DAE1 for <rtcweb@ietf.org>; Wed, 20 Apr 2016 09:03:22 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id k142so44815800oib.1 for <rtcweb@ietf.org>; Wed, 20 Apr 2016 09:03:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tiAVY0X9c5O+CSWEkzMU93sd4TeEcJ2pWmEaLHLGJ+s=; b=pFvqK7SolVfrlqTJZT1najrEsWAwenGGLbcPMx9QPucXA15eIud0ElwJDxwf+QAM1K xDYzsuLoNgFcyzy6QyP0MFPA1yXP9arecYtkLKak8ySQTx329nRspm63FLPtzgHORXXb SUE2iXsJ5itVoE6DgFxwxEZz8KGqQNudxjNwqeI60las/AK62UNGOSIw2sKrUB7N4FAZ d03sselU+KS3E4gDslB6UChMaQYXYpRWxX66H2AV3OHckVvvvHgGQPNvSrCoodjfh2pS iU7RUIik+n9SI/CMMDIp0U1sYTdSIFuSEaLPiCtJ9LzZxpXGf5z554hRfG1Eaj1eOtMq b3BA==
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:from:date :message-id:subject:to; bh=tiAVY0X9c5O+CSWEkzMU93sd4TeEcJ2pWmEaLHLGJ+s=; b=LYe3CssbKWl7O86OqPd+/GjLnzp+i5/+7YTTR8YCFLdK2CStW1lYUukjw4dYMbxm/O TMGfUFKoYSAl2+vjmUuor11/4gNacv1QqRd97HM8/jXg0B9L0Jgfc9ym3SpTx+65cJwF 4M//oGKbvWkVeiDCzi/l1J48ywlOm8+ZqwArgPYAHIbKhJoTVLr2T0j4UM8UkZ/ItH7i uEZrvphrHpalInd0aMlzRCHuMOu5V2LPy67BGJacKgkyiwWiK4xOYuEtj4CyEQxFQgNr 3QaKmp13DyW8p8aCTAZu2d+QT7H/ovgHSnOVHWBLnxX7vPo/qBMqE0bBKv1P7JqqrYOh vZTQ==
X-Gm-Message-State: AOPr4FUqdQtD+j/ZLfXGdiAXJGtnOo/JtJTBDpHWRrqVs08jv1npTp3WV5Lkl95VJ8H/2bUpY6weq04QYxOV2g==
X-Received: by 10.202.80.205 with SMTP id e196mr4183604oib.126.1461168202187; Wed, 20 Apr 2016 09:03:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.22.156 with HTTP; Wed, 20 Apr 2016 09:03:02 -0700 (PDT)
In-Reply-To: <CA+9kkMA7uuSiyUARxZou9KDZ7sEg+RphHZjEK1SLWS-ptMKLKA@mail.gmail.com>
References: <CA+9kkMA7uuSiyUARxZou9KDZ7sEg+RphHZjEK1SLWS-ptMKLKA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 20 Apr 2016 09:03:02 -0700
Message-ID: <CA+9kkMCOT2To+uHtNbhcuJabq2ZZo7f6UGcddMgZSGVKxRJQDQ@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, Cullen Jennings <fluffy@cisco.com>, Sean Turner <sean@sn3rd.com>
Content-Type: multipart/alternative; boundary="001a113d7a8ca60be80530ecbbfb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/AJRwSjdp4JMlHtlkaPFBHsK05Sw>
Subject: Re: [rtcweb] Confirmation of DTMF issue
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, 20 Apr 2016 16:03:24 -0000

Having seen confirmation of this approach and no new issues, we will move
forward with this language.
Thanks to everyone working on the issue,

Ted, Cullen, Sean

On Wed, Apr 13, 2016 at 1:31 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> With Martin's friendly amendments, the room at IETF 95 agreed to the
> follow as the resolution of the DTMF discussion.  The chairs would like
> anyone who has new issues with this to let us know as soon as possible and
> no later than Wednesday, April 20th, noon UTC,
>
>
> "DTMF events generated by a WebRTC endpoint MUST have a duration of no
> more than 8000 ms and no less than 40 ms.  The recommended default duration
> is 100 ms for each tone. The gap between events MUST be no less than 30 ms;
>  the recommended default gap duration is 70 ms.
>
> WebRTC endpoints are not required to do anything with RFC 4733 tones sent
> to them, except gracefully drop them. There is currently no API to inform
> JavaScript about the received DTMF or other RFC 4733 tones."
>
> regards,
>
> Ted, Cullen, and Sean
>

v2.23.0 | Report a Bug | By Email