Nexus Observatory Sign inCreate account
Observatory Protocol

/

Specification

/

Wire bindings

One binding per plane, each an open standard.

The normative wire bindings of Observatory Protocol 0.1: control, data, events, exchange, evidence and telemetry.

Read the specificationContribute
Functions
12
State machines
11
Objects
21
Standards
48

The practice this part continues.

1984 End to end, rough consensus
Saltzer, Reed and Clark argued that functions placed in the network can be completely and correctly implemented only with the knowledge of the end systems; RFC 1958 recorded the principle for the Internet’s architecture. The IETF’s working method, summarised in RFC 7282 as “rough consensus and running code”, sets the standard for how an open protocol should change. The protocol keeps authority at the site and changes only through open proposals. [1][2][3]

Normative bindings for Observatory Protocol 0.1.

The control, data, evidence and exchange planes are separate; the exchange plane never opens an inbound management path into a site.

Control
TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
Data, in the field
MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
Data, site to upstream
At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
Events
Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
Exchange
OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.
Evidence
DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
Telemetry
OpenTelemetry OTLP.

References

Sources for the historical and standards statements on this page.

  1. Saltzer, J. H., Reed, D. P., and Clark, D. D. (1984). “End-to-End Arguments in System Design.” ACM Transactions on Computer Systems 2(4). web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf
  2. Carpenter, B., ed. (1996). RFC 1958, “Architectural Principles of the Internet.” IETF. www.rfc-editor.org/rfc/rfc1958
  3. Resnick, P. (2014). RFC 7282, “On Consensus and Humming in the IETF.” IETF. www.rfc-editor.org/rfc/rfc7282
  4. Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org/rfc/rfc2119
  5. Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org/rfc/rfc8174

Read it, test it, propose a change.

The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.

Read the specificationContribute

One protocol, the languages you ship in.

Client libraries and the node agent, each tested against the conformance suite. Languages, licences and dates are set when a release is prepared.

Read it, test it, propose a change.

The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.