Issues from WebRTC-direct to discuss.

[sukhman-sukh]

Description

Py-libp2p has webrtc-direct almost fully implemented as a transport layer module. The connection dialer, streaming, SDP management, and certificate management components are complete. However, there are two remaining blockers that need resolution:

Listener implementation

In js-libp2p, the WebRTC base library provides an ICEUDPMuxListener for handling incoming STUN requests:
https://github.com/libp2p/js-libp2p/blob/cf9aab5c841ec08bc023b9f49083c95ad78a7a07/packages/transport-webrtc/src/private-to-public/listener.ts#L154-L155

I have not found an equivalent in Python (aiortc or related libraries). Guidance or a stable workaround here would be very helpful.

Remote fingerprint handling

In js-libp2p, remoteFingerprint is available on RTCPeerConnection:
https://github.com/libp2p/js-libp2p/blob/main/packages/transport-webrtc/src/private-to-public/utils/get-rtcpeerconnection.ts#L63-L70

However, aiortc does not expose remote_fingerprint directly.

Blockers

• Lack of a listener equivalent to ICEUDPMuxListener

• No remote_fingerprint support in aiortc

Request

Looking for suggestions, stable workarounds, or design guidance for implementing these two missing pieces so that webrtc-direct can be completed in Py-libp2p.