IETF Logo Mail Archive

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

Mary Barnes <mary.ietf.barnes@gmail.com> Sat, 19 November 2011 02:29 UTC

Return-Path: <mary.ietf.barnes@gmail.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 7D41321F846B for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 18:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.088
X-Spam-Level:
X-Spam-Status: No, score=-103.088 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 G9juzkyqIbMQ for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 18:29:42 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DA0AD21F8469 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 18:29:41 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so938694vcb.31 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 18:29:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CZOVmRSRHWLsAXeURtIJtSKWjfseuR8IAXgGomscK7Q=; b=OHRM/TdguLovznAaOWkSAslKNhhOvyNbnEthYXQobGnQmcEJPw8RRtZl5TgYA2UI1j RrJEAwh3aa1nbiRgKkh9XgXRiMz6JuPPnJEf+RfJmJvf0YT2zPtzu9oWWInwnbWyZJ0O XRcDvCNH/hlLfTxAm5/M915RpiK6Ojm/m/RJw=
MIME-Version: 1.0
Received: by 10.52.34.207 with SMTP id b15mr6229326vdj.19.1321669780306; Fri, 18 Nov 2011 18:29:40 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Fri, 18 Nov 2011 18:29:40 -0800 (PST)
In-Reply-To: <CALiegfmFizZ7zC55MCHVs_w6EO-FHfn2fSH4+yqCD5O82T3MTw@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>
Date: Fri, 18 Nov 2011 20:29:40 -0600
Message-ID: <CAHBDyN6V9VVb20QRmz9KeFrp2CxTmG5Cz_28gDGQxb881huEBw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: text/plain; charset="ISO-8859-1"
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: Sat, 19 Nov 2011 02:29:42 -0000

On Fri, Nov 18, 2011 at 4:05 AM, Iñaki Baz Castillo <ibc@aliax.net> 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.
>
That document will not become a standard.  We already dispatched it
(scroll down to IETF-79):
http://trac.tools.ietf.org/wg/dispatch/trac/wiki

Mary.

> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email