FEC Framework (fecframe)
Last Modified: 2008-12-16
Additional information is available at tools.ietf.org/wg/fecframe
Chair(s):
Transport Area Director(s):
Transport Area Advisor:
Mailing Lists:
General Discussion: fecframe@ietf.orgTo 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 forwarderror 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:
SDP Elements for FEC Framework (46006 bytes)Methods to convey FEC Framework Configuration Information (36283 bytes)
RTP Payload Format for 1-D Interleaved Parity FEC (65976 bytes)
DVB Application-Layer Hybrid FEC Protection (24151 bytes)
Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in FEC Framework (27110 bytes)
RTP Payload Format for Raptor FEC (20891 bytes)
No Request For Comments
