Last Call Review of draft-ietf-xrblock-independent-burst-gap-discard-02
review-ietf-xrblock-independent-burst-gap-discard-02-opsdir-lc-liu-2016-08-08-00

Request Review of draft-ietf-xrblock-independent-burst-gap-discard
Requested rev. no specific revision (document currently at 03)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-08-01
Requested 2016-07-11
Authors Varun Singh, Colin Perkins, Alan Clark, Rachel Huang
Draft last updated 2016-08-08
Completed reviews Genart Last Call review of -03 by Christer Holmberg
Opsdir Last Call review of -02 by Will LIU (diff)
Assignment Reviewer Will LIU 
State Completed
Review review-ietf-xrblock-independent-burst-gap-discard-02-opsdir-lc-liu-2016-08-08
Reviewed rev. 02 (document currently at 03)
Review result Ready
Review completed: 2016-08-08

Review
review-ietf-xrblock-independent-burst-gap-discard-02-opsdir-lc-liu-2016-08-08






Hi all,




 




I have reviewed draft-ietf-xrblock-independent-burst-gap-discard-02 as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments
 were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any
 other last call comments.




 




“This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows the reporting of burst and gap discard metrics independently of the burst and gap loss metrics for use
 in a range of RTP applications.”




 




My overall view of the document is fine and ready for publication.




 




 




Nits:




 




Page 1:




>>    Audio/Video Transport Working Group                             V. Singh




>>    Internet-Draft                                              callstats.io




Only double check the affiliation on the first page. According to last page, this might be “Nemu Dialogue Systems Oy”?




 




Another thing is, you may consider to put the reference of dejitter buffers,  [RFC5481] , at the first time this term used in section 1.1 , instead of in section 1.4.




 







Regards,




Will (Shucheng LIU)