4 ms·
First, you have to secure all the computers. Capability Based Security for everyone. This lets us all run mobile code without danger. (No more virus or worm iss
by mikewarot 5y ago
First, you have to secure all the computers. Capability Based Security for everyone. This lets us all run mobile code without danger. (No more virus or worm issues)
Next, we use 128 bit IP addresses, 32 bit port and protocol numbers, and absolutely forbid NAT as a way of getting more addresses. (no ip address shortage)
Next, all email has to be cryptographically signed by the sending domain using public key encryption. (No more spam)
Next, selling internet access [EDIT]ONLY is strictly prohibited. Either connections can host servers, or find a different business model. Any node of the internet should be able to run a small server. (No more censorship in the walled gardens) Yes, I know it's stupid to try to host a server on the upload bandwidth I get from a cable modem, but it shouldn't be prohibited. If I want to see my webcams from anywhere, it shouldn't require someone else's server.
DNS should be done using a blockchain, it would need some iteration to get it right.
- rlt 5y agoMostly agree except instead of “prohibiting” certain things the systems we build should disincentivize them. e.x. No need to prohibit NAT if there are more than enough IPs to go around.
- Koffiepoeder 5y ago> Next, selling internet access is strictly prohibited. Not sure if this is attainable, someone has to draw the cables and maintain them. What do you propose, that everyone does this for themselves? I don't think we'll be seeing much fiber cable, nor internet users then. What with trans-oceanic cables? In the end someone's got to pay the bill. I do agree however that DNS should be free and decentralized. The difficulty here would be to avoid domain hoarders. Maybe through some verification / vouching system? On the other hand that seems a lot like PGP keyservers, which also didn't turn out all too great. All in all, difficult problems. Maybe the current system isn't all too bad after all?
- mikewarot 5y agoI edited my entry, I hope it makes sense... access is different than connection... access forces us to be consumers, connection lets us be suppliers.
- bruce511 5y ago>> next, all email has to be cryptographically signed by the sending domain using public key encryption. (No more spam) How does this work? Would every email address need to get a public/private key? From where? Does someone get to control who can use email? How much does it cost? Do the certs expire? How do we manage the system for billions of email addresses? I ask this with genuine interest - I'm not sure how a cert-required email system would work - or how it would help with spam...
- mikewarot 5y agoIf I wanted to send email from mike@warot.com, I'd simply use my DNS specified MX server, and it would sign the outbound email (I'd have to log in, for the email to be forwarded). Any forwarding server could check the signature against the MX specified server and get the public key for the domain. If the signature didn't match, the email would get rejected. We'd have to agree on standard protocols, but all domains would manage their own keys, nothing would be centralized past the already centralized DNS system.
- mlinksva 5y agoYou had me at cabsec (I don't think this terminology has taken hold, but I see it on one of your blogs https://capabilitiesdigest.blogspot.com/2015/10/the-cabsec-fork-in-road.html https://capabilitiesdigest.blogspot.com/2015/10/the-cabsec-f...), lost me at blockchain. Fortunately the first item is conceivably remediable without other changes in Internet design, e.g., Fuchsia, right?