Last Call Review of draft-ietf-aqm-eval-guidelines-11

Request Review of draft-ietf-aqm-eval-guidelines
Requested rev. no specific revision (document currently at 13)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-05-04
Requested 2016-04-21
Authors Nicolas Kuhn, Preethi Natarajan, Naeem Khademi, David Ros
Draft last updated 2016-05-09
Completed reviews Genart Last Call review of -11 by Ralph Droms (diff)
Genart Telechat review of -11 by Ralph Droms (diff)
Secdir Last Call review of -11 by Tero Kivinen (diff)
Opsdir Last Call review of -11 by Linda Dunbar (diff)
Assignment Reviewer Linda Dunbar 
State Completed
Review review-ietf-aqm-eval-guidelines-11-opsdir-lc-dunbar-2016-05-09
Reviewed rev. 11 (document currently at 13)
Review result Has Issues
Review completed: 2016-05-09


I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments
 were written primarily for the benefit of the operational area directors. Document editors and WG chairs should treat these comments just like any other last call comments.



The document is well written and provides a good description on useful metrics that can be used to measure the performance of network in delivering packets
 from A to B.  


However, for flows traversing various domains of network (which may have  layers of layers tunnels in between), the following aspects need more clarification:




Section 2.1: How to measure Flow Size? All the packets sent over the course of the active flow * each packet size?



Figure 1: Is the Router L closest to A? and Router R closest to B? How those two routers are selected?  there could be many routers between Router L and Router R that have
 extra large buffer to cause delay, or multiple paths traversing over multiple routers, some of which have larger buffer and others have small, causing jitter.





Linda Dunbar