Open p-shahi opened 1 year ago
Hi, @p-shahi!
notion link for more reliable with UDP (therefore QUIC) is inaccessible
Could you please update it?
Work for this is being done at https://github.com/ChainSafe/js-libp2p-quic
@nikelborm The latest link for the hole punching measurement is here: https://github.com/probe-lab/network-measurements/blob/main/results/rfm15-nat-hole-punching.md#final-report-nat-hole-punching-measurement-campaign
and the final report actually shows: "In this NAT hole punching measurement campaign, we found that the success rate of hole punching is approximately 70%. Moreover, we discovered that the success of hole punching does not depend on the round trip time, and QUIC/UDP is not more likely to succeed than TCP" https://github.com/probe-lab/network-measurements/blob/main/results/rfm15-nat-hole-punching.md#conclusion-1
Thanks for sharing @p-shahi! That's very helpful
I guess the insight regarding why is from this section
While the hole punch success rates for TCP and QUIC are roughly the same, we see a completely different picture when both clients are allowed to use both transports for hole punching. In that case, we end up with a QUIC connection in almost 81% of the cases. We can explain this with generally faster connection establishment of QUIC connections. libp2p tries to hole punch using both transports at the same time, so both connection attempts race against each other. As soon as one connection succeeds, libp2p closes the remaining in-flight ones.