\/<\/p>Specification<\/a>\/<\/p>Implementers<\/b> Profiles and planes for implementers.<\/h1> What an implementation of each profile must provide, and the planes across which it communicates.<\/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>Profiles<\/span><\/li>Reading order<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>1984 End to end, rough consensus<\/dt>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\u2019s architecture. The IETF\u2019s working method, summarised in RFC 7282 as \u201crough consensus and running code\u201d, sets the standard for how an open protocol should change. The protocol keeps authority at the site and changes only through open proposals. [1]<\/span><\/sup>[2]<\/span><\/sup>[3]<\/span><\/sup><\/dd> <\/dl><\/section>What each implementation provides.<\/h2>Choose the profile that matches what you build; it names the functions you must implement.<\/p> <\/header>Node agents and devices<\/dt>OBSP-NODE: Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit.<\/dd> Site controllers<\/dt>OBSP-SITE: OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier).<\/dd> Cluster and grid control planes<\/dt>OBSP-GRID: OBSP-SITE plus Federate and Exchange.<\/dd> Hardware, software, model and data providers<\/dt>OBSP-PROVIDER: Admit, Describe, Exit.<\/dd> Applications reading products<\/dt>OBSP-CONSUMER: Exchange, Correct (subscribe).<\/dd> <\/dl><\/section>Four ways into the specification.<\/h2> <\/header>Specification The functions<\/h3>The twelve functions and their requirements.<\/a>Specification The state machines<\/h3>Typed transitions and their evidence.<\/a>Specification The wire bindings<\/h3>One open binding per plane.<\/a>Specification Conformance<\/h3>Profiles and levels.<\/a> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>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<\/a><\/li>Carpenter, B., ed. (1996). RFC 1958, “Architectural Principles of the Internet.” IETF. www.rfc-editor.org\/rfc\/rfc1958<\/a><\/li>Resnick, P. (2014). RFC 7282, “On Consensus and Humming in the IETF.” IETF. www.rfc-editor.org\/rfc\/rfc7282<\/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>Implementers<\/b> Profiles and planes for implementers.<\/h1>
What an implementation of each profile must provide, and the planes across which it communicates.<\/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>Profiles<\/span><\/li>Reading order<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>1984 End to end, rough consensus<\/dt>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\u2019s architecture. The IETF\u2019s working method, summarised in RFC 7282 as \u201crough consensus and running code\u201d, sets the standard for how an open protocol should change. The protocol keeps authority at the site and changes only through open proposals. [1]<\/span><\/sup>[2]<\/span><\/sup>[3]<\/span><\/sup><\/dd> <\/dl><\/section>What each implementation provides.<\/h2>Choose the profile that matches what you build; it names the functions you must implement.<\/p> <\/header>Node agents and devices<\/dt>OBSP-NODE: Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit.<\/dd> Site controllers<\/dt>OBSP-SITE: OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier).<\/dd> Cluster and grid control planes<\/dt>OBSP-GRID: OBSP-SITE plus Federate and Exchange.<\/dd> Hardware, software, model and data providers<\/dt>OBSP-PROVIDER: Admit, Describe, Exit.<\/dd> Applications reading products<\/dt>OBSP-CONSUMER: Exchange, Correct (subscribe).<\/dd> <\/dl><\/section>Four ways into the specification.<\/h2> <\/header>Specification The functions<\/h3>The twelve functions and their requirements.<\/a>Specification The state machines<\/h3>Typed transitions and their evidence.<\/a>Specification The wire bindings<\/h3>One open binding per plane.<\/a>Specification Conformance<\/h3>Profiles and levels.<\/a> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>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<\/a><\/li>Carpenter, B., ed. (1996). RFC 1958, “Architectural Principles of the Internet.” IETF. www.rfc-editor.org\/rfc\/rfc1958<\/a><\/li>Resnick, P. (2014). RFC 7282, “On Consensus and Humming in the IETF.” IETF. www.rfc-editor.org\/rfc\/rfc7282<\/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>
Choose the profile that matches what you build; it names the functions you must implement.<\/p> <\/header>
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>