Observatory ProtocolNode registryCluster and grid control plane
Cluster and grid control plane
A group of site cells under one operator, sharing fleet, policy and release, and the control plane that serves products through the exchange plane.
- 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
Cluster role. (OBSP 0.1 §3) Profile for cluster and grid control planes. (OBSP 0.1 §7.1)
- Class
- Compute, relay and control
Edge computers, relays, site cell controllers, clusters and federation peers. - Protocol role
CLUSTERCluster. (OBSP 0.1 §3)- Conformance profile
OBSP-GRIDCluster and grid control plane (OBSP 0.1 §7.1)- Technology domains
- 5G core and edge computing, Data, pipelines and exchange
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 |
|---|---|---|
| Exchange | OpenAPI 3.1, the OGC API family, SensorThings, STAC and WIS 2.0 | (OBSP 0.1 §6; OpenAPI 3.1; OGC API; OGC SensorThings API; STAC; WMO WIS 2.0) |
| Events | Event envelopes mapped to CloudEvents 1.0; channels in AsyncAPI 3 | (OBSP 0.1 §6; CloudEvents 1.0; AsyncAPI 3.0) |
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
fleet-projectionFleetProjectionproduct-manifestProductManifestplanPlancorrection-noticeCorrectionNoticeevent-envelopeEventEnvelope
Accepts
observation-recordObservationRecordobserved-state-receiptObservedStateReceiptsystem-packSystemPackprovider-manifestProviderManifestproof-receiptProofReceipt
Lifecycle and conformance
OBSP-GRID 12 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-GRID | Contract |
|---|---|---|---|
| §5.1 | Join | Yes | Contracted |
| §5.2 | Admit | Yes | Contracted |
| §5.3 | Describe | Yes | Contracted |
| §5.4 | Time | Yes | Contracted |
| §5.5 | Observe | Yes | Contracted |
| §5.6 | Qualify | Yes | Contracted |
| §5.7 | Federate | Yes | Open gap G-FED-1 |
| §5.8 | Orchestrate | Yes | Open gap G-ORCH-1 |
| §5.9 | Correct | Yes | Contracted |
| §5.10 | Exchange | Yes | Open gap G-EXCH-1 |
| §5.11 | Prove | Yes | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | Yes | Contracted |
Conformance cases that apply
| Case | What it tests | Kind | Evidence |
|---|---|---|---|
| CT-GRID-001 | Federate: fleet projection across cells | schema | fleet-projection |
| CT-GRID-002 | Exchange: product manifests published to consumers | schema | product-manifest |
| CT-GRID-003 | Orchestrate: system packs compiled into reconciliation assignments | schema | system-pack reconciliation-assignment |
| 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 |
| CT-SITE-001 | Admit: sources admitted by manifest and qualification record | schema | source-manifest qualification-record |
| CT-SITE-002 | Correct: correction notices supersede with a new digest | invariant | correction-notice |
| CT-SITE-003 | Prove: proof receipts for the local verifier role | schema | proof-receipt |
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)
- OpenAPI 3.1OpenAPI Specification 3.1.0(OpenAPI 3.1)
- OGC APIOGC API family of standards(OGC API)
- OGC SensorThings APIOGC SensorThings API(OGC SensorThings API)
- STACSpatioTemporal Asset Catalog specification(STAC)
- WMO WIS 2.0WMO Information System(WMO WIS 2.0)
- CloudEvents 1.0CloudEvents specification(CloudEvents 1.0)
- AsyncAPI 3.0AsyncAPI specification 3.0.0(AsyncAPI 3.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.
- Read APIs and OGC endpoints are an open gap in OBSP 0.1 (G-EXCH-1). (OBSP 0.1 §9)
G-FED-1FederationBinding and AuthorityLease schemas and the peer exchange protocol (Federate). (OBSP 0.1 §9)G-ORCH-1Plan signing path and TUF update metadata (Orchestrate). (OBSP 0.1 §9)G-EXCH-1Observation, product and catalogue read APIs and OGC endpoints (Exchange). (OBSP 0.1 §9)G-PROVE-1Proof challenge protocol and verifier service (Prove). (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 ChainsWater and Food SystemsHumanitarian 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 §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.
- OpenAPI 3.1 OpenAPI Specification 3.1.0 spec.openapis.org/oas/v3.1.0 Checked
- OGC API OGC API family of standards ogcapi.ogc.org/ Checked
- OGC SensorThings API OGC SensorThings API www.ogc.org/standards/sensorthings/ Checked
- STAC SpatioTemporal Asset Catalog specification stacspec.org/ Checked
- WMO WIS 2.0 WMO Information System community.wmo.int/en/activity-areas/wis Checked
- CloudEvents 1.0 CloudEvents specification cloudevents.io/ Checked
- AsyncAPI 3.0 AsyncAPI specification 3.0.0 www.asyncapi.com/docs/reference/specification/v3.0.0 Checked
- 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
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §9: Gaps register Observatory Protocol 0.1 (draft), CC BY 4.0.