SACM considerations?

[wmunyan]

Given that the SACM architecture draft has officially expired, and the SACM working group will be closed once its last remaining draft (CoSWID) is published, are there considerations within this group as to what is being instantiated? Will the SACM architecture draft be pulled into this group?

[adammontville]

Hi Bill.

I’m not sure that the draft will be pulled in explicitly, but (and others please correct me where I’m mistaken) we are working on an implementation that should inform any reincarnation of that draft.

Kind regards,

Adam

On Jan 21, 2022, at 8:12 AM, Bill M @.***> wrote:

Given that the SACM architecture draft has officially expired, and the SACM working group will be closed once its last remaining draft (CoSWID) is published, are there considerations within this group as to what is being instantiated? Will the SACM architecture draft be pulled into this group?

— Reply to this email directly, view it on GitHub https://github.com/opencybersecurityalliance/PACE/issues/22, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQVELERLWDQ3DZBZ2JODDDUXFSTJANCNFSM5MPT5LTQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.

[dlemire60]

I think right now I would say that the SACM architecture ID is foundation / inspiration for the prototyping work to be done under OCA PACE. As the focus of the PACE effort is prototyping, I don't have any near-term expectations that we'd update / revise / expand on the SACM Architecture draft. However, I'd agree with @adammontville that our results should (hopefully) "inform any future reincarnation of that draft".

[slarchacki22]

Added to FAQ at the 4/25/2022 PACE meeting