IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Sat, 28 September 2013 22:53 UTC

Return-Path: <martin.thomson@gmail.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 1B5E821F9CF3 for <rtcweb@ietfa.amsl.com>; Sat, 28 Sep 2013 15:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 u5buVDmxb3-6 for <rtcweb@ietfa.amsl.com>; Sat, 28 Sep 2013 15:53:19 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9B55611E8127 for <rtcweb@ietf.org>; Sat, 28 Sep 2013 15:53:13 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id l18so2093554wgh.4 for <rtcweb@ietf.org>; Sat, 28 Sep 2013 15:53:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Xf8BTvlD+S2ea+5ZKm2dM48Y+LN362HHk0rrN1hmBEs=; b=KlYUOGazalULbIOFsHGHWiHkgpSfnA8Csp95Rl+OnnFqIrpseKAFdmymKtNAQHo1/b Hqfgr9Mj2wpwEFlUCroBF7suV77XlAUTG/0tGJdzMqlHJyBLQrr9R6Tua9+GQCrOMJ5e Fn8qDufcnovGF19HVYSJFBQSe1YPGWX1RGuI0KBUkQ5x+aHtQJ6866bV0HQfQNLl2X82 wwAZ/Bj4PO1ua/Th8Hrd53s+yBNrAZNoeT88uQEEg06pOXBPqtvtLftGlniER9Qqq8/n EG/tG4lvurYNYbRQm0KMI2nP27pgLFny6aY5j6yOW5HmsOJfI80TVse4oFFr7Inq5Q7O hbJg==
MIME-Version: 1.0
X-Received: by 10.180.187.2 with SMTP id fo2mr7766164wic.65.1380408792751; Sat, 28 Sep 2013 15:53:12 -0700 (PDT)
Received: by 10.194.158.227 with HTTP; Sat, 28 Sep 2013 15:53:12 -0700 (PDT)
Received: by 10.194.158.227 with HTTP; Sat, 28 Sep 2013 15:53:12 -0700 (PDT)
In-Reply-To: <5244104D.4010401@alvestrand.no>
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>
Date: Sat, 28 Sep 2013 15:53:12 -0700
Message-ID: <CABkgnnWyYCdpSxXyiYb+4BzMpME85671x5JzxJX08RiyQd+SFQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="001a11c38c82bca43404e7797707"
Cc: rtcweb@ietf.org
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, 28 Sep 2013 22:53:27 -0000

On Sep 26, 2013 8:46 PM, "Harald Alvestrand" <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.

Actually, Windows does provide an API for this exact purpose, it's just not
particularly well-suited to what geopriv needed, i.e. getting changing
values. It is good enough for the purpose we are taking about. That isn't
much help for other operating systems, I'll concede.

Applications can send their own DHCP requests...maybe. You need to listen
on port 69 (from memory) for which you have to have the usual special
dispensation, and you have to compete with the OS DHCP agent. It's not
pretty either way.

v2.23.0 | Report a Bug | By Email