Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with the behavior that is described in this document.
The TIP interoperability application role MUST extend the common abstract data model that is specified in section 3.1.1 to include the following data elements:
TIP Interoperability Application Name: A name object that is used to identify the TIP interoperability application with the underlying transport protocol, as specified in [MS-CMPO].
TIP Interoperability Provider Name: A name object that identifies the TIP interoperability provider that the TIP interoperability application MUST use.
A TIP interoperability application MUST implement the states for its supported connection types as specified in the following subsections of section 3.2.1.