Re: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 21 September 2013 00:09 UTC

Return-Path: <bernard_aboba@hotmail.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 0EF8821F9F40 for <rtcweb@ietfa.amsl.com>; Fri, 20 Sep 2013 17:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level:
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLJwsccRx0Hc for <rtcweb@ietfa.amsl.com>; Fri, 20 Sep 2013 17:09:44 -0700 (PDT)
Received: from blu0-omc1-s21.blu0.hotmail.com (blu0-omc1-s21.blu0.hotmail.com [65.55.116.32]) by ietfa.amsl.com (Postfix) with ESMTP id 282F121F85E6 for <rtcweb@ietf.org>; Fri, 20 Sep 2013 17:09:44 -0700 (PDT)
Received: from BLU169-W25 ([65.55.116.8]) by blu0-omc1-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Sep 2013 17:09:40 -0700
X-TMN: [mh3jqD7vKvwkjLT5gHrIwlNiool+Md1C]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W25E3AD9CC285253ED354BF93230@phx.gbl>
Content-Type: multipart/alternative; boundary="_4ce0a1dd-6b02-49d9-89cb-d89bc8d7abef_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Fri, 20 Sep 2013 17:09:39 -0700
Importance: Normal
In-Reply-To: <523CBB62.6000007@alvestrand.no>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB11667BBA0@xmb-aln-x02.cisco.com>, <079001ceb618$2f551ae0$8dff50a0$@stahl@intertex.se>, <523CBB62.6000007@alvestrand.no>
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Sep 2013 00:09:40.0187 (UTC) FILETIME=[DDA1C2B0:01CEB65E]
Subject: Re: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 21 Sep 2013 00:09:50 -0000

Harald said: 
  
> In this case, it's "only" a DHCP option, but what new DHCP options do we 
> have that have become widely used in the last 10 years?

[BA] And of those, which ones are supported by *browsers*?
 
I do think it is useful for a browser to be able to locate a local TURN server, if this is to happen it will need to be done at the application layer, not via DHCP.