- From: Justin Uberti via GitHub <noreply@w3.org>
- Date: Fri, 20 Jun 2025 19:17:07 +0000
- To: public-webrtc-logs@w3.org
TURN-TLS is well defined by RFC 5766, so we can set that aside. Here, we can either try to focus on: 1) ICE-TLS using FQDN candidates 2) ICE-TCP but with a fake TLS handshake, a la "ssltcp". #1 is tricky due to unclear procedures for resolving FQDNs WRT ICE, as @fippo mentions. (eg v4 vs v6, multiple IPs returned from the query, etc) #2 might also be tricky as we'd need to signal the fact that the candidate needs the fake handshake, and probably also what version of handshake should be used. The IETF also historically frowned upon techniques that try to circumvent network restrictions, so that could also be an obstacle. Long story short, I think this is worth pursuing, but it's not going to be a cakewalk. -- GitHub Notification of comment by juberti Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/236#issuecomment-2992585230 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 June 2025 19:17:08 UTC