I have no idea who was the reviewer (academic or industry or whatever). However, he didn't actually object to the assertion that latency increases with congestion; he only raised the question of the which latency values would be typical/reasonable for a congestion DoS attack. Notice also that the relevant parameter is end-to-end latency (or RTT), not the per-device latency. And surely, there can be wide variety here (that's why we do experiments under different values and plot graphs....). The question is, what is the most important range to focus on (when measuring and comparing different protocols). 

Anyway, thanks for the comments; if anyone has such data they can share, that'll be great  and appreciated. 
--
Amir 



On Sun, Jan 26, 2020 at 7:17 AM Saku Ytti <saku@ytti.fi> wrote:
On Sun, 26 Jan 2020 at 13:11, Etienne-Victor Depasquale <edepa@ieee.org> wrote:

> " he/she doubts that delays increase significantly under network congestion since he/she thinks that the additional queuing is something mostly in small routers such as home routers (and maybe like the routers used in our emulation testbed) "
>
> Wow, this is the first time I've found an academic challenging the increase of delay in routers under network congestion.

I don't know if context implies reviewer was academic. Whilethe common
case remains that latencies per link jump from low microseconds to
tens of milliseconds during congestion of BB interface, there are also
a lot of deployments using devices (trident, tomahawk) with minimal
buffering not allowing even millisecond of buffering during
congestion. Reviewer may have thought of those devices when they
answered, but I agree that answer would be generally wrong.


--
  ++ytti