[AusNOG] another ipv6 Q

[Matt Palmer]

On Thu, Jul 03, 2014 at 12:03:23AM +0000, Alex Samad - Yieldbroker wrote:
> So we have a ipv4 class C assigned to us.

There's a fairly good chance you don't.  You may well have a /24 address
range assigned, but not all /24s are class C blocks.

> What if any pitfalls are there for using the ipv4 in ipv6 address space ?

Not sure what you're referring to here.  Did you mean?

* The v6-mapped prefix ::ffff:0:0/96?  That isn't *actually* routable
  space.  It's a convention for allowing software to handle v4 and v6
  addresses by only implementing v6 support (more-or-less).

* The SIIT prefix ::ffff:0:0:0/96?  That's an absolete translation mechanism
  that really should be avoided.

* The 6to4 prefix 2002::/16?  That's workable if you've got a local 6to4
  tunnel endpoint, but it's really much better just to get native or
  fixed-tunnel (if you have to) IPv6 connectivity.

* Something else entirely.  Please expand.

- Matt