IETF Logo Mail Archive

Re: [rtcweb] FEC for audio?

"Timothy B. Terriberry" <tterriberry@mozilla.com> Tue, 20 May 2014 13:49 UTC

Return-Path: <tterriberry@mozilla.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3D81A0460 for <rtcweb@ietfa.amsl.com>; Tue, 20 May 2014 06:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.929
X-Spam-Level:
X-Spam-Status: No, score=-3.929 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 mR7Wj_zxjC2m for <rtcweb@ietfa.amsl.com>; Tue, 20 May 2014 06:49:19 -0700 (PDT)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id D131E1A06EF for <rtcweb@ietf.org>; Tue, 20 May 2014 06:49:19 -0700 (PDT)
Received: from [172.17.0.43] (50-78-100-113-static.hfc.comcastbusiness.net [50.78.100.113]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id EA277F2AD9 for <rtcweb@ietf.org>; Tue, 20 May 2014 06:49:18 -0700 (PDT)
Message-ID: <537B5D5E.2020402@mozilla.com>
Date: Tue, 20 May 2014 06:49:18 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 SeaMonkey/2.26
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <CAOJ7v-1qEpkWShmw1SQKh4_BLKycF=egu42TS9o9+Smtof36pg@mail.gmail.com> <CAJrXDUESUa-xm9y22OAVKAw5z=WnkY4-X6XFZOoXwvkMoDnaoQ@mail.gmail.com> <537A6190.4060709@mozilla.com> <CAOJ7v-2mb6DkakaEWMxJwqqLSePb7NrOcF-DSycW-CftBGdmcA@mail.gmail.com> <CAOJ7v-1YxHhVm8NE4H3ZkCuOtN4CsUgQoiV1GN3w3NKRWhqWMw@mail.gmail.com> <537AACDA.20603@mozilla.com> <CAOJ7v-3Qi7=jt__BKUfzaBZTfTZ=bdHuzskeRpnbDRbOUYxpGA@mail.gmail.com>
In-Reply-To: <CAOJ7v-3Qi7=jt__BKUfzaBZTfTZ=bdHuzskeRpnbDRbOUYxpGA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/6G5yPwu_gYoYg9NTGhsFfMP1S4A
Subject: Re: [rtcweb] FEC for audio?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 20 May 2014 13:49:21 -0000

Justin Uberti wrote:
> I don't think we would send a standalone FEC packet, given the overheads
> - I would expect we would use RFC 2198 encoding and send 5109 FEC as
> piggyback on the 'next' audio packet, similar to how I understand the
> internal FEC works. This would have (5 + 10 + 4) * 8 = 152 bits of
> overhead per packet, or ~8 Kbps when using 20 ms frames.

Yes, that would be much better.

v2.23.0 | Report a Bug | By Email