3 ms·
I think you've pretty much got it, but what makes it work is that you're overprovisioned at each level. You don't have to set up an addressing scheme that's gua
by teraflop 11y ago
I think you've pretty much got it, but what makes it work is that you're overprovisioned at each level. You don't have to set up an addressing scheme that's guaranteed to be able to satisfy every conceivable request as a contiguous range. The extra buffer means that if you run out at one level, you can get another allocation from the next level up without having to advertise it globally.
Right now, if you need more IPv4 addresses, you have to buy a /22 or so from someone else. Because the address space is so hotly-contested, that block could come from almost anywhere, which means every core router on the internet needs to remember where it lives on the actual topology.
With IPv6, maybe once in a while a customer comes along who needs more than a /56. No big deal; you just give them another (maybe non-contiguous, if you're unlucky) allocation from the ISP's block. The ISP needs to remember that both allocations belong to the same customer, and route packets accordingly. But everyone else can just route based on the ISP's all-encompassing prefix. That's what makes the system fundamentally more scalable.
- ghshephard 11y agoReally good point about the ISP just reaching into it's /32 allocation. Also, If there is the slightest chance that you will ever need more than a /56, (I.E. you are anything other than a vanilla home business account) the ISP will almost always give you a /48 right out of the gate anyways, and so you have on the very first day 65,536 subnetworks to work with. After that, everything you say is also true, if the customer starts to run low on those 65,536 subnetworks, the ISP can simply reach into it's /32, and then hand out a second /48 in the rare scenario that someone is using more than 65,536 subnetworks that need to be globally routed.