Subject: [nwcrg] Fwd: New Version Notification for draft-roca-nwcrg-generic-fec-api-02.txt

From: Vincent Roca <[email-masked]>
Date: Mon, 2 Jul 2018 17:51:44 +0200

Hello everybody,

Please find bellow the -02 version of our I-D on a Generic Sliding Window FEC Codes API.
It now comes with full API proposal, encoder and decoder included, although this API is far from finalised.

To be discussed…
Cheers,

  Vincent

> De: [email-masked]
> Objet: New Version Notification for draft-roca-nwcrg-generic-fec-api-02.txt
> Date: 2 juillet 2018 à 17:48:18 UTC+2
> À: "Cedric Adjih" <[email-masked]>, "Morten Pedersen" <[email-masked]>, "Vincent Roca" <[email-masked]>, "Cedric Adjih" <[email-masked]>, "Jonathan Detchart" <[email-masked]>, "Morten V. Pedersen" <[email-masked]>
> 
> 
> A new version of I-D, draft-roca-nwcrg-generic-fec-api-02.txt
> has been successfully submitted by Vincent Roca and posted to the
> IETF repository.
> 
> Name:		draft-roca-nwcrg-generic-fec-api
> Revision:	02
> Title:		Generic Application Programming Interface (API) for Sliding Window FEC Codes
> Document date:	2018-07-02
> Group:		Individual Submission
> Pages:		42
> URL:            https://www.ietf.org/internet-drafts/draft-roca-nwcrg-generic-fec-api-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-roca-nwcrg-generic-fec-api/
> Htmlized:       https://tools.ietf.org/html/draft-roca-nwcrg-generic-fec-api-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-roca-nwcrg-generic-fec-api
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-roca-nwcrg-generic-fec-api-02
> 
> Abstract:
>   This document introduces a generic Application Programming Interface
>   (API) for sliding window FEC codes.  This API is meant to be
>   compatible with any sliding window FEC code.  It defines the core
>   procedures and functions meant to control the codec (i.e.,
>   implementation of the FEC code).  However, it leaves out all upper
>   layer aspects that are the responsibility of the application or
>   protocol making use of the codec.  As a consequence, this is not an
>   API for a FEC Scheme since certain mechanisms that must be defined by
>   any FEC Scheme (e.g., signalling and FEC Payload IDs) are the
>   responsibility of the caller instead of being addressed by the codec.
>   A first goal of this document is to pave the way for a future open-
>   source implementation of such codes, another goal is to simplify the
>   development of content delivery protocols that rely on sliding window
>   FEC codes for robust transmissions.
> 
> 
> 
> 
> 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
>