APNIC just got another IPv4 /8 thus only 5 left:
http://www.nro.net/media/remaining-ipv4-address-below-5.html
(And the spammers will take the rest...)
So, if your company is not doing IPv6 yet, you really are really getting
late now.
Greets,
Jeroen
(PS: There seems to be a trend for people calling themselves"IPv6
Pioneers" as they recently did something with IPv6, if you didn't play
in the 6bone/early-RIR allocs you are not a pioneer as you are 10 years
late)
Thought it was the other way around. There are 12 remaining: 7 will be
allocated normally, with the remaining 5 split across the five RIRs.
-S.
Jeroen Massar wrote:
APNIC just got another IPv4 /8 thus only 5 left:
http://www.nro.net/media/remaining-ipv4-address-below-5.html
(And the spammers will take the rest...)
Just for clarification, that article says 5% left, not 5x /8.
According to Leo's E-mail earlier, they have 12 /8s left in the free pool.
And +1 on the "pioneers" comment too.
Paul.
And +1 on the "pioneers" comment too.
Paul.
IPv6 Hipsters..Doing it before it was cool.
IPV4 ->easy();
IPV6->really().Really().Difficult();
Jeroen Massar <jeroen@unfix.org> writes:
So, if your company is not doing IPv6 yet, you really are really getting
late now.
They won't listen.
Jens
I'll listen, but I need my vendors, carriers, etc. to all get on board first.
Jeff
Nah...
Get IPv6 for your clients today, think about your servers for later...
Then you will be able to ask all the right questions and apply the right pressure to your vendors, carriers, etc....
My clients can't use IPv6 when my infrastructure and carriers don't support it.
Jeff
Smells like a business opportunity to steal your customers.
Thanx!
Only if you're prepared for the bloody onslaught of DDoS.
Jeff
> And +1 on the "pioneers" comment too.
Paul.
IPv6 Hipsters..Doing it before it was cool.
Late to the party...
The hipsters have already moved on having grown bored with their v6
deployments around 2004.
Uh.... that would be 12 left -- 7 general distribution and 5 reserved for the
global end allocation policy.
That's 5%, not 5 /8s.
Owen
Have you done IPv6?
I have... It's not even difficult(), let alone really().Really().Difficult().
Owen
If you aren't telling your existing vendors that you need IPv6 now, you
need to be. If your vendors aren't getting the message, it's well past
time to take action and start looking for other vendors.
Owen
* Owen DeLong <owen@delong.com> [2010-10-18 17:27]:
Have you done IPv6?
I have... It's not even difficult(), let alone really().Really().Difficult().
maybe not from a users standpoint (that comes later when it misbehaves
again). from an implementors (I have written a lot of kernel-side
networking code and networking related daemons, including a full-blown
bgpd, and that unfortunately included having to deal with v6)
viewpoint - IPv6 is a desaster. Why people take up that crap is beyond
me, instead of working on a viable alternative that doesn't suck.
Which is certainly possible.
Owen,
He did not display the return values of these functions.
I think his IPv6 one returns FALSE;
- Jared
Most of that junk can honestly be ignored. 
- Jared
I would say that at this point it is too late to resist v6 deployment
but it might be a good time to work on the "next thing" and use v6 as an
example of how not to do it next time.
It certainly is going to present some security challenges for some
folks, particularly the ones that have been using dynamic nat pools to,
in effect, block inbound connections. Firewall vendors are going to see
a windfall from v6, I think.
G
Wait, and OpenBSD developer that thinks everyone else's work is crap?
Shocking...
I encourage you to build and deploy your viable alternative...
thanks
joel