Re: [rtcweb] #1: RFC 4734 citation
Iñaki Baz Castillo <ibc@aliax.net> Wed, 31 October 2012 17:13 UTC
Return-Path: <ibc@aliax.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 4F02321F864A for <rtcweb@ietfa.amsl.com>; Wed, 31 Oct 2012 10:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NsCc5xmGpLT for <rtcweb@ietfa.amsl.com>; Wed, 31 Oct 2012 10:13:04 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3661B21F861C for <rtcweb@ietf.org>; Wed, 31 Oct 2012 10:13:04 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so1360538lbo.31 for <rtcweb@ietf.org>; Wed, 31 Oct 2012 10:13:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=LJ+GWzEwli+r4pQzqqBEnZTa952T3JeOS5O1/vQ2uoA=; b=QF3lw0x3X5hWn1ZOLwTrgkO36QwdCMex7tBBe77/Fsithu4pwoYAZJR8SFy5IIAhle llWNKco9KNzPd5SgY8+CVLtzZO/TiML8II7VIITlqahPbhscnXYikkd0J4O4GXwLmGj+ 60HDXV92gLnj/2BUlZGUkc7Bbl1TAbc5jwWDulw+U7HbjfCxBrQG80+24mjS9ABrcqCC s2fVNcggbOFzOU20zSPfPob2sYFC99z1yj9Ub85Pq19MB5YjWTo+ofLOIAUFHtYJ67zi qscJqArKSOkxN3P9T3zHOaj7zfa5XOdOqS7jRX3bF9kzItmqRdY0RKMAQyTrDgnagElZ ounQ==
Received: by 10.152.109.145 with SMTP id hs17mr34749626lab.5.1351703583205; Wed, 31 Oct 2012 10:13:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.2.71 with HTTP; Wed, 31 Oct 2012 10:12:43 -0700 (PDT)
In-Reply-To: <50914270.9020907@alvestrand.no>
References: <066.ee8d274029b0215df9ff464ea44b5fe7@trac.tools.ietf.org> <CALiegfkSohug3__vra9R=1vMfSX46_tDvFOuJOsxjUFE54eXYQ@mail.gmail.com> <50914270.9020907@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 31 Oct 2012 18:12:43 +0100
Message-ID: <CALiegfmX_F5HgNoZ107ru9UjAF1JbUy2mNc-Gv5v7v6YJt=tWQ@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="bcaec54ee77ceb279804cd5e0344"
X-Gm-Message-State: ALoCoQkQVIWQOL7mLuddkDCItOdXcSpTp2IAOiXJLb1lHlXZW3Xa8aZ++vQ0eb9n4lsdDm7m74Be
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] #1: RFC 4734 citation
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: Wed, 31 Oct 2012 17:13:05 -0000
2012/10/31 Harald Alvestrand <harald@alvestrand.no> > On 10/30/2012 02:06 PM, Iñaki Baz Castillo wrote: > >> 2012/10/23 rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.**org<trac%2Brtcweb@trac.tools.ietf.org> >> >: >> >>> Telephone Event - [RFC4734] >>> >> Could somebody give some points about why DTMFs over media are >> required in WWW? Isn't DTMF mechanism OLD enough to incorporate it >> into WebRTC? >> >> Autoanswer: interoperability with legacy telephony world. >> >> Autoanswer (and you should know this by heart now, it's been said so > many times): > > Use case 4.3.2 from draft-ietf-rtcweb-use-cases-**and-requirements-09: > > 4.3.2. Fedex Call > > 4.3.2.1. Description > > Alice uses her web browser with a service something like Skype to be > able to phone PSTN numbers. Alice calls 1-800-gofedex. Alice should > be able to hear the initial prompts from the fedex IVR and when the > IVR says press 1, there should be a way for Alice to navigate the > IVR. > > If you want to argue for having that use case deleted from the > requirements, start a debate on that topic. If you have an alternative > solution, state that in the positive as what should go into the -audio- > draft instead of RFC 4734. Well, as we all assume that media gateways are requried for interoperability with other VoIP networks, I assume it would be not so hard that the gateway receives the "DTMF's" via WWW means (HTTP, WebSocket...) and generates RTP DTMF's in the legacy leg. Anyhow I expect that it's not so hard to implement RTP DTMF's in a media stack, but I would not like to hear about "my PBX's does not detect Chrome's DTMF's". :) -- Iñaki Baz Castillo <ibc@aliax.net>
- Re: [rtcweb] #1: RFC 4734 citation Randell Jesup
- [rtcweb] #1: RFC 4734 citation rtcweb issue tracker
- Re: [rtcweb] #1: RFC 4734 citation Iñaki Baz Castillo
- Re: [rtcweb] #1: RFC 4734 citation Matthew Kaufman
- Re: [rtcweb] #1: RFC 4734 citation rtcweb issue tracker
- Re: [rtcweb] #1: RFC 4734 citation Harald Alvestrand
- Re: [rtcweb] #1: RFC 4734 citation Iñaki Baz Castillo
- Re: [rtcweb] #1: RFC 4734 citation Bernard Aboba
- Re: [rtcweb] #1: RFC 4734 citation Roman Shpount
- Re: [rtcweb] #1: RFC 4734 citation Bernard Aboba
- Re: [rtcweb] #1: RFC 4734 citation rtcweb issue tracker