Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt

Simon Perreault <simon.perreault@viagenie.ca> Tue, 21 January 2014 15:06 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC02D1A02BB for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 07:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 sQgxORiExggO for <pntaw@ietfa.amsl.com>; Tue, 21 Jan 2014 07:06:30 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA0D1A0166 for <pntaw@ietf.org>; Tue, 21 Jan 2014 07:06:30 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 471F840367 for <pntaw@ietf.org>; Tue, 21 Jan 2014 10:06:30 -0500 (EST)
Message-ID: <52DE8CF5.1050609@viagenie.ca>
Date: Tue, 21 Jan 2014 10:06:29 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: pntaw@ietf.org
References: <9F33F40F6F2CD847824537F3C4E37DDF17CBE35E@MCHP04MSX.global-ad.net> <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
In-Reply-To: <CALDtMr+_jUti7BNVRubuncCU9rAZx4NqM3Ru1jtEbRF+uBMMEw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pntaw] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:06:32 -0000

Le 2014-01-21 04:37, Oleg Moskalenko a écrit :
> If the browsers are supporting the error 300, then a TURN server
> administrator can relatively easy set a load balancing scheme. If
> the browsers do not support it, then it becomes a more complicated
> issue and an implementation-dependent procedure.
>
> As far as I know, no current browser supports 300 response from TURN
> server. It would be very nice if the TURN server administrator could
> rely on that feature.

+1

In addition, I believe the missing keyword to understand the importance 
of this is "anycast".

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca