13.07.2015 Views

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2 MessagesThe following sections specify how <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> messages are transportedand also specify <strong>VDS</strong> Remote <strong>Protocol</strong> message syntax.2.1 TransportThe <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> uses the DCOM Remote <strong>Protocol</strong>, as specified in [<strong>MS</strong>-DCOM], as its transport. On its behalf, the DCOM Remote <strong>Protocol</strong> uses the following RPC protocolsequence: RPC over TCP, as defined in [<strong>MS</strong>-RPCE].To access an interface, the client requests a DCOM connection to its object UUID endpoint on theserver, as specified in section 1.9.The RPC version number for all interfaces is 0.0.An implementation of the <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> MUST configure its DCOMimplementation or underlying RPC transport with the RPC_C_AUTHN_LEVEL_PKT_PRIVACY securityparameter.The <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> interfaces make use of the underlying DCOM securityframework, as specified in [<strong>MS</strong>-DCOM], and rely on it for access control. DCOM differentiatesbetween launch and access. An implementation of the <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> MAYdifferentiate between launch and access permission, and MAY impose different authorizationrequirements for each interface.2.2 Message SyntaxThe following sections specify <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> message syntax. Unlessotherwise stated, all data types and messages for the <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote <strong>Protocol</strong> MUST besupported.All enumeration structures contain a zero value defined as <strong>VDS</strong>_XXX_UNKNOWN. The zero values inthe enumerations are never valid as an input parameter. They are only used as an outputparameter.2.2.1 Common Data Types2.2.1.1 Data Types2.2.1.1.1 ULONGLONGThe ULONGLONG data type is defined in [<strong>MS</strong>-DTYP].2.2.1.1.2 DWORDThe DWORD data type is defined in [<strong>MS</strong>-DTYP].2.2.1.1.3 <strong>VDS</strong>_OBJECT_IDThe <strong>VDS</strong>_OBJECT_ID data type defines the <strong>VDS</strong> object identifier as a GUID for <strong>Virtual</strong> <strong>Disk</strong><strong>Service</strong> Remote <strong>Protocol</strong> storage objects.This type is declared as follows:[<strong>MS</strong>-<strong>VDS</strong>] — v20110610<strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> (<strong>VDS</strong>) <strong>Protocol</strong> <strong>Specification</strong>Copyright © 2011 Microsoft Corporation.Release: Friday, June 10, 201126 / 360

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!