WebRTC transports and multiaddrs

Thank you for your answer. So to generalize the concept, multiaddrs only represent the connection establishment and not the communication, right? WebRTC might be the only case where connection and communication don’t use the same channel though, so this problem only applies here. This is mainly because WebRTC is meant for the browsers, and we can’t use UPnP in browser Javascript to do port forwarding, unlike in the Go and Node.js implementations of libp2p.