Spindel/IoT colo

## IoT colo
# Internet of Things
## A co-location in your home.

### A real co-location
In a normal co-location (colo for short) a provider has a data hall, where they install servers of various kinds for their customers. The colo stands for power and connectivity, and some level of out-of-band monitoring to do billing or capping.

The monitoring is usually on the network level, from switches and packet flows, and not internal to your server ("what is running now") and is used to prevent customers from interfering with others, and to alert customers in case of their servers failing.

### The home co-location

The home is a crappy colo. There is no redundant power, and usually not an UPS unless for very important things ( The home owners own computer / NAS ).

The network in the home is also quite bad. There is little isolation, at most only between Wifi and wired.
You also have a lot of NAT, crap ipv6 support, and DHCP servers that break standards.

### IoT Co-location

In the IoT sense, you, the colo provider, pay to run another company's hardware, in your own colo.  You don't necessarily have access to the software inside, most of the time you're not allowed "proper" admin access, cannot do patching or updating, because you do not control the software inside. Even if it's [Free Software](https://www.fsf.org/) in the FSF sense.

So. You pay for these, you pay their hosting, power and networking. You have no proper monitoring of what they are doing. You have no way to see what their update status is. And you have no proper experience in running a co-location.  There is no Network level isolation, you can barely see if they got DHCP leases from your in-home "Edge router".

## Why is this bad?
So. This is bound to be a security and maintenance nightmare.  You are not an admin. You don't want to be an admin. You want to be a consumer. You want these co-located servers to provide you with a service, and be done with it.
You never signed up for this, at least not in your own head. You thought you bought an appliance. Instead you ended up being a co-location host.

Did that IoT device run a BitTorrent client to fetch it's updates? Is it using your bandwidth to serve neighbour connectivity to others?
Did they decide to tunnel out traffic over interesting protocols, to provide STUN-like services for other devices?
Are they simply downloading their updates over clear-text HTTP? Do the consume even KNOW what this means?


This is sadly the state of the art.
And it's sucks.

Join me and make it better.
	# Internet of Things
	## A co-location in your home.

	### A real co-location
	In a normal co-location (colo for short) a provider has a data hall, where they install servers of various kinds for their customers. The colo stands for power and connectivity, and some level of out-of-band monitoring to do billing or capping.

	The monitoring is usually on the network level, from switches and packet flows, and not internal to your server ("what is running now") and is used to prevent customers from interfering with others, and to alert customers in case of their servers failing.

	### The home co-location

	The home is a crappy colo. There is no redundant power, and usually not an UPS unless for very important things ( The home owners own computer / NAS ).

	The network in the home is also quite bad. There is little isolation, at most only between Wifi and wired.
	You also have a lot of NAT, crap ipv6 support, and DHCP servers that break standards.

	### IoT Co-location

	In the IoT sense, you, the colo provider, pay to run another company's hardware, in your own colo. You don't necessarily have access to the software inside, most of the time you're not allowed "proper" admin access, cannot do patching or updating, because you do not control the software inside. Even if it's [Free Software](https://www.fsf.org/) in the FSF sense.

	So. You pay for these, you pay their hosting, power and networking. You have no proper monitoring of what they are doing. You have no way to see what their update status is. And you have no proper experience in running a co-location. There is no Network level isolation, you can barely see if they got DHCP leases from your in-home "Edge router".

	## Why is this bad?
	So. This is bound to be a security and maintenance nightmare. You are not an admin. You don't want to be an admin. You want to be a consumer. You want these co-located servers to provide you with a service, and be done with it.
	You never signed up for this, at least not in your own head. You thought you bought an appliance. Instead you ended up being a co-location host.

	Did that IoT device run a BitTorrent client to fetch it's updates? Is it using your bandwidth to serve neighbour connectivity to others?
	Did they decide to tunnel out traffic over interesting protocols, to provide STUN-like services for other devices?
	Are they simply downloading their updates over clear-text HTTP? Do the consume even KNOW what this means?


	This is sadly the state of the art.
	And it's sucks.

	Join me and make it better.