\/<\/p>Specification<\/a>\/<\/p>State machines<\/b> States are entered on evidence, never on assertion.<\/h1> Eleven state machines, from enrolment to revocation. Every transition is typed, and a state is entered only on the evidence its transition names.<\/p> Read the specification<\/a>Contribute<\/a> Functions<\/dt>12<\/dd> State machines<\/dt>11<\/dd> Objects<\/dt>21<\/dd> Standards<\/dt>48<\/dd> <\/dl> <\/section> Specification<\/a>Functions<\/a>State machines<\/a>Flows<\/a>Objects<\/a>Participants<\/a>Standards<\/a>Conformance<\/a>Governance<\/a>Changes<\/a>Implementers<\/a>Wire bindings<\/a>Reference scenes<\/a> <\/nav> On this page<\/p>Lineage<\/span><\/li>State machines<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>Time A shared clock<\/dt>Coordinated Universal Time is computed by the BIPM from data contributed by timing laboratories; IEEE 1588 defines the Precision Time Protocol, and ITU-T G.8275.1 profiles it for phase and time synchronisation across networks. In the protocol, time is a function in its own right: a measurement whose clock cannot be trusted cannot be published as trusted. [1]<\/span><\/sup>[2]<\/span><\/sup>[3]<\/span><\/sup><\/dd> 2023 Attested identity<\/dt>The IETF RATS architecture (RFC 9334) describes how one party appraises evidence about the state of another. The protocol\u2019s Join and Admit functions apply that model to instruments: a participant begins untrusted and is admitted on evidence, not on assertion. [4]<\/span><\/sup><\/dd> <\/dl><\/section>Typed transitions, evidence at every step.<\/h2>Select a machine, then a state, to read what it leads to and the evidence each transition requires.<\/p> <\/header> UNENROLLED<\/p>DISCOVERED<\/p>ATTESTING<\/p>IDENTITY_ISSUED<\/p>POLICY_BOUND<\/p>PLAN_STAGED<\/p>LOCAL_READY<\/p>DEGRADED<\/p>QUARANTINED<\/p>REVOKED<\/p> Selected state<\/dt>UNENROLLED<\/dd> Leads to<\/dt>DISCOVERED when hardware inventory recordedQUARANTINED when bootstrap integrity failure<\/dd> Reached from<\/dt>Entry state<\/dd> <\/dl> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>Bureau International des Poids et Mesures. “Realizing and disseminating international reference time scales: UTC, UTCr and TT(BIPM).” www.bipm.org\/en\/time-ftp<\/a><\/li>IEEE Std 1588-2019. “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.” doi.org\/10.1109\/IEEESTD.2020.9120376<\/a><\/li>ITU-T Recommendation G.8275.1. “Precision time protocol telecom profile for phase\/time synchronization with full timing support from the network.” www.itu.int\/rec\/T-REC-G.8275.1<\/a><\/li>Birkholz, H., et al. (2023). RFC 9334, “Remote ATtestation procedureS (RATS) Architecture.” IETF. www.rfc-editor.org\/rfc\/rfc9334<\/a><\/li>Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org\/rfc\/rfc2119<\/a><\/li>Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org\/rfc\/rfc8174<\/a><\/li><\/ol><\/section><\/main> Read it, test it, propose a change.<\/h2>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.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>
\/<\/p>State machines<\/b> States are entered on evidence, never on assertion.<\/h1>
Eleven state machines, from enrolment to revocation. Every transition is typed, and a state is entered only on the evidence its transition names.<\/p> Read the specification<\/a>Contribute<\/a> Functions<\/dt>12<\/dd> State machines<\/dt>11<\/dd> Objects<\/dt>21<\/dd> Standards<\/dt>48<\/dd> <\/dl> <\/section> Specification<\/a>Functions<\/a>State machines<\/a>Flows<\/a>Objects<\/a>Participants<\/a>Standards<\/a>Conformance<\/a>Governance<\/a>Changes<\/a>Implementers<\/a>Wire bindings<\/a>Reference scenes<\/a> <\/nav> On this page<\/p>Lineage<\/span><\/li>State machines<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>Time A shared clock<\/dt>Coordinated Universal Time is computed by the BIPM from data contributed by timing laboratories; IEEE 1588 defines the Precision Time Protocol, and ITU-T G.8275.1 profiles it for phase and time synchronisation across networks. In the protocol, time is a function in its own right: a measurement whose clock cannot be trusted cannot be published as trusted. [1]<\/span><\/sup>[2]<\/span><\/sup>[3]<\/span><\/sup><\/dd> 2023 Attested identity<\/dt>The IETF RATS architecture (RFC 9334) describes how one party appraises evidence about the state of another. The protocol\u2019s Join and Admit functions apply that model to instruments: a participant begins untrusted and is admitted on evidence, not on assertion. [4]<\/span><\/sup><\/dd> <\/dl><\/section>Typed transitions, evidence at every step.<\/h2>Select a machine, then a state, to read what it leads to and the evidence each transition requires.<\/p> <\/header> UNENROLLED<\/p>DISCOVERED<\/p>ATTESTING<\/p>IDENTITY_ISSUED<\/p>POLICY_BOUND<\/p>PLAN_STAGED<\/p>LOCAL_READY<\/p>DEGRADED<\/p>QUARANTINED<\/p>REVOKED<\/p> Selected state<\/dt>UNENROLLED<\/dd> Leads to<\/dt>DISCOVERED when hardware inventory recordedQUARANTINED when bootstrap integrity failure<\/dd> Reached from<\/dt>Entry state<\/dd> <\/dl> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>Bureau International des Poids et Mesures. “Realizing and disseminating international reference time scales: UTC, UTCr and TT(BIPM).” www.bipm.org\/en\/time-ftp<\/a><\/li>IEEE Std 1588-2019. “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.” doi.org\/10.1109\/IEEESTD.2020.9120376<\/a><\/li>ITU-T Recommendation G.8275.1. “Precision time protocol telecom profile for phase\/time synchronization with full timing support from the network.” www.itu.int\/rec\/T-REC-G.8275.1<\/a><\/li>Birkholz, H., et al. (2023). RFC 9334, “Remote ATtestation procedureS (RATS) Architecture.” IETF. www.rfc-editor.org\/rfc\/rfc9334<\/a><\/li>Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org\/rfc\/rfc2119<\/a><\/li>Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org\/rfc\/rfc8174<\/a><\/li><\/ol><\/section><\/main> Read it, test it, propose a change.<\/h2>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.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>
On this page<\/p>
Select a machine, then a state, to read what it leads to and the evidence each transition requires.<\/p> <\/header>
UNENROLLED<\/p>
DISCOVERED<\/p>
ATTESTING<\/p>
IDENTITY_ISSUED<\/p>
POLICY_BOUND<\/p>
PLAN_STAGED<\/p>
LOCAL_READY<\/p>
DEGRADED<\/p>
QUARANTINED<\/p>
REVOKED<\/p>
Sources for the historical and standards statements on this page.<\/p> <\/header>
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.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>