Re: [rtcweb] Data transfer

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 16 September 2011 07:00 UTC

Return-Path: <saul@ag-projects.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 AC60F21F8BC5 for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level:
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
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 Pa6+KQNZvfTo for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 338A421F8B3F for <rtcweb@ietf.org>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id AD2EAB019A; Fri, 16 Sep 2011 09:02:45 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id D07CDB019A; Fri, 16 Sep 2011 09:02:32 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
In-Reply-To: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net>
Date: Fri, 16 Sep 2011 09:02:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4D8FAAB-51AD-407B-8A49-3BD8C234AB98@ag-projects.com>
References: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net>
To: Olle E. Johansson <oej@edvina.net>
X-Mailer: Apple Mail (2.1084)
Cc: 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: Fri, 16 Sep 2011 07:00:32 -0000

Hi Olle,

On Sep 16, 2011, at 8:32 AM, Olle E. Johansson wrote:

> A comment on the list made me go back and re-read the charter. One thing I had missed is the data transfer part of rtcweb.
> 
> "The goal is to enable innovation on
>   top of a set of basic components.  One core component is to enable
>   real-time media like audio and video, a second is to enable data
>   transfer directly between clients."
> 
> Most of the discussions on the list has been about the media. What are the ideas for data transfer? Applications?
> 

Maybe I arrived a bit late to the party ;-) but so far I've seen discussions mainly around RTP (and related) media.

> To me, this seems like an interesting feature. If it's a plain data transfer session, a bidirectional session, it's a way to open a session from Javascript to any server, acting as an rtcweb client, which is different from the current sandbox model. I could have missed this discussion, but if not, I think this is an interesting topic to bring up.
> 
> Another note, which I think is purely a mistake, is to forget realtime text - T.140 and just state audio and video. The T.140 users are natural early adoptor users of rtcweb.
> 

I can think of another use case for "data transfer": MSRP. A browser looks looks like a good place for having IM sessions over MSRP. Supporting file transfers would also be awesome, and MSRP is just a TCP pipe where data flows, so maybe this "data transfer" layer is the right place to do this?


Regards,

--
Saúl Ibarra Corretgé
AG Projects