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

Ted Hardie <ted.ietf@gmail.com> Fri, 18 December 2015 21:44 UTC

Return-Path: <ted.ietf@gmail.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 6C1DA1B393E for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 13:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] 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 PMMH9uvQW79U for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 13:44:19 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (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 074321B393D for <rtcweb@ietf.org>; Fri, 18 Dec 2015 13:44:19 -0800 (PST)
Received: by mail-qg0-x231.google.com with SMTP id v36so43481073qgd.2 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 13:44:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PiMWMZlj832CieM+28dtu0DmLrMR1fH2g2dI1HgBQSo=; b=CRTQ8f6Dhm7j1Re6VtsHph53VotoBP7t9KNVXceaZRmzWyXHNK62JzE70GLFmsWpb1 2h2v1ct6BGTu2DNMr+KRWP+kXNGl7Ct0FV+pZq/+0rq3H1abj6+i5zUTyLp4jvMVGm4/ 109x7iyUUFqn9aj2WkcP8f1HaZ6/1ubmnm9zyeshHXpILVEd61iBF9YYBGDqWwlhU4yc pCe94T6MyOMWkgyTyJ0zGVPC1uRpg6tayxmbW24IZbT9FFUMYkp3XgkPuHQV7da47lC9 ALb2Th9MzHq4WPqbkOPtX5vKE5P6lfZ0VKOn3eyc2WyF965VyQnx/aua8T0jj/zgzmJt aAnA==
MIME-Version: 1.0
X-Received: by 10.141.28.149 with SMTP id f143mr8762277qhe.66.1450475058160; Fri, 18 Dec 2015 13:44:18 -0800 (PST)
Received: by 10.55.14.211 with HTTP; Fri, 18 Dec 2015 13:44:18 -0800 (PST)
In-Reply-To: <CAD5OKxtDGUv3akJTe6ZRYNhQN=SMY_R+GeV_Kg67Y6EYq+aV=A@mail.gmail.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>
Date: Fri, 18 Dec 2015 13:44:18 -0800
Message-ID: <CA+9kkMCvAcxnc=QdGvTm3=VNOQ3TtO+d8PfbfVA8sLeEA6rRqg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary="001a11422e8e98e8fe0527330a9a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/QI_W9-BxcNFfdoDqlML5m4TB9f4>
Cc: Cullen Jennings <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: Fri, 18 Dec 2015 21:44:21 -0000

On Fri, Dec 18, 2015 at 1:10 PM, Roman Shpount <roman@telurix.com> wrote:

> On Fri, Dec 18, 2015 at 2:34 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> On Fri, Dec 18, 2015 at 10:32 AM, Roman Shpount <roman@telurix.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> Since the decision not to support A-D DTMF digits was never made on the
>>> IETF list (I have looked through the archive and cannot find it), I do not
>>> think they should be removed.
>>>
>>>
>> ​Can you say more about what use there would be in supporting them?
>>
>
> First of all, DTMF support is there for legacy support.
> ​  ​​​I generally dislike when features are removed from an established
> capability set without a good reason.
>

​We have stretched very far in many directions to be reasonable in our
support of WebRTC to legacy use cases, but ​I don't think we can argue that
WebRTC has an established capability set that includes these, nor has
anyone given flows where a legacy system would reasonably emit them toward
a WebRTC client.


>
> ​Can anyone name me a single commercial PSTN VoIP gateway which does not
> support A-D DTMF tones? I cannot think of one. I believe it would generally
> make sense to implement whole set defined in
> https://tools.ietf.org/html/rfc4733#section-3.2 instead of just 3/4. From
> what I know there is no extra implementation to support A-D DTMF tone. It
> looks like these tones are removed for aesthetic reasons only.
>

​No, the point Cullen made was that they were sufficiently hit-or-miss in
terms of system blocking that they were effectively unreliable *in the
contexts where WebRTC and legacy might interact*.​



> As far as more specific examples are concerned:
>
> DTMF tones A-D are used to provide a way to access hidden flows in IVR
> systems. For instance, when inbound call center is integrated with an
> external auto-dialer, auto-dialer places a call to call center IVR and uses
> a hidden flow accessible via one of those tones to connect directly to a
> waiting agent.
>
> ​Given that they likely would block the receipt of those tones from
external clients in order to avoid this access from outside, this seems
like one of the cases that Cullen alluded to; it is permitted only part of
the time and the access it provides is not standard.​



> DTMF tones A-D are also commonly used by ham radio operators to integrate
> with PSTN, such as http://www.echolink.org/Help/dtmf_functions.htm
>
>
​This seems far outside our remit.​


> DTMF tone A-D are used to provide prioritized call handling service in ITU
> Q.955.3 specification which is still used by some PBX and phone systems.
>
>
​Again, not at all clear that a WebRTC client would ever expect to use
these features of a PBX.

Finally, some calling card like systems allow remote control of functions
> such as flash by mapping them to extended DTMF tones.
>
>
​If there is a calling card system using WebRTC, I have not heard of it.
Can you provide a pointer?​

​The main point here is that we need a consistent set.  I take it you do
agree with that point, and disagree only on whether the set should include
A-D.  Do I have that right?

Ted


Regards,
> _____________
> Roman Shpount
>
>