[Fecframe] FW: New Version Notification for draft-ietf-fecframe-dvb-al-fec-03
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fecframe] FW: New Version Notification for draft-ietf-fecframe-dvb-al-fec-03



This version addresses the comments we received during the initial WGLC process. Please review this one and let us know if you have further comments.

http://www.ietf.org/id/draft-ietf-fecframe-dvb-al-fec-03.txt

Chairs,
Could you start a new WGLC process?

Thanks,
-acbegen

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission at ietf.org] 
Sent: Wednesday, September 16, 2009 12:02 PM
To: Ali C. Begen (abegen)
Cc: stockhammer at nomor.de
Subject: New Version Notification for draft-ietf-fecframe-dvb-al-fec-03 


A new version of I-D, draft-ietf-fecframe-dvb-al-fec-03.txt has been successfuly submitted by Ali Begen and posted to the IETF repository.

Filename:	 draft-ietf-fecframe-dvb-al-fec
Revision:	 03
Title:		 DVB-IPTV Application-Layer Hybrid FEC Protection
Creation_date:	 2009-09-16
WG ID:		 fecframe
Number_of_pages: 11

Abstract:
The Annex E of the DVB-IPTV technical specification defines an
optional Application-layer Forward Error Correction (AL-FEC) protocol
to protect the streaming media carried over RTP transport.  The DVB-
IPTV AL-FEC protocol uses two layers for FEC protection.  The first
(base) layer is based on the 1-D interleaved parity code.  The second
(enhancement) layer is based on the Raptor code.  By offering a
layered approach, the DVB-IPTV AL-FEC protocol offers a good
protection against both bursty and random packet losses at a cost of
decent complexity.  This document describes how one can implement the
DVB-IPTV AL-FEC protocol by using the 1-D interleaved parity code and
Raptor code that have already been specified in separate documents.
                                                                                  


The IETF Secretariat.



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.