[. . . 2 of 2 thread on binary fractal in computing]
Take the following real world network structure as an illustration of that point. #Purism provides a mobile network service called AweSIM. That is a private company network inside of T-mobile which is owned by Deutsche Telecom which operates in many countries around the world. The internet backbone is inside the US (with various intercept points throughout) but the nature of the internet is global. The internet is not a local intranet.
We’ve all seen illustrations of scale that take the following form: your house, your country, your planet, the solar system, the milky way. Computing and networking are essentially re-namings of scale relationships.
AweSIM is a VPN (plus mobile network) inside an ISP inside a global internet. There may be further subdivisions inside that “VPN.” What if you used a “VPN” inside a VPN, a walled network inside another walled network? We do all the time. https inside a VPN is not entirely visible to the VPN. SSL and private DNS still encrypts even if the domain name can be known by the network provider. For even greater privacy, a circuit of connections can be connected to multiple circuits of proxies just as a VPN can take multiple hops (i.e Tor). So really, it is all a matter of sub- and super- division in addition to certain other network design principles.
You can even think in terms of this scale paradigm when people start moaning that FTP is plaintext. The real reason my friends like this protocol is that FTP also stands for F the Police. https://ftp. - is not plaintext. It is like a VPN inside a ISP; an non-encrypted domain inside encryption. Do you think an onionsite is plaintext if it is http: //56randomcharacters .onion? Remember, just http and no s! No, of course not.
The question is: where is the wall of your scale and who has permission to get in?
#FTP #Encryption #Security #networking #CS #Tor #VPN #ISP #Scale