Re: [rtcweb] rtcweb-transports reference to TRAM discovery

Harald Alvestrand <harald@alvestrand.no> Wed, 17 December 2014 17:09 UTC

Return-Path: <harald@alvestrand.no>
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 909381A902D for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 09:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 tMgooRd2OQIe for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 09:09:37 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 2374A1A902B for <rtcweb@ietf.org>; Wed, 17 Dec 2014 09:07:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 669E37C378D for <rtcweb@ietf.org>; Wed, 17 Dec 2014 18:07:03 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6xt_KPbTZ16 for <rtcweb@ietf.org>; Wed, 17 Dec 2014 18:06:59 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:ed33:64f:45c0:8aa8]) by mork.alvestrand.no (Postfix) with ESMTPSA id 326867C3797 for <rtcweb@ietf.org>; Wed, 17 Dec 2014 18:06:59 +0100 (CET)
Message-ID: <5491B831.70704@alvestrand.no>
Date: Wed, 17 Dec 2014 18:06:57 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <9F33F40F6F2CD847824537F3C4E37DDF1E63FB08@MCHP04MSX.global-ad.net> <CABcZeBOpX0vM9NJeKY5e+S13oKrLW3Td53qcxRkCHa2=nv=EGg@mail.gmail.com> <CANO7kWBY1MTU1A2fWo0E5Y6TQ1o+vWSz22pnWz6+5s7SFQcP-g@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF1E63FD67@MCHP04MSX.global-ad.net> <CAOJ7v-1NnS1QOF-Ujv7a=qCnXrQ0htd0b4TFUDaKgwik9Rd=-Q@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF1E643D2C@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF1E643D2C@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/6FXyLnd8nyYR0pdCl7xCLsITYzo
Subject: Re: [rtcweb] rtcweb-transports reference to TRAM discovery
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: Wed, 17 Dec 2014 17:09:43 -0000

On 12/17/2014 05:19 PM, Hutton, Andrew wrote:
> OP: 15 December 2014 22:44 Justin Uberti Wrote:
>> I think making it a requirement is probably premature until we have a
>> WG document that explains what should happen when you discover one of
>> these network-provided TURN servers.
>> Once https://tools.ietf.org/html/draft-schwartz-rtcweb-return-04 is
>> accepted as a WG doc, we can add a requirement for support for RETURN
>> and server discovery.
>>
>> Unclear whether it needs to be MUST-strength until we get some
>> implementation feedback though.
>>
> -transports already states " WebRTC browsers MUST support configuration of STUN and TURN servers, both from browser configuration and from an application".
>
> So it looks like we already have a requirement but no explanation of what should happen when both are available.

The last times we've talked about this, people have imagined configuring 
this via the same mechanism as configuring HTTP proxies (nonstandard 
script at a nonstandard URL).

Autodiscovery may be preferable, but it's not clear that it removes the 
need for the script-like things.

>
> Looks like we need to adopt draft-schwartz-rtcweb-return and explain this stuff. I would certainly support that and put some effort into getting this done.
>
> Andy
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb