| ▲ | jaysonvantuyl 11 hours ago | |
I feel like this completely misses the entire point (or at least half the functionality) of ASNs. ASNs give you an identity at the peering level that can be used to dynamically provision routes; so it is used to evolve (over time) where a given network-level address lives. Making it part of the address now makes that mapping vastly less flexible. The list of things it breaks is breathtaking: - Transferring a subnet between providers can't be done (the ASN part changes). - Providing the same services on multiple providers doesn't work (different ASNs can't advertise the same address). - Various types of multicast domain management break (global networks that use IBGP for internet multicast routing need to figure out their prefixes). Then there's the bootstrapping problem with the mix of layer 3 / layer 7. And JWT used everywhere? And no integrated solutions for things like DNSSEC (warts and all)? No apparent attention to distributed implementations of (now consolidated) core infrastructure? Say what you want about systemd, at least there is arguably someone applying a different (but consistent) design to a real problem. This "proposal" feels like someone with limited understanding of the design principles behind the Internet opened up ChatGPT and asked it to fix "problems" that they barely understand. I try not to be mean to the well-meaning, but... well... some people aspire to operate at a level for which they are entirely unqualified. | ||