IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 26 September 2013 23:56 UTC

Return-Path: <fluffy@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 B326B21E80CB for <rtcweb@ietfa.amsl.com>; Thu, 26 Sep 2013 16:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.562
X-Spam-Level:
X-Spam-Status: No, score=-110.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 MafnrYmuvaeC for <rtcweb@ietfa.amsl.com>; Thu, 26 Sep 2013 16:55:58 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id C24DF21E80CC for <rtcweb@ietf.org>; Thu, 26 Sep 2013 16:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=812; q=dns/txt; s=iport; t=1380239750; x=1381449350; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uGEgpAG8UyG2nngXGgxFrlrm9zMUDgfBiab8/e4OSXk=; b=Xs6Luk7qBbVfOM5+1e4c0ktBtr3LSFgR79ixbY78xLBDl2XGmQxE04oE oHFHhJVo3GNL1CJOi6emm5c44znzS4O4wSyEIv0eDftFLRjrbtASzpXwi mOKzlwRUmRdQJiKCJhHqG6gMY4fsoNiM4v0UWJGOPaZ9f0WZlX50VSr6e A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFACjJRFKtJXG9/2dsb2JhbABbgwc4wRuBGhZtB4IlAQEBAwE6PwULAgEIGB4QMiUCBA4FiAAGvQSPHjMHgx2BAQOXfZF4gWaBPg
X-IronPort-AV: E=Sophos;i="4.90,989,1371081600"; d="scan'208";a="262051468"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 26 Sep 2013 23:55:47 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r8QNtkbs000512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 26 Sep 2013 23:55:46 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.15]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Thu, 26 Sep 2013 18:55:45 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
Thread-Topic: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
Thread-Index: AQHOuH4XwliCL5K4nkCG0uCnhbf1JJnWFfMAgAHIA1CAANji7Q==
Date: Thu, 26 Sep 2013 23:55:45 +0000
Message-ID: <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>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0CDABB@008-AM1MPN1-042.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 26 Sep 2013 23:56:03 -0000

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

v2.23.0 | Report a Bug | By Email