IETF Logo Mail Archive

Re: [rtcweb] Support DTMF "codec" or expose DTMF in signaling? (Re: DTMF usecase before DTMF API)

Justin Uberti <juberti@google.com> Fri, 18 November 2011 20:02 UTC

Return-Path: <juberti@google.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 D94881F0C81 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 12:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.792
X-Spam-Level:
X-Spam-Status: No, score=-102.792 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bf5riaQZRaK for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 12:02:38 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id E7C0E1F0C7C for <rtcweb@ietf.org>; Fri, 18 Nov 2011 12:02:37 -0800 (PST)
Received: by yenm7 with SMTP id m7so312928yen.31 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 12:02:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=gLcUnx12ukWZv/EqQG6jR13JujgbZH5NBeP1HJ0TgZE=; b=AF+/pLQpa3CfIRIgUBKGJ1TbDs3sZ5U1gxe3aIYhUTKp8Sgc/DlkzPttvDhUhrC6qb OS1svIoFjiVGNXABP+8Q==
Received: by 10.50.100.194 with SMTP id fa2mr4400869igb.49.1321646557229; Fri, 18 Nov 2011 12:02:37 -0800 (PST)
Received: by 10.50.100.194 with SMTP id fa2mr4400861igb.49.1321646557123; Fri, 18 Nov 2011 12:02:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.194.134 with HTTP; Fri, 18 Nov 2011 12:02:17 -0800 (PST)
In-Reply-To: <CAD5OKxtQTgT5W4mECdc-O_ST7XFgjUmy_K-GxEJ27Jw-_2z9vw@mail.gmail.com>
References: <CAOJ7v-18cNX8xussOPXSEoFxAARu8WriL8XgxPVUXBrWhz=FFg@mail.gmail.com> <4EC28CF5.6000109@jesup.org> <D666B5A5-BF2E-46B7-B97F-06C3736E8357@acmepacket.com> <CAOJ7v-3v5Zu9ZOuL3Qqu+aEDJ4a3cqH+oJ2yj_ewOpxKe=jA_g@mail.gmail.com> <733D6CE2-2360-4688-8268-3503F7E2460C@acmepacket.com> <9A05449A-C0FB-4548-AA80-728EC82218BB@acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE9B22@inba-mail01.sonusnet.com> <4EC5C6FB.4040804@alvestrand.no> <6725A83E-0BB0-4F86-AB27-75027E317710@acmepacket.com> <4EC60963.8060508@alvestrand.no> <CALiegfmFizZ7zC55MCHVs_w6EO-FHfn2fSH4+yqCD5O82T3MTw@mail.gmail.com> <4EC63561.10909@skype.net> <CALiegfnraby3e_TKMj95VUvaEyg3deomL=yciw0EW13O5q9w5w@mail.gmail.com> <4EC6480D.7080505@skype.net> <CALiegfnCZMJ0GYpehD3XGsN=cGHHXMA1FFD5PfKSVRc7SYE+4w@mail.gmail.com> <4134053A-A1D9-4E52-9A53-3F5790A2F405@acmepacket.com> <CALiegfmm8HFO+ODU3RxCznam1512UdQnzW6iQrXKFCNWV73RPQ@mail.gmail.com> <CAD5OKxtQTgT5W4mECdc-O_ST7XFgjUmy_K-GxEJ27Jw-_2z9vw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 18 Nov 2011 15:02:17 -0500
Message-ID: <CAOJ7v-3gYPjAKST_K9tvU4DAGHyyapujf8t9KeDMKE3geutQ=Q@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary="e89a8f3ba4d58e53f004b207d1cc"
X-System-Of-Record: true
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Support DTMF "codec" or expose DTMF in signaling? (Re: DTMF usecase before DTMF API)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Nov 2011 20:02:39 -0000

On Fri, Nov 18, 2011 at 2:33 PM, Roman Shpount <roman@telurix.com> wrote:

>
>
> On Fri, Nov 18, 2011 at 1:57 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
>> 2011/11/18 Hadriel Kaplan <HKaplan@acmepacket.com>:
>> > Unfortunately draft-kaplan-dispatch-info-dtmf-package will never become
>> a standard.  I presented it a couple IETF meetings ago, and was basically
>> told to go away and never bring it back to the IETF.  (despite the fact it
>> was the main use-case and motivation for creating INFO packages to begin
>> with)
>>
>> Opss... then, why do we need the "SIP INFO Method and Package
>> Framework"? just for having a generic "framework"? for nothing?
>> It's hard to believe :(
>>
>>
> This whole framework was shut down because it was not usable for some
> applications (record and press # type) due to luck of synchronization with
> media stream. Since it did not work for some applications it was ruled to
> be generally undesirable. Kind of similar to the SRTP discussion we were
> having on this list. The result is interesting too: whoever needed DTMF
> over INFO ignored that it is not a standard and used it anyway (since it
> has applications were it is desirable, like calling cards).
>
> Instead of DTMF specific API, I would prefer a mechanism for CODEC
> specific extensions and implement DTMF this way.
>

Can you make a proposal for what you'd like to see here? My view is that
DTMF is a special case already, so the most pragmatic approach is a special
case DTMF API.

> _____________
> Roman Shpount
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email