1.5 Prerequisites/Preconditions

The NSPI client implementation is expected to possess the network address of the server. This network address satisfies the requirements of a network address for the underlying transport of remote procedure call (RPC). This allows the NSPI client to initiate communication with the NSPI server using the RPC protocol.

The NSPI client and NSPI server are expected to share at least one security provider in common for the RPC transport. This allows the NSPI server to authenticate the NSPI client.

The NSPI client is expected to possess credentials recognized by the server. These credentials are obtained from the shared security provider. The mechanism for obtaining these credentials is specific to the protocol of the security provider used.

The NSPI server is expected to have determined any local policies as specified in sections 2, 3, and 5. This allows the server to provide consistent behavior for all communications in the protocol.

The server is expected to be configured to support the required codepages and language code identifiers (LCID), as specified in sections 2.2.4 and 2.2.5. This allows the server to provide the minimal required string conversions and sort orders.

The NSPI server is expected to be started and fully initialized before the protocol can start.