Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: routers do not pull the revocation list
Tomas Tormo240c458d5242
diff --git a/site/content/docs/concepts/identity.md b/site/content/docs/concepts/identity.mdindex 17e9cd97..1b530592 100644--- a/site/content/docs/concepts/identity.md+++ b/site/content/docs/concepts/identity.md@@ -224,8 +224,9 @@ the operator puts a new key first and keeps the previous key in the fileuntil every credential that key signed has expired. `GET /keys`returns the current set of keys, signed by each key in the set. Routers andnodes fetch it at enrollment and then every `--control-plane-sync-interval`,-together with the ban set, revocation list, and the mesh policy. A rotation-event only brings the next pull forward. Both+together with the ban set and the mesh policy. Nodes also pull the revocation+list and their egress assignments. A rotation event only brings the next pull+forward. Bothaccept a new set only if one of its signatures verifies under a key theyalready trust. The first key comes from enrollment, and each later key isvouched for by the key it replaces.