[OPSAWG] Fw: Re: [ntia-sbom-framing] Fwd: 🔔 WG Adoption Call on draft-lear-opsawg-sbom-access-00

[Christopher Gates <[e-mail]>]

------ Forwarded Message ------
From: "Christopher Gates" <[e-mail]>
To: "Eliot Lear" <[e-mail]>; "[e-mail]" 
<[e-mail]>
Sent: 1/4/2021 2:48:51 PM
Subject: Re: [ntia-sbom-framing] Fwd: [OPSAWG] 🔔 WG Adoption Call on 
draft-lear-opsawg-sbom-access-00

>Eliot,
>
>I joined the IETF WG, and I have some feedback....
>
>
>A "SWID tag" isn't an SBOM format, as stated here. It is an element 
>inside of an SBOM.
>Since we have removed SWID as a format we in the "NTIA SBOM WG are 
>supporting for SBOM use, shouldn't this reference be removed from the 
>IETF draft as well?
>
>
>Also, I still think that creating a Bluetooth Low Energy SBOM Adopted 
>Profile (via the Bluetooth SIG) that is harmonized with this would be a 
>good thing:
>
>
>Due the the low bandwidth of BLE we wouldn't attempt to provide the 
>SBOM via BLE, just the link to a URI that can deliver the SBOM.
>It would create a standardized UUID (16 bit) for the SBOM Adopted 
>Profile, and have a consistent set of characteristics being exposed via 
>BLE.
>This is exactly how an Adopted Profile is supposed to be defined and 
>utilized.
>
>
>Christopher Gates
>
>--------------------------------
>
>Director of Product Security
>
>www.velentium.com
>
>[phone]
>
>520 Courtney Way Suite 110
>
>Lafayette CO. 80026
>
>(GMT-7)
>
>
>
>Our new book is now shipping:
>
>Medical Device Cybersecurity for Engineers and Manufacturers
>
>U.S. 
><https://us.artechhouse.com/Medical-Device-Cybersecurity-A-Guide-for-Engineers-and-Manufacturers-P2128.aspx> 
>| Worldwide 
><https://uk.artechhouse.com/Medical-Device-Cybersecurity-A-Guide-for-Engineers-and-Manufacturers-P2073.aspx>
>
>Amazon 
><https://www.amazon.com/Medical-Device-Cybersecurity-Engineers-Manufacturers/dp/1630818151/ref=sr_1_1?dchild=1&keywords=Axel+Wirth&qid=1592335625&sr=8-1> 
>& Digital 
><https://us.artechhouse.com/Medical-Device-Cybersecurity-for-Engineers-and-Manufacturers-P2174.aspx>
>
>Security Book Of The Year! 
><https://engineering.tapad.com/the-best-information-security-books-of-2020-e7430444fbd4>
>
>
>
>“If everyone is thinking alike, then somebody isn't thinking.” -George 
>S. Patton
>
>"Facts are stubborn things."  -John Adams, 1770
>
>
>------ Original Message ------
>From: "Eliot Lear via ntia-sbom-framing" <[e-mail]>
>To: [e-mail]
>Sent: 1/4/2021 9:57:22 AM
>Subject: [ntia-sbom-framing] Fwd: [OPSAWG] 🔔 WG Adoption Call on 
>draft-lear-opsawg-sbom-access-00
>
>>FYI- this is your opportunity to contribute to the IETF.  If you think 
>>sharing of SBOMs is important, this is a starting point for the IETF 
>>to begin work on that aspect, not an end point.  Please feel free to 
>>contribute by joining the opsawg IETF list at 
>>https://www.ietf.org/mailman/listinfo/opsawg.
>>
>>Eliot
>>
>>>Begin forwarded message:
>>>
>>>From: Henk Birkholz <[e-mail]>
>>>Subject: [OPSAWG] 🔔 WG Adoption Call on 
>>>draft-lear-opsawg-sbom-access-00
>>>Date: 4 January 2021 at 17:10:19 CET
>>>To: opsawg <[e-mail]>
>>>
>>>Dear OPSAWG members,
>>>
>>>this starts a call for Working Group Adoption on 
>>>https://tools.ietf.org/html/draft-lear-opsawg-sbom-access-00 ending 
>>>on Monday, January 25.
>>>
>>>As a reminder, this I-D describes different ways to acquire Software 
>>>Bills of Material (SBOM) about distinguishable managed entities. The 
>>>work was updated by the authors on October 13th and now elaborates on 
>>>three ways SBOM can be found, including a MUD URI as one of the 
>>>options.
>>>
>>>Please reply with your support and especially any substantive 
>>>comments you may have.
>>>
>>>
>>>For the OPSAWG co-chairs,
>>>
>>>Henk
>>>
>>>_______________________________________________
>>>OPSAWG mailing list
>>>[e-mail]
>>>https://www.ietf.org/mailman/listinfo/opsawg
>>
-- 
Disclaimer: The information and attachments transmitted by this e-mail are 
proprietary to Velentium, LLC and the information and attachments may be 
confidential and legally protected under applicable law and are intended 
for use only by the individual or entity to whom it was addressed. If you 
are not the intended recipient, you are hereby notified that any use, 
forwarding, dissemination, or reproduction of this message and attachments 
is strictly prohibited and may be unlawful. If you are not the intended 
recipient, please contact the sender by return e-mail and delete this 
message from your system immediately hereafter.