specifications: Explicitly call out the unbinding flows

And refer to the threat model from the high level device and interface
lifecycle section.

Fixes #89

Signed-off-by: Samuel Ortiz <[email protected]>

specification/07-theory_operations.adoc

@@ -561,7 +561,7 @@ host supervisor domain manager may bind a TDI and a TVM together, through the
 1. The host supervisor domain manager initiates the interface binding flow by
    having the TSM move the TDI into the TDISP `CONFIG_LOCKED` state. This is
    achieved through the `sbi_covh_bind_interface()` `COVH` ABI.
-2. The TVM xref:_tdi_acceptation[verifies and accepts the locked TDI] into its
+2. The TVM xref:tdi-acceptation[verifies and accepts the locked TDI] into its
    TCB.
 3. The TVM asks the TSM to move the TDI to the TDISP `RUN` state, by calling the
    `sbi_covg_start_interface()` `COVG` ABI.
@@ -893,6 +893,11 @@ compromising any TVM confidential assets.
 As the platform resources owner, the host supervisor domain manager can assign
 a TDI to a TVM by binding them together (step 3). At any point in time, it can
 reclaim that physical resource by unbinding (step 8a) it from its TVM.
+Graceful and explicit unbinding through the `COVH` ABI will clear all
+confidential data and abort any outstanding DMA requests, as described in the
+xref:interface-unbinding[Interface Unbinding] section. Implicit TDI unbinding
+from the host supervisor domain manager represents a security threat that is part
+of the xref:05-security_model.adoc#security-model[CoVE-IO threat model] scope.
 
 Before binding a TDI and a TVM together, the host supervisor domain manager must
 first require the TSM to connect (step 1) to the physical device through secured