%% You should probably cite draft-roca-nwcrg-generic-fec-api-07 instead of this revision.
@techreport{roca-nwcrg-generic-fec-api-04,
    number =    {draft-roca-nwcrg-generic-fec-api-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-roca-nwcrg-generic-fec-api/04/},
    author =    {Vincent Roca and Jonathan Detchart and Cédric Adjih and Morten Pedersen},
    title =     {{Generic Application Programming Interface (API) for Sliding Window FEC Codes}},
    pagetotal = 23,
    year =      2018,
    month =     nov,
    day =       4,
    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.},
}