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

Matthew Kaufman <matthew@matthew.at> Sat, 19 December 2015 14:12 UTC

Return-Path: <matthew@matthew.at>
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 1A9971A89F9 for <rtcweb@ietfa.amsl.com>; Sat, 19 Dec 2015 06:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 KGZqgm_4yiJb for <rtcweb@ietfa.amsl.com>; Sat, 19 Dec 2015 06:12:19 -0800 (PST)
Received: from mail.eeph.com (mail.eeph.com [192.135.198.155]) by ietfa.amsl.com (Postfix) with ESMTP id DDCDF1A89F6 for <rtcweb@ietf.org>; Sat, 19 Dec 2015 06:12:19 -0800 (PST)
Received: from [172.20.15.234] (unknown [201.229.38.3]) (Authenticated sender: matthew@eeph.com) by mail.eeph.com (Postfix) with ESMTPSA id 91E75502755; Sat, 19 Dec 2015 06:12:19 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Matthew Kaufman <matthew@matthew.at>
X-Mailer: iPhone Mail (13C75)
In-Reply-To: <DD796B68-3AC4-4ADD-A150-E11AC3236466@gmail.com>
Date: Sat, 19 Dec 2015 10:12:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E00F6CA-B7F7-4D2E-BEA5-C9BEA392A48F@matthew.at>
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> <CAD5OKxtxLqvXFSkUJeHSQk1Owh1mOJAPWUoogZaU_mJ1qnQtPQ@mail.gmail.com> <DD796B68-3AC4-4ADD-A150-E11AC3236466@gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/htpsnsO9r2FC-0VeQdKy5lkNF1c>
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "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 14:12:21 -0000

Two-way radio system gateways would benefit from having these tones available.

Matthew Kaufman

(Sent from my iPhone)

> On Dec 19, 2015, at 7:43 AM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
>> On Dec 18, 2015, at 20:12, Roman Shpount <roman@telurix.com> wrote:
>> 
>> 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.
> 
> [BA] Bingo. To remove optional tones and discovery of tone capability, we either have to prohibit A-D or mandate that these tones be supported. 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb