3 ms·
I wouldn't bother with AS numbers in IP packet headers because it requires a mechanism of syncronising AS routes on the client side while the client should not
by jeroenhd 6y ago
I wouldn't bother with AS numbers in IP packet headers because it requires a mechanism of syncronising AS routes on the client side while the client should not be bothered with routing.
The idea of BGP works fine but needs to have the proper security measures in place. I don't think TCP/IP should contain complex routing systems like that.
I'd love to have IPsec to become the HTTPS for all protocols but there's no way that's going to happen without a proper mechanism to support random connections. My attempts at making IPsec work for communication between devices (so not just L2TP VPNs) so far have all been thwarted by complicated software configurations and outdated guides with questionable security recommendations.
- talideon 6y agoOf having AS numbers in the IP packet isn't actually all that bad. It's just a matter of where. This comment (https://news.ycombinator.com/item?id=23418691 https://news.ycombinator.com/item?id=23418691) from elsewhere on the thread suggests making the ASN the top 32 bits of the IPv6 address, which would solve a whole slew of issues. Clients don't (and shouldn't) care about the routing information built into the address, but building the ASN into the IP address isn't so bad. And to keep things compact, the ASN could be in little endian order.