Re: [rtcweb] Data transfer

Saúl Ibarra Corretgé <> Fri, 16 September 2011 07:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AC60F21F8BC5 for <>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.642
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pa6+KQNZvfTo for <>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 338A421F8B3F for <>; Fri, 16 Sep 2011 00:00:32 -0700 (PDT)
Received: by (Postfix, from userid 5001) id AD2EAB019A; Fri, 16 Sep 2011 09:02:45 +0200 (CEST)
Received: from [] ( []) by (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?= <>
In-Reply-To: <>
Date: Fri, 16 Sep 2011 09:02:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Olle E. Johansson <>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [rtcweb] Data transfer
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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?


Saúl Ibarra Corretgé
AG Projects