You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of a scenario where you completely trust the path between the endpoints AND need TURN seems far-fetched to me. draft-banks seems to be dead, anyway (published in 2021 and never got a -01, far less an adoption, as far as the datatracker goes).
The idea of a scenario where you completely trust the path between the endpoints AND need TURN seems far-fetched to me. draft-banks seems to be dead, anyway (published in 2021 and never got a -01, far less an adoption, as far as the datatracker goes).
In this case the combination of the turn scheme with transport=quic should raise an error. The only supported scheme for QUIC must be turns.
We need a spec for running TURN over QUIC, similar to: RTP over QUIC (RoQ), who agree?
It should be possible to use both, Streams or Unreliable Datagrams
The URL would look like this:
turns:example.com?transport=quic&reliable=true
The text was updated successfully, but these errors were encountered: