Skip to content

Update OpenChain-Telco-SBOM-Guide_EN.md#214

Closed
Jimmy-ahlberg wants to merge 1 commit intomainfrom
Jimmy-ahlberg-patch-1
Closed

Update OpenChain-Telco-SBOM-Guide_EN.md#214
Jimmy-ahlberg wants to merge 1 commit intomainfrom
Jimmy-ahlberg-patch-1

Conversation

@Jimmy-ahlberg
Copy link
Collaborator

Adding encryption and storage requirement.

Adding encryption and storage requirement.
@MasahiroDAIKOKU
Copy link
Contributor

MasahiroDAIKOKU commented Sep 4, 2025

@vargenau
Thank you very much for creating and sharing draft 1.2. I apologize if I have posted this in the wrong place.

  • Does this describe the process of conveying the SBOM between the provider and consumer, rather than requiring the SBOM to be encrypted within the provider's organization? Since it is a "SHALL" requirement, it is preferable to specify the conditions as much as possible.
  • And, since we use the terms "consumer" and "consum" in Section 1 and 3.1 and elsewhere, it would be better to standardize the terminology. In 3.8.2 Rationale, I think “both the provider and the consumer of an SBOM” is clearer than “both the provider and the recipient of an SBOM.” What do you think?

@vargenau
Copy link
Collaborator

Cannot merge to official version 1.1.
Draft 1.2 created instead.

@vargenau vargenau closed this Sep 11, 2025
@vargenau
Copy link
Collaborator

vargenau commented Sep 11, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants