pub struct Revocation<const N: usize> { /* private fields */ }rustcrypto only.Expand description
§12.2.4.1’s revocation walk: the part that cannot be done in one command.
Constructed with every node whose ACL or NOC still names the old version, and ticked off as
each is updated. is_complete is the only thing that may be reported as
success — and §12.2.4.1 says outright that it may never arrive, because “some Nodes are
permanently offline or otherwise unreachable”.
Implementations§
Source§impl<const N: usize> Revocation<N>
impl<const N: usize> Revocation<N>
Sourcepub fn begin(
previous: &JointFabricTags,
nodes: impl IntoIterator<Item = NodeId>,
) -> Result<Self>
pub fn begin( previous: &JointFabricTags, nodes: impl IntoIterator<Item = NodeId>, ) -> Result<Self>
Begins a revocation: the new tags, and every node that has to be visited.
nodes is the whole fabric, administrators included — §12.2.4.1 updates NOCs and ACL
entries, and a node whose ACL still lists the old Administrator CAT is a node the revoked
administrator can still administer.
The tags every node is being moved to.
Sourcepub fn updated(&mut self, node: NodeId) -> bool
pub fn updated(&mut self, node: NodeId) -> bool
Records that one node now holds the new version.
Returns whether it was one that still owed the update — a second report for the same node is not progress, and counting it would let a retry loop declare the fabric safe.
Sourcepub fn outstanding(&self) -> &[NodeId]
pub fn outstanding(&self) -> &[NodeId]
The nodes that have not been reached yet.
Sourcepub fn is_complete(&self) -> bool
pub fn is_complete(&self) -> bool
Whether every node has moved, and the revocation has actually taken effect.