1.7 Versioning and Capability Negotiation

  • Article

This document covers versioning issues in the following areas:

  • Supported Transports: This protocol can be implemented over either TCP or UDP running on either IPv4 or IPv6, as discussed in section 2.2.1.

  • Protocol Versions: This protocol specifies a mechanism by which the protocol client and TURN server can explicitly indicate what version of the protocol is supported. The protocol client does this by including the MS-Version attribute in an Allocate request message. The TURN server does this by including the MS-Version attribute in an Allocate response message. The MS-Version attribute is specified in section 2.2.2.17.

  • Security and Authentication Methods: This protocol supports authentication through long-term credentials supplied in the Allocate request message. This is specified in section 3.1.12.

  • Capability Negotiation: This protocol does not have any capability negotiation constraints.