You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
There isn't a definitive way to determine whether or not a measurement
For example, the
rtt
test has aprotocol
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 aprotocol
oficmp
andtwping
would add aprotocol
oftwamp
.To Do
can-run
method return an additional field containing the as-would-be-run test specThe text was updated successfully, but these errors were encountered: