Re: [nwcrg] New Version Notification for draft-roca-nwcrg-generic-fec-api-05.txt

Vincent Roca <vincent.roca@inria.fr> Wed, 27 March 2019 16:39 UTC

Return-Path: <vincent.roca@inria.fr>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A300412033D for <nwcrg@ietfa.amsl.com>; Wed, 27 Mar 2019 09:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 Dyzu0ZoZbZPH for <nwcrg@ietfa.amsl.com>; Wed, 27 Mar 2019 09:39:31 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90181120310 for <nwcrg@irtf.org>; Wed, 27 Mar 2019 09:39:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.60,277,1549926000"; d="scan'208";a="376028399"
Received: from ral079r.vpn.inria.fr ([128.93.178.79]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2019 17:39:20 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <155370446222.10323.15162817640176075950.idtracker@ietfa.amsl.com>
Date: Wed, 27 Mar 2019 17:39:19 +0100
Cc: Vincent Roca <vincent.roca@inria.fr>
Content-Transfer-Encoding: quoted-printable
Message-Id: <849D3E32-19C7-4DFB-8DE7-A777404D0835@inria.fr>
References: <155370446222.10323.15162817640176075950.idtracker@ietfa.amsl.com>
To: nwcrg@irtf.org
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/YFxz7Kmy1PiXDexaDI5-0YuQTho>
Subject: Re: [nwcrg] New Version Notification for draft-roca-nwcrg-generic-fec-api-05.txt
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2019 16:39:34 -0000

Hi all,

This new version contains fixes for problems identified during the hackathon.
Yet they have not all been implemented as some of the small issues
need more thoughts. See:
https://github.com/irtf-nwcrg/rg-materials/blob/master/ietf104-2019-03/ietf104_swif_hackathon.md

Cheers,

  Vincent, on behalf of the hackathon team

> Le 27 mars 2019 à 17:34, internet-drafts@ietf.org a écrit :
> 
> 
> A new version of I-D, draft-roca-nwcrg-generic-fec-api-05.txt
> has been successfully submitted by Vincent Roca and posted to the
> IETF repository.
> 
> Name:		draft-roca-nwcrg-generic-fec-api
> Revision:	05
> Title:		Generic Application Programming Interface (API) for Sliding Window FEC Codes
> Document date:	2019-03-27
> Group:		Individual Submission
> Pages:		24
> URL:            https://www.ietf.org/internet-drafts/draft-roca-nwcrg-generic-fec-api-05.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-05
> 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-05
> 
> 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
>