IETF Logo Mail Archive

Re: [rtcweb] Nils comments [Was: WGLC for draft-ietf-rtcweb-ip-handling]

Cullen Jennings <fluffy@iii.ca> Fri, 27 April 2018 18:22 UTC

Return-Path: <fluffy@iii.ca>
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 5E2D4124205 for <rtcweb@ietfa.amsl.com>; Fri, 27 Apr 2018 11:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable 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 m-G_u2EM5JLL for <rtcweb@ietfa.amsl.com>; Fri, 27 Apr 2018 11:22:26 -0700 (PDT)
Received: from smtp73.iad3a.emailsrvr.com (smtp73.iad3a.emailsrvr.com [173.203.187.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FEEE127AD4 for <rtcweb@ietf.org>; Fri, 27 Apr 2018 11:22:26 -0700 (PDT)
Received: from smtp26.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp26.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id B0861542E; Fri, 27 Apr 2018 14:22:17 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp26.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 5144E5733; Fri, 27 Apr 2018 14:22:17 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (S0106004268479ae3.cg.shawcable.net [70.77.44.153]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Fri, 27 Apr 2018 14:22:17 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_548A517E-C246-405D-BE62-F52F4D04EB9F"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAOJ7v-3wBVdfacAvb=VOggMXWMD1-5Oq-GCb5cNSCy3_-ur3Gw@mail.gmail.com>
Date: Fri, 27 Apr 2018 12:22:15 -0600
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, RTCWeb IETF <rtcweb@ietf.org>
Message-Id: <A58B5A3B-DF5E-484B-ADD5-EBA539D0F250@iii.ca>
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.com> <F9EB7388-9E76-43E0-8C9B-61D3E50357F7@mozilla.com> <CAOJ7v-38kH4peZVVJU8itve2P+93eGaVdJ60MVcaRo3Xu86uTQ@mail.gmail.com> <296F0D20-F716-4C6C-8ABB-9FC21FC8189D@mozilla.com> <CAOJ7v-3wBVdfacAvb=VOggMXWMD1-5Oq-GCb5cNSCy3_-ur3Gw@mail.gmail.com>
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/3FDzj0awRHtFihQB01UTlxJSY5A>
Subject: Re: [rtcweb] Nils comments [Was: WGLC for draft-ietf-rtcweb-ip-handling]
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 27 Apr 2018 18:22:28 -0000


> On Apr 17, 2018, at 3:15 AM, Justin Uberti <juberti=40google.com@dmarc.ietf.org> wrote:
> 
> IMO "trusting the TURN relay but not the application" is not a significant enough benefit to merit adding specific functionality for.
> 

In the case were the TURN server is provided by the JS, I agree. But in the case where the configuration of the browser provided the TURN server, then I think it is as trusted as say a VPN server.

v2.23.0 | Report a Bug | By Email