In mid-April, an Internet Draft turned up in my timelines that wants to rethink the routing foundation of the internet — with OAuth2 tokens, a central Zone Server and egress validation against WHOIS. My hot take after three readings. Summary in 90 seconds In April 2026, an IETF Internet Draft was submitted that wants to rethink the routing foundation of the internet: IPv8 with 64-bit addresses, a central Zone Server, OAuth2 tokens at the network layer, and egress validation against WHOIS. The draft has no IETF working-group sponsor, appears to be largely AI-generated, and contains three architectural features I consider dangerous from a DevSecOps perspective: OAuth tokens at the wrong layer, a single point of catastrophe in the Zone Server, and built-in surveillance infrastructure. Bill Buchanan sees it more kindly — but he only checked the steering wheel, didn't start the car. When IPv8 turned up in my timelines in mid-April, I was puzzled. Was this meant to be a serious proposal?…