Skip to content
Reference

RCV Embargo Scenario: Reporter + Coordinator + Vendor

Overview

The RCV embargo scenario follows the embargo from end to end in a three-party case. A Reporter submits a report to a Coordinator, who opens the case and invites a Vendor. Creating the case activates the default embargo. So the later proposal of the Reporter revises that embargo, and does not start a first one. The Coordinator then ends the embargo deliberately, before the vulnerability is published.

Participants:

  • Reporter — discovers the vulnerability, submits the report and proposes new embargo terms.
  • Coordinator — receives the report, then validates, engages and owns the case. It activates the revised embargo and later ends it.
  • Vendor — joins by invitation, consents to the revision and develops the fix.
  • Case Actor — the actor that holds the CASE_MANAGER role for this case. It commits every embargo decision to the ledger and relays each proposal to the other participants.

Protocol narrative

1. Report submission

The Reporter submits the report, the Coordinator validates it and engages the case, and the Vendor joins by invitation. The default embargo is active from case creation, so the case is at Embargo Management (EM) state ACTIVE.

Antecedent: Reporter has knowledge of the vulnerability.

2. Embargo proposal

The Reporter proposes new embargo terms. The proposal goes only to the CASE_MANAGER. The CASE_MANAGER moves the case to EM REVISE, records the proposal and relays it to the Coordinator and the Vendor.

The Vendor accepts, which records its consent and changes no EM state. The Coordinator, as Case Owner, answers with its decision for the case. It activates the revision, and the case returns to EM ACTIVE.

Each participant waits for the relayed invitation on its own replica. No participant waits for a message from another participant.

With the revised embargo in force, the Reporter asks about it in a case note, and the Vendor answers. In this scenario the Reporter proposes terms before it asks anything, and the Vendor's next decision comes after its answer.

Antecedent: the case is engaged and EM is ACTIVE.

3. Fix lifecycle

The Vendor reports the fix ready. The embargo does not change.

Antecedent: the revised embargo is active.

4. Embargo termination

The Coordinator terminates the embargo. The CASE_MANAGER records the termination, and EM moves to EXITED on the canonical case. EM then moves to EXITED on each replica when the ledger entry reaches it.

Antecedent: the revised embargo is active.

5. Publication

Every participant reports publication. The embargo has already ended. So publication has no embargo to end, and EM stays EXITED.

Antecedent: the embargo has ended.

6. Case closure

Every participant closes the case. The Vendor and the Reporter leave first. The Coordinator, the Case Owner, leaves last. A departure sent after the owner's is not recorded, so every other participant's departure is recorded first.

Antecedent: the vulnerability has been published.

7. Ledger dump

The scenario writes each participant's case ledger for the invariant harness, on success and on failure.

The story as the code tells it

This is the plot of the scenario as the demo code composes it, generated from that code. It is here so a reader can check the narrative above against what the demo actually runs; where the two disagree, the narrative is the one written independently, so read it as the claim and this as the evidence.

  1. Reporter decides: Report it to a Coordinator
  2. The Reporter submits its report; the Coordinator engages the case.
  3. Coordinator decides: Invite the Vendor
  4. The Coordinator invites the Vendor, and the Invite is delivered.
  5. Vendor decides: Accept the invite
  6. The Vendor accepts the Invite, takes its replica and triages the report.
  7. The Reporter's and the Vendor's replicas catch up with the case.
  8. Reporter decides: Propose new embargo terms
  9. Case creation activated the default embargo, before anyone proposed.
  10. The Reporter revises the default embargo; the Coordinator activates it.
  11. The Reporter asks whether the revised embargo leaves time for a fix.
  12. Vendor decides: Report the fix ready
  13. The Vendor reports fix ready and stops at VFd (CSB-15-002).
  14. The fix being ready leaves the embargo in force.
  15. The Coordinator ends the embargo deliberately, before publication.
  16. Each participant reports public disclosure, the Coordinator first.
  17. Publication leaves the already-ended embargo ended.
  18. Every participant closes the case; the Case Owner leaves last.
  19. Closing the case leaves the already-ended embargo ended.