Only 5x IPv4 /8 remaining at IANA

Tue Oct 19 19:00:01 UTC 2010

On Oct 19, 2010, at 11:30 AM, Franck Martin wrote:

> No, no....
> 
> Putting your servers on IPv6 is a major task. Load balancers, proprietary code, log analysis, database records... all that needs to be reviewed to see if it is compatible with IPv6 (and a few equipments need recent upgrades if even they can do IPv6 today).
> 
No, it really isn't so bad in most cases. Yes, if you're using load balancers, you need IPv6 capable LB. That's about
90% of the LB market now. Log analysis, yeah, you're going to need to update your parsers, OR, configure your LB
to do 6->4 translation. (Of course you lose something in the translation in that case).

Yes, you _MAY_ need to update database records, but, most servers don't actually.

> Putting your client machines (ie internal network) to IPv6 is relatively easy. Enable IPv6 on the border router, you don't need failover (can built it later) as anyhow the clients will failover to IPv4 if IPv6 fails... So as failover is not needed you can have a separate simple IPv6 network infrastructure on top of your IPv4 Infrastructure.
> 
Depends on your environment, actually. Most IT environments it turns out to be a pretty major challenge, if, for no
other reason than the fact that most Firewall/IDS/IPS vendors are terribly lagging in their IPv6 products.

> So my advocacy, is get your client (I'm not talking about customers here, but client as client/server) machines on IPv6, get your engineers, support staff,.. to be familiar with IPv6, then all together you can better understand how to migrate your servers infrastructure to IPv6 (and your customers to IPv6 if you are an ISP).
> 
We can agree to disagree. I have found that it is far more important (and generally easier) to get your servers on to IPv6
so that when the first IPv6-only eyeballs start to emerge (approximately June, 2011, btw), you're able to serve those customers without having to limit them to LSN/CGN/NAT64/etc. access to your services.

> If you do that, you will see migration to IPv6 is made much easier, and much faster.
> 
Hasn't been my experience doing a number of IPv6 migrations.

Owen

> ----- Original Message -----
> From: "Owen DeLong" <owen at delong.com>
> To: "Franck Martin" <franck at genius.com>
> Cc: "Jonas Frey (Probe Networks)" <jf at probe-networks.de>, "Jeffrey Lyon" <jeffrey.lyon at blacklotus.net>, "NANOG list" <nanog at nanog.org>
> Sent: Tuesday, 19 October, 2010 8:55:56 PM
> Subject: Re: Only 5x IPv4 /8 remaining at IANA
> 
> Servers work just fine over tunnels if necessary too.
> 
> Get your public-facing content and services on IPv6 as fast as possible.
> Make IPv6 available to your customers as quickly as possible too.
> 
> Finally, your internal IT resources (other than your support department(s)) can
> probably wait a little while.
> 
> Owen
> 
> On Oct 18, 2010, at 1:41 PM, Franck Martin wrote: