Re: [rtcweb] Data transfer

[Magnus Westerlund <[e-mail]>]

Hi,

When it comes to the data transfer the discussion we have had back in
the beginning of the summer made it clear that there was clear interest
for an unreliable peer to peer datagram based channel.

Use cases include game data, meta information in conferencing. But it is
for whatever the the JS application have use for it.

When it comes to reliable data the result of the discussion was a bit
more unclear. Some interest existed, but no one was willing to be a
driving proponent to both propose technology and use cases.

When it comes to the unreliable data channel we are awaiting that
draft-cbran-rtcweb-data-00 is updated to try to provide something at
least worth discussing. As the WG has no consensus yet on the details
for solving this channel, any contribution is most welcome.

I agree that when it comes to T.140 it can easily be included as media
format that shall be supported. We have had several suggesting that and
no real objections. One can note that there goes 13 proposals for text
transfer to the dozen.

Maybe the simplest is to make a consensus call on this.

Cheers

Magnus

On 2011-09-16 09:02, Saúl Ibarra Corretgé wrote:
> 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
> 
> 
> 
> _______________________________________________ rtcweb mailing list 
> [e-mail] https://www.ietf.org/mailman/listinfo/rtcweb
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------