[nwcrg] Fwd: Protocol Action: 'WebRTC Forward Error Correction Requirements' to Proposed Standard (draft-ietf-rtcweb-fec-10.txt)

Marie-Jose Montpetit <marie@mjmontpetit.com> Tue, 16 July 2019 21:26 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 76109120136 for <nwcrg@ietfa.amsl.com>; Tue, 16 Jul 2019 14:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=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=mjmontpetit-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id c-bWUStZ3b_D for <nwcrg@ietfa.amsl.com>; Tue, 16 Jul 2019 14:26:25 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 7C26512007C for <nwcrg@irtf.org>; Tue, 16 Jul 2019 14:26:25 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id k8so42472933iot.1 for <nwcrg@irtf.org>; Tue, 16 Jul 2019 14:26:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:date:message-id:subject:to; bh=S9yJA9/pRVuGUMUXF2+1mJJV5HV3ilyvnvVTqxzZb9k=; b=zrnF9BXHcK1LWFsUXcyQGGj7ZyqJlkXnXVoH6K5xk04TdiFOgyhtws940F9cXDu4rD BUmtVfxv06/NN4LCYFWsM05N1TkPJw8t0AFslXyBT4JHj9aLrzukTyYjQoXZ+1su9wou 8FJvxDaVn5FpSuws2B+Sm3pKnA6p2o7hrBlcW2oRduPxtAQIuQj9T9yTmzn+PZv/vF5l 0F+REGASqR7U4g8GUIDW0q64lYA24DGji4TrH3q0foQK/NCqTIwiUrA+diaoGu3KmdAt 5pbCugIIyEv3qYjFD8NqNE0+AMrySjpChJBCi7Yt/5YwnDiBcCW7cY2zE9FplWJVKM3E bNJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=S9yJA9/pRVuGUMUXF2+1mJJV5HV3ilyvnvVTqxzZb9k=; b=XGHhN6KSGCS9NrR6vekMG0g8vsxy1G3hXB0Nz9rLqGaCB/5vnHiSySVZ/X+cYKRAlb j0uTkWxs5VCJHus7o8D1jVNQ8IYz52XCSR/xCzH/S5r7S2wepGuPYlgJpVd9zm7TGy4w 5QmgHqlMXId3JP0jTiQdKM+S2LgVMwvUTMC0DtGQcX502celgTj7kw3cGi8650Mf2fE9 v0gBSYnsx179wdYaevS8snoAiqCes5vFbfBzijeL/HSXR5W+pby1TPE4xxckK1a4zR6z AXOy9mjWvZSHd9ZaCF4SRda1MUHnmtdYVY0zQIA0jJ3S9uOtIvmMwn8W8FWz9yMrvRT0 v5VQ==
X-Gm-Message-State: APjAAAWWZYxWw6V0LSZLPjgIkdrL1HW5eN4aUs/K/sIwEmuFaiSLHypA E/Z+sxL4zQshUO4LnrW9czO4rlCD/kdHHnz0+1dYPQ==
X-Google-Smtp-Source: APXvYqw2M4j42KbYUpAYN6tUhn2j5PwezMFTPawWjG6p4JBQeYauFxCOPO1qAB2N95botWZFHPn7Hsg8uAcxuOkLEfk=
X-Received: by 2002:a5d:948a:: with SMTP id v10mr3185203ioj.103.1563312384490; Tue, 16 Jul 2019 14:26:24 -0700 (PDT)
Received: from 895490483151 named unknown by gmailapi.google.com with HTTPREST; Tue, 16 Jul 2019 14:26:23 -0700
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
MIME-Version: 1.0
Date: Tue, 16 Jul 2019 14:26:23 -0700
Message-ID: <CAPjWiCQTC4ShsGrCP2s4KnqR85cYy4FVm9UdmX+1gOL0t3q64Q@mail.gmail.com>
To: nwcrg <nwcrg@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000005a0b39058dd30751"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/7VLVrmPdTG-474ICd62Wg4t9GBc>
Subject: [nwcrg] Fwd: Protocol Action: 'WebRTC Forward Error Correction Requirements' to Proposed Standard (draft-ietf-rtcweb-fec-10.txt)
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 21:26:27 -0000

Of interest to our group

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory

> ---------- Forwarded message ---------
> From: The IESG <iesg-secretary@ietf.org>
> Date: Tue, Jul 16, 2019 at 14:12
> Subject: Protocol Action: 'WebRTC Forward Error Correction Requirements'
> to Proposed Standard (draft-ietf-rtcweb-fec-10.txt)
> To: IETF-Announce <ietf-announce@ietf.org>
> CC: Ted Hardie <ted.ietf@gmail.com>om>, <adam@nostrum.com>om>, <
> rtcweb-chairs@ietf.org>gt;, <draft-ietf-rtcweb-fec@ietf.org>rg>, <
> rtcweb@ietf.org>gt;, The IESG <iesg@ietf.org>rg>, <rfc-editor@rfc-editor.org>
> The IESG has approved the following document:
> - 'WebRTC Forward Error Correction Requirements'
>   (draft-ietf-rtcweb-fec-10.txt) as Proposed Standard
> This document is the product of the Real-Time Communication in WEB-browsers
> Working Group.
> The IESG contact persons are Adam Roach, Alexey Melnikov and Barry Leiba.
> A URL of this Internet Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-fec/
> Technical Summary
>    In situations where packet loss is high or perfect media quality is
>    essential, Forward Error Correction (FEC) can be used to proactively
>    recover from packet losses.  This specification provides guidance on
>    which FEC mechanisms to use, and how to use them, for WebRTC
>    implementations.
> Working Group Summary
>   The working group support for the document was generally high.  One
>   issued was raised in working group last call regarding the
>   effectiveness of the Opus internal FEC mechanism.  The document
>   currently states that it is RECOMMENDED for protection against
>   individual packet loss and that other methods are needed for
>   multi-packet protection.  This mirrors text in RFC 6716 and
>   accurately captures a limitation of the in-band FEC mechanism.  The
>   question of effectiveness is thus tightly tied to the loss pattern.
>   While data on this was presented, there was no evident consensus to
>   update the requirement, so the recommendation from RFC 6716 was
>   retained.
> Document Quality
>   This document appears to have the support of the relevant development
>   community and will likely be implemented and deployed.  Reviews by Mo
>   Zanaty, Magnus Westerlund, and Bernard Aboba were particularly helpful.
> Personnel
>   Ted Hardie is the Document Shepherd. Adam Roach is the Responsible Area
>   Director.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce