One protocol over the protocols that already work.
The Observatory Protocol replaces none of the standards that carry signals, time, identity and data. It names the standard it uses for each part, adds only what none of them covers, and binds them with common rules for identity, time, provenance, quality and governance.
The stack
Every layer, and what binds it.
Select a layer to see the functions and objects that bind it, the standards the protocol text cites for it, and the other open standards that work at the same layer.
Governance and conformance
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| IETF RATS (RFC 9334)[1] | Join and prove: reference architecture for attester evidence, verifier appraisal and attestation results. |
| IETF SCITT (RFC 9943)[2] | Admit and prove: transparency receipts for statements about artifacts and evidence. |
| JSON Schema 2020-12[3] | All functions: authored record contracts, fail-closed validation. |
Exchange and federation
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| OpenAPI 3.1[1] | Exchange: request and response API contracts. |
| AsyncAPI[2] | Exchange: event channel contracts. |
| CloudEvents[3] | Exchange and correct: event metadata for correction-aware subscriptions. |
| OGC API Common[4] | Observe and exchange: shared building blocks for geospatial web APIs. |
| STAC[5] | Exchange and describe: Earth observation asset catalogues. |
| WMO WIS 2.0[6] | Observe and exchange: weather and environmental data exchange. |
| 3GPP TS 23.501[7] | Federate: 5G system architecture, named by the protocol page. |
| ETSI MEC[8] | Federate: multi-access edge computing for local breakout and edge applications. |
Data and semantics
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| OGC SensorThings API[1] | Describe and observe: sensing and tasking data model for sensors and observations. |
| OGC API Connected Systems[2] | Describe: connected sensors, platforms and datastreams. |
| OGC SensorML 3.0[3] | Describe: sensor and procedure description. |
| UCUM[4] | Describe: units of measure profile. |
| WMO WIGOS[5] | Describe: observing-system metadata, named by the protocol page as WIGOS metadata. |
| W3C PROV-O[6] | Qualify: provenance vocabulary, named by the protocol page as W3C PROV. |
| WMO-No. 8[7] | Qualify: guide to instruments and methods of observation. |
| FAIR principles[8] | Qualify: findable, accessible, interoperable and reusable data. |
Also at this layer, not yet named in the protocol text
Compute and runtime
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| SLSA[1] | Admit and orchestrate: build provenance levels. |
| Kubernetes[2] | Orchestrate: container scheduling baseline and dynamic resource allocation for accelerators. |
| OCI image and runtime[3] | Orchestrate: portable container images and runtime. |
| TUF | Orchestrate: signed update metadata, named by the protocol page for upgrade roll-out. |
| IETF SUIT[4] | Orchestrate: firmware update manifest architecture. |
| Sigstore[5] | Orchestrate: signing and verification of released artifacts. |
| in-toto[6] | Orchestrate: supply-chain step attestations. |
Identity and trust
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| TCG TPM 2.0[1] | Join: measured boot and platform root-of-trust candidate. |
| DMTF SPDM[2] | Join: device authentication and measurement exchange candidate. |
| DMTF MCTP and PLDM[3] | Join: platform management transport and inventory. |
| SPIFFE/SPIRE[4] | Join: reference candidate for short-lived workload identity. |
| SPDX[5] | Admit: software bill of materials and licence data. |
| CycloneDX[6] | Admit: bill of materials and vulnerability exchange. |
| IEC 62443[7] | Security reference for industrial and OT integration. |
| NIST SP 800-207[8] | Security: zero-trust architecture reference. |
Also at this layer, not yet named in the protocol text
Time
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| IEEE 1588 (PTP)[1] | Time: precision time distribution across the grid. |
| ITU-T G.8275.1[2] | Time: telecom PTP profile with full timing support, named by the protocol page. |
| IETF NTS (RFC 8915)[3] | Time: authenticated network time. |
| NIST PNT cybersecurity profile[4] | Time: resilience of positioning, navigation and timing services. |
Also at this layer, not yet named in the protocol text
- NTP version 4 · IETF RFC 5905[5]
Network and transport
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| OASIS MQTT 5.0[1] | Observe: lightweight publish and subscribe for sensor and IoT streams. |
| IETF QUIC[2] | Federate and prove: transport for peer and overlay links. |
| OPC UA[3] | Observe: industrial telemetry, read-only by default. |
| OpenTelemetry OTLP[4] | Observability of every node and service through one open telemetry standard. |
Also at this layer, not yet named in the protocol text
Physical and radio
Binding functions
Objects it carries
Standards the protocol text cites
| Standard | Role in the protocol |
|---|---|
| 3GPP Release 20[1] | Ran and core: 5G-Advanced baseline with 6G study watch. |
| O-RAN Release 5 (R005)[2] | Ran: open fronthaul, E2, A1, O1 and O2 interfaces and AI/ML workflow services. |
| AI-RAN Alliance publications[3] | AI-RAN: architecture and orchestration references for shared RAN and AI compute. |
| LoRaWAN[4] | IoT: low-power wide-area gateways and devices. |
| CCSDS standards[5] | Satellite: candidate profiles for space mission links. |
Also at this layer, not yet named in the protocol text
At scale
From one node to federated grids.
Scale comes from federation, not from a central service. Each grid keeps its own authority and exchanges products under explicit trust and policy rules.
- Join
- Admit
- Describe
- Time
- Observe
- Qualify
- Federate
- Orchestrate
- Correct
- Exchange
- Prove
- Exit and decommission
| Profile | Functions | For |
|---|---|---|
| OBSP-NODE | Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit | Node agents and devices |
| OBSP-SITE | OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier) | Site controllers |
| OBSP-GRID | OBSP-SITE plus Federate and Exchange | Cluster and grid control planes |
| OBSP-PROVIDER | Admit, Describe, Exit | Hardware, software, model and data providers |
| OBSP-CONSUMER | Exchange, Correct (subscribe) | Applications reading products |
A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. "Conformant" describes a tested scope only; it never means an outside body has approved it.
References
Sources cited on this page.
- https://www.rfc-editor.org/rfc/rfc9334.html
- https://www.rfc-editor.org/info/rfc9943/
- https://json-schema.org/draft/2020-12
- https://spec.openapis.org/oas/v3.1.1.html
- https://www.asyncapi.com/docs/reference/specification/latest
- https://cloudevents.io/
- https://www.ogc.org/standards/ogcapi-common/
- https://stacspec.org/
- https://community.wmo.int/en/activity-areas/wis
- https://www.3gpp.org/DynaReport/23501.htm
- https://www.etsi.org/technologies/multi-access-edge-computing
- https://www.ogc.org/standards/sensorthings/
- https://www.ogc.org/standards/ogc-api-connected-systems/
- https://www.ogc.org/standards/sensorml/
- https://ucum.org/ucum
- https://community.wmo.int/en/activity-areas/wigos
- https://www.w3.org/TR/prov-o/
- https://library.wmo.int/records/item/68695-guide-to-instruments-and-methods-of-observation
- https://www.go-fair.org/fair-principles/
- https://www.w3.org/TR/vocab-ssn/
- https://www.iso.org/standard/82463.html
- https://www.iso.org/standard/53798.html
- https://slsa.dev/spec/v1.2/
- https://kubernetes.io/blog/2026/04/22/kubernetes-v1-36-release/
- https://opencontainers.org/
- https://datatracker.ietf.org/wg/suit/about/
- https://www.sigstore.dev/
- https://in-toto.io/
- https://trustedcomputinggroup.org/resource/tpm-library-specification/
- https://www.dmtf.org/standards/spdm
- https://www.dmtf.org/standards/pmci
- https://spiffe.io/docs/latest/spiffe-specs/
- https://spdx.dev/specifications/
- https://cyclonedx.org/specification/overview/
- https://www.iec.ch/cyber-security
- https://csrc.nist.gov/pubs/sp/800/207/final
- https://www.rfc-editor.org/rfc/rfc5280
- https://www.w3.org/TR/did-core/
- https://www.w3.org/TR/vc-data-model-2.0/
- https://standards.ieee.org/standard/1588-2019.html
- https://www.itu.int/rec/T-REC-G.8275.1
- https://www.rfc-editor.org/rfc/rfc8915
- https://csrc.nist.gov/publications/detail/nistir/8323/final
- https://www.rfc-editor.org/rfc/rfc5905
- https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html
- https://www.rfc-editor.org/rfc/rfc9000.html
- https://opcfoundation.org/about/opc-technologies/opc-ua/
- https://opentelemetry.io/docs/specs/otlp/
- https://www.rfc-editor.org/rfc/rfc7252
- https://www.rfc-editor.org/rfc/rfc6282
- https://www.3gpp.org/specifications-technologies/releases/release-20
- https://www.o-ran.org/blog/o-ran-alliance-completed-its-specification-release-5-o-ran-r005
- https://ai-ran.org/publications/
- https://resources.lora-alliance.org/technical-specifications
- https://public.ccsds.org/Publications/default.aspx
- https://www.3gpp.org/specifications-technologies/releases/release-13
- https://www.3gpp.org/technologies/ntn-overview
- https://standards.ieee.org/ieee/802.15.4/7029/