MPE-IFEC Framework During the DVB-SH standardization activities, it was recognized that for satellite-to-handheld services, the MPE-FEC is not sufficient. Therefore, it was decided to specify a multi-burst link layer FEC framework referred to as interburst FEC (IFEC) [1]. The MPE-IFEC is specified as a generic framework that presents enough flexibility for a variety of applications. For a usage in DVB-SH, its parameters are restricted to some specific values via the "framework mapping". Two of such "mappings" are presented in this paper. One is based on MPE-FEC Reed Solomon code [6]. The other mapping is based on Raptor code as specified [7]. For more details on Raptor codes please refer to [8] and the specification in 3GPP, DVB and IETF. IFEC description will be given in the full paper. C. Extended MPE-FEC 
Despite its flexibility, the MPE-IFEC is still designed for the purpose of multicasting live video over time-slice bursts. The FEC is designed for the purpose to minimize tune-in delays, but not to minimize end-to-end delay, which is essential for data delivery services. Furthermore, MPE-IFEC is optimized towards time-slice burst delivery. Therefore an extension of MPE-FEC towards larger ADT sizes is most suitable for DVB-S2 railway scenarios. The extended MPE-FEC with Raptor codes supports bit rates, code rates, as well as latencies in much larger dimensions and is therefore significantly more suitable for the considered scenarios than the MPE-FEC.

http://www.congrex.nl/08c07/abstracts/CXNL_08C07_370852.htm