Skip to content
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

Make tools produce an as-measured test spec #1379

Open
2 tasks
mfeit-internet2 opened this issue Dec 15, 2023 · 0 comments
Open
2 tasks

Make tools produce an as-measured test spec #1379

mfeit-internet2 opened this issue Dec 15, 2023 · 0 comments
Assignees

Comments

@mfeit-internet2
Copy link
Member

There isn't a definitive way to determine whether or not a measurement

For example, the rtt test has a protocol parameter that specifies what protocol should be used to make the measurement. We've always had a "default" behavior of ICMP, which is used by the (preferred) ping tool. There's no way to look at a measurement after the fact and determine what protocol was used other than what tool did it. That's a safe assumption now, but the architecture allows for ways to make that unsafe.

Need to have the system produce a test spec that reflects what was actually measured. E.g., the ping tool would add a protocol of icmp and twping would add a protocol of twamp.

To Do

  • Make the can-run method return an additional field containing the as-would-be-run test spec
  • Add something to the run containing that data. (It could, in theory, change from run to run.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready
Development

No branches or pull requests

1 participant