1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas:
Supported Transports: This protocol uses the Distributed Component Object Model (DCOM) Remote Protocol [MS-DCOM], which in turn uses RPC over TCP as its only transport, as specified in section 2.1.
Protocol Versions: This protocol includes two DCOM interfaces (namely ITpmVirtualSmartCardManager and ITpmVirtualSmartCardManagerStatusCallback), both of which are version 0.0 as defined in section 2.2.
Security and Authentication Methods: Microsoft RPC, as defined in [MS-RPCE], is used to negotiate the authentication mechanism, as specified in [MS-SPNG] and in section 3.1.
Localization: This protocol uses predefined status codes and error codes. It is the caller’s responsibility to localize the status and error codes to localized strings.
Capability Negotiation: This protocol does not support explicit capability negotiation. However, as specified in section 3.1.4, the requestor can disable the use of the ITpmVirtualSmartCardManagerStatusCallback interface by providing a NULL callback parameter. Even if a callback parameter is provided by the requestor, the target can choose to not use the ITpmVirtualSmartCardManagerStatusCallback interface.