[rtcweb] draft-schwartz-rtcweb-return

Cullen Jennings <fluffy@cisco.com> Thu, 26 March 2015 15:20 UTC

Return-Path: <fluffy@cisco.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 69FB81AD0B8 for <rtcweb@ietfa.amsl.com>; Thu, 26 Mar 2015 08:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 oCk_dWC5jDFm for <rtcweb@ietfa.amsl.com>; Thu, 26 Mar 2015 08:20:52 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0E011AD0A0 for <rtcweb@ietf.org>; Thu, 26 Mar 2015 08:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=950; q=dns/txt; s=iport; t=1427383211; x=1428592811; h=from:content-transfer-encoding:date:subject:to: message-id:mime-version; bh=Bgh+CakdtWGK9etSVcNkkdIimHJ4Bmtf3990W2BYPyk=; b=FdNVvXHzRpfcamjBeHHa7pNsIQAXUWmMlEV+VeoUxGCoU2lm2C5aOHkW 6TvTVZmQdIW/ZwcVcrrKswx0pohPkZxxOxoZcXt2IEnAPRo/lazGTXV1G xjEFjwKEc/sIOlUuvV/t6GvbGsydeZptkfy0t9Q7zr+8dYWP5ACv5BGgI o=;
X-IronPort-AV: E=Sophos;i="5.11,472,1422921600"; d="scan'208";a="135656152"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP; 26 Mar 2015 15:20:10 +0000
Received: from [127.0.0.1] (ssh-sjc-2.cisco.com [171.68.46.188]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t2QFK8jn018420; Thu, 26 Mar 2015 15:20:09 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Mar 2015 10:20:09 -0500
To: rtcweb@ietf.org
Message-Id: <9DA8307B-263C-4951-A55C-36B42D27C08B@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/REKKdvn4eTKTJ-PHBqoixCaUc7Y>
Subject: [rtcweb] draft-schwartz-rtcweb-return
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: <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: Thu, 26 Mar 2015 15:20:56 -0000

I'd like to point out that the combination of ietf-tram-turn-server-discovery and draft-schwartz-rtcweb-return allow any network you are connected to more or less MITM your media and do things like rate limit it, generate analytics on who you are talking to, force your traffic through an intermediary that is in a  different legal jurisdiction and so on. 

They are also not clear on how the browser gets the credentials to use the discovered TURN server. This seems like a major lacking before we can significantly discuss this. 

As we have seen from the google proxy deployments, enough revenue can be generated from this relaying info to pay for the relay. I'm not keen on that happening automatically with no user consent or awareness. 

But I don't get how this will work for enterprise deployments - It's just very unclear how the JS would end with the appropriate set of TURN servers to use.