Subject: [nwcrg] Fwd: New Version Notification for draft-roca-nwcrg-fecframev2-problem-position-00.txt

From: Vincent Roca <[email-masked]>
Date: Sun, 12 Apr 2015 16:16:14 +0200

Hello everybody

FYI…

This I-D discusses how the FEC Framework (i.e., FECFRAME) can be extended to support sliding encoding windows.
It does not necessarily answers all questions, but it provides several insights.

It also introduces some key aspects of FECFRAME (in case you didn’t read carefully the various specifications), at the
light of NC use-cases.

Cheers,

  Vincent

> De: [email-masked]
> Objet: New Version Notification for draft-roca-nwcrg-fecframev2-problem-position-00.txt
> Date: 12 avril 2015 16:05:56 UTC+2
> À: "Vincent Roca" <[email-masked]>, "Vincent Roca" <[email-masked]>
> 
> 
> A new version of I-D, draft-roca-nwcrg-fecframev2-problem-position-00.txt
> has been successfully submitted by Vincent Roca and posted to the
> IETF repository.
> 
> Name:		draft-roca-nwcrg-fecframev2-problem-position
> Revision:	00
> Title:		FECFRAMEv2: Adding Sliding Encoding Window Capabilities to the FEC Framework: Problem Position
> Document date:	2015-04-12
> Group:		Individual Submission
> Pages:		18
> URL:            http://www.ietf.org/internet-drafts/draft-roca-nwcrg-fecframev2-problem-position-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-roca-nwcrg-fecframev2-problem-position/
> Htmlized:       http://tools.ietf.org/html/draft-roca-nwcrg-fecframev2-problem-position-00
> 
> 
> Abstract:
>   The Forward Error Correction (FEC) Framework (or FECFRAME) (RFC 6363)
>   has been defined by the FECFRAME IETF WG to enable the use of FEC
>   Encoding with real-time flows in a flexible manner.  The original
>   FECFRAME specification only considers the use of block FEC codes,
>   wherein the input flow(s) is(are) segmented into a sequence of blocks
>   and FEC encoding performed independently on a per-block basis.  This
>   document discusses an extension of FECFRAME in order to enable a
>   sliding (potentially elastic) window encoding of the input flow(s),
>   using convolutional FEC codes for the erasure channel, as an
>   alternative to block FEC codes.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>