WebRTC
WebRTC provides secure real-time media and data between browsers or compatible endpoints. Application signalling is separate; ICE selects direct or relay transport, and media uses DTLS-SRTP.
Scope: WebRTC — requirements depend on the selected profile.
protocol · Catalog reviewed 2026-09-27
Related requirements
Review these entries for the services used in your design.
Infrastructure Requirements
- Application signalling service
- compatible ICE, DTLS and media implementations
- STUN/TURN access and relay capacity where required.
Network & Physical Requirements
| Port / allocation | Transport | Connection / signal flow | Feature and requirement | Evidence |
|---|---|---|---|---|
| Negotiated | UDP | WebRTC peer → Selected peer / TURN relay | Profile requirement · Core ICE-selected media and DTLS-SRTP WebRTC media transport Use configured endpoint/relay ranges. TURN server port alone does not cover its media relay allocation. | Source checked 2026-09-27 RFC 8835, Sections 3.4 and 4: middlebox functions and media transport |
Physical, link and configuration requirements
configuration · Profile requirement · Core
Obtain the application’s signalling URLs, transports and port configuration. WebRTC leaves this protocol choice to the application.
WebRTC application signalling architecture
HTTPS and WebSocket are common browser mechanisms; do not assume a universal WebRTC signalling socket.
Source checked 2026-09-27
1 Introduction; 3 Architecture and Functionality GroupsRFC 8825, January 2021
Gotchas & IT Notes
- ⚠There is no universal WebRTC firewall range. Capture service URLs, ICE policy, relay allocations and browser/endpoint capabilities.