Mesh Networks and Data Transport(1): The Cord Cutting Voluntaryist/Anarchist

I've always been quite fascinated with the idea of mesh networks, diverse path and dynamic routing. With the emergence of wireless technologies highly reliable, and scalable last mile data transport solutions have never been so accessible. Being a Solutions Architect for telecommunications providers I have been fortunate enough to monitor, design and deploy large scale layer 2/3 telecom networks with dynamic routing, and mesh topology in various applications. 

What is a Mesh Network? 

A mesh network is a network topology in which each node relays data for the network. All mesh nodes cooperate in the distribution of data in the network. Mesh networks can relay messages using either a flooding technique or a routing technique.

-wiki

What is Backhaul?

It is aggregating last mile circuits with core and core edge circuits. In various networks configurations it could be seen as when the data is leaving the customer premise. The data is being backhauled to another interconnection or POP. Backhaul is often configured in multiple layers both software and hardware, LAN and WAN.

My objective is to identify some of potential obstacles that may lie in the way of building a robust high quality of service network that can support high quality data transport from video to VoIP services. There are many ways to solve various opportunities. 

It is important to understand that if each CPE device is expected to support multiple devices, multiple computers, visitor devices, printers, indoor/outdoor WAP, TVs, Smart Stream boxes etc., then the degree to which the desired quality of network services and reliability is the degree to which you must use high quality reliable hardware and correct network configuration. A few questions that would need to be addressed:

- Where is power for all sites? Commercial or renewable? 

- What is line of site to various sites (LoS)? Physical topography.  

- Would the network need to support dynamic routing protocols such as ISIS, MPLS, VPLS or OSPF? This    certainly effects the hardware needed.

- What services are desired? VoIP, IPSec? This also effects hardware decisions.

Perhaps a numerous section sized Anarchist community forms just outside of Acapulco, Mexico inspired by @JeffBerwick and others which leads to service needs at over 100 different dwellings? 

Or perhaps @AdamKokesh would like to deploy a local outdoor/indoor mesh network across his 10 acres? Both applications are solvable in similar ways.

Many Voluntaryists wish to cut the cords from the large monopoly service providers but find it very difficult. IP addresses are scarce with centralized allocation. This will continue to be a problem until something new and revolutionary is invented like CJDNS, which implements an encrypted IPv6 network using public key cryptography for network address allocation and a distributed hash table for routing.

As it stands moving forward I would advise that high quality hardware and engineering be standardized to support low latency sensitive services like VoIP. I'd like for my Voluntaryist brothers to realize that it will take significant capital to support these services for a permanent Anarchist community; but it has never been more cost effective, reliable or scalable to do so in history. With this and information accessibility people can build their own communications networks, from Last Mile to Core Edge to Core Network which would lead to a private end to end encrypted layer 2 network to give/sell access. I would love to have the opportunity to help design and build-out the communication network needed in this hypothetical Acapulco community someday...