IETF Logo Mail Archive

Re: [rtcweb] [tram] TURN permissions for private ips

Philipp Hancke <fippo@goodadvice.pages.de> Wed, 05 August 2015 22:20 UTC

Return-Path: <fippo@goodadvice.pages.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE941ACDDF; Wed, 5 Aug 2015 15:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YDSOyEcXksq1; Wed, 5 Aug 2015 15:20:03 -0700 (PDT)
Received: from lo.psyced.org (lost.in.psyced.org [188.40.42.221]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 265501ACDDE; Wed, 5 Aug 2015 15:20:02 -0700 (PDT)
Received: from [192.168.1.202] (71-94-211-114.static.knwc.wa.charter.com [71.94.211.114]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t75MKAHQ028790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 6 Aug 2015 00:20:13 +0200
Message-ID: <55C28C05.1000901@goodadvice.pages.de>
Date: Wed, 05 Aug 2015 15:19:49 -0700
From: Philipp Hancke <fippo@goodadvice.pages.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Simon Perreault <sperreault@jive.com>, Justin Uberti <juberti@google.com>
References: <20150805130607.20844.70680.idtracker@ietfa.amsl.com> <CABcZeBMWVU9a1_e_47qddA04WhXG55QYzFA=dTrYgi+DuLQhKA@mail.gmail.com> <55C24293.5000603@cs.tcd.ie> <55C24C09.8020404@goodadvice.pages.de> <55C256C8.80606@jive.com> <CAOJ7v-3hyFhHiFq4eujLznXtehkUSxZati8YZ23o-RPLH=J5zg@mail.gmail.com> <55C287A4.8050600@jive.com>
In-Reply-To: <55C287A4.8050600@jive.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/wbMJDPHSMNMftEyW6GtTF6UFaqs>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [rtcweb] [tram] TURN permissions for private ips
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 05 Aug 2015 22:20:05 -0000

Am 05.08.2015 um 15:01 schrieb Simon Perreault:
> Le 2015-08-05 17:35, Justin Uberti a écrit :
>> I am somewhat sympathetic to that, but given that there is measurable
>> downside here - extra candidate pairs that take time to check - can you
>> supply a concrete example of where the client choosing not to pair a
>> TURN candidate with a RFC1918 address would cause a problem?
>
> I can't!
>
> Philipp's proposal certainly does make practical sense when you consider
> it as an ugly optimization hack rather than something that is necessary
> to make things work. Phrase it so that this is clear and I'll be all for
> it. :)

incidentally, that's how I came up with it a while back:
https://code.google.com/p/webrtc/issues/detail?id=4634
:-)

v2.23.0 | Report a Bug | By Email