RTP Payload Format for Raptor Forward Error Correction (FEC)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, fecframe mailing list <email@example.com>, fecframe chair <firstname.lastname@example.org> Subject: Protocol Action: 'RTP Payload Format for Raptor FEC' to Proposed Standard (draft-ietf-fecframe-rtp-raptor-07.txt) The IESG has approved the following document: - 'RTP Payload Format for Raptor FEC' (draft-ietf-fecframe-rtp-raptor-07.txt) as a Proposed Standard This document is the product of the FEC Framework Working Group. The IESG contact persons are David Harrington and Wesley Eddy. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-fecframe-rtp-raptor/
Technical Summary This document specifies an RTP payload format for Forward Error Correction / (FEC) repair data produced by the Raptor FEC schemes. Raptor FEC schemes are specified for use with the IETF FEC Framework which supports transport of repair data over both UDP and RTP. This document specifies the payload format which is required for the use of RTP to carry Raptor repair flows. Working Group Summary There were no seriously contentious issues during the WG process. IETF Last Call ends 11/3, the requested date for a telechat. If there are substantive comments during IETF LC, I will push this to a later telechat. Document Quality The Working Group feedback covered both the quality of the document itself as well as the technical issues with the content of the document. Personnel Document Shepherd - Greg Shepherd Responsible Area Director - David Harrington <email@example.com> RFC Editor Note 1) references need updating; fecframe-framework and fecframe-sdp-elements have been published. 2) in the Introduction s/MAY/might/g 3) in multiple places, the Controller should be the PAYLOAD WG rather than the AVT WG 4) some examples will be provided for "applications that use ..."