RTP Payload Format for Flexible Forward Error Correction (FEC)
draft-ietf-payload-flexible-fec-scheme-20

Note: This ballot was opened for revision 16 and is now closed.

Alvaro Retana No Objection

Warren Kumari No Objection

Like others, I found the 2-D description confusing -- but I'm *so* not a SME here, and figured it's probably just me :-)

(Ben Campbell; former steering group member) Yes

(Adam Roach; former steering group member) No Objection

(Alexey Melnikov; former steering group member) No Objection

I found 2-D description confusing as well.

(Benjamin Kaduk; former steering group member) (was Discuss) No Objection

Thank you for addressing my DISCUSS points (and de-confusing me on how the
recovery state is consolidated across the different SSRCs and packets it covers)!

(Deborah Brungard; former steering group member) No Objection

(Ignas Bagdonas; former steering group member) No Objection

(Martin Vigoureux; former steering group member) No Objection

(Mirja Kühlewind; former steering group member) No Objection

Thanks for the well-written document! And thanks for addressing the TSV-ART comments (and thanks Bernard for the review)!

(Spencer Dawkins; former steering group member) No Objection

I do have one question - the IESG has approved https://datatracker.ietf.org/doc/draft-ietf-tsvwg-fecframe-ext/, which updates RFC 6363 to support sliding encoding window codes, in addition to block codes, and it seems like that would be useful for real-time payload FEC here. Is that something that people have looked at?

(Suresh Krishnan; former steering group member) No Objection