1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
==================================================================
### 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 ###
==================================================================
Nope
==================================================================
### 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).
==================================================================
### 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 ###
==================================================================
nope
==================================================================
|