Join

A node proves what it is, receives an identity and a policy, then a signed plan. 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. A verifier MUST bind the result to a nonce and an expiry. Identity MUST be short-lived and renewable (X.509 SVID, SPIFFE-style URI). Long-lived shared secrets MUST NOT be used. The bootstrap bundle MUST be signed by the site’s enrolment key and carry the trust anchors, policy reference and the first plan digest. Evidence: enrolment receipt, attestation result, identity issuance record.

Objects

8

Actors

0

Standards

5

Domains

6

Objects it moves

Actors it involves

Standards it is drawn against

Domains that rely on it

5G core and edge computing

Positioning, navigation and timing

Edge hardware and runtime

IoT and low-power wireless

Security, identity and supply chain

Field deployment and operations

1. Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org/rfc/rfc2119
2. Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org/rfc/rfc8174