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)

Giridhar Mandyam <mandyam@qti.qualcomm.com> Thu, 21 March 2019 15:43 UTC

Return-Path: <mandyam@qti.qualcomm.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 1B443130E94; Thu, 21 Mar 2019 08:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 tVb-jEMa1Xbb; Thu, 21 Mar 2019 08:43:28 -0700 (PDT)
Received: from alexa-out-sd-02.qualcomm.com (alexa-out-sd-02.qualcomm.com [199.106.114.39]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C5B8127988; Thu, 21 Mar 2019 08:43:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1553183008; x=1584719008; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=fx6HItuQe2apL6/EQjhMwAzb2MhrDCgChz/+oT07QiU=; b=sJBridIXxlgbFy/TxqnZXApe6NTZ8bnUkFdJ0zB0/EOeOzm5eKv2vZKl 0OPZzmyVhdo5ZGd7uD9M55QNu3QpYhJ3+hoo/eRQKU9GiDSfpV/akasA0 b7Wq6huIhmVNeiRjwuvKyjaOT0/aWGGbB/ZZxZVOX5AIvQzGTXlvaf3t0 Y=;
X-IronPort-AV: E=Sophos; i="5.60,253,1549958400"; d="scan'208,217"; a="38733694"
Received: from unknown (HELO ironmsg05-sd.qualcomm.com) ([10.53.140.145]) by alexa-out-sd-02.qualcomm.com with ESMTP; 21 Mar 2019 08:43:26 -0700
Received: from nasanexm01a.na.qualcomm.com ([10.85.0.81]) by ironmsg05-sd.qualcomm.com with ESMTP/TLS/AES256-SHA; 21 Mar 2019 08:43:26 -0700
Received: from NASANEXM01C.na.qualcomm.com (10.85.0.83) by nasanexm01a.na.qualcomm.com (10.85.0.81) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 21 Mar 2019 08:43:25 -0700
Received: from NASANEXM01C.na.qualcomm.com ([10.85.0.83]) by NASANEXM01C.na.qualcomm.com ([10.85.0.83]) with mapi id 15.00.1395.000; Thu, 21 Mar 2019 08:43:25 -0700
From: Giridhar Mandyam <mandyam@qti.qualcomm.com>
To: Bernard Aboba <bernard.aboba@gmail.com>, "payload@ietf.org" <payload@ietf.org>
CC: "roni.even@mail01.huawei.com" <roni.even@mail01.huawei.com>, The IESG <iesg@ietf.org>, "draft-ietf-payload-flexible-fec-scheme@ietf.org" <draft-ietf-payload-flexible-fec-scheme@ietf.org>
Thread-Topic: [payload] Protocol Action: 'RTP Payload Format for Flexible Forward Error Correction (FEC)' to Proposed Standard (draft-ietf-payload-flexible-fec-scheme-18.txt)
Thread-Index: AQHU38Hpy/Y+aT9PEkKCMAIq5eMfDaYWrl2A//+K7IA=
Date: Thu, 21 Mar 2019 15:43:24 +0000
Message-ID: <4654947926ae4a368fad694118cd9da3@NASANEXM01C.na.qualcomm.com>
References: <155315770054.9919.5577297727640600792.idtracker@ietfa.amsl.com> <CAOW+2dsvLU=LSJCFfsNHFSXkvo7enjr-RFgqjuNFDsqg+xq_MA@mail.gmail.com>
In-Reply-To: <CAOW+2dsvLU=LSJCFfsNHFSXkvo7enjr-RFgqjuNFDsqg+xq_MA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.80.80.8]
Content-Type: multipart/alternative; boundary="_000_4654947926ae4a368fad694118cd9da3NASANEXM01Cnaqualcommco_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/rQHVNo8k8-8zQD0_Yrs_ozk10N8>
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:43:31 -0000

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

I did not ignore any “problems”.  I just did not see an actionable  proposal for specific text that could be added to the I.-D.  If you have suggestions, please provide them.

If the discussion is going to be this contentious, I am afraid we will have trouble reaching a desired outcome – a complete and usable specification.

-Giri

From: Bernard Aboba <bernard.aboba@gmail.com>
Sent: Thursday, March 21, 2019 8:39 AM
To: payload@ietf.org
Cc: roni.even@mail01.huawei.com; The IESG <iesg@ietf.org>; draft-ietf-payload-flexible-fec-scheme@ietf.org
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)


CAUTION: This email originated from outside of the organization.
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<mailto: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<mailto:payload@ietf.org>
https://www.ietf.org/mailman/listinfo/payload

v2.23.0 | Report a Bug | By Email