Re: [rtcweb] Data transfer

Hadriel Kaplan <HKaplan@acmepacket.com> Mon, 19 September 2011 06:57 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A86121F8B9E for <rtcweb@ietfa.amsl.com>; Sun, 18 Sep 2011 23:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level:
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHdMKt3Qd2O9 for <rtcweb@ietfa.amsl.com>; Sun, 18 Sep 2011 23:57:52 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3269321F8B91 for <rtcweb@ietf.org>; Sun, 18 Sep 2011 23:57:51 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 19 Sep 2011 03:00:10 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.150]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Mon, 19 Sep 2011 03:00:07 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Randell Jesup <randell-ietf@jesup.org>
Thread-Topic: [rtcweb] Data transfer
Thread-Index: AQHMdpnDuV+LINVU8Uu/KmHCjLRx8w==
Date: Mon, 19 Sep 2011 07:00:07 +0000
Message-ID: <BACD0D94-357F-4E4A-AE8C-10F23468C45C@acmepacket.com>
References: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net> <CALiegfnOx9VeW6vmoHHV2Aopo1ECK7Ud51Lo0o0pAVBi=6LRjQ@mail.gmail.com> <4E7358AC.8030509@ericsson.com> <CALiegfk_Wza-y61N6Scx6dSuT77XwjBnWhGe5wPBt2-zTxfhYA@mail.gmail.com> <4E735FC8.20906@ericsson.com> <4E76C3D2.1010005@jesup.org>
In-Reply-To: <4E76C3D2.1010005@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E5C070E2EC5EE74F8EC0FBE526875646@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Data transfer
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 19 Sep 2011 06:57:53 -0000

On Sep 19, 2011, at 12:23 AM, Randell Jesup wrote:

>> 3. Use TCP over UDP
> This is what I had been assuming we'd do.  It might have been nice to use
> SCTP-over-UDP instead; that would cover more cases without having to drop
> into doing network protocols in javascript for example, but it doesn't
> appear there's an extant open-source example, so it's a hard sell.
> 

I think you'll want to do whatever-shim-transport-it-is in the browser rather than in JS no matter what.  As much as I hate to say it, SCTP over UDP kinda makes sense, given all of it's various modes of operation.  

Whatever gets picked, it needs to support fragmentation at a layer above UDP to make it through various NATs/firewalls/CGNs. 

-hadriel
p.s. why do you say there's no open-source of SCTP?  FreeBSD has it, though it might be out of date;  sctplib is also under LGPL (http://www.sctp.de/sctp-download.html).