Re: [rtcweb] Transports questions on IPv6

Justin Uberti <juberti@google.com> Wed, 05 March 2014 18:16 UTC

Return-Path: <juberti@google.com>
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 BCD6A1A00BB for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 10:16:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Level:
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_66=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
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 pOBKMKyz-z15 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 10:16:25 -0800 (PST)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0537D1A012A for <rtcweb@ietf.org>; Wed, 5 Mar 2014 10:16:24 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id im17so1400167vcb.19 for <rtcweb@ietf.org>; Wed, 05 Mar 2014 10:16:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Mmhif3hRSLf32twtDDDQl2QWtUGuO7h5oRD4+ejs0CQ=; b=VhYx24uUG3OLjIFBacPsc24xOVnRKFrijST0BnCX3H7B8jUqpri8x2PQDgUxM49ItF NHbVJDj4kHUPXHkhGTDvHW8KSsWnEvjrslMO8YeddKz0Lnkc5H7fn5kU0TBYW5T4TRMp 30wubv5s5gtIglho8I9XErReE7gZqS00/JcvM4OsN1UarhkwV1YkQIxSKQppXJtcqTgI T376iSFldMJuhZ3MefUzxGFQqHr2he7dkSRlWEfLtLvtH6tn2LPZzaVaaAcrcbfNUehH 3ofsFJjDk2x/9fUdV/7gP4NVDNYn5vM45S6ts2Q6zVnPJ/LBWuCr6J/Nifd3XmBAyMgj A+Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Mmhif3hRSLf32twtDDDQl2QWtUGuO7h5oRD4+ejs0CQ=; b=Pb/ySJItt/NNqYZfMUS4syLku6VrbL+d5rkGKFeyBPJrVL77XeI4O66BH97ft/1/13 GytdIwboZR6A4FndAZHR8gZVEv3j+HYX+I9QwsUtVh+VcHPFVCM/5ZrMmMEwLrv/jXRa 6AMnOgM8LGonnoWH3oijOGkXKtZGwBxa8klgUbxgZZqxZODyQYcz1am9zz9KvAoai0SQ gh/QAYigBHBuM4qqfanMzvDx/92Jjzf0LfcIhKYDHjdIzr+3u+ockKaiKcYx+xZMbIHf xa7EH8QNpIGvcEKX1fQ2Qpq9MrfIyEy+qYdbuSuCbgjAqG5Q5bXn1bePNUIXts7mfNv1 i+/A==
X-Gm-Message-State: ALoCoQldnXn9Jv+HLWs6er7XBNpCHAdf5ABqzaIcbS2sdd+zSWHy+8ipuy/7hOhsewXxoh8qOQ24HYk+tUb5uuWc/r3r+YN6K1rCTIq22qo0rwGZ5/5GxevCAyk/Hi2vqQNGP2VHpAEWEnwXVwhap6lly8lQCIH3ZlHKRZN2tcIzOOrsD7VcVa1sK4JuZZmd5vbI5BTzfdHA
X-Received: by 10.58.228.35 with SMTP id sf3mr1209678vec.7.1394043380667; Wed, 05 Mar 2014 10:16:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 5 Mar 2014 10:16:00 -0800 (PST)
In-Reply-To: <5317490E.3090701@viagenie.ca>
References: <CAOJ7v-3vukxXzUN5ttEnJ0dTu2YX=N7qdPDqzy8iXaRwMuH7eQ@mail.gmail.com> <5317490E.3090701@viagenie.ca>
From: Justin Uberti <juberti@google.com>
Date: Wed, 5 Mar 2014 18:16:00 +0000
Message-ID: <CAOJ7v-0SuHwrp4L1buF==6hsFd_uwY786DFeRLeP-bcEykGqyQ@mail.gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary=047d7bdc969c81b35304f3e0040e
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/6fFi5UoPlyYHTmW8bRgrv8pWpR4
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 18:16:28 -0000

On Wed, Mar 5, 2014 at 3:55 PM, Simon Perreault <simon.perreault@viagenie.ca
> wrote:

> 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.
>

Imagine I am a v6-only endpoint. Via IPv6, I allocate 2 ports on the TURN
server, v4 and v6. The remote client is v4-only, and via IPv4 it also
allocates v4 and v6 on its TURN server. So we need to relay to connect v4
and v6. Which path should be preferred?

a) Caller -- TURN/v6 --> TURN Server(Caller, v4 alloc) <-- v4 -- Callee
[ Caller candidate is relay, Callee candidate is host ]
b) Caller -- v6 --> TURN Server(Callee, v6 alloc) <-- TURN/v4 -- Callee
[ Caller candidate is host, Callee candidate is relay ]

I worked this through and I think ICE will choose (b), due to the (G>D?1:0)
tiebreaker, which seems right to me. So no action needed :)



> > 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.
>

I was assuming that WebRTC endpoints will need to do cross-family
allocations, to handle the case where they are talking to a v4-only or
v6-only endpoint and they are not v4- or v6- capable. If so, the transports
draft will need to reference the SSODA work once it becomes a WG item,
since I don't think WebRTC endpoints should create additional sockets to do
cross-family allocations (we have enough sockets already, as shown below).


> > 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
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>