This records the best-case, shortest, round-trip time observed in this loopback test session, giving the admin a best-case latency floor for the tested path segment, useful as a baseline to compare cktOamLoopbackReceivedHigh and cktOamLoopbackReceivedAvg against when judging how much variability exists in the path's response times. For example, a low and stable cktOamLoopbackReceivedLow paired with a much higher Received Avg would tell the admin the path is capable of fast responses but is inconsistent under whatever conditions caused the slower averages.