IETF Logo Mail Archive

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

Justin Uberti <juberti@google.com> Mon, 30 April 2018 22:03 UTC

Return-Path: <juberti@google.com>
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 42F91127275 for <rtcweb@ietfa.amsl.com>; Mon, 30 Apr 2018 15:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 OEO3qBb6LDuH for <rtcweb@ietfa.amsl.com>; Mon, 30 Apr 2018 15:03:24 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 836021271FD for <rtcweb@ietf.org>; Mon, 30 Apr 2018 15:03:24 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id e20-v6so11916788iof.4 for <rtcweb@ietf.org>; Mon, 30 Apr 2018 15:03:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t8sJQf98tvxpK56wblWZcocADV3h62C4ymLh+MA5cjM=; b=JrNTNBjIA7MUZELCO81hJj9kxwH51NV+JotaZOxEZP/+5WwB9xW/HAbWzZ5pu36iwo BMA+wakI9Lldg/pDI+EskW7W1Eya/iUrJwTL58/D6zk32rGSIbs6u83t4dIfLHpQ1I5N Oj8AJrH5TyGUwiRa1npfJYjreu9urAzNRnXYs8n9L0sYjYuxghzjuqAnfaopRTdNHbKq hv3ADbiBfh5bQkyNTfYR/YhEGRlRN/EQC+9U3dyqDCuGN1cBkPIJ/iHLPL94f5pmxUmz ydk1jE89G5YS4oL0FYfYiu9EDGsj2LlSF3ujpJaIka6pzFU5FSOy/WqqPXnycZZiSylN mVow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t8sJQf98tvxpK56wblWZcocADV3h62C4ymLh+MA5cjM=; b=KvRojdW2SpX0LWOw6kuyx/Wzqfrwg1MO5HVEr5wD4et0kq3A8uxtMn/l1nGDkYGRj4 K07EfKfj874xN4NiAglgQ8a04UqyksOV+M9iQhS8DSVLx4nFX7hKxM1nI4JeI10qCAHO S4MQ8x756JLuC478xWVzFJC5rRHHfJppjsN0B7BZTVF4JB2Hnxfqx80xdKZ/Rg2UnUfg 7cVKZe/7tfsJS+n427fXBjvjOS7gczwEr3rZnAd24cAUbrictH+isvpjqPSg6CgbRjLS oGKLajWano0VH4BzhlPmXfyxAJHJtQeCwmZe4LF6qIPRS6v66B0+TqPSPg5wQh7z2vAD PAlA==
X-Gm-Message-State: ALQs6tC6OtNbvKQnxIOnfjrUAulOSTmZLSqk7haeDjemaZtyz91jmyA6 t/fBSxOciJKBebQrf1rrolWri99vHtlqPaerScNtSA==
X-Google-Smtp-Source: AB8JxZrQsOs7yY0X5OMj85K6Ib02D9FFw9RlmHeFnkehhls3e8y/w9qHtKmer+mnHgXyk0UGtUEO1FuDBbSv35foWm4=
X-Received: by 2002:a6b:4514:: with SMTP id s20-v6mr14811758ioa.38.1525125803353; Mon, 30 Apr 2018 15:03:23 -0700 (PDT)
MIME-Version: 1.0
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> <A58B5A3B-DF5E-484B-ADD5-EBA539D0F250@iii.ca>
In-Reply-To: <A58B5A3B-DF5E-484B-ADD5-EBA539D0F250@iii.ca>
From: Justin Uberti <juberti@google.com>
Date: Mon, 30 Apr 2018 22:03:12 +0000
Message-ID: <CAOJ7v-3FbN7v00Lzc5kJV4Nsw5DD0c6zLDLY+x1AgSOEHSt_WA@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bfbad9056b18054b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/AxNM-S3p6q5svvCbNXrQmgiGSAM>
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: Mon, 30 Apr 2018 22:03:26 -0000

Any TURN server provided by the browser is in effect a proxy, and forcing
use of said proxy can be done either through firewall config or explicit
selection of Mode 4. (IOW, no new mode is needed.)

The document originally pointed at RETURN as an example of how such TURN
proxying could work, but was removed in order to avoid a dependency.

On Fri, Apr 27, 2018 at 11:22 AM Cullen Jennings <fluffy@iii.ca> wrote:

>
>
> 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