Observatory ProtocolNode registryEdge compute node
Edge compute node
An edge computer that runs a node agent and workloads at the site. It applies signed plans in the smallest reversible step and records what it applied.
- Version
- 0.1.0-draft
- Status
- Draft specification
- Specification
- CC BY 4.0
- Code
- Apache-2.0
- Steward
- GCRI Canada
- Source
- obsp-0.1-foundation
Role
The specification lists an edge computer as a node. (OBSP 0.1 §3) The node agent applies the smallest reversible step and rolls back on failure. (OBSP 0.1 §5.8)
- Class
- Compute, relay and control
Edge computers, relays, site cell controllers, clusters and federation peers. - Protocol role
NODENode. (OBSP 0.1 §3)- Conformance profile
OBSP-NODENode agent and device. In this profile, orchestrate here means applying a signed plan, not compiling one (OBSP 0.1 §7.1)- Technology domains
- Edge hardware and runtime
Interfaces
The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)
| Interface | Binding | Sources |
|---|---|---|
| Control | TLS 1.3 with mutual authentication, protobuf messages in obsp.v1 | (OBSP 0.1 §6) |
| Updates | Signed plans with TUF metadata; SUIT manifests for device firmware | (OBSP 0.1 §5.8; TUF; IETF RFC 9019) |
| Platforms | Kubernetes, lightweight edge Kubernetes and plain Linux, on x86_64 and arm64 | (OBSP 0.1 §13) |
Schemas it emits and accepts
Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)
Emits
node-manifestNodeManifestattestation-evidenceAttestationEvidencetime-qualityTimeQualityobserved-state-receiptObservedStateReceiptreconciliation-receiptReconciliationReceiptobservation-recordObservationRecorddecommission-recordDecommissionRecord
Accepts
node-bootstrap-bundleNodeBootstrapBundleattestation-resultAttestationResultplanPlanreconciliation-assignmentReconciliationAssignmentsystem-packSystemPackrequest-contextRequestContext
Lifecycle and conformance
OBSP-NODE 7 of 12 functions. (OBSP 0.1 §7.1) A level is reached only with the evidence it names. (OBSP 0.1 §7.2)
| Clause | Stage | In OBSP-NODE | Contract |
|---|---|---|---|
| §5.1 | Join | Yes | Contracted |
| §5.2 | Admit | No | Contracted |
| §5.3 | Describe | Yes | Contracted |
| §5.4 | Time | Yes | Contracted |
| §5.5 | Observe | Yes | Contracted |
| §5.6 | Qualify | Yes | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | Yes | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | Yes | Contracted |
Conformance cases that apply
| Case | What it tests | Kind | Evidence |
|---|---|---|---|
| CT-NODE-001 | Join: node manifest, attestation evidence and the verifier's result | invariant | node-manifest attestation-evidence attestation-result request-context |
| CT-NODE-002 | Join: bootstrap bundle received from the site cell | schema | node-bootstrap-bundle |
| CT-NODE-003 | Describe: sensor passports and the calibration records they cite | invariant | sensor-passport calibration-record |
| CT-NODE-004 | Time: time quality reported as explicit state | invariant | time-quality |
| CT-NODE-005 | Observe: observation records and event envelopes | schema | observation-record event-envelope |
| CT-NODE-006 | Observe: store and forward replay with its result | schema | replay-batch replay-batch-result |
| CT-NODE-007 | Qualify: quality flags and provenance travel with values | schema | quality-flag provenance |
| CT-NODE-008 | Orchestrate: a signed plan applied with a reconciliation receipt | schema | plan reconciliation-receipt observed-state-receipt |
| CT-NODE-009 | Exit: decommission with revoked identities and a full export | invariant | decommission-record |
Run these cases in the onboarding check
Levels
- Declared
- Signed self-declaration naming profile, version and scope.
- Self-tested
- Conformance report (obsp conformance run) produced by the participant, with digests of the tested artifacts.
- Lab-tested
- Conformance report (obsp conformance run) and lab test record from a qualified lab.
- Qualified
- Lab report plus field observation for the declared scope and a qualification-record.
- Suspended
- Suspension notice with reason.
- Withdrawn
- Withdrawal notice.
Identity, attestation and security
Requirements of the join function and of the security model. (OBSP 0.1 §5.1; OBSP 0.1 §8) Attestation follows the RATS architecture, passport model. (IETF RFC 9334 §5.1)
- A node MUST present attestation evidence (RATS, RFC 9334, passport model) rooted in a hardware root of trust where the device class has one (TPM 2.0, DICE or a secure element), or a software root explicitly marked SOFTWARE_ROOT otherwise. (OBSP 0.1 §5.1)
- A verifier MUST bind the result to a nonce and an expiry. (OBSP 0.1 §5.1)
- Identity MUST be short-lived and renewable (X.509 SVID, SPIFFE-style URI spiffe://<trust-domain>/node/<uni>). (OBSP 0.1 §5.1)
- Long-lived shared secrets MUST NOT be used. (OBSP 0.1 §5.1)
- The bootstrap bundle MUST be signed by the site cell's enrolment key and carry the trust anchors, policy reference and the first plan digest. (OBSP 0.1 §5.1)
Root-of-trust classes the attestation evidence schema accepts: TPM2, DICE, SECURE_ELEMENT, SOFTWARE_ROOT. (OBSP 0.1 §5.1)
A hardware root follows TPM 2.0 or DICE where the device class has one. (TCG TPM 2.0; TCG DICE)
- Architecture
- Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
- Device identity
- Attested; hardware root where the class has one; short-lived certificates; revocation within the site cell's offline window (OBSP 0.1 §8)
- Workload identity
- SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
- Keys
- Site cell keys held by the grid operator; customer-held keys for upstream services; HSM or TPM-sealed where available (OBSP 0.1 §8)
- Supply chain
- SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
- Time
- Authenticated time (P3, §5.4); time integrity gates receipts (OBSP 0.1 §8)
- OT environments
- IEC 62443 zones and conduits for industrial deployments (OBSP 0.1 §8)
- Privacy
- Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)
Interoperability profile and standards
The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)
- TUFThe Update Framework(TUF)
- IETF RFC 9019A Firmware Update Architecture for Internet of Things (SUIT)(IETF RFC 9019)
- IETF RFC 9124A Manifest Information Model for Firmware Updates in IoT Devices (SUIT)(IETF RFC 9124)
- ETSI MECMulti-access Edge Computing(ETSI MEC)
- TCG TPM 2.0Trusted Platform Module Library Specification(TCG TPM 2.0)
Not yet defined
What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.
- Plan signing with TUF is an open gap in OBSP 0.1 (G-ORCH-1). (OBSP 0.1 §9)
G-ORCH-1Plan signing path and TUF update metadata (Orchestrate). (OBSP 0.1 §9)
Across the consortium
Related pages on the consortium's other networks, in their own words.
- Standards
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.Early Warning and Anticipatory ActionHazards and Disaster Risk ReductionCities and the Built EnvironmentCommunities, Learning and ContributionIndustry, Trade and Supply ChainsHumanitarian Action and DevelopmentData and EvidenceClimate and Earth SystemsEnergy and Critical InfrastructureOpen Infrastructure and Developers
- Index
- Country risk indicators that observations with provenance and quality can inform.risksindex.com
- Academy
- Training for implementers and operators of observing systems.risksacademy.com
- Reports
- Published evidence with provenance, citation and corrections.nexustandards.com/nexus-reports
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.8: Orchestrate Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.1: Profiles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- TUF The Update Framework theupdateframework.io/ Checked
- IETF RFC 9019 A Firmware Update Architecture for Internet of Things (SUIT) www.rfc-editor.org/rfc/rfc9019.html Checked
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
- OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.2: Conformance levels Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.1: Join Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- IETF RFC 9334 Remote ATtestation procedureS (RATS) Architecture www.rfc-editor.org/rfc/rfc9334.html Checked
- TCG TPM 2.0 Trusted Platform Module Library Specification trustedcomputinggroup.org/resource/tpm-library-specification/ Checked
- TCG DICE Device Identifier Composition Engine architectures trustedcomputinggroup.org/work-groups/dice-architectures/ Checked
- IETF RFC 9124 A Manifest Information Model for Firmware Updates in IoT Devices (SUIT) www.rfc-editor.org/rfc/rfc9124.html Checked
- ETSI MEC Multi-access Edge Computing www.etsi.org/technologies/multi-access-edge-computing Checked
- OBSP 0.1 §9: Gaps register Observatory Protocol 0.1 (draft), CC BY 4.0.