IETF Logo Mail Archive

Re: [rtcweb] Transports: RFC 6062 support

Simon Perreault <simon.perreault@viagenie.ca> Thu, 06 March 2014 09:11 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 3BBC91A018A for <rtcweb@ietfa.amsl.com>; Thu, 6 Mar 2014 01:11:43 -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 0wI5ZN2uwjPS for <rtcweb@ietfa.amsl.com>; Thu, 6 Mar 2014 01:11:33 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 245231A019D for <rtcweb@ietf.org>; Thu, 6 Mar 2014 01:11:30 -0800 (PST)
Received: from porto.nomis80.org (h230.viagenie.ca [206.123.31.230]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 8BBD8403E7; Thu, 6 Mar 2014 04:11:25 -0500 (EST)
Message-ID: <53183BBB.3040409@viagenie.ca>
Date: Thu, 06 Mar 2014 09:11:23 +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: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <CAOJ7v-0-U8ycUYcOwRGxgZVDQmdPMXC4Qt7F+uAn29AGOepX7w@mail.gmail.com> <CABAmMA00xA1TbXsQRYYnuukYyurZzdG8nKr95aT4gxHxQtNiMw@mail.gmail.com>, <CAOJ7v-0xiG-omwmpXm9koakab+EDFo7W=gW+WY4fGS6QVKfALQ@mail.gmail.com> <4A409D06-511D-424D-8285-E38B3E08292D@skype.net> <53177A5E.7030704@viagenie.ca> <AE1A6B5FD507DC4FB3C5166F3A05A4844FABAB0B@TK5EX14MBXC296.redmond.corp.microsoft.com>
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A4844FABAB0B@TK5EX14MBXC296.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/e6ELjSXJ8F2z6A4mZr_3P_q4yHs
Subject: Re: [rtcweb] Transports: RFC 6062 support
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: Thu, 06 Mar 2014 09:11:43 -0000

Le 2014-03-05 20:39, Matthew Kaufman (SKYPE) a écrit :
> TRAM is solving the "without the assistance of the JavaScript" case (finding corporate servers or ISP servers)... I'm sure that some of the larger RTCWEB application providers will be more than capable of figuring out which TURN servers will be best to assign to their customers.

Right. So the "TCP on the short legs, UDP on the long leg" argument
currently only holds for large application providers.

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

v2.23.0 | Report a Bug | By Email