IETF Logo Mail Archive

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

"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Sun, 29 September 2013 00:49 UTC

Return-Path: <jlaurens@cisco.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 2274421E813F for <rtcweb@ietfa.amsl.com>; Sat, 28 Sep 2013 17:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 8LNjBXrnbXSB for <rtcweb@ietfa.amsl.com>; Sat, 28 Sep 2013 17:49:43 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id E292421F9B91 for <rtcweb@ietf.org>; Sat, 28 Sep 2013 17:49:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4327; q=dns/txt; s=iport; t=1380415782; x=1381625382; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=opMLxF7r6RNmVoI//ExHvWUoRTntal6E1HnkeTmQ+uE=; b=XNMVCUv/KRpTts2i0ndbIrdL8TpazvA1SL+632Iy3DHDQ+1SWQpMI5hh 52f5D0ZRd4cv5fGbSBCkxre8NVVxqA0rYjhPkecLbji4Mx8IRvGlBDgOH aCvj4s/CUaMLmrLoI2PN36cxIUck0zwLItBMGo/r9YT1YtM03HwdMXkhi o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAFAIp4R1KtJV2d/2dsb2JhbABZgkNEOK5uihSHeEqBIRZtB4ImAQEEAQEBaxsCAQgEOwcnCxQDAQ0CBBOHdAMPDLpPjGaCZwuDH4EDA5YXgWiBL4sWhTSBZoE+
X-IronPort-AV: E=Sophos; i="4.90,1002,1371081600"; d="scan'208,217"; a="265772926"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 29 Sep 2013 00:49:40 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8T0neQW021151 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Sun, 29 Sep 2013 00:49:40 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.247]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Sat, 28 Sep 2013 19:49:40 -0500
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: "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: AQHOvKyWX1UMcPyVcEy1G/MdfbXyXJnb4jVy
Date: Sun, 29 Sep 2013 00:49:40 +0000
Message-ID: <3CD8C0AB-3E69-4E95-9ED7-198AA4568A25@cisco.com>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB11667BBA0@xmb-aln-x02.cisco.com>, <523c6d3d.c9d1440a.3b96.7499SMTPIN_ADDED_BROKEN@mx.google.com>, <CAD6AjGRXr5kPRQdN+4jkgXHciN3NE7HiRmsb7kaYuzwHEPa7ZA@mail.gmail.com>, <C5E08FE080ACFD4DAE31E4BDBF944EB1166CC702@xmb-aln-x02.cisco.com>, <5244104D.4010401@alvestrand.no>, <CABkgnnWyYCdpSxXyiYb+4BzMpME85671x5JzxJX08RiyQd+SFQ@mail.gmail.com>, <BLU169-W98EC710F291837B36C14F0932B0@phx.gbl>
In-Reply-To: <BLU169-W98EC710F291837B36C14F0932B0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_3CD8C0AB3E694E959ED7198AA4568A25ciscocom_"
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: Sun, 29 Sep 2013 00:49:48 -0000

Why not have this at least optionally specified in JavaScript in the browser? This way those who "own" the apps have control and aren't relying on correct implementation of others (necessarily)

On Sep 28, 2013, at 8:41 PM, "Bernard Aboba" <bernard_aboba@hotmail.com<mailto:bernard_aboba@hotmail.com>> wrote:


On Sep 26, 2013 8:46 PM, "Harald Alvestrand" <harald@alvestrand.no<mailto:harald@alvestrand.no>> wrote:
"So far, neither the POSIX standard nor any OS vendor has offered a generic facility to access information made available in DHCP packets."


[BA] The Windows DHCP client API does provide this:

http://msdn.microsoft.com/en-us/library/windows/desktop/aa363351(v=vs.85).aspx


In particular, the SendParams argument to the DhcpRequestParams function can be used to request a particular parameter (e.g. TURN server address), which will then be returned in the RecdParams variable.


Nevertheless, I still think that using DHCP to configure the TURN server address in a browser isn't a good idea.  For one thing, since DHCP is effectively unsecured, this mechanism could be used by a rogue DHCP server to force traffic to a rogue turnserver.   Great for surveillance!


_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email