Re: [tram] signature based 3rd party scheme

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 30 April 2015 16:42 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAEE1A8898 for <tram@ietfa.amsl.com>; Thu, 30 Apr 2015 09:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 a5rB8c5zTtGE for <tram@ietfa.amsl.com>; Thu, 30 Apr 2015 09:42:20 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FA251A87D4 for <tram@ietf.org>; Thu, 30 Apr 2015 09:42:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3A571BE59; Thu, 30 Apr 2015 17:42:19 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGUoHBnALfNy; Thu, 30 Apr 2015 17:42:18 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.30.127]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 29051BE58; Thu, 30 Apr 2015 17:42:18 +0100 (IST)
Message-ID: <55425B69.6080008@cs.tcd.ie>
Date: Thu, 30 Apr 2015 17:42:17 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "tram@ietf.org" <tram@ietf.org>
References: <913383AAA69FF945B8F946018B75898A47821E90@xmb-rcd-x10.cisco.com> <55409F56.3090003@cs.tcd.ie> <913383AAA69FF945B8F946018B75898A47822B94@xmb-rcd-x10.cisco.com> <55422C68.8010505@cs.tcd.ie> <913383AAA69FF945B8F946018B75898A47822E1B@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A47822E1B@xmb-rcd-x10.cisco.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/B323bxbD2qkisL19VoD36HKu7do>
Subject: Re: [tram] signature based 3rd party scheme
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 16:42:21 -0000


On 30/04/15 17:36, Tirumaleswar Reddy (tireddy) wrote:
> Yes, third party authorization can be used by the TURN server in the
> Enterprise network to identify the WebRTC server.
> 

Indeed, if the current draft were the only way to do this then all
enterprises would have to pre-arrange things with all WebRTC servers.
IMO that won't work well, if at all.

A signature based scheme could be used in various ways, e.g. to
allow calls that don't consume much b/w regardless but to only
allow calls setup by whitelisted WebRTC servers when those calls
collectively consume a lot of b/w consumption.

The latter sounds like something that's much easier to deploy
to me and seems to meet some real use cases.

I really think the current wg draft is terribly limited in terms
of the kinds of use cases for which it'll work. I hope that the
wg consider those limitations seriously. (Or if you have already
please just point me at the archive/minutes that reflect that
discussion.)

S.