Re: [rtcweb] Data transfer

"Timothy B. Terriberry" <tterriberry@mozilla.com> Mon, 19 September 2011 04:34 UTC

Return-Path: <prvs=236d0731c=tterriberry@mozilla.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 70CEE21F8B52 for <rtcweb@ietfa.amsl.com>; Sun, 18 Sep 2011 21:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.955
X-Spam-Level:
X-Spam-Status: No, score=-0.955 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, MISSING_HEADERS=1.292]
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 GATisPZ0qpsb for <rtcweb@ietfa.amsl.com>; Sun, 18 Sep 2011 21:34:17 -0700 (PDT)
Received: from mxip3i.isis.unc.edu (mxip3i.isis.unc.edu [152.2.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id E955221F8B4D for <rtcweb@ietf.org>; Sun, 18 Sep 2011 21:34:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEACfGdk6sGgRa/2dsb2JhbABChFWhYoF6gVMBAQQBIxVAAQULCxoCBRYLAgIJAwIBAgFFEAMBBwKHc6QhkECBLIQ7gREEh2+QZRKMMA
X-IronPort-AV: E=Sophos;i="4.67,550,1309752000"; d="scan'208";a="184450180"
Received: from mr2a.isis.unc.edu (HELO smtp.unc.edu) ([172.26.4.90]) by mxip3o.isis.unc.edu with ESMTP; 19 Sep 2011 00:36:36 -0400
X-UNC-Auth-As: tterribe
X-UNC-Auth-IP: 69.181.137.38
Received: from [172.17.0.5] (c-69-181-137-38.hsd1.ca.comcast.net [69.181.137.38]) (authenticated bits=0) by smtp.unc.edu (8.14.4/8.14.3) with ESMTP id p8J4aXIW021949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rtcweb@ietf.org>; Mon, 19 Sep 2011 00:36:36 -0400 (EDT)
Message-ID: <4E76C6D0.6090506@mozilla.com>
Date: Sun, 18 Sep 2011 21:36:32 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101120 Gentoo/2.0.10 SeaMonkey/2.0.10
MIME-Version: 1.0
CC: rtcweb@ietf.org
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>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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 04:34:17 -0000

> There are many other uses of peer-to-peer data, such as file-transfer
> during
> chat(you want reliable or you get to re-invent a reliable protocol over
> UDP),

Perhaps this should be added as a use-case? It has strong implications 
for the congestion control algorithm, as discussed at the interim 
telecon: you can have an arbitrarily large amount of data to send as 
fast as your pipe can carry it, and that has to compete with the media 
traffic.