Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-18.txt
Giridhar Mandyam <mandyam@qti.qualcomm.com> Tue, 05 March 2019 17:21 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 2A3AF128B36 for <payload@ietfa.amsl.com>; Tue, 5 Mar 2019 09:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 0oagEnj51sVN for <payload@ietfa.amsl.com>; Tue, 5 Mar 2019 09:21:05 -0800 (PST)
Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE3812D4F3 for <payload@ietf.org>; Tue, 5 Mar 2019 09:21:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1551806464; x=1583342464; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=spJUtHuLOOxFzIhGmciD217UxSGW2JnuzWFgYsFjyaw=; b=yQysXQiIdWA7z6bGy7r5mavbcsu5i6ENZBH88TiBX3Zqh9A5y+ZjSACE RqxGNPNdru1S08SaQCc+XIEZ4iWBni3PEeDn20yPgnU+Yw78EPqIUlhmD p56JZrG2JWfMhG6deFCbV6hQgGRAPw8Qlm9LAmmVI9oXqSIuC14IVnfm5 Q=;
X-IronPort-AV: E=Sophos;i="5.58,444,1544515200"; d="scan'208";a="31795920"
Received: from unknown (HELO ironmsg05-sd.qualcomm.com) ([10.53.140.145]) by alexa-out-sd-01.qualcomm.com with ESMTP; 05 Mar 2019 09:21:04 -0800
Received: from nasanexm01g.na.qualcomm.com ([10.85.0.33]) by ironmsg05-sd.qualcomm.com with ESMTP/TLS/AES256-SHA; 05 Mar 2019 09:21:04 -0800
Received: from NASANEXM01C.na.qualcomm.com (10.85.0.83) by NASANEXM01G.na.qualcomm.com (10.85.0.33) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 5 Mar 2019 09:21:03 -0800
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; Tue, 5 Mar 2019 09:21:03 -0800
From: Giridhar Mandyam <mandyam@qti.qualcomm.com>
To: "payload@ietf.org" <payload@ietf.org>
Thread-Topic: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-18.txt
Thread-Index: AQHU03eOAhGPSJgDx0OlJJufQSSE1aX9SGfA
Date: Tue, 05 Mar 2019 17:21:03 +0000
Message-ID: <b8ca3183b6aa4e4f97b16346859588a5@NASANEXM01C.na.qualcomm.com>
References: <155180634247.24571.9901113243096289600@ietfa.amsl.com>
In-Reply-To: <155180634247.24571.9901113243096289600@ietfa.amsl.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/_iLvceSu5EOcViO8lPrBRb2i5IU>
Subject: Re: [payload] I-D Action: 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: Tue, 05 Mar 2019 17:21:07 -0000
My apologies in advance for not getting final confirmation from Benjamin K. on whether we have addressed the concerns he has raised, but I wanted to get a new version up before the blackout period begins prior to the next IETF meeetings. -Giri -----Original Message----- From: payload <payload-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org Sent: Tuesday, March 5, 2019 9:19 AM To: i-d-announce@ietf.org Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-18.txt ------------------------------------------------------------------------- CAUTION: This email originated from outside of the organization. ------------------------------------------------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Payloads WG of the IETF. Title : RTP Payload Format for Flexible Forward Error Correction (FEC) Authors : Mo Zanaty Varun Singh Ali Begen Giridhar Mandyam Filename : draft-ietf-payload-flexible-fec-scheme-18.txt Pages : 44 Date : 2019-03-05 Abstract: 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 complexity. The RTP payload formats that are defined in this document address scalability issues experienced with the earlier specifications, and offer several improvements. Due to these changes, the new payload formats are not backward compatible with earlier specifications, but endpoints that do not implement this specification can still work by simply ignoring the FEC repair packets. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-payload-flexible-fec-scheme/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-18 https://datatracker.ietf.org/doc/html/draft-ietf-payload-flexible-fec-scheme-18 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-flexible-fec-scheme-18 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ payload mailing list payload@ietf.org https://www.ietf.org/mailman/listinfo/payload
- [payload] I-D Action: draft-ietf-payload-flexible… internet-drafts
- Re: [payload] I-D Action: draft-ietf-payload-flex… Giridhar Mandyam