- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Thu, 19 Jun 2025 12:57:09 +0000
- To: public-webrtc-logs@w3.org
> Rather FQDN based only RFC 8445 put FQDN based ICE candidates into a limbo (pointer needed). It is a tough problem... "SSLTCP" used a fake SSLv2 handshake and from what I gathered came up in libjingle during the mid-2000s. The closest thing I have seen to an actual spec is [MS-TURN](https://learn.microsoft.com/en-us/openspecs/office_protocols/ms-turn/9e434b27-eb13-4249-b031-2d15c3835c8b) which calls it "Pseudo-TLS over TCP". The gist is basically "put a TLS 1.0" handshake with hardcoded stuff to fool firewalls. I assume it did back then but these days I expect DPI to reject TLS 1.0 handshakes. The nice property is that it avoids double encryption -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/236#issuecomment-2988021849 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 June 2025 12:57:11 UTC