Share via

1.7 Versioning and Capability Negotiation

  • Article

This specification covers versioning issues in the following areas:

  • Supported Transports: This protocol is implemented using SOAP over HTTP as specified in section 2.1.

  • Protocol Versions: This protocol has two interface versions as specified in section 2.

  • Security and Authentication Methods: This protocol passively supports Kerberos authentication over HTTP or HTTPS (as specified in [KERBKEY] and NT LAN Manager (NTLM) authentication over HTTP or HTTPS (as specified in [NTLM]).

  • Capability Negotiation: The RMS: ISV Extension Protocol supports limited capability negotiation via the <VersionData> type (section 2.2.4.3) that is present on all SOAP-based protocol requests. On a request, the <VersionData> structure contains a <MinimumVersion> and <MaximumVersion> value, indicating the range of versions the client is capable of understanding. On a response, the <VersionData> structure contains <MinimumVersion> and <MaximumVersion> values that the RMS server is capable of understanding.