Goals

  • Provide a mechanism for revoking an SCMS component other than root CA.

  • Define procedures to enable continued SCMS operations after the revocation.

Assumptions

  • The technical component of the SCMS Manager will coordinate the revocation of SCMS components to enable continued operations.

  • When an SCMS component is revoked, the function that it provided will be taken over by a peer device with sufficient privileges and capabilities to continue operations.  The peer device may be a pre-existing device that is taking on additional work or a newly added (i.e., replacement) device.  

  • This use case specifies the requirements that are common among all non-root SCMS component revocations.  Individual use cases will provide specific details that are unique to each component type. 

Attachments: