[rfc-dist] RFC 8680 on Forward Error Correction (FEC) Framework Extension to Sliding Window Codes

rfc-editor@rfc-editor.org Tue, 14 January 2020 23:38 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54A212093D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Jan 2020 15:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Wn0oQUMo8Jiy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Jan 2020 15:38:54 -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 77CBA12002F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Jan 2020 15:38:54 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7B976F4071F; Tue, 14 Jan 2020 15:38:51 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id EEF26F4071E; Tue, 14 Jan 2020 15:38:49 -0800 (PST)
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
Message-Id: <20200114233849.EEF26F4071E@rfc-editor.org>
Date: Tue, 14 Jan 2020 15:38:49 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8680_on_Forward_Error_Correction_=28FEC?= =?utf-8?q?=29_Framework_Extension_to_Sliding_Window_Codes?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8680

        Title:      Forward Error Correction (FEC) Framework 
                    Extension to Sliding Window Codes 
        Author:     V. Roca,
                    A. Begen
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2020
        Mailbox:    vincent.roca@inria.fr, 
                    ali.begen@networked.media
        Pages:      19
        Updates:    RFC 6363

        I-D Tag:    draft-ietf-tsvwg-fecframe-ext-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8680

        DOI:        10.17487/RFC8680

RFC 6363 describes a framework for using Forward Error Correction
(FEC) codes to provide protection against packet loss.  The framework
supports applying FEC to arbitrary packet flows over unreliable
transport and is primarily intended for real-time, or streaming,
media.  However, FECFRAME as per RFC 6363 is restricted to block FEC
codes.  This document updates RFC 6363 to support FEC codes based on a
sliding encoding window, in addition to block FEC codes, in a
backward-compatible way. During multicast/broadcast real-time content
delivery, the use of sliding window codes significantly improves
robustness in harsh environments, with less repair traffic and lower
FEC-related added latency.

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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org