-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: explain the throttling methodology #1546
Conversation
- outline the current methodology; - explain its theoretical assumptions; - describe limitations; - mention possible future directions. Part of ooni/ooni.org#1406.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed with @bassosimone, we should also document the following:
- how we can use this methodology while looking at data from webconnectivity v0.5: analyzing speeds between domains across different temporal data points.
Apart from this, the document looks good and is well-explained. This serves as a good foundation to analyse throttling incidents.
Additionally, mention comments that were provided by @agrabeli, @albertodainotti, et al., during a recent gathering focusing on network measurements where I presented this work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good. I left a small comment. I think this should be good to go
Co-authored-by: DecFox <[email protected]>
outline the current methodology;
explain its theoretical assumptions;
describe limitations;
mention possible future directions.
Part of ooni/ooni.org#1406.
Closes #684 because we've now gone full circle and we have infrastructure to setup a comparable experiment via richer input without the need of implementing a new experiment.