Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-13.txt
Giridhar Mandyam <mandyam@qti.qualcomm.com> Tue, 11 December 2018 19:01 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 31A48130F30
for <payload@ietfa.amsl.com>; Tue, 11 Dec 2018 11:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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]
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 ks8CnVjqlKWL for <payload@ietfa.amsl.com>;
Tue, 11 Dec 2018 11:01:57 -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 CFD65130F18
for <payload@ietf.org>; Tue, 11 Dec 2018 11:01:56 -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=1544554916; x=1576090916;
h=from:to:subject:date:message-id:references:in-reply-to:
content-transfer-encoding:mime-version;
bh=dqw3osbg3/gQPMyQe6HHAIoGJtrDPiSPdfp1oXfX6aE=;
b=l8dX8fhpXiO5WSZdk2ome0jk+YUr97bWKstGnFt9Stny9/2fuaqzTM0e
+6yLHkaRWvEk50M7GnGxz68ahJTiy8ihN923TKso/LWSjY8Zge3I7x2fQ
7231em7SSM28ILcq+FtgkgUE6DEz5xjcS0Utf/scSzCeWGE7ymy6BCwjk w=;
X-IronPort-AV: E=Sophos;i="5.56,343,1539673200"; d="scan'208";a="17129643"
Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30])
by alexa-out-sd-01.qualcomm.com with ESMTP; 11 Dec 2018 11:01:55 -0800
X-IronPort-AV: E=McAfee;i="5900,7806,9103"; a="311667999"
Received: from nasanexm01a.na.qualcomm.com ([10.85.0.81])
by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/AES256-SHA;
11 Dec 2018 11:01:55 -0800
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; Tue, 11 Dec 2018 11:01:55 -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,
11 Dec 2018 11:01:55 -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-13.txt
Thread-Index: AQHUkYNOwBwcl0RgWUyBftJvM248iKV547eQ
Date: Tue, 11 Dec 2018 19:01:54 +0000
Message-ID: <d47f7a5e86374769b38b361ada051036@NASANEXM01C.na.qualcomm.com>
References: <154455457454.13143.14509030085765652926@ietfa.amsl.com>
In-Reply-To: <154455457454.13143.14509030085765652926@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/cLm8rfbQXrgMgA1LZv3m9NLxDEw>
Subject: Re: [payload] I-D Action:
draft-ietf-payload-flexible-fec-scheme-13.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, 11 Dec 2018 19:01:59 -0000
Please note that I cleared out as many nits as I thought made sense. Current nit check showed zero errors, but a few warnings and comments. I also updated the avtext-rid reference. I modified the abstract slightly as inclusion of references violated RFC 7322, Sec. 4.3. As a result, I removed those references from the abstract and added a sentence in the Introduction that provided the references. -Giri Mandyam -----Original Message----- From: payload <payload-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org Sent: Tuesday, December 11, 2018 10:56 AM To: i-d-announce@ietf.org Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-13.txt 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-13.txt Pages : 41 Date : 2018-12-11 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 decent 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-13 https://datatracker.ietf.org/doc/html/draft-ietf-payload-flexible-fec-scheme-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-flexible-fec-scheme-13 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
- Re: [payload] I-D Action: draft-ietf-payload-flex… Magnus Westerlund
- Re: [payload] I-D Action: draft-ietf-payload-flex… Giridhar Mandyam
- Re: [payload] I-D Action: draft-ietf-payload-flex… Roni Even (A)
- Re: [payload] I-D Action: draft-ietf-payload-flex… Magnus Westerlund