Background
#15451 (comment)

Starting scope proposal

the following terms to start scoping out the finished good inventory and logistics part of this issue
and devote the allocation of starter kit to a different issue and track it separately
Background

1. The starter kit consists of several sub-sku that will be shipped from vendors to a FGI/L company
2. FGI/Lwill store the material in a secured, insured warehouse
3. On request from Magma TSC - the FGIL entity will ship out one or more SKUs against a shipping account on Fedex or UPs or DHL.
4. On receiving the units back from users - FGI/L will log and store them in the warehouse
5. This shipping transaction is anticipated to be a dozen to two times per year
6. The FGIL company will charge for the services up front against a Linux Foundation PO

Why this and why now?

LF is a software/legal entity that can not do FGI/L.
This part of the 'starter kit' inventory has to decided upon ideally before we place orders for HW

Mickey has raised the issue of physical security, meaning attacks based on access to the hardware in storage. Jordan says that the image is created by Connect5G, installed by the logistics provider, and re-installed when a unit has been returned. The defense is to set a standard policy to re-image every time; eliminate the possibility of not re-imaging.

The image will be standardized and its hash can be checked by the recipient of a unit. We should suggest they verify it. We should provide that hash.

Another possibility is to have an architecture like an rPI with a removable SSD.

I reviewed governance documents for information relevant to funding of the starter kits.

Technical Charter 5C is relevant: