Re: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED

"Roni Even" <ron.even.tlv@gmail.com> Thu, 28 June 2012 21:21 UTC

Return-Path: <ron.even.tlv@gmail.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 0160711E8091 for <rtcweb@ietfa.amsl.com>; Thu, 28 Jun 2012 14:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 GGxg6XmA3XrE for <rtcweb@ietfa.amsl.com>; Thu, 28 Jun 2012 14:21:01 -0700 (PDT)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id A94E011E8087 for <rtcweb@ietf.org>; Thu, 28 Jun 2012 14:21:00 -0700 (PDT)
Received: by wgbds11 with SMTP id ds11so503349wgb.1 for <rtcweb@ietf.org>; Thu, 28 Jun 2012 14:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=g9g+evlBD+YebI6nDWgn6H0HjWta+M2Yk7sMPJuaVuA=; b=A1kpdfHG+InZK/K7+cKGwQsR1m3w09Ct4LDcaiW7/Wi22VpH6zRK7rd269Ozk7D4fS jBZn6K+8hIV4on3WE9O86mWgLP2EloPLyPlJbXCVpY0RyccVxgT+H93Mi26Sn8ImcVqX OwvTEX5DuEaV+79Yn3hDv53eOcJF4hxjxrfjTfWK8BsahPQ82goIi5mrLerWQ3SB6KdH RvxO3d8nH7QJLrB4X8kDkOtzzlaOjEedTuBiib+g1FaFTBvbfQDE5v6CpMsENNB9IdKC /08/npsdIP7l+Rlc2HLJcS026BMDZR6KYgFsjZGauZddZafWmtGzGSTIHV2cMYj5hawc 9zFA==
Received: by 10.216.51.206 with SMTP id b56mr2124708wec.9.1340918459587; Thu, 28 Jun 2012 14:20:59 -0700 (PDT)
Received: from RoniE ([109.64.198.75]) by mx.google.com with ESMTPS id d10sm1780483wiy.3.2012.06.28.14.20.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jun 2012 14:20:58 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
References: <4FEAB80A.7040207@ericsson.com> <4FEC0C73.4030709@ericsson.com> <00af01cd553d$b72ce070$2586a150$@gmail.com> <4FEC675B.8080002@ericsson.com>
In-Reply-To: <4FEC675B.8080002@ericsson.com>
Date: Fri, 29 Jun 2012 00:20:39 +0200
Message-ID: <00ec01cd557c$40a42fa0$c1ec8ee0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIWS+mLc/5Xu0n/e00tw8qzpIQ1cwJcOV0LAZIEwWACL3ajTZZNcnkQ
Content-Language: en-us
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED
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: Thu, 28 Jun 2012 21:21:02 -0000

Hi Magnus,
The demo in the interim of what happens in retransmission was not in par
with my experience with any other recovery  methods including receiver based
repair without FEC.
Roni

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] 
Sent: 28 June, 2012 4:17 PM
To: Roni Even
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or
RECOMMENDED

On 2012-06-28 16:52, Roni Even wrote:
> Hi Magnus,
> So using retransmission is at the cost of losing lip synch which is 
> very noticeable. I am not saying that it does not work to do 
> retransmission, my claim that it is not practical and this is why I do 
> not think it is required.

My experience with using this system several times a week for the last two
years says that it is not that noticable. The type of video image
degradations you get from unrepaired burst losses are so much worse.

I also think it is important that we consider the goals. If your goal is a
really high quality telepresence system then this approach is most likely
not usable. But, most WebRTC applications doesn't have that quality
requirements nor the user expectancies to be significantly annoyed at a
short loss of lip sync. The bit-rate savings that RTP retransmission
provides compared to FEC is much more important in my mind.

I think the Google hangout session during the interim showed the importance
of having some video being much higher than having no video or requiring
video with perfect sync with audio. And Justin said, Google Hangout uses
Retransmission.

Cheers

Magnus


> Roni
> 
> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On 
> Behalf Of Magnus Westerlund
> Sent: 28 June, 2012 9:49 AM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or 
> RECOMMENDED
> 
> Hi,
> 
> As Individual I like to state my position.
> 
> We have a video conference system developed by my colleagues used 
> internally at Ericsson that uses RTP Retransmission for video, not for 
> audio with great success. This is implemented such that we actually 
> allow the video to fall behind the audio when packet loss and 
> retransmission is not able to repair in a timely enough fashion. The 
> benefit is minimal overhead and still no loss induced degradations in 
> the video. Yes, we get degradation in form of frame display jittering 
> and short freezes. But those events that are truly visible are rare over
wired networks.
> 
> I am personally convinced that RTP Retransmission is great tool in the 
> toolbox when it comes to improve media quality in many use cases. Yes 
> there are scenarios where RTP retransmission is less efficient. Long 
> RTTs (over
> 200-400 ms) is the primary source of degradations. Compared to FEC it 
> so much more efficient from bandwidth consumption perspective.
> 
> I also think it is important that we have some mandatory to implement 
> tool for making the transport more robust now that we have a consensus 
> that we are not going for a FEC solution in the initial specification.
> 
> Thus my personal position is that RTP Retransmission should be 
> REQUIRED to implement.
> 
> Cheers
> 
> Magnus
> 
> 
> On 2012-06-27 09:36, Magnus Westerlund wrote:
>> WG,
>>
>> We had a discussion at the interim if RTP Retransmission is to be 
>> considered REQUIRED or RECOMMENDED to implement. I would like to see 
>> if we can first have some discussion on this topic before moving on 
>> to see if we can get a consensus here on the mailing list.
>>
>> Please provide your views on this topic.
>>
>> Cheers
>>
>> Magnus Westerlund
>> (As Chair and document editor)
>>
>>
>> ---------------------------------------------------------------------
>> - Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> Färögatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ---------------------------------------------------------------------
>> -
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------