a consistent and non-abitrary manner.

For the introductory purposes of this study, and based on cursory analysis of existing M-Lab data which was generated during suspected throttling events, we substantially rely on NDT’s measurements of round trip time, packet loss, throughput and network-limited time ratio as potential identicators of network disruption.[^4]

Round Trip Time (RTT)

:   ($MinRTT, MaxRTT, \frac{SumRTT}{CountRTT}$)\
    The time taken for the round trip of traffic between the server to client, computed as the difference between the time a packet is sent and the time an acknowledgement is received, also known as latency. There are a diversity of causes for latency, including ‘insertion latency’ (the speed of the network link), the physical distance of the path taken, ‘queue latency’ (time spent in the buffer of network routers), and ‘application latency.’ The last of these components, application latency, is accounted for within the NDT test under the metrics of *Receiver and Sender-limited time windows*. We are interested in latency that occurs due to network properties, primarily the queue, insertion and path latencies. Since the time taken should not change dramatically, fluctuations indicate a meaningful change in connectivity, such as a network outage that increases latency due to traffic to 