2.1 Transport

For its transport, this protocol uses the Distributed Component Object Model (DCOM) Remote Protocol, as specified in [MS-DCOM]. The DCOM Remote Protocol uses the following RPC protocol sequence: RPC over TCP, as specified in [MS-RPCE].

To access an interface, the client requests a DCOM connection to its object UUID endpoint on the server, as described in Standards Assignments (section 1.9).

The RPC version number for all interfaces is 0.0.

An implementation of the Shadow Copy Management Protocol MAY configure its DCOM implementation or underlying RPC transport with authentication parameters to restrict client connections. The details of this behavior are implementation-specific.<3>

The Shadow Copy Management Protocol interfaces make use of the underlying DCOM security framework, as specified in [MS-DCOM], and rely on it for access control. DCOM differentiates between launch and access.<4>