1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas:
Supported Transports: The DNS Server Management Protocol uses the RPC protocol as a transport and multiple RPC transports.
Protocol Versions: This protocol has a version number of 5.0.
Security and Authentication Methods: Authentication and security are provided as specified in [MS-RPCE].
The DNS server requests the principal name for the security provider available on the system. Then Providers, for whom a principal name was obtained, are registered as supported authenticating mechanism for RPC calls. An RPC client using TCP, immediately after creating a binding attempts to negotiate authentication using RPC_C_AUTHN_GSS_NEGOTIATE and authentication level as RPC_C_AUTHN_LEVEL_PKT_INTEGRITY as specified in sections 2.1.1 and 2.1.2.
Localization: This protocol passes text strings in various methods. Localization considerations for such strings are specified where relevant.
Capability Negotiation: The DNS Server Management Protocol does not support negotiation of the protocol version to use. Instead, this protocol uses only the protocol version number specified in the IDL for versioning and capability negotiation. Note that the present version of the IDL includes a client version input parameter (dwClientVersion) for some of the method calls (section 2.2.1.2.1). This parameter allows the server to provide responses conforming to earlier versions of certain data structures associated with those method calls, while allowing extensibility of the present version of the protocol.