1.7 Versioning and Capability Negotiation

This specification covers versioning issues in the following areas:

Supported Transports: This protocol uses the RPC protocol sequence ncacn_ip_tcp, as specified in section 2.1.

Protocol Versions: This protocol has only one interface version, which is version 1.0, as specified in section 2.1.

Security and Authentication Methods: [MS-RPCE] uses Generic Security Services (GSS) [RFC2743] to negotiate the authentication mechanism with the protocol, as specified in [MS-SPNG] and [RFC4178]. This negotiation is described in section .

Capability Negotiation: This protocol does not perform any explicit capability negotiation between client and server. The server configuration is stored in Active Directory and is versioned there. The processing rules for this versioning scheme are described in section Configuration information is transferred from server to client unconditionally, as specified in section

Currently, this protocol specifies a single version of the server configuration object (section, and a fixed set of configuration choices for cryptographic algorithms. When any other cryptographic algorithms are configured in the server configuration object, both server and client behavior is undefined.