Interactions Between the RM and EM Models
The specification governs
This page explains the design of the Vultron Protocol. It is informative: the normative text is the Vultron Protocol Specification. Where this page and the specification differ, the specification governs.
This page lists the constraints on how the Report Management (RM) and Embargo Management (EM) processes interact. The RM process is specific to each Participant. The EM process is global to the case. For this reason, most constraints describe which RM states a Participant should be in when it takes part in an EM transition.
Formulas on this page use \(q^{rm}\) for the RM state of a Participant and \(q^{em}\) for the EM state of the case. The formulas use the single-letter state abbreviations from each model. The RM process model introduces the RM abbreviations. The EM formal model defines the EM abbreviations. You do not need the rest of the EM formal model to read this page.
For how an embargo runs from start to finish, see the Embargo Lifecycle explanation.
Start Embargo Negotiations As Early as Possible
A Sender often wants to know the embargo terms before it sends a report. The protocol serves that need, but not by running the EM process ahead of the report. The EM process is per case, so before a case exists there is no EM state machine for a transition to occur in.
Two mechanisms give the Sender what they need instead:
-
Read the Recipient's published default. A Report Recipient's published default embargo is a standing proposal. A Sender that reads this default knows the terms in advance, with no exchange at all. If the Recipient has published nothing, the short protocol default applies. The Sender then still knows the floor.
-
State terms with the report. A Sender proposes its own terms by including a proposed embargo with the report submission. If the two sets of terms differ, the shortest proposal wins and the longer one becomes a proposed revision. Agreement thus occurs at case creation, not in a negotiation before it.
The EM process SHALL NOT begin before a case exists. A Sender that wishes to fix terms before sharing a report SHALL either rely on the Recipient's published default embargo or include a proposed embargo with the report submission.
This Guidance Changed
Earlier versions of this page let the EM process begin before the Sender sent the report to a potential Participant (\(q^{rm} \in S\)). The first step was the propose transition \(q^{em} \in N \xrightarrow{p} P\). ADR-0096: A Protocol Default Embargo Replaces the Pre-Case Phase withdrew that.
The motivation was sound, and the sections above keep it. A Participant may want to ensure acceptable embargo terms before it shares a report with a potential recipient.
The mechanism was not. EM is a global per-case state machine. A \(N \xrightarrow{p} P\) transition before any case exists therefore names a machine instance that cannot exist. The two mechanisms above deliver the same assurance without a pre-case phase.
The EM process SHALL begin when a recipient reaches RM Received (\(q^{rm} \in R\)), because that is when the case exists. For an embargo-eligible case, this requirement is not merely a SHOULD. An embargo is established at case creation, from the Recipient's published default, the Sender's proposal, or the protocol default.
The diagram below shows the EM process beginning when the case is created.
---
title: EM Begins at Case Creation
---
stateDiagram-v2
direction LR
state RM {
Received
}
state EM {
None --> Proposed : propose
Proposed --> Active : accept
}
RM --> EM : begin at<br/>case creation
The protocol applies the propose and accept transitions above atomically at case creation. The intermediate Proposed state is never externally observable (EP-04-002).
Negotiate Embargoes for Active Reports
Because an embargo-eligible case already starts with an Active embargo, later proposals are revisions (\(q^{em} \in A \xrightarrow{p} R\)). A case still at EM None after creation was not embargo-eligible. No embargo may be proposed for that case while it is still not embargo-eligible (VP-06-001). A proposal from None (\(q^{em} \in N \xrightarrow{p} P\)) would need a case at None to become embargo-eligible after creation. Nothing in the protocol does that today (ADR-0096).
The constraints below apply to either kind of proposal. The diagrams show the None to Proposed step. Every rule on this page that mentions EM Proposed governs only that later step. The case-creation traversal never rests in Proposed, so no Participant can observe the case in that state or act on it there (EP-04-002).
A Participant MAY propose embargo terms in any of the active RM states (\(q^{rm} \in \{ R,V,A \}\)).
The first diagram shows the active RM states, from which proposing is allowed.
---
title: Proposing From an Active RM State
---
stateDiagram-v2
direction LR
state RM {
Received
Valid
Accepted
}
state EM {
None --> Proposed : propose
}
RM --> EM : ok to<br/>proceed
A Participant SHOULD NOT propose embargo terms from an inactive RM state (\(q^{rm} \in \{ I,D,C \}\)).
The second diagram shows the inactive RM states, from which proposing should be avoided.
---
title: Proposing From an Inactive RM State
---
stateDiagram-v2
direction LR
state RM {
Invalid
Deferred
Closed
}
state EM {
None --> Proposed : propose
}
RM --> EM : avoid
The RM state subsets define the active and inactive sets.
Negotiate Embargoes Through Validation and Prioritization
Embargo Management MAY run in parallel to validation (\(q^{rm} \in \{R,I\} \xrightarrow{\{v,i\}} \{V,I\}\)) and prioritization (\(q^{rm} \in V \xrightarrow{\{a,d\}} \{A,D\}\)) activities.
Renegotiate Embargoes While Reports Are Valid Yet Unclosed
EM revision proposals (\(q^{em} \in A \xrightarrow{p} R\)) and acceptance or rejection of those proposals (\({q^{em} \in R \xrightarrow{\{a,r\}} A}\)) MAY occur during any of the valid yet unclosed RM states (\({q^{rm} \in \{ V,A,D \} }\)).
The diagram below shows the revision cycle running while the report is valid yet unclosed. Accepting a revision returns the case to Active under the new terms. Rejecting a revision normally keeps the prior terms in force and returns to Active.
Sometimes the CS is already public, exploited, or attacked when the Case Owner rejects the last open revision. In that condition, the CASE_MANAGER follows the rejection with a termination in the same act. EM then ends in eXited, not in Active (MSM-07-032, EMB-04-002).
---
title: Revising an Embargo While the Report Is Valid Yet Unclosed
---
stateDiagram-v2
direction LR
state RM {
Valid
Accepted
Deferred
}
state EM {
Revise --> Active : accept
Revise --> Active : reject
Active --> Revise : propose
}
RM --> EM : ok to<br/>proceed
Avoid Embargoes for Invalid Reports
A Participant in RM Invalid (\(q^{rm} \in I\)) SHOULD NOT propose embargo terms.
The diagram below shows the proposal to avoid.
---
title: Avoid Proposing From RM Invalid
---
stateDiagram-v2
direction LR
state RM {
Invalid
}
state EM {
None --> Proposed : propose
}
RM --> EM : avoid
...but Don't Lose Momentum if Validation Is Pending
Outstanding embargo negotiations (\(q^{em} \in P \xrightarrow{\{r,p\}} \{N,P\}\)) MAY continue in RM Invalid (\(q^{rm} \in I\)), for example if additional information is expected that may promote the report from Invalid to Valid (\(q^{rm} \in I \xrightarrow{v} V\)).
As noted above, nothing produces an outstanding proposal in Proposed at present. This rule would therefore govern only a case at None that later became embargo-eligible. The diagram below shows an outstanding proposal that can still be superseded or rejected while the report waits in Invalid.
---
title: Continuing an Outstanding Negotiation From RM Invalid
---
stateDiagram-v2
direction LR
state RM {
Invalid --> Valid: (anticipated)
}
state EM {
Proposed --> Proposed : propose
Proposed --> None : reject
}
RM --> EM : ok to<br/>proceed
Only Accept Embargoes for Possibly Valid Yet Unclosed Reports
Embargo Management MAY proceed from EM Proposed to EM Active (\(q^{em} \in P \xrightarrow{a} A\)) when RM is neither Invalid nor Closed (\(q^{rm} \in \{R,V,A,D\}\)).
As above, this rule covers the acceptance of a proposal made after case creation. The case-creation acceptance is atomic. At that point the Case Owner is in RM Received, which this rule allows anyway. The diagram below shows the RM states from which accepting a proposal is allowed.
---
title: Accepting a Proposal From a Potentially Valid Yet Unclosed RM State
---
stateDiagram-v2
direction LR
state RM {
Received
Valid
Accepted
Deferred
}
state EM {
Proposed --> Active : accept
}
RM --> EM : ok to<br/>proceed
Embargo Management SHOULD NOT proceed from EM Proposed to EM Active when RM is Invalid or Closed (\(q^{rm} \in \{I,C\}\)).
The diagram below shows the RM states from which accepting a proposal should be avoided.
---
title: Avoid Accepting a Proposal From RM Invalid or Closed
---
stateDiagram-v2
direction LR
state RM {
Invalid
Closed
}
state EM {
Proposed --> Active : accept
}
RM --> EM : avoid
Embargo Management MAY proceed from EM Proposed to EM None (\(q^{em} \in P \xrightarrow{r} N\)) when RM is Invalid or Closed.
The diagram below shows rejection as the allowed outcome from those states.
---
title: Rejecting a Proposal From RM Invalid or Closed
---
stateDiagram-v2
direction LR
state RM {
Invalid
Closed
}
state EM {
Proposed --> None : reject
}
RM --> EM : ok to<br/>proceed
Report Closure, Deferral, and Active Embargoes
The RM process of each Participant can interact with the case-level EM process in several ways. The sections below describe them.
Participants SHOULD NOT close reports (\(q^{rm} \in \{R,I,D,A\} \xrightarrow{c} C\)) while an embargo is active (\(q^{em} \in \{ A,R \}\)).
The diagram below shows the closures to avoid while the embargo is Active or being revised.
---
title: Avoid Closing a Report During an Active Embargo
---
stateDiagram-v2
direction LR
state RM {
Received --> Closed: close
Invalid --> Closed: close
Deferred --> Closed: close
Accepted --> Closed: close
}
state EM {
Active
Revise
}
EM --> RM : avoid
Instead,
Reports with no further tasks SHOULD be held in either Deferred or Invalid (\({q^{rm} \in \{ D,I\}}\)), depending on the report validity status, until the embargo has terminated (\({q^{em} \in X}\)).
This hold lets Participants stop work on a report but still maintain their participation in an extant embargo. Even so,
Participants who choose to close a report (\(q^{rm} \in \{R,I,D,A\} \xrightarrow{c} C\)) while an embargo remains in force (\(q^{em} \in \{A,R\}\)) SHOULD communicate their intent to either continue to adhere to the embargo or terminate their compliance with it.
Report closure or deferral alone does not terminate an embargo.
A Participant's closure or deferral (\(q^{rm} \in \{C,D\}\)) of a report while an embargo remains active (\(q^{em} \in \{A,R\}\)) and while other Participants remain engaged (\(q^{rm} \in \{R,V,A\}\)) SHALL NOT automatically terminate the embargo.
The diagram below shows that the RM closures do not imply the EM terminate transition.
---
title: Report Closure Does Not Terminate the Embargo
---
stateDiagram-v2
direction LR
state RM {
Received --> Closed: close
Invalid --> Closed: close
Deferred --> Closed: close
Accepted --> Closed: close
}
state EM {
Active --> eXited: terminate
Revise --> eXited: terminate
}
RM --> EM : does not imply
The protocol expects Participants to continue to adhere to the embargo until the embargo is explicitly terminated. However,
Participants MAY choose to terminate their compliance with an embargo at any time.
This choice is usually an undesirable development. The Participant must still tell the other Participants about this choice. The other Participants can then decide whether the extant embargo is still viable.
Any changes to a Participant's intention to adhere to an active embargo SHOULD be communicated in addition to any necessary notifications regarding RM or EM state changes.
Upon receipt of a Participant's notification of intent to end their compliance with an embargo, other Participants MAY choose to terminate the embargo.
Closing a Case While an Embargo Is Active
The RM process is specific to each Participant, but the EM process is global to the case. One Participant's closure therefore leaves the shared embargo in force for everyone else (VP-13).
The Case Owner is different, because the Case Owner's departure closes the case for every Participant. While the embargo is Active or being revised, the CASE_MANAGER refuses the Case Owner's request to leave. The case then stays open with the embargo in force (CM-23). The Case Owner terminates the embargo first, for example once the vulnerability is public, and then leaves. Close your participation in the case-management how-to shows the messages involved.