netutils/coturn
1
0
Fork 0
mirror of https://github.com/coturn/coturn.git synced 2026-10-24 00:08:57 +03:00
Code Activity
Files
dependabot/github_actions/github/codeql-action-4.39.0
coturn/STATUS.md
Pavel Punsky 7c24c88a4c Document RFC 8489 and RFC 8656 instead of only the specs they obsolete (#2049) 
README.md and STATUS.md advertised RFC 5389, RFC 5766 and RFC 6156
without mentioning the RFCs that obsolete them, so the docs
simultaneously claimed conformance to dead specs and understated what
the code actually does: dual allocation, ADDRESS-ERROR-CODE, the
440/443/508 error codes and the RFC 8656 channel-number range are all
implemented and none were mentioned.

Both files now name RFC 8489 and RFC 8656, annotate the obsoleted specs
as such, and state the two gaps explicitly rather than leaving them
implied - the RFC 8489 authentication additions and RFC 8656 ICMP
relaying are absent. The transport and relay-protocol lists cite RFC
8656 rather than RFC 5766.

Drops the TURN-bis draft-04 line: that draft was published as RFC 8656,
now listed above it.

Merge order: the RFC 8489 entry credits first-wins handling of repeated
attributes, which is only complete once the Send DATA and ChannelBind
XOR-PEER-ADDRESS fixes have landed.
2026-08-11 20:32:04 -07:00

4.4 KiB
Raw Permalink Blame History

Currently implemented functionality:

  1. RFC5389 (new STUN protocol) full server and client implementations. RFC 8489 obsoletes RFC 5389: its message-processing rules are implemented, but its authentication additions (MESSAGE-INTEGRITY-SHA256, PASSWORD-ALGORITHMS, USERHASH, the nonce cookie) are not, so RFC 8489 clients use that spec's backward-compatible MD5/SHA-1 path. We do not maintain strict compatibility with the obsolete RFC 3489 "old STUN" protocol.

  2. RFC5766 TURN protocol full server and client implementations, updated to RFC 8656, which obsoletes RFC 5766. ICMP relaying (RFC 8656 Section 11.5) is not implemented. We support file-based long term user credentials, for now. We added experimental DTLS protocol, too.

  3. RFC6156 TURN IPv6 extension, folded into RFC 8656 and implemented including dual allocation.

  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 (DEPRECATED, opt-in via --rfc3489-compatibility; scheduled for removal in the next major release - see docs/rfc3489-deprecation.md).

  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/TCP network engine (NEV_UDP_SOCKET_PER_THREAD) optimized for modern kernels; all previous engine variants removed.

  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 consolidated into NEV_UDP_SOCKET_PER_THREAD (see item 30).

  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).

  56. TLS1.3 support (with openssl-1.1.1+)

  57. openssl-3.0 support

  58. Windows build support, MSVC and MinGW

  59. Add support to Prometheus as metrics interface

  60. Sanitize DB connection strings before printing to log

  61. Syslog facility support as an additional logging mechanism provider

  62. Support LibreSSL

  63. CMake as an alternative build system

Things to be implemented in future (the development roadmap) are described in the TODO file.

View Git Blame Copy Permalink