Earlier quoted context omitted.
That's more to do with increasing prices than decreasing demand
In the traditional capitalist model, those are the same thing.
Only in a perfectly efficient market, which is pretty rare in the real world.
IP addresses through 2024
81–90 of 90 posts
Re: IP addresses through 2024
#82I do want to point out one thing that is a common misconception by IT engineer types: > The use of NATs force the interactions into client-initiated transactions... (abbreviated) There is absolutely ZERO chance that that, let's say Roomba, is going to let you connect directly to your vacuum robot at your home, from your cell, over ipv6, without going through their proxy server in an AWS Datacenter in Virgina. The nat…
But perhaps a competitor would allow you to do that. There is at least a niche of users who would prefer not to have everything go through the company's servers.
Re: IP addresses through 2024
#83Earlier quoted context omitted.
Yet there will still be comments asking why IPv8 can't be IPv4 with another few sets of digits tagged onto the end, as if that would somehow be compatible with the current implementation of IPv4.
I swear it is easier to argue with flat earthers than with people who want IPv4 but with more addresses.
I just hope that by making the joke, I won't accidentally make fetch happen :-D
Re: IP addresses through 2024
#84One thing I've wondered is how routing will work out in the long term for IPv6. If I recall correctly, IPv6 routing was supposed to be hierarchical based on ISP and region, and that would help routing tables. But what if companies in the US, for example, buy a /19 and then divide it up and use it across the globe? I assume routers will have to come with a lot more RAM.
IPv6 routing was supposed to be hierarchical... The Internet gave up on that a while ago. IPv6 routing works like IPv4 where people just advertise whatever routes they want. Router RAM has been fixed with newer HBM-based ASICs supporting millions of routes.
Then making gigantic (less than /32) allocations makes even less sense! If we're not doing that, contiguous address space for orgs is far less important.
Re: IP addresses through 2024
#85Earlier quoted context omitted.
People get caught up in how many IPv6 addresses exist, as if we will always have enough to go around. Recently Capital One was assigned a /16, enough for every ATM in the US to be its own ISP and make its own customer allocations. We continue to repeat the same mistakes that made people believe we needed v6 in the first place. We will never run out of IPv6, but I believe in my lifetime you won't be able to get new v6…
> We continue to repeat the same mistakes that made people believe we needed v6 in the first place. The IPv6 designers already thought of that and prepared for that eventuality. Only 1/8 of all available IPv6 addresses (the ones starting with the bits 001) is available for allocation under the current rules. If and when that gets exhausted, there will still be more than 5/8 of all IPv6 addresses available to be alloc…
Do current routers deal with other addresses correctly? This reminds me a little of the challenges in reclaiming 240.0.0.0/4 [0].
[0] - https://blog.benjojo.co.uk/post/class-e-addresses-in-the-rea...
Re: IP addresses through 2024
#86Earlier quoted context omitted.
People get caught up in how many IPv6 addresses exist, as if we will always have enough to go around. Recently Capital One was assigned a /16, enough for every ATM in the US to be its own ISP and make its own customer allocations. We continue to repeat the same mistakes that made people believe we needed v6 in the first place. We will never run out of IPv6, but I believe in my lifetime you won't be able to get new v6…
> We continue to repeat the same mistakes that made people believe we needed v6 in the first place. The IPv6 designers already thought of that and prepared for that eventuality. Only 1/8 of all available IPv6 addresses (the ones starting with the bits 001) is available for allocation under the current rules. If and when that gets exhausted, there will still be more than 5/8 of all IPv6 addresses available to be alloc…
> Only 1/8 of all available IPv6 addresses (the ones starting with the bits 001) is available for allocation under the current rules.
Yes yes yes, all sorts of really super serious policies were put in place to prevent abuse of IPv4 allocation rules too.
Re: IP addresses through 2024
#87Earlier quoted context omitted.
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.
/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.
I understand it's "nothing", but it's also more I can ever use!
Re: IP addresses through 2024
#88Earlier quoted context omitted.
/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.
I understand it's "nothing", but it's also more I can ever use!
If 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.
Re: IP addresses through 2024
#89Earlier quoted context omitted.
I understand it's "nothing", but it's also more I can ever use!
If 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…
Yep! 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.
Re: IP addresses through 2024
#90Earlier quoted context omitted.
If 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…
Yep! 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.
> 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. :)