Multipath WebRTC Solutions

[Kevin Wang]

I'm looking to get WebRTC working over multiple connection paths similar to MPTCP. I've got a hacky solution working but it works by proxying WebRTC connections over each path instead of a more elegant solution.

Since each path results in a separate ICE candidate pair, one idea I've had is to disable ICE candidate selection and instead send data over multiple, valid ICE candidates with some load balancing mechanism. The specification states that a candidate must eventually be nominated, but what happens if I never nominate a candidate? Since data can flow through candidates even if not selected, would this cause any problems down the line?

Does anyone have any thoughts about if this would work? Also open to other ideas. I know WebRTC has explicitly chosen to not support multi-homing, but I'm wondering if there are workarounds for that.

Kevin