RFC 8681 on Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME
rfc-editor@rfc-editor.org Tue, 14 January 2020 23:38 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70132120B48; Tue, 14 Jan 2020 15:38:58 -0800 (PST)
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 wiAnQ7e7weMQ; Tue, 14 Jan 2020 15:38:56 -0800 (PST)
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 B0D0D12002F; Tue, 14 Jan 2020 15:38:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 55CBAF4073A; Tue, 14 Jan 2020 15:38:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8681 on Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME
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, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200114233854.55CBAF4073A@rfc-editor.org>
Date: Tue, 14 Jan 2020 15:38:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/r5zXiTcS7SJkY-_FdpKx4id4Hz0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2020 23:39:02 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8681
Title: Sliding Window Random Linear Code (RLC)
Forward Erasure Correction (FEC) Schemes
for FECFRAME
Author: V. Roca,
B. Teibi
Status: Standards Track
Stream: IETF
Date: January 2020
Mailbox: vincent.roca@inria.fr,
belkacem.teibi@gmail.com
Pages: 37
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-rlc-fec-scheme-16.txt
URL: https://www.rfc-editor.org/info/rfc8681
DOI: 10.17487/RFC8681
This document describes two fully specified Forward Erasure
Correction (FEC) Schemes for Sliding Window Random Linear Codes
(RLC), one for RLC over the Galois Field (a.k.a., Finite Field)
GF(2), a second one for RLC over the Galois Field GF(2), each time
with the possibility of controlling the code density. They can
protect arbitrary media streams along the lines defined by FECFRAME
extended to Sliding Window FEC Codes. These Sliding Window FEC Codes
rely on an encoding window that slides over the source symbols,
generating new repair symbols whenever needed. Compared to block FEC
codes, these Sliding Window FEC Codes offer key advantages with
real-time flows in terms of reduced FEC-related latency while often
providing improved packet erasure recovery capabilities.
This document is a product of the Transport Area Working Group 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