IETF Logo Mail Archive

Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio

Roman Shpount <roman@telurix.com> Sat, 19 December 2015 01:12 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 707161A024E for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 17:12:25 -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 pe7xohnbeivF for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 17:12:24 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 F358C1A0250 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 17:12:23 -0800 (PST)
Received: by mail-ig0-x22b.google.com with SMTP id m11so3264892igk.1 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 17:12:23 -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:content-type; bh=7s/pW/T02qBoRkoIvmolk3HZsQk5TBl3Pj54fkYVf+E=; b=Ru8wN4qVSb/BSGWIF4I7hVrxqBU/AVIZxnvpI0s7PJkR2ons7F9r4oy1Z4bHWb0Iqj ul+lcNeG+HzWoTfRkWPdYaYkLJWwUpvb4HEOuvgIGAYJEqRcB7HOm6IkEhpb1JTHoDdO kWZJc1rxFB5rjArur3qgJQuhh9WhYR30dZC3MFABL6KC3D8bwFzGVZo5263p3djjZo2F +AbIii/vbBTRcwpkso/DSs9OLqNJ1TbbRMNb7PEAez8HdypeivbJHn+lVgg9QFPaDVkQ RaPaNfYiEa1HffI/U0hlohAT2Mo4h/ooEabfNWeiUWEzgT1a1EMxN+WQc0vRlvUuleUx NgaQ==
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:content-type; bh=7s/pW/T02qBoRkoIvmolk3HZsQk5TBl3Pj54fkYVf+E=; b=V3zmhNh325Qs6s4fcA0p9W/lAY7hvNMeqIheUMP841aJ7dHXwPPf6hTtQfdKfvXgpp 7HNuQv1xkPwb0F8T/ZICusc8oNrWW6A4BIt6zQ1cNHsARO7VGDgLOr658iWs8x1nTitP X9mtbyM1FdXugtfEtnHM/jZ3Q7dFPSoZGRFCekOkesKemWR7VIGlGYxhZomZsV2WHTRZ qbQHJbvPem3h+vfYzIYwYpu5uQmsjqke/8Iu2VV2Ss3mADUyZk/ZaVgi+GOwx2tYOFYp 9REAhP7l0yQEQ774eXXefXHR/9j5IMELhJF01pdNhebTyBIqmzohZ4gcfxbA+SfwNdZP Qpww==
X-Gm-Message-State: ALoCoQmOTKYmU3JbcYCgBbjQIa4fGZtXXN9NmJDNeV5+8E6n7WSO0sDZHctsW9nThQ6ZhOjFqDtiOKA3WYoiMtXAbcMQ3Wi99w==
X-Received: by 10.50.73.199 with SMTP id n7mr6218854igv.1.1450487543434; Fri, 18 Dec 2015 17:12:23 -0800 (PST)
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com. [209.85.213.171]) by smtp.gmail.com with ESMTPSA id n14sm3652797igx.17.2015.12.18.17.12.21 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 17:12:22 -0800 (PST)
Received: by mail-ig0-f171.google.com with SMTP id jw2so3522874igc.1 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 17:12:21 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.126.35 with SMTP id mv3mr6615169igb.24.1450487541564; Fri, 18 Dec 2015 17:12:21 -0800 (PST)
Received: by 10.36.105.15 with HTTP; Fri, 18 Dec 2015 17:12:21 -0800 (PST)
In-Reply-To: <F9264ABC-E856-44B4-9E7E-8359B5D39A55@cisco.com>
References: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com> <CAD5OKxtvhaqx=H10=fUiGAjvnGAb_g89p2TZT9iNEg2F9k+6FA@mail.gmail.com> <CA+9kkMApyK4YPaWbQATy9zGfCOd3Dyfr8cY2amODgFE4XQCA=A@mail.gmail.com> <CAD5OKxtDGUv3akJTe6ZRYNhQN=SMY_R+GeV_Kg67Y6EYq+aV=A@mail.gmail.com> <CA+9kkMCvAcxnc=QdGvTm3=VNOQ3TtO+d8PfbfVA8sLeEA6rRqg@mail.gmail.com> <CAD5OKxtu-dsahdwL7t7Br34V-guqKmsdTsztOK_8sSsvWYsF=g@mail.gmail.com> <CA+9kkMBxbmGggCUaBPVtsJ7o3ZvBS=xvDKkmvfJxdVbM8NgiEQ@mail.gmail.com> <CAD5OKxvaJTRtfDQLwpvi+etdh8ZQvP5eRROSvRY2Hg-Uasisww@mail.gmail.com> <F9264ABC-E856-44B4-9E7E-8359B5D39A55@cisco.com>
Date: Fri, 18 Dec 2015 20:12:21 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtxLqvXFSkUJeHSQk1Owh1mOJAPWUoogZaU_mJ1qnQtPQ@mail.gmail.com>
Message-ID: <CAD5OKxtxLqvXFSkUJeHSQk1Owh1mOJAPWUoogZaU_mJ1qnQtPQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="047d7b1635d5aa9542052735f2d2"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/yz_yKDnv4DvAh_BoASLX-HGCGwk>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio
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: Sat, 19 Dec 2015 01:12:25 -0000

On Fri, Dec 18, 2015 at 7:10 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>
wrote:

>
> On Dec 18, 2015, at 3:24 PM, Roman Shpount <roman@telurix.com> wrote:
>
> This applies to all DTMF tones, not A-D specifically. What I am saying is
> that WebRTC endpoints must be able to generate all DTMF tones including A-D
> and send them to legacy PSTN (gateway).
>
>
> The thing people keep asking is why? what is the use case ?
>
> I don’t feel like I have seen an answer to this.
>
>
Because there are IVR systems that use them. They are much less common then
IVR systems that use 0-9 * and # but they do exist. I have provided 4
examples of real IVR systems that use these tones. How many do you need to
keep the extra tones? All these systems can probably be re-engineered not
to use A-D tones, but since this is all legacy no one will spend the time.

Your argument that these tones should be removed since they are sometimes
blocked (When exactly? The only places I see them blocked are some
international carriers) and would not work. The same applies to all DTMF
tones. We should remove all telephone-events based on this logic.

Most importantly I do not want optional tones. So, if we decide to remove
A-D, they should not be allowed in the WebRTC API. If these tones are
allowed in WebRTC API, everyone must implement them.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email