Re: [rtcweb] Transports questions on IPv6

Simon Perreault <simon.perreault@viagenie.ca> Wed, 05 March 2014 15:56 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 858361A023D for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 07:56:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 Xv7T8osEFkt5 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 07:56:03 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 971031A022E for <rtcweb@ietf.org>; Wed, 5 Mar 2014 07:56:03 -0800 (PST)
Received: from porto.nomis80.org (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B2BFF4040A for <rtcweb@ietf.org>; Wed, 5 Mar 2014 10:55:59 -0500 (EST)
Message-ID: <5317490E.3090701@viagenie.ca>
Date: Wed, 05 Mar 2014 15:55:58 +0000
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-3vukxXzUN5ttEnJ0dTu2YX=N7qdPDqzy8iXaRwMuH7eQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-3vukxXzUN5ttEnJ0dTu2YX=N7qdPDqzy8iXaRwMuH7eQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/3TfG1LvRduLIFUBPOwsF6OAbxF4
Subject: Re: [rtcweb] Transports questions on IPv6
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: <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: Wed, 05 Mar 2014 15:56:07 -0000

Since you asked for more...

Le 2014-03-05 14:56, Justin Uberti a écrit :
> which path (v6-to-TURN or v6-from-TURN) should be prioritized?

I'm sorry, I don't understand this question.

> Note also that these v4->v6 or v6->v4 allocations will be dependent on the SSODA work being discussed in TRAM, since this is the only way to allocate v4 and v6 TURN from a single host candidate.

I don't understand what you mean.

> Also worth noting:
> 
> With the current default settings, a single STUN and TURN server, and assuming a dual-stack host with two network interfaces, a PeerConnection with audio, video, and data will generate
> 
> 5 (components) * 4 (local-udp+stun+turn+local-tcp) * 2 (interfaces) * 2 (IP protocols) = 80 candidates

It's....... it's beautiful!

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