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

(Martin Stiemerling) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Just one substantive comment (the first one). While I'm not
objecting, I'd like to understand why you haven't put in that
MUST...

- p19, you have m=8 as the default, which is fine, but you only
say that that SHOULD be supported and used. That means that an
imlplementation could claim to conform to this spec that only
supported m=16 or some other value.  It would seem better to
say that m=8 MUST be supported by all implementations, esp.
since you imply that different methods will be used to
implement different m values. Is there a reason to not have
that MUST?

The rest are nits:

- abstract is terminology-rich, would be nicer if simplified.

- p5, "Some of them..." which "them"? (Same on p6)

- p11, it'd be nicer if L[x] was shown twice as wide as F[x] in
the simple FEC encoding diagram

- p12, would it be useful to say that the value of E in an SDP
has to be <2^16?

(Brian Haberman) No Objection

(Russ Housley) No Objection

(Barry Leiba) No Objection

(Pete Resnick) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection