---
title: "Federation peer | Observatory Protocol"
description: "A cluster or site cell that exchanges with another trust domain under a federation binding. No binding, no exchange."
url: https://nexusobservatory.com/nodes/fed-peer/
publisher: GCRI Canada
updated: 2026-11-18
---

[Observatory Protocol](https://nexusobservatory.com/)[Node registry](https://nexusobservatory.com/nodes/)Federation peer

# Federation peer

A cluster or site cell that exchanges with another trust domain under a federation binding. No binding, no exchange.

**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

[Onboard a node](https://nexusobservatory.com/onboarding/)

[Explore the schemas](https://nexusobservatory.com/schemas/)

## Role

Federation peer role. (OBSP 0.1 §3) Federation is asynchronous exchange under an explicit binding. (OBSP 0.1 §5.7)

**Class**: [Compute, relay and control](https://nexusobservatory.com/nodes/#c=compute) Edge computers, relays, site cell controllers, clusters and federation peers.
**Protocol role**: `FED\_PEER` Federation peer. (OBSP 0.1 §3)
**Conformance profile**: `OBSP-GRID` Cluster and grid control plane (OBSP 0.1 §7.1)
**Technology domains**: [Data, pipelines and exchange](https://nexusobservatory.com/technical/domains/data/)
**Sectors**: [Government and public safety](https://nexusobservatory.com/applied/sectors/public-safety/), [Communities and rural](https://nexusobservatory.com/applied/sectors/communities/), [Industrial](https://nexusobservatory.com/applied/sectors/industrial/), [Scientific](https://nexusobservatory.com/applied/sectors/scientific/), [Environment and climate](https://nexusobservatory.com/applied/sectors/environment/), [Energy](https://nexusobservatory.com/applied/sectors/energy/)

## 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 |
| --- | --- | --- |
| Federation | Asynchronous exchange under a federation binding and authority lease | (OBSP 0.1 §5.7) |
| Transport | QUIC may be used on lossy links | (OBSP 0.1 §6) |

## 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-projection`](https://nexusobservatory.com/schemas/#s=fleet-projection) FleetProjection
- [`event-envelope`](https://nexusobservatory.com/schemas/#s=event-envelope) EventEnvelope
- [`product-manifest`](https://nexusobservatory.com/schemas/#s=product-manifest) ProductManifest

### Accepts

- [`fleet-projection`](https://nexusobservatory.com/schemas/#s=fleet-projection) FleetProjection
- [`event-envelope`](https://nexusobservatory.com/schemas/#s=event-envelope) EventEnvelope
- [`correction-notice`](https://nexusobservatory.com/schemas/#s=correction-notice) CorrectionNotice

## 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)

5.1 Join 5.2 Admit 5.3 Describe 5.4 Time 5.5 Observe 5.6 Qualify 5.7 Federate 5.8 Orchestrate 5.9 Correct 5.10 Exchange 5.11 Prove 5.12 Exit and decommission

Figure 1The twelve stages of the lifecycle. The stages in the type's profile are marked.

### Conformance cases that apply

| Case | What it tests | Kind | Evidence |
| --- | --- | --- | --- |
| CT-GRID-001 | Federate: fleet projection across cells | schema | [`fleet-projection`](https://nexusobservatory.com/schemas/#s=fleet-projection) |
| CT-GRID-002 | Exchange: product manifests published to consumers | schema | [`product-manifest`](https://nexusobservatory.com/schemas/#s=product-manifest) |
| CT-GRID-003 | Orchestrate: system packs compiled into reconciliation assignments | schema | [`system-pack`](https://nexusobservatory.com/schemas/#s=system-pack) [`reconciliation-assignment`](https://nexusobservatory.com/schemas/#s=reconciliation-assignment) |
| CT-NODE-001 | Join: node manifest, attestation evidence and the verifier's result | invariant | [`node-manifest`](https://nexusobservatory.com/schemas/#s=node-manifest) [`attestation-evidence`](https://nexusobservatory.com/schemas/#s=attestation-evidence) [`attestation-result`](https://nexusobservatory.com/schemas/#s=attestation-result) [`request-context`](https://nexusobservatory.com/schemas/#s=request-context) |
| CT-NODE-002 | Join: bootstrap bundle received from the site cell | schema | [`node-bootstrap-bundle`](https://nexusobservatory.com/schemas/#s=node-bootstrap-bundle) |
| CT-NODE-003 | Describe: sensor passports and the calibration records they cite | invariant | [`sensor-passport`](https://nexusobservatory.com/schemas/#s=sensor-passport) [`calibration-record`](https://nexusobservatory.com/schemas/#s=calibration-record) |
| CT-NODE-004 | Time: time quality reported as explicit state | invariant | [`time-quality`](https://nexusobservatory.com/schemas/#s=time-quality) |
| CT-NODE-005 | Observe: observation records and event envelopes | schema | [`observation-record`](https://nexusobservatory.com/schemas/#s=observation-record) [`event-envelope`](https://nexusobservatory.com/schemas/#s=event-envelope) |
| CT-NODE-006 | Observe: store and forward replay with its result | schema | [`replay-batch`](https://nexusobservatory.com/schemas/#s=replay-batch) [`replay-batch-result`](https://nexusobservatory.com/schemas/#s=replay-batch-result) |
| CT-NODE-007 | Qualify: quality flags and provenance travel with values | schema | [`quality-flag`](https://nexusobservatory.com/schemas/#s=quality-flag) [`provenance`](https://nexusobservatory.com/schemas/#s=provenance) |
| CT-NODE-008 | Orchestrate: a signed plan applied with a reconciliation receipt | schema | [`plan`](https://nexusobservatory.com/schemas/#s=plan) [`reconciliation-receipt`](https://nexusobservatory.com/schemas/#s=reconciliation-receipt) [`observed-state-receipt`](https://nexusobservatory.com/schemas/#s=observed-state-receipt) |
| CT-NODE-009 | Exit: decommission with revoked identities and a full export | invariant | [`decommission-record`](https://nexusobservatory.com/schemas/#s=decommission-record) |
| CT-SITE-001 | Admit: sources admitted by manifest and qualification record | schema | [`source-manifest`](https://nexusobservatory.com/schemas/#s=source-manifest) [`qualification-record`](https://nexusobservatory.com/schemas/#s=qualification-record) |
| CT-SITE-002 | Correct: correction notices supersede with a new digest | invariant | [`correction-notice`](https://nexusobservatory.com/schemas/#s=correction-notice) |
| CT-SITE-003 | Prove: proof receipts for the local verifier role | schema | [`proof-receipt`](https://nexusobservatory.com/schemas/#s=proof-receipt) |

[Run these cases in the onboarding check](https://nexusobservatory.com/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)

- [3GPP TS 23.501](https://www.3gpp.org/dynareport/23501.htm) System architecture for the 5G System ( 3GPP TS 23.501 )
- [ETSI MEC](https://www.etsi.org/technologies/multi-access-edge-computing) Multi-access Edge Computing ( ETSI MEC )

## 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 federation binding, the authority lease and the peer protocol have no contract in OBSP 0.1 (G-FED-1). ( OBSP 0.1 §9 )
- `G-FED-1` FederationBinding and AuthorityLease schemas and the peer exchange protocol (Federate). ( OBSP 0.1 §9 )
- `G-ORCH-1` Plan signing path and TUF update metadata (Orchestrate). ( OBSP 0.1 §9 )
- `G-EXCH-1` Observation, product and catalogue read APIs and OGC endpoints (Exchange). ( OBSP 0.1 §9 )
- `G-PROVE-1` Proof 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 Nexus Standards**: Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry. [Early Warning and Anticipatory Action](https://nexustandards.com/early-warning/)[Hazards and Disaster Risk Reduction](https://nexustandards.com/hazards/)[Communities, Learning and Contribution](https://nexustandards.com/communities/)[Industry, Trade and Supply Chains](https://nexustandards.com/industry-trade/)[Data and Evidence](https://nexustandards.com/data/)[Climate and Earth Systems](https://nexustandards.com/climate/)[Energy and Critical Infrastructure](https://nexustandards.com/energy-infrastructure/)
**Index The Global Risks Index**: Country risk indicators that observations with provenance and quality can inform. [risksindex.com](https://risksindex.com/)
**Academy Risk Academy**: Training for implementers and operators of observing systems. [risksacademy.com](https://risksacademy.com/)
**Reports Reports at Nexus Standards**: Published evidence with provenance, citation and corrections. [nexustandards.com/nexus-reports](https://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](https://nexusobservatory.com/development/text/#c-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
2. [OBSP 0.1 §5.7: Federate](https://nexusobservatory.com/development/text/#c-5-7) Observatory Protocol 0.1 (draft), CC BY 4.0.
3. [OBSP 0.1 §7.1: Profiles](https://nexusobservatory.com/development/text/#c-7-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
4. [OBSP 0.1 §6: Wire bindings](https://nexusobservatory.com/development/text/#c-6) Observatory Protocol 0.1 (draft), CC BY 4.0.
5. JSON Schema 2020-12 JSON Schema draft 2020-12 [json-schema.org/draft/2020-12](https://json-schema.org/draft/2020-12) Checked 2026-11-12
6. [OBSP 0.1 §4.3: Request context](https://nexusobservatory.com/development/text/#c-4-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
7. [OBSP 0.1 §7.2: Conformance levels](https://nexusobservatory.com/development/text/#c-7-2) Observatory Protocol 0.1 (draft), CC BY 4.0.
8. [OBSP 0.1 §5.1: Join](https://nexusobservatory.com/development/text/#c-5-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
9. [OBSP 0.1 §8: Security model](https://nexusobservatory.com/development/text/#c-8) Observatory Protocol 0.1 (draft), CC BY 4.0.
10. IETF RFC 9334 Remote ATtestation procedureS (RATS) Architecture [www.rfc-editor.org/rfc/rfc9334.html](https://www.rfc-editor.org/rfc/rfc9334.html) Checked 2026-11-12
11. TCG TPM 2.0 Trusted Platform Module Library Specification [trustedcomputinggroup.org/resource/tpm-library-specification/](https://trustedcomputinggroup.org/resource/tpm-library-specification/) Checked 2026-11-12
12. TCG DICE Device Identifier Composition Engine architectures [trustedcomputinggroup.org/work-groups/dice-architectures/](https://trustedcomputinggroup.org/work-groups/dice-architectures/) Checked 2026-11-12
13. [OBSP 0.1 §13: Sovereign deployment for every operator and environment](https://nexusobservatory.com/development/text/#c-13) Observatory Protocol 0.1 (draft), CC BY 4.0.
14. 3GPP TS 23.501 System architecture for the 5G System [www.3gpp.org/dynareport/23501.htm](https://www.3gpp.org/dynareport/23501.htm) Checked 2026-11-12
15. ETSI MEC Multi-access Edge Computing [www.etsi.org/technologies/multi-access-edge-computing](https://www.etsi.org/technologies/multi-access-edge-computing) Checked 2026-11-12
16. [OBSP 0.1 §9: Gaps register](https://nexusobservatory.com/development/text/#c-9) Observatory Protocol 0.1 (draft), CC BY 4.0.

On this page

1. Role
2. Interfaces
3. Schemas it emits and accepts
4. Lifecycle and conformance
5. Identity, attestation and security
6. Interoperability profile and standards
7. Not yet defined
8. Across the consortium
9. References

- [View the source](https://nexusobservatory.com/development/text/)
- [Report a defect](https://nexusobservatory.com/development/take-part/)
- [Propose a change](https://nexusobservatory.com/development/proposals/)
- [Changes](https://nexusobservatory.com/governance/changes/)
