mirror of https://github.com/coturn/coturn
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
111 lines
3.1 KiB
111 lines
3.1 KiB
==================================================================
|
|
|
|
### I. PLATFORMS SUPPORT ###
|
|
|
|
==================================================================
|
|
|
|
1) Fedora official package (turnserver or coturn ? TBD).
|
|
|
|
2) MS Windows support.
|
|
|
|
Cygwin is supported. A "real" MS-Windows port would
|
|
involve a usable GUI.
|
|
|
|
==================================================================
|
|
|
|
### II. DOCS ###
|
|
|
|
==================================================================
|
|
|
|
1) User's manual.
|
|
|
|
2) Developer's manual.
|
|
|
|
==================================================================
|
|
|
|
### III. NETWORK ENGINE ###
|
|
|
|
==================================================================
|
|
|
|
1) Kernel module for data channels.
|
|
|
|
==================================================================
|
|
|
|
### IV. PERFORMANCE OPTIMIZATION ###
|
|
|
|
==================================================================
|
|
|
|
1) A smarter load balancer has to be implemented.
|
|
|
|
The load balancer has to have a heartbeat channels with
|
|
the slave servers, currently it is only just a dumb
|
|
round-robin load distributor.
|
|
|
|
==================================================================
|
|
|
|
### V. SECURITY ###
|
|
|
|
==================================================================
|
|
|
|
1) Per-realm black/white lists.
|
|
|
|
==================================================================
|
|
|
|
### VI. STANDARDS SUPPORT ###
|
|
|
|
==================================================================
|
|
|
|
1) For extra difficult NAT/FWs, consider implementing Websockets.
|
|
|
|
2) ALPN with TLS and DTLS (when OpenSSL 1.0.2 is available).
|
|
|
|
3) Redirect draft.
|
|
|
|
4) DTLS 1.2 (when available).
|
|
|
|
5) TURN Proxy ? http://tools.ietf.org/html/draft-schwartz-rtcweb-return-00
|
|
|
|
==================================================================
|
|
|
|
### VII. MISC FEATURES ###
|
|
|
|
==================================================================
|
|
|
|
1) Locale support (?).
|
|
|
|
Currently we assume that all text data is 8-bits ASCII
|
|
encoded, like C locale. It would be nice to support localized
|
|
strings (both 8-bits and 2-bytes). But I am not sure
|
|
whether this is really important, given the essentially
|
|
backend nature of the TURN Server. The TURN server is so
|
|
deeply "hidden" in the network infrastructure that the
|
|
significant code complication may be unjustified.
|
|
|
|
2) HTTP or GUI status monitor and management.
|
|
|
|
For enterprise users, a management (configuration, status
|
|
and statistics) GUI has to be implemented. Currently, all
|
|
these features are available through the shell command
|
|
line, telnet client and through Redis command line.
|
|
|
|
3) Traffic recording (for selected allocations).
|
|
|
|
That would be a helpful feature for a large enterprise
|
|
(for testing and security purposes).
|
|
|
|
4) Ganglia monitoring.
|
|
|
|
5) Web API to the database (oAuth keys, for example).
|
|
|
|
6) Key exchange mechanism for oAuth.
|
|
|
|
==================================================================
|
|
|
|
### VIII. CODING STUFF ###
|
|
|
|
==================================================================
|
|
|
|
1) uclient program upgrade to a full solution.
|
|
|
|
==================================================================
|
|
|
|
|