FEC Framework (fecframe)
------------------------

 Charter
 Last Modified: 2008-12-16

 Current Status: Active Working Group

 Chair(s):
     Greg Shepherd  <gjshep@gmail.com>
     Marshall Eubanks  <tme@multicasttech.com>

 Transport Area Director(s):
     Magnus Westerlund  <magnus.westerlund@ericsson.com>
     Lars Eggert  <lars.eggert@nokia.com>

 Transport Area Advisor:
     Magnus Westerlund  <magnus.westerlund@ericsson.com>

 Mailing Lists: 
     General Discussion:fecframe@ietf.org
     To Subscribe:      https://www.ietf.org/mailman/listinfo/fecframe
     Archive:           http://www.ietf.org/mail-archive/web/fecframe

Description of Working Group:

The object of this group is to develop standards for using forward 
error correction (FEC) codes with applications in the Internet to 
provide protection against packet loss. The group will develop a
framework for application of FEC codes to arbitrary packet flows over
unreliable transport protocols over both IP multicast and unicast. The
group will build on the work of the RMT working group in the form of 
the FEC Building Block developed there to ensure that the framework
developed can support multiple FEC codes and maintain independence
between FEC codes and content delivery protocols. Note: framework
here is a protocol framework, with a design to be determined, but 
suitable for interoperable implementations. It is not used in the 
sense often used by IETF of a document akin to requirements.

A primary objective of this framework is to support FEC for streaming
media. The group will coordinate closely with AVT and MMUSIC working
groups to ensure that this use-case is fully specified both in terms of
interactions with RTP/RTCP and application layer signalling. The group 
will also coordinate with the DCCP working group, at least, 
considering that transport's role in streaming media.

The group will work with the RMT working group to ensure that the FEC
Building Block defined in RMT supports both the RMT use-cases (object
delivery over multicast) and the more general FEC protection of IP 
flows over unreliable unicast and multicast transport. The group will 
also consider developing its charter to include for proposals for 
standardization of specific FEC codes - taking on this work from the 
RMT working group - including consideration of their areas of 
applicability and generality.

Specification of hybrid schemes involving both retransmission and
forward error correction will be out of scope of the group. However the
group should consider of whether work on such schemes should be
considered in a future phase.

 Goals and Milestones:

   Done         Working Group consensus on requirements and their 
                prioritization for the FEC protocol framework 

   Done         Completed selection of solution to develop and mature 

   Done         FEC framework requirements WG soft-freeze 

   Done         FEC Streaming Framework WG soft-freeze 

   Mar 2008       FEC Grouping informational draft submitted to MMUSIC 

   Nov 2008       FEC Streaming Framework submitted as Proposed Standard 

   Nov 2008       FEC framework requirements submitted as Proposed Standard 

   Nov 2008       Usage of FEC framework with RTP submitted as Proposed Standard 

   Nov 2008       FEC SDP Elements submitted as Proposed Standard 

   Nov 2008       Discuss re-chartering 


 Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Feb 2007 Jul 2009   <draft-ietf-fecframe-framework-05.txt>
                Forward Error Correction (FEC) Framework 

Feb 2008 Aug 2009   <draft-ietf-fecframe-sdp-elements-04.txt>
                SDP Elements for FEC Framework 

Aug 2008 May 2009   <draft-ietf-fecframe-interleaved-fec-scheme-05.txt>
                RTP Payload Format for 1-D Interleaved Parity FEC 

Aug 2008 Sep 2009   <draft-ietf-fecframe-dvb-al-fec-03.txt>
                DVB-IPTV Application-Layer Hybrid FEC Protection 

Oct 2008 Jul 2009   <draft-ietf-fecframe-raptor-01.txt>
                Raptor FEC Schemes for FECFRAME 

Oct 2008 May 2009   <draft-ietf-fecframe-1d2d-parity-scheme-01.txt>
                RTP Payload Format for Non-Interleaved and Interleaved Parity 
                FEC 

 Request For Comments:

  None to date.