Telechat Review of draft-ietf-payload-rtp-opus-08
review-ietf-payload-rtp-opus-08-genart-telechat-holmberg-2015-04-13-00

Request Review of draft-ietf-payload-rtp-opus
Requested revision No specific revision (document currently at 11)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2015-04-07
Requested 2015-04-02
Authors Julian Spittka , Koen Vos , Jean-Marc Valin
I-D last updated 2015-04-13
Completed reviews Genart Last Call review of -07 by Christer Holmberg (diff)
Genart Telechat review of -08 by Christer Holmberg (diff)
Secdir Last Call review of -07 by Derek Atkins (diff)
Assignment Reviewer Christer Holmberg
State Completed
Request Telechat review on draft-ietf-payload-rtp-opus by General Area Review Team (Gen-ART) Assigned
Reviewed revision 08 (document currently at 11)
Result Ready w/nits
Completed 2015-04-13
review-ietf-payload-rtp-opus-08-genart-telechat-holmberg-2015-04-13-00

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>



Document:                         draft-ietf-payload-rtp-opus-08



Reviewer:                           Christer Holmberg



Review Date:                     11 April 2015



IETF LC End Date:             17 February 2015



IETF Telechat Date:         9 April 2015



Summary:        Most of the comments I gave on a previous version of the
document have been addressed. However, it seems like one of the comments have
not been addressed.



Major Issues: None



Minor Issues: I previously gave the following comment:



“Regarding SDP, I think it would be good to have the ABNF syntax for the a=fmtp
parameter (currently you only have descriptive text of the different
parameters). It makes the life for the parser implementers
 much easier :)”



I guess one, by reading section 7 and the examples, can figure out how to
encode the a=fmtp parameter, but I think it would to explicitly define the
syntax.





Editorial nits: None