%% You should probably cite draft-ietf-tsvwg-fecframe-ext instead of this I-D.
@techreport{roca-tsvwg-fecframev2-02,
    number =    {draft-roca-tsvwg-fecframev2-02},
    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-tsvwg-fecframev2/02/},
    author =    {Vincent Roca and Ali C. Begen},
    title =     {{Forward Error Correction (FEC) Framework version 2}},
    pagetotal = 51,
    year =      2016,
    month =     oct,
    day =       6,
    abstract =  {This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks 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. This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) that is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined that are not specific to a particular FEC scheme, and FEC schemes can be defined that are not specific to a particular Content Delivery Protocol. The first version of FECFRAME defined in RFC 6363 was restricted to block FEC codes. The FECFRAME version 2 defined in this document adds the possibility to use Convolutional FEC Codes in addition to Block FEC Codes. It obsoltes RFC 6363.},
}