What are STUN, TURN and ICE?

We techies love our acronyms, but ICE, STUN, TURN, TURN… might be a little too much. What exactly are these things? Why do they exist and how does LiveSwitch use them? The purpose of this article is to demystify these techniques and their use.

Ultimately, the goal of real-time applications is high-throughput, low-latency communication between various clients that may (or may not) be behind restrictive firewall rules. This means the preferred priority of the following network communication protocols:

  1. UDP – Directly between the source and destination of the media stream.
  2. UDP – Indirect (relay) between the source and destination of a media stream.
  3. TCP – Indirect (relay) between the source and destination of a media stream via TCP.
  4. TCP/TLS – Indirect (relay) between the source and destination of a media stream, over TCP, with an additional layer of encryption.

Now that we know what we want, what does this have to do with STUN, TURN and ICE?

UDP – directly between the source and destination of the media stream

In order to establish a UDP connection between two clients, we need to be able to negotiate through the firewall. To do this, a given client must be able to target other clients’ public IP addresses and negotiated ports. However, most clients do not know their public IP addresses. This is where STUN comes in. STUN is a tool for

The postWhat are STUN, TURN and ICE? first appeared on Lenix Blog .

This article is reprinted from https://blog.p2hp.com/archives/9588
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment