RTP Payload Format for Flexible Forward Error Correction (FEC)
draft-ietf-payload-flexible-fec-scheme-20
Yes
(Ben Campbell)
No Objection
(Adam Roach)
(Alvaro Retana)
(Deborah Brungard)
(Ignas Bagdonas)
(Martin Vigoureux)
(Suresh Krishnan)
Note: This ballot was opened for revision 16 and is now closed.
Warren Kumari
No Objection
Comment
(2019-02-20 for -17)
Not sent
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 IESG member
Yes
Yes
(for -16)
Unknown
Adam Roach Former IESG member
No Objection
No Objection
(for -17)
Not sent
Alexey Melnikov Former IESG member
No Objection
No Objection
(2019-02-19 for -17)
Not sent
I found 2-D description confusing as well.
Alvaro Retana Former IESG member
No Objection
No Objection
(for -17)
Not sent
Benjamin Kaduk Former IESG member
(was Discuss)
No Objection
No Objection
(2019-03-08 for -18)
Sent for earlier
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 IESG member
No Objection
No Objection
(for -17)
Not sent
Ignas Bagdonas Former IESG member
No Objection
No Objection
(for -17)
Not sent
Martin Vigoureux Former IESG member
No Objection
No Objection
(for -17)
Not sent
Mirja Kühlewind Former IESG member
No Objection
No Objection
(2019-02-21 for -17)
Sent
Thanks for the well-written document! And thanks for addressing the TSV-ART comments (and thanks Bernard for the review)!
Spencer Dawkins Former IESG member
No Objection
No Objection
(2019-02-19 for -17)
Sent
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 IESG member
No Objection
No Objection
(for -17)
Not sent