[123623] in North American Network Operators' Group
Re: IP4 Space
daemon@ATHENA.MIT.EDU (Tim Chown)
Fri Mar 12 07:25:33 2010
Date: Fri, 12 Mar 2010 12:24:49 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: NANOG list <nanog@nanog.org>
In-Reply-To: <201003120042.o2C0goOt069392@drugs.dv.isc.org>
X-ECS-MailScanner-From: tjc@login.ecs.soton.ac.uk
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Mar 12, 2010 at 11:42:50AM +1100, Mark Andrews wrote:
>
> > Does it make sense/work to do this for internal operations even if our
> > outside connections are IPv4 only (forget about tunneling). Even more
> > mundane questions like how to deal with IPv4 only networked printers
> > when everything else is IPv6?
>
> As for IPv4 only printers you can continue to run dual stack
> internally forever if you want. Otherwise put them on their
> own vlan and connect to them over NAT64 or run a proxy service.
Our approach to v6 deployment has always been about enabling capability
where it is available. The trick is then to have the right tools to
manage and monitor it.
The interesting thing about printers is that even quite low end network
printers (like the HP Laserjet I have) have had IPv6 for quite a while.
You can even configure DHCPv6 on the one I'm using.
Just look for capabilities/features as you refresh equipment and it
makes things that little easier.
Tim
