Candidats ICE et connectivité

ICE stands for Interactive Connectivity Establishment. It's a crucial framework in WebRTC that helps establish direct connections between peers, even when they are behind tricky networks like NATs or firewalls.

Think of ICE as a smart detective. It finds all possible routes for two people to talk directly and then picks the best one.

Many devices connect to the internet through routers that use NAT (Network Address Translation) or have firewalls. These act like security guards, often blocking direct incoming connections.

• NAT: Hides private network IPs behind a single public IP.
• Firewalls: Block unauthorized access.

Without ICE, establishing a direct peer-to-peer connection in such environments would be nearly impossible.

An ICE Candidate is essentially a potential network address and port where a peer can be reached. Each peer collects multiple candidates representing different ways it can communicate.

These candidates are like different phone numbers or addresses you might have: your home number, your work number, a friend's number where you can be reached, etc. ICE tries them all.

There are three main types of ICE candidates:

• Host Candidates: These are the peer's actual local IP addresses. They work best for direct connections within the same local network.
• Server Reflexive Candidates: Obtained from a STUN server. This is your public IP address and port as seen by an external server, helping peers behind NATs find each other.
• Relayed Candidates: Obtained from a TURN server. If direct connection isn't possible, a TURN server relays all traffic. This is the last resort.

When a WebRTC connection is initiated, each peer's browser (the WebRTC agent) starts collecting ICE candidates. It actively queries the local network, STUN servers, and potentially TURN servers to find all possible communication paths.

This collection process happens continuously in the background as the RTCPeerConnection is being set up.

In JavaScript, you listen for icecandidate events on your RTCPeerConnection object to get these candidates. Each event provides a new candidate to share with the remote peer via your signaling server.

Once candidates are gathered, they must be exchanged between the two peers. This happens through your signaling server, the same server used to exchange SDP offers and answers.

• Each peer sends its collected candidates to the signaling server.
• The signaling server forwards these candidates to the other peer.

This process is often called "trickle ICE" because candidates are sent as they are found, rather than waiting for all of them.

After exchanging candidates, ICE begins its connectivity checks. Both peers try to establish connections using every possible pair of local and remote candidates. This involves sending small "STUN binding requests" to test reachability.

ICE then prioritizes and selects the most efficient and reliable path. It prefers direct host connections, then STUN-relayed public IPs, and finally TURN-relayed connections.

In this lesson, you learned about ICE Candidates and how they enable WebRTC to establish peer-to-peer connections across diverse networks.

• ICE candidates are potential network addresses.
• They come in types: Host, Server Reflexive (STUN), and Relayed (TURN).
• Peers gather and exchange these candidates via a signaling server.
• ICE then performs connectivity checks to find the best possible path for direct communication.

ICE is the unsung hero ensuring your real-time calls find a way through the internet's complexities!