[133231] in North American Network Operators' Group
Re: Pointer for documentation on actually delivering IPv6
daemon@ATHENA.MIT.EDU (Chuck Anderson)
Tue Dec 7 09:05:32 2010
Date: Tue, 7 Dec 2010 09:05:25 -0500
From: Chuck Anderson <cra@WPI.EDU>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <alpine.BSF.2.00.1012070803380.41008@murf.icantclick.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Tue, Dec 07, 2010 at 08:18:31AM -0500, david raistrick wrote:
> On Mon, 6 Dec 2010, Owen DeLong wrote:
>
>> Seriously, though, you're welcome to use fd00::/8 for exactly that
>> purpose. The problem is that you (and hopefully it stays this way)
>> won't have much luck finding a vendor that will provide the NAT for you
>> to do it with.
>
> [with my flame-retardant hat installed firmly]
>
> So what's the IPV6 solution for PCI compliance, where 1.3.8 requires the
> use of RFC1918 space? Admitedly, it's been a year or two since I last
> had to engineer around that particular set of rules...but it's life or
> death for a lot of folks.
Simple. Use RFC1918 IPv4 along side global IPv6 addresses. Done :-)
