Re: [rtcweb] Coding for rtcweb

Frank Fitzek <ff@es.aau.dk> Wed, 29 May 2013 19:08 UTC

Return-Path: <ff@es.aau.dk>
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 0D4CC21F8D70 for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 12:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level:
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, HELO_EQ_DK=1.009]
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 u9v2JPQjfqjv for <rtcweb@ietfa.amsl.com>; Wed, 29 May 2013 12:08:23 -0700 (PDT)
Received: from ad-exchedge02.aau.dk (ad-exchedge03.aau.dk [130.225.194.128]) by ietfa.amsl.com (Postfix) with ESMTP id A27B221F9746 for <rtcweb@ietf.org>; Wed, 29 May 2013 12:08:22 -0700 (PDT)
Received: from AD-EXCHHUB2-1.aau.dk (172.25.14.38) by ad-exchedge03.aau.dk (130.225.194.128) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 29 May 2013 21:08:13 +0200
Received: from [192.168.2.107] (93.220.68.28) by smtp.aau.dk (172.25.14.35) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 29 May 2013 21:08:14 +0200
Message-ID: <51A6521D.7080301@es.aau.dk>
Date: Wed, 29 May 2013 21:08:13 +0200
From: Frank Fitzek <ff@es.aau.dk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jonathan DETCHART <jonathan.detchart@isae.fr>
References: <51A4E78C.3050500@es.aau.dk> <51A5CCDB.6030601@isae.fr>
In-Reply-To: <51A5CCDB.6030601@isae.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [93.220.68.28]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Coding for rtcweb
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: Wed, 29 May 2013 19:08:29 -0000

Jonathan,

great so lets sit down and see how we can collaborate on this. Let us 
know when you are in Berlin as we are there for the whole period. We can 
sit down with Morten and see how to work towards real time support.

Should we aim to present something at the rtcweb meeting to the group to 
talk about the coding potential?

In the end it is all about running code.

All the best and see you in Berlin

FF


On 05/29/2013 11:39 AM, Jonathan DETCHART wrote:
> Hi Frank,
>
> Glad to see ISAE is not the only company which wants to combine 
> network coding and webrtc.
> As I said in Orlando, we integrated our network coding library 
> (Tetrys) inside both VLC RTC modules.
> We just encapsulate RTP packets inside Tetrys packets (application 
> layer) at the sender, and do the reverse operation at the receivers.
>
> We also work on the integration of NC in webrtc.
> We saw that webrtc already integrates a FEC mechanism (you can find 
> the sources in the rtp_rtcp module). We would like to estimate if NC 
> could improve webrtc performance.
>
> We will attend Berlin meeting and we'll be happy to discuss with you 
> about our proposal to assess whether it is possible to converge 
> towards compilant implementations.
>
> So, we will be happy to participate to the discussion in Berlin.
>
> Best regards,
> Jonathan
>
> Le 28/05/2013 19:21, Frank Fitzek a écrit :
>> Dear all,
>>
>> I attended the meeting in Orlando and heard about your activities. I 
>> was highly motivated to follow this activity closer and plan to 
>> attend again in Berlin.
>>
>> In our research group we are interested in P2P in combination with 
>> coding, namely network coding. I scanned the documents but could not 
>> find anything related yet. We have a network coding library and plan 
>> to integrate it to webrtc. We plan to have a running system in autumn 
>> for the Vancouver meeting.
>>
>> Are there any other people in this group that look into similar 
>> directions?
>>
>> Looking forward to start a discussion here or in Berlin.
>>
>> FF
>>
>