For the RTT and loss% measurements Trippy just does the obvious thing (i.e. RTT = recv time - send time and loss% = lost / total_sent). There is a plan [0] to

For the RTT and loss% measurements Trippy just does the obvious thing (i.e. RTT = recv time - send time and loss% = lost / total_sent). There is a plan [0] to add custom columns to Trippy and then to add various jitter measurements [1]. Thanks for pointing out the above RFCs, I'll take a look at those and see if they make sense to add to Trippy. [0] https://github.com/fujiapple852/trippy/issues/757 https://github.com/fujiapple852/trippy/issues/757 [1] https://github.com/fujiapple852/trippy/issues/39 https://github.com/fujiapple852/trippy/issues/39