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

Roman Shpount <roman@telurix.com> Mon, 21 December 2015 23:46 UTC

Return-Path: <roman@telurix.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 CEA381ACE9C for <rtcweb@ietfa.amsl.com>; Mon, 21 Dec 2015 15:46:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 bB6o1Bkg8FxT for <rtcweb@ietfa.amsl.com>; Mon, 21 Dec 2015 15:46:52 -0800 (PST)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::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 850A21ACE9A for <rtcweb@ietf.org>; Mon, 21 Dec 2015 15:46:52 -0800 (PST)
Received: by mail-io0-x231.google.com with SMTP id e126so170686935ioa.1 for <rtcweb@ietf.org>; Mon, 21 Dec 2015 15:46:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pxyVBUUNHF15yYcdMHmzTIeB4tcJTCE1y8CHSrAgilg=; b=sRUYV23yDHrEMR+ix3T9/T2mXNoryKUeEmp5YUs3grwIMRNgivF38EZuj1sMI683u9 P8/pcYcw1gSLHntP46Cev5g6zvcfTNRBiqRXkCfXJRzCQCS+WqU/Rm2CNVlhkN3YNAjj BerAA84RyMf3dXf5WO5YTMG9ezUQ9WkFMKNE+9tVa5G9dpC3q9cFH8837uXvV7i9TtbG qeV6kcFTFLU+ntAtAhSr2dfjZ+M11SygdCXy1eBenzUqAqbIDxGo39VOc+sDa23ok86Q xQFCduUQjyVdXnmpEu2FBFjwd3VS7kBPM33dTDs/HUo1qQAzvKEcsbCRisJMR9cO2RBf PTzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pxyVBUUNHF15yYcdMHmzTIeB4tcJTCE1y8CHSrAgilg=; b=CEkg6bMHltvAXkzvcj97GA+dqr2J5qQhXky/zmB3cXZbs6GXuqX1lMTCuzjHcwf2x0 JYrbAnNsnfbt07Xuw0JIiJipcKyyMWetzFA4ActiiD+H3hd+s4uYF4Cy5Ts0/4teCh6v HTkfooowKhcK2Hp+pr6V/6sLYyQ45kWDcm3vHnLf7rjFgm9f1KE8/H9pD6n2bzxt+oAd aDMj1/Pcywdgl+w9MEp229R/9P4HZSY9m7tQG/Hnn5O7+4+XzDd2Nhhl7P9F/5DnSUES Yb28ABxzChAtcJlbMi4oHsF+xZ3r3Y6DpaI5bDwIHCLbSTuRhZZLPrnqlL2nCGJlmwA5 quZA==
X-Gm-Message-State: ALoCoQkS4dMbl+HvhaEf6mtB4cnafXTpTm4ffFdWXuaLU7bTxzp/sidKeskecpxbelft0n9bqn8xRQ0VKzkOhmOrG+Qz67ZHlA==
X-Received: by 10.107.166.78 with SMTP id p75mr20992164ioe.59.1450741611880; Mon, 21 Dec 2015 15:46:51 -0800 (PST)
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com. [209.85.213.169]) by smtp.gmail.com with ESMTPSA id qr1sm9131369igb.21.2015.12.21.15.46.49 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Dec 2015 15:46:50 -0800 (PST)
Received: by mail-ig0-f169.google.com with SMTP id mv3so40394814igc.0 for <rtcweb@ietf.org>; Mon, 21 Dec 2015 15:46:49 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.114.3 with SMTP id jc3mr14266059igb.2.1450741609245; Mon, 21 Dec 2015 15:46:49 -0800 (PST)
Received: by 10.36.105.15 with HTTP; Mon, 21 Dec 2015 15:46:49 -0800 (PST)
In-Reply-To: <CABkgnnWBXZ_+oUorQGv7oebA4JGcJ-E+1CYzTjhmcW_EnSUehw@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> <CA+9kkMCvAcxnc=QdGvTm3=VNOQ3TtO+d8PfbfVA8sLeEA6rRqg@mail.gmail.com> <CAD5OKxtu-dsahdwL7t7Br34V-guqKmsdTsztOK_8sSsvWYsF=g@mail.gmail.com> <CA+9kkMBxbmGggCUaBPVtsJ7o3ZvBS=xvDKkmvfJxdVbM8NgiEQ@mail.gmail.com> <CAD5OKxvaJTRtfDQLwpvi+etdh8ZQvP5eRROSvRY2Hg-Uasisww@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADE2686D@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAD5OKxvvm+8yM-tdKMqhPv+V_z6u3S3=cR0Xe1rTs46e2_iqJw@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADE27108@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CABkgnnWBXZ_+oUorQGv7oebA4JGcJ-E+1CYzTjhmcW_EnSUehw@mail.gmail.com>
Date: Mon, 21 Dec 2015 18:46:49 -0500
X-Gmail-Original-Message-ID: <CAD5OKxv+pGU0EXG496o32NeS+SLf35hwors6gF4pL1eDn4eiPg@mail.gmail.com>
Message-ID: <CAD5OKxv+pGU0EXG496o32NeS+SLf35hwors6gF4pL1eDn4eiPg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="089e0153844847b5790527711abd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/tdMYYhIN-XBNUof-4Vs7ZYOMi-w>
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: Mon, 21 Dec 2015 23:46:54 -0000

On Mon, Dec 21, 2015 at 6:28 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 22 December 2015 at 10:25, DRAGE, Keith (Keith)
> <keith.drage@alcatel-lucent.com> wrote:
> > I’d also note that some of these arguments about use cases seem to be
> going
> > into sending DTMF to webrtc endpoint, which would seem to bring us into
> use
> > cases of webRTC gateway to webRTC gateway signaling, which at least is
> not
> > covered in our current gateways document.
>
> I don't believe that there is any plan to have browsers accept DTMF,
> if anyone was considering that possibility.
>

All I wrote, and I am not sure how to state this any clearer, that since
offer/answer normally negotiates codecs in both direction, PSTN gateways
will send RFC 4733 tones to WebRTC endpoints. WebRTC endpoints should be
able to receive and safely discard them. This is completely unrelated to
A-D tones and should cover all telephone-events.

P.S. Does anyone have any comments regarding the rest of the text that I
proposed? I would think it is much more important then A-D tone support.
_____________
Roman Shpount