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

Sean Turner <sean@sn3rd.com> Mon, 04 June 2018 11:28 UTC

Return-Path: <sean@sn3rd.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 DA25612D946 for <rtcweb@ietfa.amsl.com>; Mon, 4 Jun 2018 04:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 RqGvIA6bYsVj for <rtcweb@ietfa.amsl.com>; Mon, 4 Jun 2018 04:28:31 -0700 (PDT)
Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::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 A480512D945 for <rtcweb@ietf.org>; Mon, 4 Jun 2018 04:28:31 -0700 (PDT)
Received: by mail-pl0-x232.google.com with SMTP id g20-v6so1752176plq.1 for <rtcweb@ietf.org>; Mon, 04 Jun 2018 04:28:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LzD8NY6kYyAvtjbXfsnOgAu+n4XhbEHrAqy4Cd2UuwA=; b=OfaQUwyUPaganQ5lbZDX6sILWqWqsGyWu7SymDIEqVbXgaIsRwhjk7thwrO71o8E+u gHcv/LMXJerfs58TscgM5upOS0Rvajp1dfNgvUAcJSKd0mWAYubj4ESKbn33U7PRZe/M J5lZV/0gYVVARg4txtko3mvxmVM8tSJGFJIos=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LzD8NY6kYyAvtjbXfsnOgAu+n4XhbEHrAqy4Cd2UuwA=; b=Zj7OhX4xxvuGQp4i2pg5y5l4b3njyRUlMolMhW8dpYZoPki02MfJLEZBicR8+l2jNp +eyNkYhVW30oGM3LwkUW+UVaATioruvw4uDg+RAw8ikKfw0ZUBlf9gkMm8Pnhdm4igtF xPHJqOQCftoto0mhTM5RvN7Kix0pImfwHteHCSINoPkqgE1Vk/XCRIE8SOTOXGeKkLKJ AN3p+aECO589dlScDj8cXUoX5IdPMOxywyov8t/CYzCtjqwQoHfqwX5trn73K6TwksRT 47RtsRuKJ7ayBtkCXjjwT1jDfxZXpBKu55oK5nIGbmgflrDJG6VFGjT4TPZPY3CRv2Du tVFg==
X-Gm-Message-State: ALKqPwc+D22UD/YV6zg/pXpexD0TDJvJ17Ny1Ca5qEpICqfrKeTUK1yf nVUM7PyLdUeVd+bxFj6NAsBMrC6HnVo=
X-Google-Smtp-Source: ADUXVKLcxJZgA1UPCUCeKOX0u9S8aLKqlVCG7EknFnxdXnBK9PP6cS75LOUL/tfrkxSLchtPPZTP8Q==
X-Received: by 2002:a17:902:3001:: with SMTP id u1-v6mr21485357plb.376.1528111710941; Mon, 04 Jun 2018 04:28:30 -0700 (PDT)
Received: from [5.5.33.250] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id g15-v6sm59204248pgv.58.2018.06.04.04.28.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Jun 2018 04:28:29 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <0051C70E-362F-4E20-9DF8-9290DD4EB989@mozilla.com>
Date: Mon, 04 Jun 2018 13:28:22 +0200
Cc: Justin Uberti <juberti=40google.com@dmarc.ietf.org>, Nils Ohlmeier <nohlmeier@mozilla.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9216A555-846F-4E87-9D8B-2F2014B598FC@sn3rd.com>
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> <CAOJ7v-3FbN7v00Lzc5kJV4Nsw5DD0c6zLDLY+x1AgSOEHSt_WA@mail.gmail.com> <D6DEE1F6-A105-4095-902D-CB6F5AA2D937@mozilla.com> <CAOJ7v-2aXsQrwJ77+MsZ0cw-cx=VJTccFJwc9rxSFjdd+bCs-g@mail.gmail.com> <0E876BDE-C438-43AD-B87A-95894ADCBF8F@sn3rd.com> <574256E1-7AF4-4E25-9462-04B4B599C801@mozilla.com> <CAOJ7v-3uxT2fZdxxcz93TsSMFHaJCOURZnv=_aNiYo-enS3D9g@mail.gmail.com> <6DF5B202-803F-452B-B17E-5346F4C6FB4B@iii.ca> <CAOJ7v-1KHxmE+i0H5wJ68L3_-L=pcUiFwSz=9pTGybrr7V-5dQ@mail.gmail.com> <0051C70E-362F-4E20-9DF8-9290DD4EB989@mozilla.com>
To: RTCWeb IETF <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/kgCQBEDaNKvsBQE-g5xl7RGAcK8>
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, 04 Jun 2018 11:28:34 -0000

Let’s let this simmer until June 11th, but then we ought to merge it.

spt

> On Jun 4, 2018, at 06:11, Nils Ohlmeier <nohlmeier@mozilla.com> wrote:
> 
> I reviewed the diff and I think it helps to clarify this.
> 
> Best
>   Nils
> 
>> On Jun 3, 2018, at 20:48, Justin Uberti <juberti=40google.com@dmarc.ietf.org> wrote:
>> 
>> Agreed. Created https://github.com/juberti/draughts/pull/102 that adds a high-level discussion of enterprise TURN servers, hopefully enough to clarify the situation.
>> 
>> If you think "browser-provided TURN server" is a clearer term, I could use that instead.
>> 
>> 
>> 
>> On Mon, May 14, 2018 at 6:21 AM Cullen Jennings <fluffy@iii.ca> wrote:
>> 
>> 
>>> On May 11, 2018, at 11:08 AM, Justin Uberti <juberti=40google..com@dmarc.ietf.org> wrote:
>>> 
>>> Thanks for the PR. I spent some time thinking about this and ultimately concluded that more significant changes to the document will be necessary if it is to prescribe how a browser-provided TURN server should be handled, essentially incorporating much of the guidance from https://tools.ietf.org/html/draft-ietf-rtcweb-return-02
>>> 
>>> For example, candidates produced from the TURN server should not have raddr/rport set; interactions between the browser-provided and any application-provided TURN server need to be described; the question of whether local candidates should be provided needs to be considered.
>>> 
>>> As such, I see 3 paths forward here:
>>> a) Leave the document as-is. While leaving some ambiguity on this topic, the eventual (hopefully) publication of RETURN should clarify things, at which point we can publish a -bis.
>>> b) Discuss the general concept of browser-provided TURN servers, but mention that this is an area of further study, and give some guidance based on our current understanding. That is, explain how the existing modes would work in the presence of a browser-provided TURN server.
>>> c) Restore the reference to RETURN and progress the RETURN doc.
>>> 
>>> Overall, I don't expect the mode recommendations to change in the presence of a browser- or network- provided TURN server, so I think any changes here will be almost entirely additive.
>>> 
>>> Thoughts?
>> 
>> 
>> I lean towards option B as it sounds like it meets our current needs and allows us to separate out the harder stuff to do later. 
>> 
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb