IETF Logo Mail Archive

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

Matthew Kaufman <matthew.kaufman@skype.net> Fri, 18 November 2011 10:37 UTC

Return-Path: <matthew.kaufman@skype.net>
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 332B521F8B28 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level:
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 azjDqZ2UBkB2 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:37:32 -0800 (PST)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id 2B73921F8AB9 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 02:37:32 -0800 (PST)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id 4A177CF; Fri, 18 Nov 2011 11:37:31 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mx; bh=aVUhgF8yoypN5x O+1Q2wp2iP9KM=; b=OurAfhVJo8RFHmgMNKLrQALJuzJ7KURVNb1YCv7HZgXx3t RMB1/oxzkxHVzEkk7K+A07l0Z+QJIWXilqb2RfN5QtU8Ep7inf5Dmlb6NZJXevMS 19cvNHs55v5eIfGvq3zcTkzhSAJ+PAcxh1/30f7B96YX51jE/Cg49C1BLsuac=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :mime-version:to:cc:subject:references:in-reply-to:content-type: content-transfer-encoding; q=dns; s=mx; b=PoukKB7vsjEFmqom0QOShA H7qSS0dUa/cCvwUM3oxAr8gZnBATgH0cZpfGs8SU59qVRNjPQDctyE9+we5K1AEG Ddt6ulnSvD3qUZRga2BrZSVr3DtpF2ckoUdMlQGZehqIfnatoQddJFBX8QP9bhFU YwbSG87kkL3Oxd+fH0NxM=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id 4888A7FE; Fri, 18 Nov 2011 11:37:31 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 307261672681; Fri, 18 Nov 2011 11:37:31 +0100 (CET)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iL9BiGDZ9asu; Fri, 18 Nov 2011 11:37:26 +0100 (CET)
Received: from Matthew-Kaufman-Air.local (unknown [203.69.99.16]) by zimbra.skype.net (Postfix) with ESMTPSA id CF75235073D9; Fri, 18 Nov 2011 11:37:24 +0100 (CET)
Message-ID: <4EC63561.10909@skype.net>
Date: Fri, 18 Nov 2011 18:37:21 +0800
From: Matthew Kaufman <matthew.kaufman@skype.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Iñaki Baz Castillo <ibc@aliax.net>
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>
In-Reply-To: <CALiegfmFizZ7zC55MCHVs_w6EO-FHfn2fSH4+yqCD5O82T3MTw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
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 10:37:36 -0000

On 11/18/11 6:05 PM, Iñaki Baz Castillo wrote:
> 2011/11/18 Harald Alvestrand<harald@alvestrand.no>:
>>> H.323 and SIP both offer a signaling-plane means of indicating DTMF, other
>>> than RFC 2833/4733.  For H.323 it's H.245 User Input Indications (UII)
>>> messages.  For SIP it's officially KPML (RFC 4730), but in practice it's not
>>> popular.  Two vendors I know of support it, but it's a drop in the bucket
>>> compared to rfc2833 or SIP INFO.
>> OK, thanks.
>>
>> So the discussion that is really part of the IETF's task here is to pick one
>> (and preferably one) way that WebRTC applications are recommended to do
>> DTMF.
> In case http://tools.ietf.org/html/draft-kaplan-dispatch-info-dtmf-package-00
> becomes a standard, there is no need to send DTMF over the media
> stream (when interoperating with SIP networks). Since this just
> concerns the in-the-wire signaling it becomes up to the application
> developer.
>
>
Are you advocating that we not put DTMF-in-media support in browsers (in 
which case I have a good argument against), or are you simply making an 
observation about an alternative that may also become available?

Matthew Kaufman

v2.23.0 | Report a Bug | By Email