Observatory ProtocolNode registryAuthenticated network time (NTS)
Authenticated network time (NTS)
A network time server that authenticates its responses with Network Time Security, so a node can trust network time without a local grandmaster.
- 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
Network time MUST be authenticated (NTS) or come from a site grandmaster. (OBSP 0.1 §5.4)
- Class
- Timing sources
The references a node draws its time from. Their quality reaches the grid as time quality records. - Protocol role
- Not a protocol role: a time source whose quality each node reports.
- Conformance profile
- No conformance profile applies to the server itself.
- Technology domains
- Positioning, navigation and timing
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 |
|---|---|---|
| Key establishment | NTS key establishment over TLS | (IETF RFC 8915) |
| Time | NTPv4 with NTS extension fields | (IETF RFC 5905; IETF RFC 8915) |
| Reported as | time-quality sourceClass NTS | (OBSP 0.1 §5.4) |
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)
Lifecycle and conformance
No conformance profile applies to the server itself.
| Clause | Stage | In a profile | Contract |
|---|---|---|---|
| §5.1 | Join | No | Contracted |
| §5.2 | Admit | No | Contracted |
| §5.3 | Describe | No | Contracted |
| §5.4 | Time | No | Contracted |
| §5.5 | Observe | No | Contracted |
| §5.6 | Qualify | No | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | No | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | No | Contracted |
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)
- IETF RFC 8915Network Time Security for the Network Time Protocol(IETF RFC 8915)
- IETF RFC 5905Network Time Protocol Version 4(IETF RFC 5905)
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.
- Standards
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.nexustandards.com
- 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 §5.4: Time Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- IETF RFC 8915 Network Time Security for the Network Time Protocol www.rfc-editor.org/rfc/rfc8915.html Checked
- IETF RFC 5905 Network Time Protocol Version 4 www.rfc-editor.org/rfc/rfc5905.html 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 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.