summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdam Ierymenko <adam.ierymenko@gmail.com>2014-09-03 16:50:06 -0700
committerAdam Ierymenko <adam.ierymenko@gmail.com>2014-09-03 16:50:06 -0700
commit4dbeb97eb9bd67fadd893252de602144d5ed9c23 (patch)
tree04f88885b35dae6c1a1f3530d5f0552afb240f10
parent34349d1a618238ec2c97468616064213bf676d47 (diff)
downloadinfinitytier-4dbeb97eb9bd67fadd893252de602144d5ed9c23.tar.gz
infinitytier-4dbeb97eb9bd67fadd893252de602144d5ed9c23.zip
docs
-rw-r--r--netconf-service/README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/netconf-service/README.md b/netconf-service/README.md
index 90b97bb6..ae5fb8b9 100644
--- a/netconf-service/README.md
+++ b/netconf-service/README.md
@@ -2,6 +2,8 @@
## What is it?
+It's the thing that controls virtual networks. It's a completely separate subsystem from supernodes; see the [Technical FAQ](https://github.com/zerotier/ZeroTierOne/wiki/Technical-FAQ) for more information on that.
+
ZeroTier's 16-digit / 64-bit network IDs are actually two numbers packed together into one. The most significant 40 bits / first 10 digits of a network ID are the ZeroTier address of the *network configuration master* responsible for issuing network configurations and certificates to members of the network. The least significant 24 bits / last 6 digits are an arbitrary 24-bit number used to identify this network on its given master.
When a ZeroTier node joins a network or updates its network configuration, it queries the network configuration master and receives a response containing either an error or a dictionary with that node's membership information and (if it's a private network) membership certificate.