IETF Logo Mail Archive

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

Justin Uberti <juberti@google.com> Fri, 27 September 2013 15:58 UTC

Return-Path: <juberti@google.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 C6AF221F8E40 for <rtcweb@ietfa.amsl.com>; Fri, 27 Sep 2013 08:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 YM-9cTzjJKJZ for <rtcweb@ietfa.amsl.com>; Fri, 27 Sep 2013 08:58:47 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4FE21F9123 for <rtcweb@ietf.org>; Fri, 27 Sep 2013 08:58:47 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id tp5so4275249ieb.26 for <rtcweb@ietf.org>; Fri, 27 Sep 2013 08:58:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=iXEuoljB7kpdGsGp2MlRXkWJo/mvEUIlLYeSusUQG7s=; b=G0r8HgZGjhBK/9EYLXSDXcp9wuuEkcJbnYKxIj3r8wVkAVUht+99LFchTH9SCkNLdf 7OfiLBYuDVKg0NThssec2C3J1OcJVRMlup7ZNdk+r9YGTEo6jJIZNZF8xPEi/gKBLOFn sUsyw/coviX6FxmG5IDs3FiDnbcBYICLdU4xX3MT8m6bL4SHVS1n0bONhqUhih8j7diP 1q27A6A3Iu+mdz4Lok/67pwrB748qmwupysTZEeqcEcFLWy10Y3HUJbFaB6BL4tYOQO+ Q20m6ok0B8Hbv0S+CcUPn5zCjen2nAfvz9koNPHZ1+GVzmm0BqEPfreW6g215lFzhlBr KQKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=iXEuoljB7kpdGsGp2MlRXkWJo/mvEUIlLYeSusUQG7s=; b=F9u2EQvTWOvWe5eQjq6DkSKpYJ5utOuyU3FE7UB+MvgNM7CrIqGkunSz8TdtWxEoNt sV2//WEvwh4JlsTKeWWF9O0Ji99NB0KFK/qlgtCi8T/yZAQhisLlhUZA+tdYjLSL3ffp e9I1M+zzHzwaarBREQQEZxcykIIFyo7hT8LmiiKY02DaIfrT+lIYA5JmzAelUKei05Wa 0/irgeMpmRwCqzUVXZStqObMwvTW2YMp7SBhTM+xGBi/yeuI5rTkyteqIbjwPtRCqW52 hWxOYmDYNagBxcwAErwux5YxHJweU/XCr+GZLLDKVhek30nenz+LZrwMCH1NPgvRJCg3 mo+Q==
X-Gm-Message-State: ALoCoQkIQCA7mcJStsv+2MIqLIfbwNzVslvSYgmjLqw1KqCszlL7EtKDmwsiqCyppIiLEsdn4yfwxw3HhfbWl9p0LmhhT3ckN1PvQeG8tQZS/azDlJpCCG4iNTGD36lSrkdMlogaISemRmpuxl6c06EohJxH7SChMRLxTwuy8kfotcowA8/KBsN5f0qY7KnEtxML/1EkKtex
X-Received: by 10.42.97.71 with SMTP id m7mr6993056icn.33.1380297525639; Fri, 27 Sep 2013 08:58:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.12.104 with HTTP; Fri, 27 Sep 2013 08:58:25 -0700 (PDT)
In-Reply-To: <9304FCD1-7727-4F98-A810-F75D48769128@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> <E44893DD4E290745BB608EB23FDDB7620A0CDABB@008-AM1MPN1-042.mgdnok.nokia.com> <9304FCD1-7727-4F98-A810-F75D48769128@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 27 Sep 2013 08:58:25 -0700
Message-ID: <CAOJ7v-00g+tCDoV2_4sL5mwk6vHJRpM-TOX9Xv8C_ayvfMGhHA@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="20cf303bf958b364f404e75f8f88"
Cc: "rtcweb@ietf.org" <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: Fri, 27 Sep 2013 15:58:47 -0000

Agree. I still think that extending PAC files to include TURN information
is the right way to go.

PAC files can already be discovered via DHCP or DNS, there is no need to
reinvent this wheel.


On Thu, Sep 26, 2013 at 4:55 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote:

>
> I think we need to give some advise to the browsers vendors on what they
> should implement to find turn servers
>
> On Sep 26, 2013, at 5:13 AM, "Markus.Isomaki@nokia.com" <
> Markus.Isomaki@nokia.com> wrote:
>
> > Hi,
> >
> > Cullen Jennings wrote:
> >>
> >> I will note that browsers have many ways to learn about HTTP proxies
> from
> >> the network and it seems to me that using some of theses same technique
> >> might also be a good way to learn about TURN servers.
> >
> > I agree. I assume that in enterprises it would be the same people
> managing both of these.
> >
> > Is there something the IETF can or should do about this, or do we just
> assume it will happen? A new DHCP option is something the IETF could easily
> do, but I also doubt how usable that would be.
> >
> > Markus
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email