Re: [Covidimpacts-workshop] Forward Error Correction Qs

Mirja Kuehlewind <ietf@kuehlewind.net> Fri, 13 November 2020 11:25 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: covidimpacts-workshop@ietfa.amsl.com
Delivered-To: covidimpacts-workshop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1203A0E80; Fri, 13 Nov 2020 03:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WGINmtvLfbY; Fri, 13 Nov 2020 03:25:27 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68523A0E7F; Fri, 13 Nov 2020 03:25:26 -0800 (PST)
Received: from p200300dee707b600088b61e08819d0e9.dip0.t-ipconnect.de ([2003:de:e707:b600:88b:61e0:8819:d0e9]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1kdXCg-0002QD-Qj; Fri, 13 Nov 2020 12:25:18 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <B5215A9F-8B5F-4A6B-AD1E-58689519CFC2@iii.ca>
Date: Fri, 13 Nov 2020 12:25:17 +0100
Cc: "Livingood, Jason" <Jason_Livingood=40comcast.com@dmarc.ietf.org>, "covidimpacts-workshop@iab.org" <covidimpacts-workshop@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E36430C8-2A5F-4C46-A48E-BAFDD3A9F71B@kuehlewind.net>
References: <6262F72F-387A-47C3-9CCD-89D5C98CC166@cable.comcast.com> <B5215A9F-8B5F-4A6B-AD1E-58689519CFC2@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1605266727;4f40a47f;
X-HE-SMSGID: 1kdXCg-0002QD-Qj
Archived-At: <https://mailarchive.ietf.org/arch/msg/covidimpacts-workshop/iJbPABQFG_njcYqV4Y34fNcZOnA>
Subject: Re: [Covidimpacts-workshop] Forward Error Correction Qs
X-BeenThere: covidimpacts-workshop@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: COVID-19 Network Impacts Workshop <covidimpacts-workshop.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/covidimpacts-workshop>, <mailto:covidimpacts-workshop-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/covidimpacts-workshop/>
List-Post: <mailto:covidimpacts-workshop@iab.org>
List-Help: <mailto:covidimpacts-workshop-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/covidimpacts-workshop>, <mailto:covidimpacts-workshop-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2020 11:25:29 -0000

So you say the reaction to too few bandwidth was sending more data...?

Is the FEC fixed or is that somehow adopted dynamically?



> On 13. Nov 2020, at 04:55, Cullen Jennings <fluffy@iii.ca> wrote:
> 
> 
> To get a bit more specific about the webex FEC bandwidth …
> 
> I’ll talk about webex here but the the situation is similar for the other major web conferencing vendors. Note there is a lots of fine print to this… The amount of FEC bits that are  allocated is regularly changed and tuned (all the major vendors do this) and varies by things like geo, customer type, how much coffee the developers got, which version of of the product, A/B testing, and so on. What I am describing here would be the case for a significant portion of webex traffic in later summer / early fall time ranges. 
> 
> The audio codec is opus and the video codec is H.264 or slight variants of that. There are some special case use of AV1 but I'm talking just about the normal cases that are on H.264. This is for the audio / video flowing to and from a webex users desktop or mobile client. WebRTC in browsers is a different story. I’m including retransmission technique in this “FEC” bandwidth even though some people might argue it is not strictly FEC. 
> 
> The combined bandwidth for the audio + the FEC for audio is greater that the bandwidth for the video + the FEC for the video. 
> 
> Yep, I know that is not what most people would expect but it is where things ended up for some good reason, and probably some bad reasons too. The media is typically sent over SRTP which makes it pretty easy to verify theses numbers in wireshark. I don’t plan to do any tutorials on how to reverse engineer webex :-) 
> 
> The amount of audio FEC was not this high before COVID-19. This was added to deal with deteriorating network conditions relative that webex was operating in. I expect the amount of FEC to go down over time thought it is hard to guess what might happen in the short term with currently rising COVID-19 case numbers in many countries. 
> 
> I got asked about if a conference had 8 people and 5 of them had video turned off, was this a total statistic that added all the people with and without video together or something. It is not, it is about the bandwidth going from a conference to a single user that has both audio and video turned on. 
> 
> 
> 
> 
>> On Nov 12, 2020, at 9:37 AM, Livingood, Jason <Jason_Livingood=40comcast.com@dmarc.ietf.org> wrote:
>> 
>> In Wednesday’s session I was intrigued by Cullen’s comment about forward error correction (FEC) potentially leading to audio bitrates for conferencing exceeding that of video. I was curious if that potentially pertained to add A/V codecs or just one specific codec? And can this be quantified?
>>  
>> Lastly, if this is indeed as critical an issue as it seemed, how does the feedback loop to the codec developers work so that there could be a software fix leading to a real world improvement?
>>  
>> Thanks!
>> Jason
>> -- 
>> Covidimpacts-workshop mailing list
>> Covidimpacts-workshop@iab.org
>> https://www.iab.org/mailman/listinfo/covidimpacts-workshop
> 
> -- 
> Covidimpacts-workshop mailing list
> Covidimpacts-workshop@iab.org
> https://www.iab.org/mailman/listinfo/covidimpacts-workshop