summaryrefslogtreecommitdiff
path: root/node/Packet.hpp
diff options
context:
space:
mode:
Diffstat (limited to 'node/Packet.hpp')
-rw-r--r--node/Packet.hpp25
1 files changed, 17 insertions, 8 deletions
diff --git a/node/Packet.hpp b/node/Packet.hpp
index c2e6da00..fed6aacf 100644
--- a/node/Packet.hpp
+++ b/node/Packet.hpp
@@ -742,14 +742,23 @@ public:
VERB_NETWORK_CONFIG_REQUEST = 0x0b,
/**
- * Network configuration refresh request:
- * <[...] array of 64-bit network IDs>
- *
- * This can be sent by the network controller to inform a node that it
- * should now make a NETWORK_CONFIG_REQUEST.
- *
- * It does not generate an OK or ERROR message, and is treated only as
- * a hint to refresh now.
+ * Network configuration update push:
+ * <[8] network ID to refresh>
+ * <[2] 16-bit number of address/timestamp pairs to blacklist>
+ * [<[5] ZeroTier address of peer being revoked>]
+ * [<[8] blacklist credentials older than this timestamp>]
+ * [<[...] additional address/timestamp pairs>]
+ *
+ * This can be sent by a network controller to both request that a network
+ * config be updated and push instantaneous revocations of specific peers
+ * or peer credentials.
+ *
+ * Specific revocations can be pushed to blacklist a specific peer's
+ * credentials (COM, tags, and capabilities) if older than a specified
+ * timestamp. This can be used to accomplish expedited revocation of
+ * a peer's access to things on a network or to the network itself among
+ * those other peers that can currently reach the controller. This is not
+ * the only mechanism for revocation of course, but it's the fastest.
*/
VERB_NETWORK_CONFIG_REFRESH = 0x0c,