RTP Payload Format for Flexible Forward Error Correction (FEC)
RFC 8627
Note: This ballot was opened for revision 16 and is now closed.
(Ben Campbell) Yes
Ignas Bagdonas No Objection
Deborah Brungard No Objection
(Spencer Dawkins) No Objection
Comment (2019-02-19 for -17)
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?
Benjamin Kaduk (was Discuss) No Objection
Comment (2019-03-08 for -18)
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)!
Suresh Krishnan No Objection
Warren Kumari No Objection
Comment (2019-02-20 for -17)
Like others, I found the 2-D description confusing -- but I'm *so* not a SME here, and figured it's probably just me :-)
Mirja Kühlewind No Objection
Comment (2019-02-21 for -17)
Thanks for the well-written document! And thanks for addressing the TSV-ART comments (and thanks Bernard for the review)!
Alexey Melnikov No Objection
Comment (2019-02-19 for -17)
I found 2-D description confusing as well.