Marten Seemann

> I am going to start on this spike next week and report the findings here after. @thomaseizinger Any updates on this? Really curious to hear what you found out!

Great work, happy to see progress here @thomaseizinger! When I built a network simulator for QUIC testing, I had a similar problem, and maybe the solution is transferrable here: https://github.com/marten-seemann/quic-network-simulator....

Regarding iperf: Thank you for digging into this, @MarcoPolo! It would be really useful to have an iperf on TCP for comparison, as I've asked for in [my review](https://github.com/libp2p/test-plans/pull/184#pullrequestreview-1464557397) last...

Sounds like a good idea. What that be copy of the ping test, or can we somehow add another dimension to the matrix?

Makes sense. Having this tested end-to-end (with "real" NATs) is valuable, even if rust-libp2p and js-libp2p don't have an implementation right away.

This effort is currently blocked by https://github.com/testground/testground/issues/1488.

With the new wo-testground setup (we really need a better name for that…) this should be not too difficult to implement. I hacked a PoC in the [rtt-test branch](https://github.com/libp2p/test-plans/tree/rtt-test), although...

This mostly looks good. > 2. https://github.com/filecoin-project/data-transfer-benchmark is likely a good place to start from. Yes, but we'll probably want to end up with something that doesn't pull in dependencies...

Unless this happens organically, this is probably difficult to write a reliable test case for. We’d need to have one implementation generate a multiaddr that another implementation doesn’t understand. An...

There’s two types of „unsupported addresses“: 1. addresses of transports that you’re not listening on 2. addresses containing multiaddress components you don’t know about. This happens when we define new...