RTP Payload Format for BroadVoice Speech Codecs
draft-ietf-avt-rtp-bv-04
Yes
(Allison Mankin)
No Objection
(Alex Zinin)
(Bert Wijnen)
(Brian Carpenter)
(David Kessens)
(Margaret Cullen)
(Mark Townsley)
(Scott Hollenbeck)
Note: This ballot was opened for revision 04 and is now closed.
Allison Mankin Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Objection
No Objection
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
(2005-05-11)
Unknown
In section 9, is Magnus' last name misspelled?
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
(was No Record, No Objection)
No Objection
No Objection
(2005-05-11)
Unknown
Per RFC3555, shouldn't there be a published specification reference for BV32?
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
(2005-05-09)
Unknown
There is a blank line in the middle of figure 1.
Sam Hartman Former IESG member
No Objection
No Objection
(2005-05-08)
Unknown
Is the wording in security considerations for encryption and compression the one Russ and Allison eventually settled on?
Scott Hollenbeck Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
(2005-05-10)
Unknown
This document is not limited to the vendor tree because multiple vendors and an industry consortium have agreed to it. That justifies this as a COMMON registration. The document reads, though, as if it were for a vendor specific registration, and the registrants may wish to remove some of the more marketing-literature appropriate phrases to highlight that this codec will be valid beyond Broadcom's wares.