Re: [ippm] Adoption call for draft-cpaasch-ippm-responsiveness

Hello Ruediger,

thanks for your feedback! Please see inline:

> On Dec 22, 2021, at 11:16 PM, Ruediger.Geib@telekom.de wrote:
> 
> Hi Marcus,
> 
> Noting that some more work needs to be added, I support adoption.
> 
> Some comments:
> - I'd appreciate if the draft was covering expectable operational scenarios, namely
>  * There may be no bottleneck buffer - the test/metric needs to detect that and act appropriate.

I'm not sure what you mean ? Every flow is limited by some bottleneck that sits somewhere. Sometimes, it's the last mile, sometimes it's the Wi-Fi connectivity, sometimes flows become CPU-limited. But there always is a bottleneck somewhere that is limiting things at which point a buffer is building up (even though that "buffer" may be just 1 packet large)

>  * One might be interested in the metric while the test adds an insignificant load only. While receiver tries to consume service X, what's the metric seen from Y? 
>     (may help to clarify, whether the access causes trouble or another network section).

That would indeed be interesting for trouble-shooting and debugging. I believe this is out-of-scope though.

> - Measuring the maximum RPM as seen from the test server is part of the test or it isn't? That's not clear to me by now.
>  I'm favouring to make measuring the maximum RPM part of the test, this may help to scale results.

The methodology defines to only measure from the client as we are interested in responsiveness as a metric that is (as close as possible) representative of an end-user experience.

When you say "maximum RPM", do you mean that on an "idle" network?

> - The test set-up should prevent application as DoS attack tool.

The json-fetch at the beginning of the test allows server-side CDN deployments to "rate-limit" clients by simply delaying the response to the json-fetch.

What else do you have in mind regarding a DoS attack tool?

Thanks,
Christoph

> Regards,
> 
> Ruediger
> 
> 
> From: Marcus Ihlar <marcus.ihlar@ericsson.com >
> Subject: [ippm] Adoption call for draft-cpaasch-ippm-responsiveness
> Date: December 6, 2021 at 7:52:58 AM PST
> To: "ippm@ietf.org<mailto:ippm@ietf.org>" <ippm@ietf.org<mailto:ippm@ietf.org>>
> List-Id: IETF IP Performance Metrics Working Group 
> 
> Hi IPPM,
> 
> This email starts an adoption call for draft-cpaasch-ippm-responsiveness, "Responsiveness under Working Conditions". This document specifies the "RPM Test" for measuring user experience when the network is fully loaded. The intended status of the document is Experimental.
> 
> https://datatracker.ietf.org/doc/draft-cpaasch-ippm-responsiveness/
> 
> https://datatracker.ietf.org/doc/html/draft-cpaasch-ippm-responsiveness-01
> 
> This adoption call will last until Monday, December 20. Please review the document, and reply to this email thread to indicate if you think IPPM should adopt this document.
> 
> BR,
> Marcus
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org<mailto:ippm@ietf.org>
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm