Hi, On Fri, Jun 28, 2013 at 01:27:19PM +0530, Suresh Ramasubramanian wrote:
I know the size of the v6 namespace Remember that we are currently working with a smaller effective size.. The allocated part of v6, with martian filters to block out the rest
And out of that.. Well, the more space poorly administered allocation policies squander by handing them to abusers without very much due diligence, the more trouble the rest of us face
I'm aware of all that, but I *can* do the math. Inside RIPE's /12, there are *one million* /32s.
As for the future, I won't try predicting what the internet will be like and what devices from where will connect over v6. I would just tell you to avoid history repeating itself so we don't look back with regret at this conversation after a decade or two
I've heard that argument so many times over the last 16 years where the much more important goal should have been "get IPv6 deployed!" instead of worrying about "not giving out IPv6 addresses to <somesortofentity>, as they might run out!". We're inside a /12, which has LOTS of space left. That /12 is inside a /3, which is barely touched (5 /12s out of 512 allocated). And *that* /3 has 6 more to be used, if we really mess up. I'll start to reconsider my position if we manage to fill the RIPE /12 by giving out standard-size allocations (/32) in the next 20 years. I'll start to *worry* if we fill half of 2000::/3 in the next 30 years. I'll publically admit I was wrong about my IPv6 use predictions if we fill FP001 (2000::/3) in the next 40 years. ... and *then*, we have people that can learn from what happened in FP001 and get it right in one of the next FPs. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279