IETF Logo Mail Archive

[rtcweb] Confirmation of DTMF issue

Ted Hardie <ted.ietf@gmail.com> Wed, 13 April 2016 20:32 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 A1E6512E4BF for <rtcweb@ietfa.amsl.com>; Wed, 13 Apr 2016 13:32:03 -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 Bp7kRF4k2H0m for <rtcweb@ietfa.amsl.com>; Wed, 13 Apr 2016 13:32:02 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (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 1BBB312E4BD for <rtcweb@ietf.org>; Wed, 13 Apr 2016 13:32:02 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id t129so85483974vkg.2 for <rtcweb@ietf.org>; Wed, 13 Apr 2016 13:32:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=OgfH2bUrGu6UYKTBTQvUMidaNtD8qEQcRQrpqrLLoXg=; b=SNhwbHI9//6db3l1J3e2PI9FnQqu5VhisOR0UinNQHbMWgVh2nFaRaPGLeVRocjD6o SYufwX5T7Si2OyNCZprDv/fR1PsIV+3iKSW3+O8kkjVr9U8zYlR/zPCbXILBN6uDlkkp +RyLkNCZigUqgR+ZIq5z0ewKyYAjK4dpDp7lybZltgTnxTKatY4r/fYiEjZNsDpSm+Q0 tEHtIqUuiDcpyn79Z60e84qdQp6KsbsKMj/P0oGRWj0KClHr4BHvBvKHnKv6+dPw/2OP Kta1Kb2ifZ68phxumYVnko6+8IT2qxA4LwvbgbGx1CcBP/pwLkzhzWxAeIFKZmGKoCJW gujQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OgfH2bUrGu6UYKTBTQvUMidaNtD8qEQcRQrpqrLLoXg=; b=cRYi1D5bECfjy9q74iE7c8GNVTXCDFiiLeiRtaiRAlQbphInqEtYLYHZztjctEZCJ3 TOXbAF/3VTARUJr2bSUKnt07dMsFKRiJxGaYFeMpOQRa+4Ry9D+SzXbvdasnhLZUC7+7 7R9XT9lmS7RaqAtPRxwNvn/bNZxKcSiKj+Va/YB0N8J+a54J0j3ePt34ZQ+YIaNxCSOn a3XYhFxnpgNFVOoOM4ubOgGsed5UdG13E7ARN/n0wa0Z57JIJI7ZOxPghx1p+649b/Ej 2WuTkPNlvlHoJFii+YE2jNfC3qEsvdOw9EoaXaT8ZNdAbAsB/i/puroe6G8MOep1w2Xa WV3A==
X-Gm-Message-State: AOPr4FUCepsQgNgLgT+ggc8r0q7rheR4/AgC/ey2aoAlnEyITXEvggdwWBTVz4GzPU4yks7lcuM0J52mxSaytw==
X-Received: by 10.159.38.49 with SMTP id 46mr5198972uag.139.1460579521200; Wed, 13 Apr 2016 13:32:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.35.111 with HTTP; Wed, 13 Apr 2016 13:31:41 -0700 (PDT)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 13 Apr 2016 13:31:41 -0700
Message-ID: <CA+9kkMA7uuSiyUARxZou9KDZ7sEg+RphHZjEK1SLWS-ptMKLKA@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="001a113e3966870a6c053063abee"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/yxt6-tgJhl0PMw3WoRX9SWoXHNc>
Subject: [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, 13 Apr 2016 20:32:03 -0000

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