[payload] RFC 8627 on RTP Payload Format for Flexible Forward Error Correction (FEC)
rfc-editor@rfc-editor.org Fri, 19 July 2019 00:32 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 5F159120139; Thu, 18 Jul 2019 17:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 csLecDd9D2DP; Thu, 18 Jul 2019 17:32:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DD7C120133; Thu, 18 Jul 2019 17:32:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EB34FB80BE2; Thu, 18 Jul 2019 17:32:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, payload@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190719003250.EB34FB80BE2@rfc-editor.org>
Date: Thu, 18 Jul 2019 17:32:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/pokwg6r3-Iqc3psSeV-9CR3dO2I>
Subject: [payload] RFC 8627 on RTP Payload Format for Flexible Forward Error Correction (FEC)
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: Fri, 19 Jul 2019 00:32:58 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8627 Title: RTP Payload Format for Flexible Forward Error Correction (FEC) Author: M. Zanaty, V. Singh, A. Begen, G. Mandyam Status: Standards Track Stream: IETF Date: July 2019 Mailbox: mzanaty@cisco.com, varun.singh@iki.fi, ali.begen@networked.media, mandyam@qti.qualcomm.com Pages: 41 Characters: 92366 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-payload-flexible-fec-scheme-20.txt URL: https://www.rfc-editor.org/info/rfc8627 DOI: 10.17487/RFC8627 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 (Flexible FEC, or "FLEX FEC"), 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 that 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; however, endpoints that do not implement this specification can still work by simply ignoring the FEC repair packets. This document is a product of the Audio/Video Transport Payloads Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC