Investigating on how Smoldot uses libp2p-webRTC

[freddyli7]

Issue summary

Now with the prototype of using WebRTC between WASM peer in browser and native rust peer completed, the question is how does this woking logic applied to the real case AKA smoldot <-> polkadot full node.

Other information and links

Two smoldot repo:
https://github.com/paritytech/smoldot — this is deprecated already
https://github.com/smol-dot/smoldot

These are the libp2p-webRTC related commits in smoldot:
Rename /webrtc to /webrtc-direct: looks like this is related to this spec
Enable WebRTC by default #2977
libp2p-webRTC related fix: When opening a WebRTC connection, the ufrag and password of SDP requests are now properly set according to the WebRTC libp2p specification
The WebRTC protocol implementation is now up to date with the specification with this commit
Add support for WebRTC #2579

The goal is to look into each one of them, specially Implement WebRTC messages framing #2896 and Add support for WebRTC #2579 and prepare for the development environment setup for litep2p-webrtc

[haikoschol]

https://github.com/ChainSafe/gossamer-parity/blob/main/webrtc/smoldot_notes.md

[haikoschol]

I'm closing this issue since we now know quite a bit about the webrtc implementation in smoldot and the issue does not have any clear deliverables.