IETF Logo Mail Archive

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

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Sat, 21 September 2013 23:14 UTC

Return-Path: <andrew.hutton@siemens-enterprise.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 A9EB421F940D for <rtcweb@ietfa.amsl.com>; Sat, 21 Sep 2013 16:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599]
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 9yy3bFmJXNL5 for <rtcweb@ietfa.amsl.com>; Sat, 21 Sep 2013 16:14:27 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id AEE7B11E81D3 for <rtcweb@ietf.org>; Sat, 21 Sep 2013 16:14:20 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 697771EB8558; Sun, 22 Sep 2013 01:14:19 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.31]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Sun, 22 Sep 2013 01:14:04 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
Thread-Index: AQHOtl7fMuig8voiEUG8usawnCEAN5nQ0kde
Date: Sat, 21 Sep 2013 23:14:03 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BD024F@MCHP04MSX.global-ad.net>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB11667BBA0@xmb-aln-x02.cisco.com>, <079001ceb618$2f551ae0$8dff50a0$@stahl@intertex.se>, <523CBB62.6000007@alvestrand.no>, <BLU169-W25E3AD9CC285253ED354BF93230@phx.gbl>
In-Reply-To: <BLU169-W25E3AD9CC285253ED354BF93230@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.196]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 23:14:32 -0000

The use case draft section 3.2.5.1 states

"It mustbe possibele to configure the browsers used in the enterprise with  network specific STUN and TURN servers.  This should be possible to achieve by autoconfiguration methods."

I had assumed that this meant using the browser configuration scripts in the same way as the browser would discover the HTTP Proxy I can see that DHCP is also an option which might be useful but I am not sure whether browsers would use it.

Andy


From: rtcweb-bounces@ietf.org [rtcweb-bounces@ietf.org] on behalf of Bernard Aboba [bernard_aboba@hotmail.com]

Sent: Saturday, September 21, 2013 1:09 AM

To: Harald Alvestrand; rtcweb@ietf.org

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




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.

v2.23.0 | Report a Bug | By Email