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 21:42 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 9F6D121E8054 for <rtcweb@ietfa.amsl.com>; Fri, 27 Sep 2013 14:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level:
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[AWL=0.094, 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 Y1O5738GKM9M for <rtcweb@ietfa.amsl.com>; Fri, 27 Sep 2013 14:42:55 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E64CC21E808C for <rtcweb@ietf.org>; Fri, 27 Sep 2013 14:42:41 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id x13so5346632ief.1 for <rtcweb@ietf.org>; Fri, 27 Sep 2013 14:42:41 -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=PwtKU3Y4NL2wHWsuNbPZbovsgn4lIKJ7oTWeiO2tutY=; b=dydje3cx4abjxHQpZFtRlhI544MHEA3wdrFS8MAjzVAG8wHqwT7XjDGlyvAbCAIpmP BC3JNtq6W/lJPA37ycmHzg/+yMCS7D+bD8gUB9cNj1pz/LX0NUGW3iST2J0qBM4h74DX TnBhYoApl2H0iI4K0+l3rGMiq3/rk8fB71ug0YP4L/zXa9NSzmqt+TgfroTLSMZEMAj6 bL0wqpYvey531smhB5Q/pkrFEVCAdC7rAw+eVLAFdHPZQ3SGp/WAsm7sAvS4t7l7BvQc neTWV9ZXHpqU6FYdA2nFSCPK+gd3khslDUtC4KLYrbz8YAJL2VboxKvmugeAZreIpy34 wfzQ==
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=PwtKU3Y4NL2wHWsuNbPZbovsgn4lIKJ7oTWeiO2tutY=; b=USYHHgACqpttQ4dlM9MZXcMYS8qksQBSe3Wp8JX5Iy325B/fV1BwCGq6fRC/F/PkU4 KAXpVIX7/t1uhdvnpR0cwh16IqU0L6fqUSo+9AMgB7x/wIMJMlgRqo/UlUiZKhjWKCm6 53wXPsHx5aHcDGX0WQ66AGAy2HJvXWSJt8b/U+x9xaVy7MxTBx7so15Un2f+8/havowb vuQzBComigtJDIBV6lLfvzwcrX1B6DdRNr/f8fv0cPjmdwDkIz9hmJBwgV7bPyJ1MQcA scmIPzS4/+Noyt68SU3ngBWRwHp4aq1qF683zdoDVrdvfblJrW9V/IcgbdiyyKptotzB 1weg==
X-Gm-Message-State: ALoCoQkTad+rltVFuGzDl5n0Cw8uxBiSbQ6gECEMVPGSOwKIq+oU7Qe4sAaF01ulcHrFypxrcRASWdtlanBBlV4RZcCUIMk0y8zM0Hzugi2+X7aDhhA590zgfzgrhfSym8I8tAmG42d5lssKppb62Z9gy25pXvBiI+1g3BnGz8V+sHRFQpoQVJAOFiBllVffywbAF0vzqAcS
X-Received: by 10.50.13.104 with SMTP id g8mr4192570igc.30.1380318161375; Fri, 27 Sep 2013 14:42:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.12.104 with HTTP; Fri, 27 Sep 2013 14:42:21 -0700 (PDT)
In-Reply-To: <FCBEDCB500188C488DA30C874B94F80E1BFCD813@xmb-rcd-x03.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> <CAOJ7v-00g+tCDoV2_4sL5mwk6vHJRpM-TOX9Xv8C_ayvfMGhHA@mail.gmail.com> <FCBEDCB500188C488DA30C874B94F80E1BFCD813@xmb-rcd-x03.cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 27 Sep 2013 14:42:21 -0700
Message-ID: <CAOJ7v-1oGnFg+_uqhn7uZFLtK4sRF-W7bFYmCQxPhn2yEnRtpg@mail.gmail.com>
To: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
Content-Type: multipart/alternative; boundary="089e013c69c6afb54a04e7645daf"
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 21:42:55 -0000

The business model is the same as for HTTP proxies. ISPs or enterprises
that want to better control their traffic will pay.


On Fri, Sep 27, 2013 at 12:44 PM, Jeremy Laurenson (jlaurens) <
jlaurens@cisco.com> wrote:

> What is the usual "business model" for this? Assume in most cases the
> servers are hosted by folks who actually have a revenue stream from the app
> that is leveraging the servers.
>
> Do we have some idea as to how the browser folks want to pay for the
> "WebRTC turn tax"?
>
>
>
>
> On Sep 27, 2013, at 11:58 AM, Justin Uberti <juberti@google.com> wrote:
>
> 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
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email