1.1 Glossary
The following terms are defined in [MS-GLOS]:
Augmented Backus-Naur Form (ABNF)
computer name
core transaction manager facet
facet
globally unique identifier (GUID)
IPv4 address in string format
Phase Zero
signal
single-phase commit
subordinate transaction manager
superior transaction manager
transaction
transaction manager
Transport Layer Security (TLS)
two-phase commit
The following terms are specific to this document:
higher-layer business logic: The application functionality that invokes the functionality that is specific to this protocol.
OleTx transaction manager (OleTx TM): A transaction manager that implements the OleTx Transaction Protocol.
partner transaction manager: A transaction manager that plays the opposite role in an enlistment. When the TIP subordinate transaction manager facet is communicating with the partner transaction manager, the partner transaction manager acts as a superior transaction manager. When the TIP superior transaction manager facet is communicating with the partner transaction manager, the partner transaction manager acts as a subordinate transaction manager. The TIP transaction manager communicating with an application facet does not communicate with a partner transaction manager.
TIP: An acronym for the Transaction Internet Protocol, which is specified in [RFC2371] section 13.
TIP command: A TIP request or reply, including action and parameters, as specified in [RFC2371] section 13.
TIP command line: That part of a TIP message that contains a single TIP command. This is specified in the TIP standard [RFC2371] section 11 as a "line of ASCII text, using only octets with values in the range 32 through 126 inclusive, followed by either a CR (an octet with value 13) or an LR (an octet with value 10)."
TIP communication: An exchange of TIP commands and responses that follows message exchange patterns that conform to the TIP specification, as specified in [RFC2371].
TIP connection: A connection that is initiated and used, as specified in [RFC2371] section 4.
TIP pipelining: The process of concatenating more than one TIP command line into a single TCP message, as specified in [RFC2371] section 12.
TIP subordinate transaction manager: A subordinate transaction manager that implements the transaction management functionality that is specified in TIP.
TIP subordinate transaction manager facet: The facet that accepts requests to push a transaction from the partner transaction manager, sends requests to pull a transaction from the partner transaction manager, and participates as a subordinate in the Two-Phase Commit protocol.
TIP superior transaction manager: A superior transaction manager that implements the transaction management functionality that is specified in TIP.
TIP superior transaction manager facet: The facet that accepts requests to pull a transaction from the partner transaction manager, sends requests to push a transaction to the partner transaction manager, drives the Two-Phase Commit protocol with the partner transaction manager, and after a failure, performs recovery.
TIP transaction manager: A transaction manager that implements the transaction management functionality that is specified in TIP.
TIP transaction manager communicating with an application facet: The facet that accepts requests to create and complete a transaction from an application.
TIP transaction manager facets: The facets that constitute the transaction manager role, namely the TIP superior transaction manager facet, the TIP subordinate transaction manager facet, and the TIP transaction manager communicating with an application facet.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
