Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QUIC as Transport for Session Traversal Utilities for NAT (STUN) #2924

Open
hakarim740-com-ra opened this issue Jan 12, 2024 · 3 comments
Open

Comments

@hakarim740-com-ra
Copy link

hakarim740-com-ra commented Jan 12, 2024

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

@hakarim740-com-ra
Copy link
Author

The turn scheme with transport=quic would be reserved for non secure QUIC draft-banks-quic-disable-encryption-00

@alvestrand
Copy link
Contributor

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).

@hakarim740-com-ra
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants