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

Bernard Aboba <bernard.aboba@gmail.com> Thu, 29 June 2017 23:45 UTC

Return-Path: <bernard.aboba@gmail.com>
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 37D2212EAFA for <perc@ietfa.amsl.com>; Thu, 29 Jun 2017 16:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CGrJCJLQjJg6 for <perc@ietfa.amsl.com>; Thu, 29 Jun 2017 16:45:28 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3F8D126BF7 for <perc@ietf.org>; Thu, 29 Jun 2017 16:45:28 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id z22so66493401uah.1 for <perc@ietf.org>; Thu, 29 Jun 2017 16:45:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=amzWvZWHZqLRi7Xi+zopew4IHOh5w4se01WDLooWsTM=; b=VrnmnD+ZfdGXfpWSDJAZloxL2soR5WRGxNGNHZ6HDobOC2UoXVJvooz8h18mNfhwDC AhMnVJNizeu+p5AQevFkB8Yp16hqKC0qjcbwKclyiL7gwbZ0JuFcpPkXF1rsnmg+2A0A PuK1xWwtEMY3nAN77EzdwouGGB8zLqtFgH8azWNLmklIzTq0fUckIBRXJ2AOKHO3aZUs YBKTfHul2fvAAcK/q/bHJxMHHzWIgZE+ZasjfeQ21xBIOUuRDitc5xrKnmnPJtnAUK29 eiYWxWcOyXdB2X87Prdnh5Yfo1hy1PBG0c7PeEk7e3ebx0dyqbJRJric65jPzYZXASUJ oOfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=amzWvZWHZqLRi7Xi+zopew4IHOh5w4se01WDLooWsTM=; b=WUfRyxQ+Ta3OIav+Aq3X4WfQFi0VhU0ZQ/tsz0AO4I9nYw6YJHrtxjZmmN8ppUaSJI YO3FLCfMSIttLLuak6APwhqb8bXWtOVRb0+5r6D7W77Aj6SymclOQG85EN3dIucG5Ml8 tMV9fzM4iBozSiJApMbMLE26wMgTtXvP8aDozkHPLzIvtSA4YX1vyiOCewBCXbI+SoV1 +1x0CFTFNgsGbJZv79G95AQQ/+0aFYbQnWCnn35+dL3rUTd4XPX5Yc79he8eswCfDFp/ lQUYcAEzKrRscOvAsCx2ep+U4JlifOjpimjibR0oB25AuTCy6LUYuhMQCBwQ1vnYfJIj 89zA==
X-Gm-Message-State: AKS2vOx1yX0QzzXEmV89WkGihKYztHI+E1zyRNVqaLZlFioKKH9+R4wd jDRl/06V4LsSFfjxzwUQ6tUTLgteog==
X-Received: by 10.176.18.200 with SMTP id o8mr11354983uac.132.1498779927696; Thu, 29 Jun 2017 16:45:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.74.202 with HTTP; Thu, 29 Jun 2017 16:45:07 -0700 (PDT)
In-Reply-To: <4C7F07F1-E4C9-474C-97E5-1CB5D9B9A9AB@iii.ca>
References: <203ee906-0af0-99ea-994f-2fd36d7fbf6a@gmail.com> <4C7F07F1-E4C9-474C-97E5-1CB5D9B9A9AB@iii.ca>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 29 Jun 2017 16:45:07 -0700
Message-ID: <CAOW+2dunDLGcZ9-AmCaAgttmETThCz6MgWO4CG+HDkjy1j01gg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "perc@ietf.org" <perc@ietf.org>
Content-Type: multipart/alternative; boundary="f403043612ba2fdb90055321e59a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/X5UJi9cLcD_SFy4uxiGbKlSyPKs>
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 23:45:31 -0000

Cullen said:

"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."

[BA]  Opus FEC can't handle burst loss, but RED can.  So if you have burst
loss (quite likely on wireless networks), RED can substantially outperform
Opus FEC.  I realize this would involve use of RED in an *atypical* way,
though.

Also, it's important to compare Opus FEC against concealment.  When that is
done, its benefits do not stand out.

On Thu, Jun 29, 2017 at 3:43 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> > 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
>
> _______________________________________________
> Perc mailing list
> Perc@ietf.org
> https://www.ietf.org/mailman/listinfo/perc
>