1.3.4.1 Relationship Between Recovery and Durability
Transaction managers and durable resource managers can use any mechanism they choose to implement the durability guarantees of an atomic transaction.
At minimum:
Before a durable resource manager or subordinate transaction manager sends a Prepared notification to its superior transaction manager, it needs to first ensure that it can derive the information that is needed to contact its superior transaction manager and to inquire about the outcome of the transaction after a transient failure. This requirement is needed for the subordinate to perform recovery on In Doubt transactions.
Before a transaction manager can communicate the transaction outcome to a subordinate participant or the root application, it has to first ensure that it can derive the transaction outcome for as long as at least one durable subordinate has not acknowledged receipt of the transaction outcome. This requirement is needed for the superior to perform recovery on Failed to Commit transactions.
Before a durable resource manager or subordinate transaction manager acknowledges a Commit notification from its superior transaction manager, it has to first ensure that it will not perform recovery on the transaction after a transient failure. This requirement allows the superior transaction manager to implement the Presumed Abort optimization.
The information that is needed to be able to contact another participant is identical to the information that was needed to establish the initial transport session with that participant, as specified in [MS-CMPO] section 1.3.3.1.