RTP Payload Format for Raptor Forward Error Correction (FEC)
draft-ietf-fecframe-rtp-raptor-07
Yes
(David Harrington)
No Objection
(Adrian Farrel)
(Dan Romascanu)
(Jari Arkko)
(Ralph Droms)
(Ron Bonica)
(Sean Turner)
(Stewart Bryant)
(Wesley Eddy)
Note: This ballot was opened for revision 07 and is now closed.
David Harrington Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
Gonzalo Camarillo Former IESG member
No Objection
No Objection
(2011-11-03)
Unknown
I support Robert's discuss and comment.
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Pete Resnick Former IESG member
(was Discuss)
No Objection
No Objection
(2011-11-25)
Unknown
A bunch of comments on 2119 usage: Overall: I'm not a big fan of SHALL instead of MUST; it seems to me that MUST works better throughout all of your uses. Specific problems: Section 3: [Addressed] 4.1: [First issue addressed] I'm not clear on why the marker bit is labeled with a SHALL. The marker bit is set to 1 for the last packet and is otherwise 0. I suppose it is a requirement, but I can't imagine how an implementation could decide to set the marker bit to 0 for a non-final packet. Seems like a silly use of SHALL. Same with the definition and use of timestamp. I don't think you need 2119 keywords here. 4.3: [Addressed] Section 6 [See DISCUSS] Section 7: [Addressed] Section 8: [Addressed] Section 11: [Addressed]
Ralph Droms Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
(was Discuss)
No Objection
No Objection
(2011-11-02)
Unknown
While it's not a hard requirement at the moment, I think it would help the quality of RTP payload documents to run them through as PAYLOAD working group items. Please consider taking that approach with future payload format specifications.
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
(2011-10-30)
Unknown
The Gen-ART Review by Brian Carpenter on 30-Oct-2011 suggests some editorial changes. Please consider them. Typo in page header title. It says: RTP Payload Fromat for Raptor s/Fromat/Format/ There are several places where an upper-case MAY is used where a plain English lower case "may" would be fine: - all three MAYs in the Introduction; - the first sentence of section 3; and - all three MAYs in the last paragraph of the Security Conisderations.
Sean Turner Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Stephen Farrell Former IESG member
(was Discuss)
No Objection
No Objection
(2011-10-30)
Unknown
- fecframework is now RFC6363 (I actually followed the reference given so the wrong reference might have but didn't mislead)
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown
Wesley Eddy Former IESG member
No Objection
No Objection
()
Unknown