1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas:
Protocol Version: A client wanting to use the EventLog Remoting Protocol Version 6.0 can attempt to connect to the UUID for the EventLog Remoting Protocol Version 6.0. If this UUID does not exist, the EventLog Remoting Protocol [MS-EVEN] UUID may still exist, and the client can attempt to connect to it.
Security and Authentication Methods: RPC servers and clients in the EventLog Remoting Protocol Version 6.0 use an RPC authentication service, as specified in section 2.1.
Localization: The EventLog Remoting Protocol Version 6.0 defines several methods that support localization. These methods each take a locale identifier (ID) (as specified in [MS-GPSI] Appendix A), which is used to determine the language preferences for localization.
The EventLog Remoting Protocol Version 6.0 RPC interface has a single version number. The version number can change, but this version of the protocol requires it to be a specific value (for more information, see section 2.1.1). The EventLog Remoting Protocol Version 6.0 can be extended by adding RPC messages to the interface with opnums lying numerically beyond those defined here. An RPC client determines whether such methods are supported by attempting to invoke the method; if the method is not supported, the RPC run time returns an "opnum out of range" error, as specified in [C706] and [MS-RPCE]. Details on RPC versioning and capacity negotiation in this situation are specified in [C706] section 6.3 and [MS-RPCE] section 1.7.