meta: feature parity with coturn
ernado opened this issue · 0 comments
ernado commented
TURN specs:
- RFC 5766 – base TURN specs
- RFC 6062 – TCP relaying TURN extension
- RFC 6156 – IPv6 extension for TURN
- RFC 7443 – ALPN support for STUN & TURN
- RFC 7635 – oAuth third-party TURN/STUN authorization
- DTLS support (http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00).
- Mobile ICE (MICE) support (http://tools.ietf.org/html/draft-wing-tram-turn-mobility-02).
- TURN REST API (http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)
- Origin field in TURN (Multi-tenant TURN Server) (https://tools.ietf.org/html/draft-ietf-tram-stun-origin-06)
- TURN Bandwidth draft specs (http://tools.ietf.org/html/draft-thomson-tram-turn-bandwidth-01)
- TURN-bis (with dual allocation) draft specs (http://tools.ietf.org/html/draft-ietf-tram-turnbis-04).
STUN specs:
- RFC 3489 – "classic" STUN
- RFC 5389 – base "new" STUN specs
- RFC 5769 – test vectors for STUN protocol testing
- RFC 5780 – NAT behavior discovery support
- RFC 7443 – ALPN support for STUN & TURN
- RFC 7635 – oAuth third-party TURN/STUN authorization
Supported ICE and related specs:
- RFC 5245 – ICE
- RFC 5768 – ICE–SIP
- RFC 6336 – ICE–IANA Registry
- RFC 6544 – ICE–TCP
- RFC 5928 – TURN Resolution Mechanism
The implementation fully supports the following client-to-TURN-server protocols:
- UDP (per RFC 5766)
- TCP (per RFC 5766 and RFC 6062)
- TLS (per RFC 5766 and RFC 6062): TLS1.0/TLS1.1/TLS1.2; ECDHE is supported.
- DTLS (http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00): DTLS versions 1.0 and 1.2.
- SCTP (experimental implementation).
Supported relay protocols:
- UDP (per RFC 5766)
- TCP (per RFC 6062)
Supported user databases (for user repository, with passwords or keys, if authentication is required):
- SQLite
- MySQL
- PostgreSQL
- Redis
- MongoDB