> On Nov 17, 2016, at 10:43 AM, Timothy B. Terriberry <[email protected]> wrote: > > Except for the issue of where the new test vectors should live, the chairs > believe that this draft is ready to go. We would like to initiate a working > group last call on draft-ietf-codec-opus-update-04 to help gather any > remaining issues. > > The draft can be found at > https://tools.ietf.org/html/draft-ietf-codec-opus-update-04 > > Please send comments to the list by the end of the day on Dec. 1.
I have reviewed this document. I haven't personally validated all the changes to the C code, but they seem plausible to me. Each of the patches’ explanatory text also seems good. However, I think the overview text could be clearer. 1. I assume none of these changes rise to the level that they would make any change to the textual description of the Opus codec? This should probably be stated explicitly. 2. The abstract and introduction should mention that this document updates the normative behavior of the codec, including the test vectors. 3. The link to the properly-formatted patch matching the document should be mentioned somewhere other than in Section 5 — especially since it actually includes patches for all the sections of the document, not just Section 5 and above. The introduction seems like a sensible place, perhaps. _______________________________________________ codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/codec
