3 ms·
The IPv6 address space is so huge, I, as an individual, was able to get a /44 no questions asked. Back in the 90's, I was able to get a IPv4 /24, no questions a
by icedchai 2y ago
The IPv6 address space is so huge, I, as an individual, was able to get a /44 no questions asked. Back in the 90's, I was able to get a IPv4 /24, no questions asked.
- auguzanellato 2y agoThere are only ~16.7 million /24s in IPv4 whereas there are more than 2000 /44 for every person living on planet earth, it’s really a different scale.
- sgjohnson 2y ago/44 is nothing. It’s 16 /48s. I have a /32 as an individual that I also got no questions asked. It’s more IPv6 space than I could ever use.
- icedchai 2y agoI understand it's "nothing", but it's also more I can ever use!
- sgjohnson 2y agoIf we measure it in /64s, yeah, it's definitely more than you could ever use. However, IPv6 space has to be measured in /48s, and IPv4 in /24s, as those are the smallest possible BGP announcable blocks. With IPv6 there's also an unwritten rule that RIRs will only assign blocks ending on a nibble boundary (with the exception of RIPE and their /29s that they expand by one bit every time you run out). So a /44 is on the second smallest nibble boundary, making it the second smallest allocation possible.
- icedchai 2y agoYep! But realistically I'm just one dude with a home network and a few VPSes doing BGP. How many /48s do I need? I was experimenting with traffic engineering so I did announce some /48's out of the /44 but that got old pretty quick.
- sgjohnson 2y ago> But realistically I'm just one dude with a home network and a few VPSes doing BGP. How many /48s do I need? Well, if the VPSes are in seperate sites, at least one per VPS, which means at least 2, which means that according to allocation policies, at least a /44. :)