bug(webrtc): Chrome data-channels not closing

Summary

When connecting a js-libp2p (browser) peer and rust-libp2p peer via webrtc, data channels are no properly closing.
The first reason for that is js-libp2p never closes them to begin with. That is being addressed here: https://github.com/libp2p/js-libp2p/pull/1976

The next issue is that the rust-libp2p WebRTC implementation webrtc-rs doesn't properly respond to the browsers stream reset, leaving the browser in a closing state.

• https://github.com/webrtc-rs/webrtc/issues/468

And in case of switching to str0m https://github.com/libp2p/rust-libp2p/issues/3659, it also has the same issue:

• https://github.com/algesten/str0m/issues/286

Possible Solution

I am opening this issue for visibility, and to possibly get some support with the PR reviews on these repositories.
This can be closed when bumping the dependency version.

Would you like to work on fixing this bug?

Yes

Start by reviewing js-libp2p PR 1976 and the linked webrtc-rs issue 468 and str0m issue 286 to confirm the upstream stream-reset behavior. Done means the relevant upstream fix is available and rust-libp2p can bump the dependency so browser data channels leave the closing state.