[arin-ppml] The non-deployment of IPv6
If the time estimates I've seen put forward here are accurate....and I see no reason to assume they wouldn't be.... then it'll be 2-3 years minimum before we see anyone out there that can ONLY do IPv6. In that time frame I'd be looking for the same sort of solution for public facing servers in the DMZ as I would for the rest of my network....namely some sort of v4 to v6 gateway service that would act as a proxy for my 4 machines and allow them to communicate with IPv6 hosts. I don't imagine it would be particulary difficult to grab a small IPv6 allocation if I needed it for that purpose... so no rush there..... and the longer I wait, the more choices I'm likely to have for v4 to v6 solutions....and the less costly they will be. Frankly at this point I don't even know if my ISP's are offering support for v6 services in my area.
From: John Curran [jcurran at arin.net]
Sent: Wednesday, December 09, 2009 3:39 PM
To: Chris Engel
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] The non-deployment of IPv6
On Dec 9, 2009, at 11:37 AM, Chris Engel wrote:
> Both. Public facing servers in the Enterprise are generaly NAT'd behind a firewall and running on Private IP space in a DMZ anyways (that's our setup and it's pretty typical of what I've seen). So even if we were to scale up to the point where we needed more external IP space and v6 was all that was available.... the only thing we would need to do....and would likely make sense to do would be to find a perimeter device that could handle v6 to v4 NATing to support those extra external v6 IP's on it's public interface (and that's assuming I need to scale beyond my current space in the first place). In other words, why would I want to try to re-invent the wheel when I don't need to, it net's me no functional advantage for my purposes and comes at considerable cost ??
I agree that you don't want to reinvent the wheel. My question is whether you'd consider getting that IPv6 address configured for your public mail and email servers sooner rather than later. The principle reason is that others could easily need that IPv6 access to your public servers well before your own internal community realizes it.
President and CEO