Skip to content

Commit 2c01868

Browse files
authored
Enhance clarity on WebRTC signaling process
Clarify the roles of codecs, media, and data channels in WebRTC signaling. Specify that TURN may be used for peers behind restrictive NAT, not always P2P.
1 parent a9c914e commit 2c01868

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

webrtc-signaling-explained.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This includes exchanging:
1616
WebRTC peers cannot discover each other on their own.
1717

1818
They need to:
19-
- agree on codecs and media setup
19+
- agree on codecs, media and datachannel setup
2020
- share network information
2121
- exchange security fingerprints
2222

@@ -75,7 +75,7 @@ Contain:
7575
6. Peer B sends Answer back via signaling channel
7676
7. Both sides exchange ICE Candidates
7777
8. ICE finds a working route
78-
9. Peers connect directly
78+
9. Peers connect directly (or through a TURN relay, but still end-to-end encrypted)
7979

8080

8181
## Signaling Server Responsibilities
@@ -95,7 +95,7 @@ It does *not*:
9595

9696
Once the WebRTC connection is established:
9797
- the signaling server is no longer required
98-
- peers communicate directly (unless TURN is used)
98+
- peers communicate directly (unless TURN is used when the peers are behind restrictive NAT)
9999

100100

101101
## Simplified Diagram

0 commit comments

Comments
 (0)