update tech book for docusaurus

docs/features/networking/_category_.json

@@ -0,0 +1,7 @@
+{
+    "label": "Network",
+    "position": 4,
+    "link": {
+      "type": "generated-index",
+    }
+  }

docs/features/networking/mycelium.md

@@ -0,0 +1,16 @@
+---
+sidebar_position: 2
+title: Mycelium
+description: Our Planetary Network
+---
+
+
+# Mycelium: Our Planetary Network
+
+![alt text](../../img/mycelium.png)
+
+The planetary network called Mycelium is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created. 
+
+In the Mycelium network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
+
+!!wiki.include page:'tech:mycelium0.md'

docs/features/networking/networking.md

@@ -0,0 +1,35 @@
+---
+sidebar_position: 1
+---
+
+
+# Network Technology Overview
+
+Our decentralized networking platform allows any compute and storage workload to be connected together on a private (overlay) network and exposed to the existing Internet network. The peer-to-peer network platform allows any workload to be connected over secure encrypted networks, which will look for the shortest path between nodes.
+
+### Secure Mesh Overlay Network (Peer-to-Peer)
+
+ZNet is the foundation of any architecture running on the TF Grid. It can be seen as a virtual private data center and the network allows all of the *N* containers to connect to all of the *(N-1)* other containers. Any network connection is a secure network connection between your containers, it creates a peer-to-peer network between containers. 
+
+![alt text](../../img/net1.png)
+
+No connection is made with the Internet. The ZNet is a single tenant network and by default not connected to the public Internet. Everything stays private. For connecting to the public Internet, a Web Gateway is included in the product to allow for public access, if and when required.
+
+### Redundancy
+
+As integrated with Web Gateway
+
+![alt text](../../img/net2.png)
+
+- Any app can get (securely) connected to the Internet by any chosen IP address made available by ThreeFold network farmers through WebW
+- An app can be connected to multiple web gateways at once, the DNS round robin principle will provide load balancing and redundancy
+- An easy clustering mechanism where web gateways and nodes can be lost and the public service will still be up and running
+- Easy maintenance. When containers are moved or re-created, the same end user connection can be reused as that connection is terminated on the Web Gateway. The moved or newly created Web Gateway will recreate the socket to the Web Gateway and receive inbound traffic.
+
+### Network Wall
+
+![](../../img/network_wall.png)
+
+For OEM projects we can implement a cloud deployment without using TCP-IP or Ethernet this can lead to super secure environments, ideal to battle the Cuber Pandemic.
+
+

docs/features/networking/webgw.md

@@ -0,0 +1,43 @@
+---
+sidebar_position: 3
+title: Web Gateway
+---
+
+# Web Gateway
+
+The Web Gateway is a mechanism to connect private networks to the open Internet in such a way that there is no direct connection between the Internet and the secure workloads running in the Zero VMs.
+
+![](../../img/webgateway.jpg)
+
+### Key Benefits
+
+- Separation between where compute workloads are and where services are exposed
+- Redundancy: Each app can be exposed on multiple web gateways at once
+- Support for many interfaces
+- Helps resolve shortage of IPv4 addresses
+
+### Implementation
+
+Some 3Nodes support gateway functionality (this is configured by the farmers). A 3Node with gateway configuration can then accept gateway workloads and forward traffic to Zero VMs that only have Planetary Network or IPv6 addresses.
+
+The gateway workloads consist of a name (prefix) that first needs to be reserved on the blockchain. Then, the list of backend IPs. There are other flags that can be set to control automatic TLS (please check Terraform documentation for the exact details of a reservation).
+
+Once the 3Node receives this workload, the network configures proxy for this name and the Planetary Network IPs.
+
+### Security
+
+Zero VMs have to have a Planetary Network IP or any other IPv6 (IPv4 is also accepted). This means that any person connected to the Planetary Network can also reach the Zero VM without the need for a proxy.
+
+So it's up to the Zero VM owner/maintainer to make sure it is secured and that only the required ports are open.
+
+### Redundant Network Connection
+
+![](../../img/redundant_net.jpg)
+
+### Unlimited Scale
+
+![](../../img/webgw_scaling.jpg)
+
+The network architecture is a pure scale-out network system. It can scale to unlimited size, there is simply no bottleneck. Network "supply" is created by network farmers, and network "demand" is done by TF Grid users.
+
+Supply and demand scale independently. For supply, there can be unlimited network farmers providing web gateways on their own 3Nodes, and unlimited compute farmers providing 3Nodes for compute and storage. The demand side is driven by developers creating software that runs on the grid, system integrators creating solutions for enterprises, and so on. Globally, there is exponentially-growing demand for data processing and storage use cases.