IETF Logo Mail Archive

Re: [Perc] DTMF in Double

Roni Even <roni.even@huawei.com> Mon, 14 August 2017 05:28 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C665124217 for <perc@ietfa.amsl.com>; Sun, 13 Aug 2017 22:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 o_0zE35vDrZT for <perc@ietfa.amsl.com>; Sun, 13 Aug 2017 22:28:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366E9126B6E for <perc@ietf.org>; Sun, 13 Aug 2017 22:28:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DTJ24820; Mon, 14 Aug 2017 05:28:42 +0000 (GMT)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 14 Aug 2017 06:28:41 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.138]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0301.000; Mon, 14 Aug 2017 13:28:31 +0800
From: Roni Even <roni.even@huawei.com>
To: Adam Roach <adam@nostrum.com>, Cullen Jennings <fluffy@iii.ca>, "perc@ietf.org" <perc@ietf.org>
Thread-Topic: [Perc] DTMF in Double
Thread-Index: AQHTFGifdLavE/mpIkiD1tCWLGrehKKCT9WAgAD/eYA=
Date: Mon, 14 Aug 2017 05:28:31 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7FD189@DGGEMM506-MBX.china.huawei.com>
References: <65EF378D-664F-46E3-8853-56E5BB52C83D@iii.ca> <c5b1ec7b-67d9-c4bb-d5dd-92aac96f189d@nostrum.com>
In-Reply-To: <c5b1ec7b-67d9-c4bb-d5dd-92aac96f189d@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.51]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.5991350A.002B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.138, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1dc9ccf31b8df7d96ae268d141922b10
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/qSWXe8ablDoApvXGEKdvPRkic0U>
Subject: Re: [Perc] DTMF in Double
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2017 05:28:47 -0000

Hi Adan,
Yes these are the two options. 
I think that the important thing here is to caution that DTMF may be used for conference control and if encrypted end to end there need to be some conference level way to receive input from the conference participants (RFC4730, 3gpp 24.229) or having a media server that MUST have the end to end keys..

DTMF can be used for conference join(MD?), for routing callers to the right agent in call centers, for input of information during the call (E2E?),.... 
The first example may be relevant to the MD while the third is in general end to end and DTMF must be encrypted.

Roni



----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]
> Sent: יום ב 14 אוגוסט 2017 00:59
> To: Cullen Jennings; perc@ietf.org
> Cc: Roni Even
> Subject: Re: [Perc] DTMF in Double
> 
> On 8/13/17 2:16 PM, Cullen Jennings wrote:
> > I think Roni had a good point about DTMF can be done with the SIP INFO
> > approach so I plan to add the text do double that says something along
> > the lines of
> >
> >     When DTMF is sent with [RFC4733], it is end-to-end encrypted and the
> >     relay can not read it so it can not be used to control the media
> >     relay.  Other out of band methods to control the relay need to can
> >     be used instead.  One way to do this is to send DTMF with [RFC6086],
> >     which will be sent in the signalling thus allowing the relay to read
> >     the DTMF.
> >
> 
> RFC6086 doesn't define how to send DTMF in the signaling path any more
> than RFC3261, RFC675, or RFC791 do.
> 
> 3GPP 24.229 does, if you want to cite that. The other two options are
> RFC4730 and "It's 2017 -- don't do that."
> 
> /a

v2.23.0 | Report a Bug | By Email