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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 22 December 2015 00:24 UTC

Return-Path: <keith.drage@alcatel-lucent.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 377C71ACEC8 for <rtcweb@ietfa.amsl.com>; Mon, 21 Dec 2015 16:24:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HtjgvxcG78V8 for <rtcweb@ietfa.amsl.com>; Mon, 21 Dec 2015 16:24:29 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B5561A6F84 for <rtcweb@ietf.org>; Mon, 21 Dec 2015 16:24:28 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 93E96A9C35A15; Tue, 22 Dec 2015 00:24:22 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id tBM0OQrE002337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Dec 2015 01:24:26 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.213]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 22 Dec 2015 01:24:26 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Roman Shpount <roman@telurix.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Working group last call for draft-ietf-rtcweb-audio
Thread-Index: AQHRPE3k0JZd2tvJAUGJKJJIm+7DEZ7WJQYA
Date: Tue, 22 Dec 2015 00:24:25 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8BADE271B9@FR712WXCHMBA11.zeu.alcatel-lucent.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> <CAD5OKxtxLqvXFSkUJeHSQk1Owh1mOJAPWUoogZaU_mJ1qnQtPQ@mail.gmail.com> <CAD5OKxstK1P+4SVGMUPfyd5GFRNnD2jZuttbXw3AQSncW18uyQ@mail.gmail.com>
In-Reply-To: <CAD5OKxstK1P+4SVGMUPfyd5GFRNnD2jZuttbXw3AQSncW18uyQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8BADE271B9FR712WXCHMBA11z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/y6geUEK2PO3kYzMfKuoprqLMjQc>
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: Tue, 22 Dec 2015 00:24:32 -0000

And the only way I can interpret this as a use case is where the ham radio remote point is also the webrtc endpoint. Is that what you are proposing?

Keith

From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Roman Shpount
Sent: 22 December 2015 00:16
To: rtcweb@ietf.org
Subject: Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio

Also, some might find interesting what ham radio receivers typically look like:

http://img3.ph.126.net/snBYUz0aHL9x7Fy2mh85MA==/1133499731230960393.jpg

and here is the microphone at higher resolution:

http://i.ebayimg.com/images/i/371238765810-0-1/s-l1000.jpg

As you can see it is designed to send A-D tones.
_____________
Roman Shpount

On Fri, Dec 18, 2015 at 8:12 PM, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:
On Fri, Dec 18, 2015 at 7:10 PM, Cullen Jennings (fluffy) <fluffy@cisco.com<mailto:fluffy@cisco.com>> wrote:

On Dec 18, 2015, at 3:24 PM, Roman Shpount <roman@telurix.com<mailto: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