Skip to content
Explanation

Protocol Specification Open Questions

The whole specification on one page

The specification is also published as a single page that holds every section and annex in order, for printing or for searching the whole text at once.

This page collects the questions the Vultron Protocol Specification leaves unresolved. They concern a disputed vendor awareness in the Case State (CS) dimension Vendor aware, Fix ready, fix Deployed (VFD), what a sender does after a processing fault, the Hypertext Transfer Protocol (HTTP) responses a receiving actor returns, how a participant acquires a role after it joins a case, and whether the Case Owner may delegate embargo activation. This page covers what the specification has not decided. For the requirements that the tests do not show the reference implementation fully meets, see Known Gaps.

Open Questions

Each question below is unresolved at the time of issue. Every one also appears inline at the point in the specification where it first matters, so a reader meeting the gap in context sees it there rather than only here.

Open question: disputing an asserted vendor awareness

The first VFD transition — v→V, vendor becomes aware — has two drive paths. The vendor can report it for itself, and the CASE_MANAGER or the Case Owner can assert it on the vendor's behalf (§13.4.1 Participant-Specific CS Transitions (VFD)). The protocol expects evidence of the notification to ground that assertion, and the reference implementation does not check for it.

Open questions: can the subject Vendor dispute an awareness that another party asserted for it? Is transport-level delivery success, a Hypertext Transfer Protocol (HTTP) 200 response, enough evidence for the assertion?

Do not infer a rule from this document's silence.

Open question: what a sender does after a processing fault

Error message types (RE, EE, CE) are deliberately unmodeled (ADR-0049). An actor that cannot process an inbound activity from an authenticated sender reports it with Create(ProcessingFault) (ASK-07-001). The fault names the failed activity and a failure class, and its receiver rules are specified (§4.11 Faults and Acknowledgments, ASK-07). On the sending side, a fault about an outstanding ask closes that ask (ASK-07-007). A fault about an embargo message calls for an inquiry (VP-11-005), and so does a fault about a report-management or case-status message that does not say what went wrong (RMB-07-001, CSB-07-001).

Open: whether the sender resends the failed activity, drops it, or escalates to a person, and whether that choice depends on the failure class. Until this is settled, that choice belongs to each implementation.

Open question: which HTTP responses a receiving actor returns

This version does not say which HTTP status code a receiving actor returns when it refuses a message. For example, it does not say whether an invalid activity gets 422, an activity addressed only to other actors gets 400, or a message that cannot be decrypted gets 400.

One option is for the protocol to specify these responses, so that a sending actor can rely on them and act on them. The other is to leave them to each server implementation. A Vultron actor built on a stock ActivityPub server returns whatever that server returns, so a protocol rule could conflict with the server it runs on.

Until this is settled, these codes are recorded as the reference implementation's choices, not as protocol requirements. The codes that HTTP itself defines, such as 405 for an unsupported method and 413 for a body that is too large, are not part of this question.

Open question: acquiring a role after joining a case

This specification says how the Case Owner offers a role to a participant, and how the participant accepts or declines the offer. It does not say how a participant already in a case asks for an additional one.

A participant admitted as a Vendor that later also needs the Coordinator role has no protocol path to request it. In practice the request is made out of band, or as an Add(Note) on the case, and the Case Owner then issues a role offer. Neither is a specified mechanism.

Open: whether the protocol should define a role-request activity, whether a participant may give up a role it already holds, and how a role that is removed rather than added is represented in the case history.

Open question: may the Case Owner delegate activating an embargo to the CASE_MANAGER?

Activating a proposed embargo is the Case Owner's decision for the case. The owner sends Add(EmbargoEvent) with target naming the VulnerabilityCase, and inReplyTo naming the Invite(EmbargoEvent) that proposed it. Ending an embargo can already be delegated: the CASE_MANAGER may send the Remove(EmbargoEvent) on the owner's behalf. Activation has no such path.

What is settled is how the owner's own answer bears on any activation. The owner's Accept(Invite(EmbargoEvent)) or Reject(Invite(EmbargoEvent)) is its consent as a participant, and its decision for the case never rewrites that answer. An owner that declined a proposal accepts it before it activates it. So if activation is ever delegated, only an owner that has accepted the proposal can authorize the CASE_MANAGER's Add.

Open: whether the owner may delegate activation at all; how a delegation is expressed on the wire, for example as part of the owner's published embargo policy or as an instruction for one case; and whether the CASE_MANAGER's Add names the owner's Accept or the proposal's Invite in inReplyTo. Once a resolution is reached, it will be reflected in this reference and in the embargo message requirements.