IETF Logo Mail Archive

Re: [payload] Protocol Action: 'RTP Payload Format for Flexible Forward Error Correction (FEC)' to Proposed Standard (draft-ietf-payload-flexible-fec-scheme-18.txt)

Bernard Aboba <bernard.aboba@gmail.com> Thu, 21 March 2019 15:39 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81FA41312CF; Thu, 21 Mar 2019 08:39:45 -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 PlkyfetDOWks; Thu, 21 Mar 2019 08:39:43 -0700 (PDT)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (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 727241312F9; Thu, 21 Mar 2019 08:39:40 -0700 (PDT)
Received: by mail-vs1-xe33.google.com with SMTP id z18so3922569vso.7; Thu, 21 Mar 2019 08:39:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CDkw+/we87BSD2avNI/cbEoaA+IeUgCv6X4eA9z6FlY=; b=jZdhKBftv0We/MxT8mB7eAZTOwpeB5hHaHQp4lkcrNNOIUxYDnILLh4BBFPqdoWcV2 BIyABI6+pFHbop9zqtBpj0fD4MI+wqX61op0SB0AoD3H/3FfG2Hn4rKDCp/0BV75OeVU 0KTNcMyb8Lc6Kl63wnuh4gmy/lYEs6+wSM5HS18uL9ZgL4IevHh0pH71XkOWZgC+VFW2 wFFmqjpt9GlZE+5jmkSIfaHKlZCVeDH/RT2h9UHG8vdsMSYEZHrNREN8xvYQ23R64zOG 8zOmO58U8FalinsA/bbUOfp0XDIhuuSmOHRGTQNFZwjsISRlLK65F2mpt1xWZbvGsxog UVRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CDkw+/we87BSD2avNI/cbEoaA+IeUgCv6X4eA9z6FlY=; b=q6plOFNyaqx/FqeVMgwgYMdjLa/K0j5miyOFSrHRFHd6vAF/MGHABe/2jd2AR5vrpl cw8rnJKOt1tjYURDBX3an/oTQKrfLrBxUZKwBLEO9pDtRyvMS4XCnQoCQ2L6Ig4dE8sS cMZUh6HgzcgWZXWl+bgvyLAp292zzvfxIcgZhEka6X0IambYAQIpNUqdepvATc3AITbP uJ5yXcXOyZpgTFNLk9xj3gpfPn5cAND9Ru264OVCoIRxCCq/Bt9StpUfbhFAk88dGXCe FHxppbB9+PGS/Po2TXOoTzVI1X5aGYwS2fbvLtD2u6IqU5C4S1Abc2Sdi6aNK2h8lmLn MISw==
X-Gm-Message-State: APjAAAU2YQTPkiTvnB0X4w1CMvskKV8zsfw8oV4Y0yrDNcSwqzZUSfmD aS4nqsRN1Hn2iB8ELG8q4UC/5onBAVCdSar1vcaGzw==
X-Google-Smtp-Source: APXvYqzQyU6pZCxVX9qPvaVS4mgEVBjRW8aA1D0uHMmqZNs40mliaKzHVqKYu92dTWoVJUE8pOFfG7ULtQUVjlTUzZ4=
X-Received: by 2002:a67:f41a:: with SMTP id p26mr2438938vsn.140.1553182778805; Thu, 21 Mar 2019 08:39:38 -0700 (PDT)
MIME-Version: 1.0
References: <155315770054.9919.5577297727640600792.idtracker@ietfa.amsl.com>
In-Reply-To: <155315770054.9919.5577297727640600792.idtracker@ietfa.amsl.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 21 Mar 2019 11:39:27 -0400
Message-ID: <CAOW+2dsvLU=LSJCFfsNHFSXkvo7enjr-RFgqjuNFDsqg+xq_MA@mail.gmail.com>
To: payload@ietf.org
Cc: roni.even@mail01.huawei.com, The IESG <iesg@ietf.org>, draft-ietf-payload-flexible-fec-scheme@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cd517005849c8b17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/Z0jxleZM9LLthYeY5D0SbTfGmK4>
Subject: Re: [payload] Protocol Action: 'RTP Payload Format for Flexible Forward Error Correction (FEC)' to Proposed Standard (draft-ietf-payload-flexible-fec-scheme-18.txt)
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2019 15:39:45 -0000

This is broken.

During review, serious issues were found with this document, and we were
working through the required changes with one of the authors (Varun).

Just because the editor decided to ignore the problems doesn't mean they
don't need to be fixed.



On Thu, Mar 21, 2019 at 4:42 AM The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has approved the following document:
> - 'RTP Payload Format for Flexible Forward Error Correction (FEC)'
>   (draft-ietf-payload-flexible-fec-scheme-18.txt) as Proposed Standard
>
> This document is the product of the Audio/Video Transport Payloads Working
> Group.
>
> The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.
>
> A URL of this Internet Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-payload-flexible-fec-scheme/
>
>
>
>
> Technical Summary:
>
> This document defines new RTP payload formats for the Forward Error
> Correction (FEC) packets that are generated by the non-interleaved  and
> interleaved parity codes from source media encapsulated in RTP.   These
> parity codes are systematic codes, where a number of FEC repair packets are
> generated from a set of source packets from one or more source RTP
> streams.  These FEC repair packets are sent in a redundancy RTP stream
> separate from the source RTP stream(s) that  carries the source packets.
> RTP source packets that were lost in   transmission can be reconstructed
> using the source and repair packets that were received.  The
> non-interleaved and interleaved parity codes   which are defined in this
> specification offer a good protection against random and bursty packet
> losses, respectively, at a cost of decent complexity.
>
>
> Working Group Summary:
>
> The document was discussed in the meetings, and on the mailing list. The
> open issues were addressed and there are no open issues; there was
> consensus on the content of the document.
>
> Document Quality:
>
> The payload was developed by members from different vendors and is part of
> the RTCWEB deliveries. Magnus Westerlund and Steve Botzko did a thorough
> review of the document.
> A request for a media type review was sent to ietf-types and media-types
> mailing lists.
>
> Personnel:
>
> Roni Even is the Document Shepherd.
> The responsible AD is Ben Campbell.
>
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload
>

v2.23.0 | Report a Bug | By Email