Share via

3.3.1 Abstract Data Model

  • Article

In addition to the abstract data model described in section 3.2.1, when implementing an IXnRemote server role an MSDTC Connection Manager: OleTx Transports Protocol partner MUST allocate and maintain the following local data element:

Server TCP Port: A 4-byte unsigned integer whose value determines the TCP port number of the RPC server endpoint.<9>

Service Network Protocols: An implementation-specific object that identifies which RPC protocol sequences to use, such as ncacn_ip_tcp, ncacn_nb_nb, ncacn_ip_udp, and ncacn_spx.<10> The ncacn_ protocols are described in [MS-RPCE] section 2.

Server Security Settings: A collection of settings the value of which represents security provider–specific settings used to configure the RPC security of the server. As those settings are internal to this protocol and no network traffic is involved in the setting of their values, the following conditions SHOULD be observed:<11>

  • They are stored on an implementation-specific source that SHOULD be secured for write access by system administrators only.

  • They SHOULD be established during installation, and the MSDTC Connection Manager: OleTx Transports Protocol does not modify the settings. It only reads them during protocol instance initialization. There are no protocols defined to initialize them.

  • Since the storage location is implementation specific, a separate tool could be used to update the storage locations independent of the protocol.

The following settings are the Server Security Settings that MUST be specified:

  • RPC Security Provider: A 4-byte unsigned integer element that identifies the security provider being used. The possible values for this element are defined in [MS-RPCE] section 2.2.1.1.7.