forked from coturn/coturn
-
Notifications
You must be signed in to change notification settings - Fork 0
/
STATUS
131 lines (75 loc) · 3.41 KB
/
STATUS
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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
Currently implemented functionality:
1) RFC5389 (new STUN protocol) full server and client
implementations. We do not maintain strict compatibility
with the obsolete RFC 3489 "old STUN" protocol.
2) RFC5766 TURN protocol full server and client
implementations. We support file-based long term
user credentials, for now. We added experimental DTLS
protocol, too.
3) RFC6156 TURN IPv6 extension.
4) We support the following client-to-server
network transports for TURN messages:
a) UDP
b) TCP
c) TLS
d) DTLS
5) Performance tested.
6) Torture and stability tests.
7) Multiple *NIX platforms tested and supported.
8) TTL field handling implemented for all platforms, preferred behavior in RFC5766.
9) TOS (DiffServ and ECN) field handling (preferred behavior of RFC 5766) implemented,
for Linux. Other platforms support the alternative behavior of RFC 5766.
10) DF field alternative behavior of RFC 5766 implemented.
11) Bandwidth limitation per session implemented.
12) RFC 5769 test vectors implemented (where applicable).
13) RFC 5780 STUN extension: NAT behavior discovery.
14) C++ mapping implemented.
15) RFC 6062 TCP relaying implemented.
16) Users can be stored in PostgreSQL database.
17) Users can be stored in MySQL database.
18) TURN Server REST API implemented.
19) Short-term credentials mechanism implemented.
20) Simple load-balancing with ALTERNATE-SERVER implemented.
21) Redis database support added.
22) RFC3489 backward compatibility.
23) Multithreaded TCP relay processing (UDP relay has been
multithreaded from the beginning).
24) Networking engine 2.0 implemented, with more scalable approach
to the UDP sockets handling.
25) DOS attack prevention logic added to the server; DOS attack client
emulation implemented.
26) Linux UDP sockets workaround added to counter RFC 1122 behavior.
27) DTLS sockets re-implemented for better scalability and for Cygwin
compatibility.
28) A number of TLS/DTLS improvements added: multiple protocols support, certificate check option.
29) SHA256 support added (experimental).
30) UDP network engine optimized for the new Linux kernels (3.9+).
31) ICE Mobility draft implemented (experimental).
32) CLI implemented.
33) DH and EC TLS ciphers added.
34) HTTP "keep alive" request supported.
35) Optimized (for thousands and more sessions) timers implementation.
36) TCP network engine optimized for the new Linux kernels (3.9+).
37) telnet-based monitor implemented.
38) Package memory copy eliminated in traffic routing.
39) Congestion avoidance implemented, for all protocols.
40) Coturn project forked from rfc5766-turn-server.
41) Multi-tenant server implemented (ORIGIN support).
42) Bandwidth draft support added.
43) MongoDB support added.
44) Double (dual) allocation added (SSODA draft).
45) Secure MySQL connection implemented.
46) Third-party security mechanism (through oAuth) implemented.
47) SQLite support added as default database.
48) DTLS1.2 supported.
49) ALPN stun.turn and stun.nat-discovery supported.
50) SSLv2 support cancelled.
51) The short-term credentials server-side support cancelled (still
supported in the client library).
52) Web HTTPS admin interface implemented.
53) SHA384 and SHA512 support added (experimental).
54) native SCTP experimental support.
55) Multi-tenant implementation based upon third-party authorization
(oAuth).
Things to be implemented in future (the development roadmap)
are described in the TODO file.