m-lab / mbm Goto Github PK

The handshake that occurs right before data starts sending is weak to NAT and loss.

Looping until a READY-ack is received on the client and until it's sent on the server will help save against loss.

The handshake that occurs right before data starts sending is weak to NAT and loss.

Adding a nonce to the READY and READY-ack will help ensure the right client is about to receive the data.

while a version is set for gflags and logging, it is not compared when a client tries to connect. If the version is meant to protect against wire protocol changes, it should be.

The client calculates the receive rate but doesn't send it to the server. If it did, the server could use this as a signal of how well the wire is keeping up with the server's attempts to send.

The client logs the sequence numbers as they're received but doesn't send them back to the server. When it does, the server will be able to count loss/reordering for UDP tests.