IETF Logo Mail Archive

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

<Markus.Isomaki@nokia.com> Thu, 26 September 2013 12:13 UTC

Return-Path: <Markus.Isomaki@nokia.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 14FCD21F9FC6 for <rtcweb@ietfa.amsl.com>; Thu, 26 Sep 2013 05:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level:
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pyFeakOcqvgp for <rtcweb@ietfa.amsl.com>; Thu, 26 Sep 2013 05:13:47 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 03BEF21F9FB9 for <rtcweb@ietf.org>; Thu, 26 Sep 2013 05:13:44 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.23]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r8QC6U6h029549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 26 Sep 2013 15:06:31 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.224]) by 008-AM1MMR1-007.mgdnok.nokia.com ([65.54.30.23]) with mapi id 14.03.0136.001; Thu, 26 Sep 2013 12:06:30 +0000
From: Markus.Isomaki@nokia.com
To: fluffy@cisco.com, cb.list6@gmail.com
Thread-Topic: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
Thread-Index: AQHOuH4XwliCL5K4nkCG0uCnhbf1JJnWFfMAgAHIA1A=
Date: Thu, 26 Sep 2013 12:06:29 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0CDABB@008-AM1MPN1-042.mgdnok.nokia.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>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1166CC702@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IoWdnCqQrUspJ5y5HR/Ccg81qyIEN84D/hR6GTUXC26eX7lfXotW/5WQV5Q3W3gT4Oss8ZbiZfl04tcVZz8Rv6/dJS+ytjXbZ7wD8sa9q6Ip22rHZuUoFZY/cGwnexoSojecOUW1jjAN3mknRuD5xEDPXK/TKtnyQt7cX9B4ZzozRoRIoJ4O0rfla9cdCN5ssZ/L8baiWf4CFxVbiiZtd74jGkdrh2fKR8ZkMc4jpcOMVqfzkdqU8guGcxcEXkd+EYJBPubCjw+avxppEicSns8SxCIs7N2AobcsrrPFbiqP4aRvI8E+YrWc8fv0y1Q3kg==
x-originating-ip: [10.236.13.87]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
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: Thu, 26 Sep 2013 12:13:53 -0000

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.30.2 | Report a Bug | By Email | System Status