RTP Payload Format for BroadVoice Speech Codecs
RFC 4298

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

(Allison Mankin) Yes

(Brian Carpenter) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

Comment (2005-05-11)
No email
send info
In section 9, is Magnus' last name misspelled?

(Ted Hardie) No Objection

Comment (2005-05-10)
No email
send info
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.

(Sam Hartman) No Objection

Comment (2005-05-08)
No email
send info
Is the wording in security considerations for encryption and compression the one Russ and Allison eventually settled on?

(Scott Hollenbeck) (was Discuss) No Objection

(Russ Housley) (was Discuss) No Objection

Comment (2005-05-09)
No email
send info
  There is a blank line in the middle of figure 1.

(David Kessens) No Objection

(Jon Peterson) (was No Record, No Objection) No Objection

Comment (2005-05-11)
No email
send info
Per RFC3555, shouldn't there be a published specification reference for BV32?

(Mark Townsley) No Objection

(Bert Wijnen) No Objection

(Alex Zinin) No Objection