[arin-ppml] The non-deployment of IPv6

John Curran jcurran at arin.net
Wed Dec 9 15:39:21 EST 2009


On Dec 9, 2009, at 11:37 AM, Chris Engel wrote:
> John,
> 
> 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. 

/John

John Curran
President and CEO
ARIN




More information about the ARIN-PPML mailing list