Re: [Perc] Double PERC draft 5 and webrtc audio FEC

Cullen Jennings <fluffy@iii.ca> Thu, 29 June 2017 22:43 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0618312EAF2 for <perc@ietfa.amsl.com>; Thu, 29 Jun 2017 15:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 jcOXUd-hxzOU for <perc@ietfa.amsl.com>; Thu, 29 Jun 2017 15:43:51 -0700 (PDT)
Received: from smtp117.ord1c.emailsrvr.com (smtp117.ord1c.emailsrvr.com [108.166.43.117]) (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 10121129B31 for <perc@ietf.org>; Thu, 29 Jun 2017 15:43:50 -0700 (PDT)
Received: from smtp7.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 5DBE9A03D7; Thu, 29 Jun 2017 18:43:45 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 17976A03C4; Thu, 29 Jun 2017 18:43:45 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.55] (d172-219-247-164.abhsia.telus.net [172.219.247.164]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Thu, 29 Jun 2017 18:43:45 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <203ee906-0af0-99ea-994f-2fd36d7fbf6a@gmail.com>
Date: Thu, 29 Jun 2017 16:43:44 -0600
Cc: "perc@ietf.org" <perc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C7F07F1-E4C9-474C-97E5-1CB5D9B9A9AB@iii.ca>
References: <203ee906-0af0-99ea-994f-2fd36d7fbf6a@gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/1WJ3m6bZ46eN2LxiByzjWHxtX0c>
Subject: Re: [Perc] Double PERC draft 5 and webrtc audio FEC
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 22:43:53 -0000

> On Jun 29, 2017, at 1:46 PM, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> wrote:
> 
> Hi all,
> 
> In the new double encryption draft that Cullen has just submitted, it is says:
> 
> 7.3.  FEC
> 
>    The algorithms recommended in [I-D.ietf-rtcweb-fec] for audio work
>    with no additional considerations.
> 
> But in ietf-rtcweb-fec it recommends to use rfc 2198 RTP payload for redundant audio data. The problem is that RED only protects the payload, and any RTP header extension will not be protected. That will prevent RED to work HBH as the receiver end will not be able to recover the OHB and perform the inner crypto on the recovered packet.
> Best regards
> 

Let me just ignore for a second that we disagree on best way to do RED when using SRTP (never mind PERC).  My read of draft-ietf-rtcweb-fec was that 2198 is a "MAY" be used but that the "RECOMMENDED" approach for opus in hybrid mode (which is preferred for WebRTC) was just to use the FEC that is build into Opus.  All the data I have seen suggests that opus FEC outperforms RED in pretty much all ways RED typically gets used so this seems somewhat reasonable. 

But that said, if you think the draft should mention RED, glad to add it. Plus the sentence in the draft probably needs to explain what works means in this context. 


> Sergop
> 
> _______________________________________________
> Perc mailing list
> Perc@ietf.org
> https://www.ietf.org/mailman/listinfo/perc