Problem description
We created an experimental solution for discovering device capabilities within NAM, capturing what hardware/firmware features a specific access point supports (e.g., 802.11 bands, Thread version, bootstrapping protocols like DPP, Matter, WKSO). These concepts are defined in Capabilities.yaml and capabilities-template.yaml. These files are being removed from the repo for now and attached here for reference while we evaluate the right long-term design approach.
Possible evolution
To be determined. Key open questions:
-
Device hardware/firmware capability inventory is a property of a physical resource, not an API implementation detail — this suggests CRR is likely not the right fit, and a bespoke endpoint (e.g., GET /network-access-devices/{id}/capabilities) may be more appropriate
-
How device capability discovery relates to Trust Domain serviceability, which is a better candidate for CRR engagement
-
Whether this work should be picked up as part of the broader Zero Touch Onboarding expansion
Alternative solution
N/A
Additional context
Files were removed as part of a structural refactor of code/API_definitions #115
capabilities-template.yaml
Capabilities.yaml
Problem description
We created an experimental solution for discovering device capabilities within NAM, capturing what hardware/firmware features a specific access point supports (e.g., 802.11 bands, Thread version, bootstrapping protocols like DPP, Matter, WKSO). These concepts are defined in Capabilities.yaml and capabilities-template.yaml. These files are being removed from the repo for now and attached here for reference while we evaluate the right long-term design approach.
Possible evolution
To be determined. Key open questions:
Device hardware/firmware capability inventory is a property of a physical resource, not an API implementation detail — this suggests CRR is likely not the right fit, and a bespoke endpoint (e.g., GET /network-access-devices/{id}/capabilities) may be more appropriate
How device capability discovery relates to Trust Domain serviceability, which is a better candidate for CRR engagement
Whether this work should be picked up as part of the broader Zero Touch Onboarding expansion
Alternative solution
N/A
Additional context
Files were removed as part of a structural refactor of code/API_definitions #115
capabilities-template.yaml
Capabilities.yaml