Skip to content

Observatory ProtocolNode registrySteward

Steward

Maintains the specification and its registers, and runs the open change process.

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

Steward role. (OBSP 0.1 §3) Versioning and change. (OBSP 0.1 §10)

Class
Operators, providers and stewards
Organisations that run deployments, supply components or maintain the specification.
Protocol role
STEWARD Steward. (OBSP 0.1 §3)
Conformance profile
No conformance profile applies to the steward.

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)

InterfaceBindingSources
ChangeObservatory Improvement Proposals in the open repository(OBSP 0.1 §10)

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

None in OBSP 0.1.

Accepts

Lifecycle and conformance

No conformance profile applies to the steward.

5.1Join5.2Admit5.3Describe5.4Time5.5Observe5.6Qualify5.7Federate5.8Orchestrate5.9Correct5.10Exchange5.11Prove5.12Exit and decommission
The twelve stages of the lifecycle. The stages in the type's profile are marked.

Identity, attestation and security

Requirements of the security model that apply to this role. (OBSP 0.1 §8)

Architecture
Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
Workload identity
SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
Supply chain
SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (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)

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.

The protocol lists no open gap for this type.

Across the consortium

Related pages on the consortium's other networks, in their own words.

StandardsNexus Standards
Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.nexustandards.com
IndexThe Global Risks Index
Country risk indicators that observations with provenance and quality can inform.risksindex.com
AcademyRisk Academy
Training for implementers and operators of observing systems.risksacademy.com
ReportsReports at Nexus Standards
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.

  1. OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
  2. OBSP 0.1 §10: Versioning and change Observatory Protocol 0.1 (draft), CC BY 4.0.
  3. OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
  4. JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
  5. OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
  6. OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
  7. OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
  8. IETF RFC 2119 Key words for use in RFCs to Indicate Requirement Levels www.rfc-editor.org/rfc/rfc2119.html Checked
  9. IETF RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words www.rfc-editor.org/rfc/rfc8174.html Checked